|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
problem with packages that have .tar.gz in the extention
Post 302557981 by doctorfoo1 on Thursday 22nd of September 2011 12:15:19 PM
09-22-2011
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I still don't know if there's a standard way to do this. I'm hoping there's a *more or less* standard way to do this across linux platforms but the platform in question is Gentoo.
Let's say I download a source tarball as tar.gz and I do the typical
gunzip app_to_install.tar.gz
tar xvf... (2 Replies)
Discussion started by: d11wtq
2 Replies
2. Shell Programming and Scripting
Hey,
How to strip the extention from filename?
MY_XML.xml -> MY_XML
MY_TEST_FILE.txt -> MY_TEST_FILE
HELLO_WORLD.xls -> HELLO_WORLD
Thanks in advance! (2 Replies)
Discussion started by: mpang_
2 Replies
3. Shell Programming and Scripting
The below tar command works fine for me,
tar -cvf - `find ./srcdir -type d` | (cd ./destdir ; tar -xvf - )
but this version is giving error to me:
cd ./srcdir &&
tar -cf - . |
gzip -9 |
cd ../destdir &&
gzip -d |
tar -xf -
error is: gzip: compressed data not read from a terminal.... (2 Replies)
Discussion started by: royalibrahim
2 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
4 files are returned when i issue 'find . -mtime -1 -type f -ls'.
./ora_475244.aud
./ora_671958.aud
./ora_934052.aud
./ora_934050.aud
However, when I issued the below command:
tar -cvf test.tar `find . -mtime -1 -type f`, the tar file only contains the 1st file -... (2 Replies)
Discussion started by: ahSher
2 Replies
5. Shell Programming and Scripting
I want to add a .txt extension to all files in a directory and it's sub directories.
So far I have managed to come up with this for the current directory but how do I do this recursively?
for e in *; do mv "$e" "`echo $e | sed -e 's/\ /_/g'`.txt"; done
Thanks (5 Replies)
Discussion started by: lewk
5 Replies
6. Shell Programming and Scripting
for some reason my code does not give the right number of files. can omeone help me please? (2 Replies)
Discussion started by: andrew1400
2 Replies
7. Shell Programming and Scripting
Trying to write program to archive files from a file system.
I got some problem with appropriate selection of files in regard to size.
Algorithm basic :
-----------------
1. Remotely executes on machine ls cmd and its output redirects and sorts by size of a files :
# cd... (0 Replies)
Discussion started by: presul
0 Replies
8. Shell Programming and Scripting
I'm working on implementing a mail indexer and it currently saves every file with a series of numbers with no extension. ex. 021545545544
I was wondering if someone could point me in the correct direction for a script that would check all the files and give it a .eml extension if it doesn't... (1 Reply)
Discussion started by: binary-ninja
1 Replies
9. Ubuntu
Hi folks,
Ubuntu 9.04
I have an old box not running for years. I just dig it out from the store room. On running;
$ sudo aptitude update
......
......
Err http://hk.archive.ubuntu.com jaunty/main Packages
404 Not Found
Err http://hk.archive.ubuntu.com jaunty/restricted Packages
... (1 Reply)
Discussion started by: satimis
1 Replies
LEARN ABOUT CENTOS
yumdb
yumdb(8) yumdb(8) NAME
yumdb - query and alter the Yum database SYNOPSIS
yumdb [command] [packages ...] DESCRIPTION
This command is used to query and alter the yum database, which is a simple key value store used in conjunction with the rpm database. Any installed package can have arbitrary data in the yum database, however the main use case is to store extra data about packages as they are installed. yumdb commands are: yumdb get <key> [pkg-wildcard]... This command will get the value for the given key, limiting to any specified packages. yumdb set <key> <value> [pkg-wildcard]... This command will set the value for the given key, to the given value, limiting to any specified packages. yumdb del <key> [pkg-wildcard]... This command will delete the given key, limiting to any specified packages. yumdb rename <old-key> <new-key> [pkg-wildcard]... This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, noth- ing happens. yumdb rename-force <old-key> <new-key> [pkg-wildcard]... This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new- key is deleted. yumdb copy <old-key> <new-key> [pkg-wildcard]... This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, nothing happens. yumdb copy-force <old-key> <new-key> [pkg-wildcard]... This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-key is deleted. yumdb search <key> <wildcard>... This command will search all packages for the given key, against any of the given wildcard values. yumdb exist <key> [pkg-wildcard]... This command will print any packages which have the given key, limiting to any specified packages. yumdb unset <key> [pkg-wildcard]... This command will print any packages which do not have the given key, limiting to any specified packages. yumdb info [pkg-wildcard]... This command will display all the data stored in the yumdb, limiting to any specified packages. yumdb sync [pkg-wildcard]... This command will add any missing data to the yumdb from the repositories, limiting to any specified packages. This is useful to run if you have had any aborted transactions (and thus. missing yumdb data). Note that "yumdb sync" cannot know all the information that would have been put into the yumdb at the time. yumdb sync-force [pkg-wildcard]... This command will replace any data in the yumdb from the repositories, limiting to any specified packages. EXAMPLES
List all the packages which don't have a from_repo key/value: yumdb unset from_repo List all the packages which were installed as dependencies: yumdb search reason dep WELL KNOWN KEYS
Note that there is no limit to the number of keys that can be created or what they may contain (for installed packages only). However this is a list of well known keys, and what they store. checksum_data checksum_type These keys store the createrepo checksum, and it's type, of the available package yum installed. Note that these are used by "yum version" to calculate the rpmdb version. command_line This key stores the entire command line, of the yum command (if it was called). from_repo from_repo_revision from_repo_timestamp These keys take values from the available package yum installed, and store the repo id, it's revision and timestamp. reason This key stores either "user" or "dep", currently. To mark if the user requested the package to be installed, or if it was brought in automatically as a dependency. Note that this is kept over updates. releasever This key stores the value of releasever, when the package was installed. installonly If this attribute has the value "keep" then this package will not be removed automatically by the installonly process (and does not count towards the installonly_limit). SEE ALSO
yum (8) rpm (8) AUTHORS
James Antill <james.antill@redhat.com>. James Antill 8 April 2010 yumdb(8)