9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
The below bash will untar each tar.bz2 folder in the directory, then remove the tar.bz2.
Each of the tar.bz2 folders ranges from 40-75GB and currently takes ~2 hours to extract. Is there a way to speed up the extraction process?
I am using a xeon processor with 12 cores. Thank you :).
... (7 Replies)
Discussion started by: cmccabe
7 Replies
2. Shell Programming and Scripting
In the bash below each .tar.bz2 (usually 2) are extracted and then the original .tar.bz2 is removed. However, only one (presumably the first extracted) is being removed, however both are extracted. I am not sure why this is? Thank you :).
tar.bz2 folders in /home/cmccabe/Desktop/NGS/API
... (3 Replies)
Discussion started by: cmccabe
3 Replies
3. Programming
I am using aria2c to download a .tar.bz2 and trying to extract it in the same command. I can download the file but not extract it. I can also manually extract the tar.bz2., but not in the same command. Thank you :).
aria2c -x8 -l log.txt -c -d /xx/xx/xxx --use-head=true --http-user "<user>" ... (8 Replies)
Discussion started by: cmccabe
8 Replies
4. Ubuntu
while extracting a tar.bz2 file using the command
tar xjf git.tar.bz2
I received error messages that shows Cannot hard link to and Cannot create symlink to error messages
what will be the reason for those error messages. (4 Replies)
Discussion started by: saravana krishn
4 Replies
5. UNIX and Linux Applications
Does anyone know a reliable source to download firefox-19.0.2.tar.bz2 from? I would think you be able to download from firefox or mozilla somewhere. I haven't gotten anything useful from my google searches. (2 Replies)
Discussion started by: cokedude
2 Replies
6. Shell Programming and Scripting
Hi experts,
I have two tar.bz2 file,:
a.tar.bz2 and b.tar.bz2
I want to put a.tar.bz2 in to b.tar.bz2
eg: b.tar.bz2 only have one file named "b.c" contained
I want it contain "b.c and a.tar.bz2"
I don't want to decompress the b.tar.bz2 to achieve this, I try with "cat a.tar.bz2 >>... (1 Reply)
Discussion started by: yanglei_fage
1 Replies
7. Shell Programming and Scripting
Hi,
I am trying to unpack and install .tar.bz2 library.
I was told to cd /
and than tar -jxvf /source-of-library-file?...tar.bz2
to get files unpacked and installed into /
Darius
$ pwd
/
$
$ tar -jxvf /tmp/local/root/ncurses-dev-addon.tar.bz2
ncurses-dev-addon/... (3 Replies)
Discussion started by: jack2
3 Replies
8. Shell Programming and Scripting
Hello,
I am using a bash script to archive directories of text files located in ${root}:
tar cf ${root}.tar ${root}*
bzip2 ${root}.tar
I'd like to compare the newly produced archive two.tar.bz2 with the second latest one.tar.bz2.
cmp one.tar.bz2 two.tar.bz2
returns
one.tar.bz2 two.tar.bz2... (2 Replies)
Discussion started by: JCR
2 Replies
9. UNIX for Advanced & Expert Users
hi
could any body tell me how to extract .tar.bz2 files
i tried using tar but in vain.
i found bzip2 in googling but i could not find it on machine unix tru64
please suggest. (1 Reply)
Discussion started by: Raom
1 Replies
PKG_SUMMARY(5) BSD File Formats Manual PKG_SUMMARY(5)
NAME
pkg_summary -- summary of binary package repository
DESCRIPTION
The file pkg_summary contains information about each package in a binary package repository as a list of variable-value pairs. The variables
describing different packages are separated by one empty line. Each line has the format VARIABLE=VALUE. If the value consists of more than
one line, each line is prefixed with VARIABLE=. Multi-line variables are guaranteed to be in consecutive lines.
The following variables are used:
BUILD_DATE
(required) The date and time when the package was built.
CATEGORIES
(required) A list of categories which this package fits in, separated by space.
COMMENT
(required) A one-line description of the package.
CONFLICTS
(optional) A list of dewey patterns of packages the package conflicts with, one per line. If missing, this package has no conflicts.
DEPENDS
(optional) A list of dewey patterns of packages the package depends on, one per line. If missing, this package has no dependencies.
DESCRIPTION
(required) A more detailed description of the package.
FILE_CKSUM
(optional) A checksum type supported by digest(1) and checksum separated by space character.
FILE_NAME
(optional) The name of the binary package file. If not given, PKGNAME.tgz can be assumed.
FILE_SIZE
(optional) The size of the binary package file, in bytes.
HOMEPAGE
(optional) A URL where more information about the package can be found.
LICENSE
(optional) The type of license this package is distributed under. If empty or missing, it is OSI-approved.
MACHINE_ARCH
(required) The architecture on which the package was compiled.
OPSYS (required) The operating system on which the package was compiled.
OS_VERSION
(required) The version of the operating system on which the package was compiled.
PKG_OPTIONS
(optional) Any options selected to compile this package. If missing, the package does not support options.
PKGNAME
(required) The name of the package.
PKGPATH
(required) The path of the package directory within pkgsrc.
PKGTOOLS_VERSION
(required) The version of the package tools used to create the package.
PREV_PKGPATH
(optional) The previous path of the package directory within pkgsrc when a package was moved. (See SUPERSEDES below for a renamed
package.)
PROVIDES
(optional) A list of shared libraries provided by the package, including major version number, one per line. If missing, this pack-
age does not provide shared libraries.
REQUIRES
(optional) A list of shared libraries needed by the package, including major version number, one per line. If missing, this package
does not require shared libraries.
SIZE_PKG
(required) The size of the package when installed, in bytes.
SUPERSEDES
(optional) A list of dewey patterns of previous packages this package replaces, one per line. This is used for package renaming.
The pkg_summary file can be generated using the pkg_info(1) -X option. For example, the following will list this data for all installed
packages:
pkg_info -X -a
SEE ALSO
digest(1), pkg_info(1)
HISTORY
The pkg_summary format was first officially documented in April 2006.
BSD
April 11, 2009 BSD