Re: using tar
mick crane [2020-06-15T19:01:32+01] wrote: > I think my memory has packed up. Mine too, and I like GNU's long-option style because I remember them easily. They are also kind of self-documenting code in shell scripts. tar --create --verbose --xz --file archive.tar.xz directory/to_archive Bash completion helps in interactive shell: tar --cr -- /// Teemu Likonen - .-.. http://www.iki.fi/tlikonen/ // OpenPGP: 4E1055DC84E9DFF613D78557719D69D324539450 signature.asc Description: PGP signature
Re: using tar
On Mon, Jun 15, 2020 at 07:30:31PM +0100, mick crane wrote: yes I see that now but without hyphen "f" can be anywhere Yes and no: any of the keys can be in any location, but their arguments must follow the key list in the order that the keys appear. For example: tar cbf 20 foo.tar /dev/null tar: Removing leading `/' from member names tar cbf foo.tar 20 /dev/null tar: foo.tar: Invalid blocking factor Try 'tar --help' or 'tar --usage' for more information. In the first case a foo.tar file is created with a blocking factor of 20, and in the second case the command blew up because the filename is before the blocking factor. With less luck, the swapped arguments wouldn't fail immediately, doing who-knows-what to the system. :)
Re: using tar
On Mon, Jun 15, 2020 at 02:34:24PM -0500, David Wright wrote: It appears you've also forgotten about man pages as well as google. The man page explains the difference between hyphenated and unhyphenated forms, and helpfully even gives a single example written in both forms: tar cfv a.tar /etc tar -cvf a.tar /etc For those who find that a challenge, there's even a broken-out format of the same example for them to copy: tar -c -v -f a.tar /etc The last one is arguably the best form to use because it complies with system conventions and is less confusing/more intuitive for someone familiar with the linux command line but not with 40 year old pre-standard tar syntax. Unfortunately we're a lazy and cliquish lot so the oddball versions remain more popular. :) We'd also probably be much better off if the tar format just went away, but change is hard.
Re: using tar
On Mon 15 Jun 2020 at 19:30:31 (+0100), mick crane wrote: > On 2020-06-15 19:17, Thomas Pircher wrote: > > mick crane wrote: > > > I thought you put the options after a hyphen with tar ? > > > > Tar accepts 3 styles of options. The style with a single dash is called > > the 'UNIX' or 'short-option' style in the man page. > > > > > "tar -cfvz archive_file.tgz ./directory_to_archive" > > > doesn't work. > > > > The `-f` option requires an argument, the tar file, so with your > > command, tar would create an output file called 'vz'. The rest of the > > command line is considered a list of files and directories to > > include in > > the archive. Tar fails because the input file archive_file.tgz does not > > exist. > > > > Try `tar -cvzf archive_file.tgz ./directory_to_archive`. > > yes I see that now > but without hyphen "f" can be anywhere It appears you've also forgotten about man pages as well as google. The man page explains the difference between hyphenated and unhyphenated forms, and helpfully even gives a single example written in both forms: tar cfv a.tar /etc tar -cvf a.tar /etc For those who find that a challenge, there's even a broken-out format of the same example for them to copy: tar -c -v -f a.tar /etc Cheers, David.
Re: using tar
On 2020-06-15 19:17, Thomas Pircher wrote: mick crane wrote: I thought you put the options after a hyphen with tar ? Tar accepts 3 styles of options. The style with a single dash is called the 'UNIX' or 'short-option' style in the man page. "tar -cfvz archive_file.tgz ./directory_to_archive" doesn't work. The `-f` option requires an argument, the tar file, so with your command, tar would create an output file called 'vz'. The rest of the command line is considered a list of files and directories to include in the archive. Tar fails because the input file archive_file.tgz does not exist. Try `tar -cvzf archive_file.tgz ./directory_to_archive`. Thomas yes I see that now but without hyphen "f" can be anywhere mick -- Key ID4BFEBB31
Re: using tar
On Mon 15 Jun 2020 at 19:24:00 +0100, mick crane wrote: > On 2020-06-15 19:07, Brian wrote: > > On Mon 15 Jun 2020 at 19:01:32 +0100, mick crane wrote: > > > > > I think my memory has packed up. > > > > So has your ability to use a search engine. Try > > > > tar options hyphen > > Ok I see what the confusion was "f" has to be the last of the options if > using hyphen Well done! -- Brian.
Re: using tar
On Mon, Jun 15, 2020 at 07:01:32PM +0100, mick crane wrote: > I think my memory has packed up. > I thought you put the options after a hyphen with tar ? > "tar -cfvz archive_file.tgz ./directory_to_archive" > doesn't work. > "tar cfvz archive_file.tgz ./directory_to_archive" > works Your fundamental problem is that the "-f" option takes an argument. The -f should be followed by the filename, which is presumably the thing ending with .tgz. But the way you've got it written now, the filename argument of the -f option is "vz". So you're asking tar to create an archive file named "vz", and you're using "archive_file.tgz" and "./directory_to_archive" as the names of the things to place inside the archive. What you want is: tar czvf archive_file.tgz ./directory_to_archive Or with the hyphen. It doesn't matter.
Re: using tar
On 2020-06-15 19:07, Brian wrote: On Mon 15 Jun 2020 at 19:01:32 +0100, mick crane wrote: I think my memory has packed up. So has your ability to use a search engine. Try tar options hyphen Ok I see what the confusion was "f" has to be the last of the options if using hyphen mick -- Key ID4BFEBB31
Re: using tar
mick crane wrote: > I thought you put the options after a hyphen with tar ? Tar accepts 3 styles of options. The style with a single dash is called the 'UNIX' or 'short-option' style in the man page. > "tar -cfvz archive_file.tgz ./directory_to_archive" > doesn't work. The `-f` option requires an argument, the tar file, so with your command, tar would create an output file called 'vz'. The rest of the command line is considered a list of files and directories to include in the archive. Tar fails because the input file archive_file.tgz does not exist. Try `tar -cvzf archive_file.tgz ./directory_to_archive`. Thomas
Re: using tar
On Mon, Jun 15, 2020 at 13:02 mick crane wrote: > I think my memory has packed up. > I thought you put the options after a hyphen with tar ? > "tar -cfvz archive_file.tgz ./directory_to_archive" You do for modern use, but the 'f' has to be the last arg in that incantation. -Tom
Re: using tar
On Mon 15 Jun 2020 at 19:01:32 +0100, mick crane wrote: > I think my memory has packed up. So has your ability to use a search engine. Try tar options hyphen -- Brian.
using tar
I think my memory has packed up. I thought you put the options after a hyphen with tar ? "tar -cfvz archive_file.tgz ./directory_to_archive" doesn't work. "tar cfvz archive_file.tgz ./directory_to_archive" works mick -- Key ID4BFEBB31
Re: Using tar and gpg from Konqueror
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Camaleón wrote: On Sat, 02 Apr 2011 12:38:05 +0700, Ken Heard wrote: While experimenting with tar and gpg files I discovered that right clicking on a file or directory name in Konqueror with gnugp installed behaves differently depending on its location. If the file or directory is located on an ext3 or xfs hard drive, the right click allows the options of compressing the file and encrypting it. If however it is located on a cf or sd card, the right click offers the compressing option; but it does not work. No encryption option is offered. Could this difference be attributable to the file system used, the hard drive using ext3or xfs, the cf and sd cards using vfat? Would either or both of these options options be available if the file system on those cards were also ext3? I dunno for konqueror or dolphin, but from Nautulis (GNOME) both options (encrypt/sign and create archive) are available on vfat volumes. Greetings, While I have yet to upgrade to Squeeze, I did discover that when I got back home to my desktop I discovered all the options you mentioned using Konqueror. Have not yet the time to check why I could not do so on the laptop. Strange. Regards, Ken Heard -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAk2y5O4ACgkQlNlJzOkJmTc93wCfUX6E9mPo+1hiy55P5TPRpHLp wlkAli+66cFIFfKssp7cse0EUnafO08= =ykva -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4db2e4ef.9090...@heard.name
Re: Using tar and gpg from Konqueror
On Sat, 02 Apr 2011 12:38:05 +0700, Ken Heard wrote: While experimenting with tar and gpg files I discovered that right clicking on a file or directory name in Konqueror with gnugp installed behaves differently depending on its location. If the file or directory is located on an ext3 or xfs hard drive, the right click allows the options of compressing the file and encrypting it. If however it is located on a cf or sd card, the right click offers the compressing option; but it does not work. No encryption option is offered. Could this difference be attributable to the file system used, the hard drive using ext3or xfs, the cf and sd cards using vfat? Would either or both of these options options be available if the file system on those cards were also ext3? I dunno for konqueror or dolphin, but from Nautulis (GNOME) both options (encrypt/sign and create archive) are available on vfat volumes. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.04.03.13.44...@gmail.com
Re: Using tar and gpg from Konqueror
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Camaleón wrote: On Sat, 02 Apr 2011 12:38:05 +0700, Ken Heard wrote: While experimenting with tar and gpg files I discovered that right clicking on a file or directory name in Konqueror with gnugp installed behaves differently depending on its location. If the file or directory is located on an ext3 or xfs hard drive, the right click allows the options of compressing the file and encrypting it. If however it is located on a cf or sd card, the right click offers the compressing option; but it does not work. No encryption option is offered. Could this difference be attributable to the file system used, the hard drive using ext3or xfs, the cf and sd cards using vfat? Would either or both of these options options be available if the file system on those cards were also ext3? I dunno for konqueror or dolphin, but from Nautulis (GNOME) both options (encrypt/sign and create archive) are available on vfat volumes. I should have mentioned that I am still using Lenny with the 3.5.10 release of Konqueror. After I upgrade to Squeeze later this month with a newer version of Konqueror or whatever replaces it (plasma-desktop?) I will check these options again. Ken -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk2Ykg8ACgkQlNlJzOkJmTcKLACfar97a1dcKD6ZVHOYEvmK4F9+ HXoAn1TUpLnyRO+JmV8cZxLIwcnFS4zV =Olvm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d989210.7070...@heard.name
Using tar and gpg from Konqueror
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While experimenting with tar and gpg files I discovered that right clicking on a file or directory name in Konqueror with gnugp installed behaves differently depending on its location. If the file or directory is located on an ext3 or xfs hard drive, the right click allows the options of compressing the file and encrypting it. If however it is located on a cf or sd card, the right click offers the compressing option; but it does not work. No encryption option is offered. Could this difference be attributable to the file system used, the hard drive using ext3or xfs, the cf and sd cards using vfat? Would either or both of these options options be available if the file system on those cards were also ext3? Regards, Ken Heard -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk2W4YsACgkQlNlJzOkJmTcQKQCfaBXdNHFQ96Yiv5qXl8IlhYzx nGMAmwQMkU49vJA0JavfE21ZsddtkQ/H =V4oq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d96e18c.3030...@heard.name
Using tar and gpg from Konqueror
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While experimenting with tar and gpg files I discovered that right clicking on a file or directory name in Konqueror with gnugp installed behaves differently depending on its location. If the file or directory is located on an ext3 or xfs hard drive, the right click allows the options of compressing the file and encrypting it. If however it is located on a cf or sd card, the right click offers the compressing option; but it does not work. No encryption option is offered. Could this difference be attributable to the file system used, the hard drive using ext3or xfs, the cf and sd cards using vfat? Would either or both of these options options be available if the file system on those cards were also ext3? Regards, Ken Heard -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk2WtjsACgkQlNlJzOkJmTdzsgCeJRiV6SC7Y4PMR42KzAHweVY2 0A8An1SmcTMvugnZRkJq3RiuHSi9n+Dq =oLnX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d96b63d.7080...@heard.name
Using tar to extract files from tape
I asked this question before, but received no answer. Sorry to post it again. The question is a simple one: can I use tar to extract a file from a tape backup made with a backup application? On a sarge machine, I have a WangDAT 3100 tape drive from the late 1990s. The tape from which I would like to recover certain files was made back in 1998 with bru 2000/xbru. # mt -f /dev/st0 status drive type = Generic SCSI-2 tape drive status = 318767616 sense key error = 0 file number = -1 block number = -1 Tape block size 512 byte. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status = 0 General status bits on (101); ONLINE IM_REP_EN I tried: # tar xvf /dev/st0 *.xyz tar: /dev/st0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now When I tried the tvf options for tar, I get the same result. How does one extract the *xyz files from the tape? -- Haines Brown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using tar to extract files from tape
Haines Brown on 2006-07-13 09:48:02 -0400: I tried: # tar xvf /dev/st0 *.xyz tar: /dev/st0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now When I tried the tvf options for tar, I get the same result. How does one extract the *xyz files from the tape? I don't know much about tape drives, but I would assume if you used dd to copy the information on the tape to a file on your disk, you'd be able to read it like a normal tar file. signature.asc Description: Digital signature
Re: Using tar to extract files from tape
On Thu, 13 Jul 2006, Alec Berryman wrote: Haines Brown on 2006-07-13 09:48:02 -0400: I tried: # tar xvf /dev/st0 *.xyz tar: /dev/st0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now When I tried the tvf options for tar, I get the same result. How does one extract the *xyz files from the tape? I don't know much about tape drives, but I would assume if you used dd to copy the information on the tape to a file on your disk, you'd be able to read it like a normal tar file. Google this issue, you have to use kernel 2.2 or set the block size to 64kb or some weird number to get the data off of the tape. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using tar to extract files from tape
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Haines Brown wrote: I asked this question before, but received no answer. Sorry to post it again. The question is a simple one: can I use tar to extract a file from a tape backup made with a backup application? Depends on the format. Tape ARchive most probably doesn't understand proprietary formats... On a sarge machine, I have a WangDAT 3100 tape drive from the late 1990s. The tape from which I would like to recover certain files was made back in 1998 with bru 2000/xbru. [snip] When I tried the tvf options for tar, I get the same result. How does one extract the *xyz files from the tape? You don't mention having tried Googling for BRU? http://www.tolisgroup.com/products/ http://www.tolisgroup.com/about/contactus.html - -- Ron Johnson, Jr. Jefferson LA USA Is common sense really valid? For example, it is common sense to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that common sense is obviously wrong. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEtm+mS9HxQb37XmcRAix8AJ0bka3/3MOvVluYoeRpImYBKyVXFwCeNipl yNatw5wUUlUMZsp3JQSZf7g= =TNZs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using tar to extract files from tape
On Thu, 13 Jul 2006, Ron Johnson wrote: gpgkeys: HTTP fetch error 7: couldn't connect: eof Haines Brown wrote: I asked this question before, but received no answer. Sorry to post it again. The question is a simple one: can I use tar to extract a file from a tape backup made with a backup application? Depends on the format. Tape ARchive most probably doesn't understand proprietary formats... Yep, what program did you use to make the backup? For me I have a cron job that runs nightly and uses tar to back things up. The command I use is... tar --totals --label=System Backup For `date -d yesterday +%m-%d-%Y` -cvf /dev/tape / Then when I want to restore something off the tape (say my home directory), I'd do the following... tar xvMf /dev/nst0 home/zoid This will restore my home directory to whatever directory I am currently in. Maybe give that a shot and see how it works. On a sarge machine, I have a WangDAT 3100 tape drive from the late 1990s. The tape from which I would like to recover certain files was made back in 1998 with bru 2000/xbru. [snip] When I tried the tvf options for tar, I get the same result. How does one extract the *xyz files from the tape? You don't mention having tried Googling for BRU? http://www.tolisgroup.com/products/ http://www.tolisgroup.com/about/contactus.html -- Ron Johnson, Jr. Jefferson LA USA Is common sense really valid? For example, it is common sense to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that common sense is obviously wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Output from gpg gpg: Signature made Thu Jul 13 12:07:02 2006 EDT using DSA key ID BDFB5E67 gpg: requesting key BDFB5E67 from hkp server keyserver.cryptnet.net gpg: no valid OpenPGP data found. gpg: Total number processed: 0 gpg: Can't check signature: public key not found -- Rob Hensley [EMAIL PROTECTED] http://www.robhensley.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
moving fs to new disk using tar
Hi all, I thought I was being very careful, but this didn't work like I'd hoped. Basically I want to move my /usr fs from one disk to another - the first will eventually be repartitioned, to use LVM and ReiserFS. Other filesystems will follow. So I used this command from / (in single user mode - that's what init 1 does, right?): tar -c --atime-preserve -l usr |tar -C /spareide -x -v --atime-preserve --preserve --same-owner I wasn't entirely clear from the man page which options were intended for use with creating and which with extracting the archive, so when in doubt I used it for both. Now, my understanding was that the -C /spareide should have started the extraction from where my nice empty filesystem was mounted on /spareide/usr - but this didn't happen. It appears to have extracted over itself in /usr, giving lots of warnings about files changing while they were being read (not all of them - maybe only the big ones?), and changing dates on some of them (again not all - dunno why) as well. I'm guessing I've made some fairly fundamental mistake somewhere - any suggestions? My other thought was that it would be nice to do all this with both filesystems unmounted - are there tools for that? Many thanks, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: moving fs to new disk using tar
heya, On Tue, Feb 11, 2003 at 05:11:08PM +1300, Richard Hector wrote: tar -c --atime-preserve -l usr |tar -C /spareide -x -v --atime-preserve --preserve --same-owner may i suggest a less confusing alternative: rsync -a usr/ /spareide it does for most intents and purposes the same thing. maybe not as efficient on a single run, but a lot easier to remember and less keystrokes too :) hth sean msg30026/pgp0.pgp Description: PGP signature
Re: moving fs to new disk using tar
On Tue, Feb 11, 2003 at 12:48:34AM -0500, sean finney wrote: heya, On Tue, Feb 11, 2003 at 05:11:08PM +1300, Richard Hector wrote: tar -c --atime-preserve -l usr |tar -C /spareide -x -v --atime-preserve --preserve --same-owner may i suggest a less confusing alternative: rsync -a usr/ /spareide Yes, thanks - with the addition of -x (cf -l for tar) because I didn't want /usr/local (sep filesystem), that's more or less what I did. I also remounted /usr read-only. The only thing I couldn't find was an equivalent to the --atime-preserve switch - perhaps rsync does that by default? Many thanks, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: backups using tar - /dev/ht0
hi ya bob... mt is complaining so you do NOT have /dev/ht0 as a device until mt worksand you can hear the tape rewind and/or eject... its NOT working yet... manually creaate a device called /dev/ht0 with mknod... and give it the type, and major and minor id if the device is made properly... it should be like crw-rw 1 root disk 37, 0 May 5 1998 /dev/ht0 until ls -la /dev/ht0 looks liek the above line... there is no point to doing any mt/tar commands.. what kind of tape drive do you have etc would dictate which tape driver yu are gonna be using c ya alvin On 10 Aug 2001, Bob Koss wrote: Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin did you try: cd /dev ./MAKEDEV ht0 That's exactly what I did. Alvin= should work, if not... Alvin more info Alvin http://www-wsg.cso.uiuc.edu/resources/unixguide/devices.html Alvin you do it the hard way # crw-rw 1 root disk 37, 0 May 5 Alvin 1998 /dev/ht0 # # manually create the device that MAKEDEV Alvin failed to do.. # donno why it didnt work for you # root# Alvin mknod /dev/ht0 c 37 0 Alvin when ready... can you access the tape ( stick in a blank Alvin tape .. :-) ) Okay, got /dev/ht0 made again. Alvinmt -f /dev/ht0 rewind mt -f /dev/ht0 eject mt: /dev/ht0: Input/output error -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: backups using tar - /dev/ht0
Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin so you do NOT have /dev/ht0 as a device Alvin manually creaate a device called /dev/ht0 with mknod... Alvin and give it the type, and major and minor id Alvin if the device is made properly... it should be like Alvin crw-rw 1 root disk 37, 0 May 5 1998 /dev/ht0 Based on the instructions that you kindly provided yesterday, I have: [EMAIL PROTECTED]:~$ cd /dev [EMAIL PROTECTED]:/dev$ ls -al ht0 crw-r--r--1 root root 37, 0 Aug 10 19:50 ht0 [EMAIL PROTECTED]:/dev$ Alvin until ls -la /dev/ht0 looks liek the above line... there Alvin is no point to doing any mt/tar commands.. It looks like we're close. Alvin what kind of tape drive do you have etc would dictate which Alvin tape driver yu are gonna be using This is an OnStream DI-30. The driver is supposed to be part of the kernel. I'm running Potato with the supplied 2.2.19pre17 kernel. -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar - /dev/ht0
Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin if the device is made properly... it should be like Alvin crw-rw 1 root disk 37, 0 May 5 1998 /dev/ht0 Alvin until ls -la /dev/ht0 looks liek the above line... there Alvin is no point to doing any mt/tar commands.. Okay, a few chgrp's and chmod's later, my ls -al looks like you want it to look. But I still get: mt -f /dev/ht0 rewind mt: /dev/ht0: Input/output error -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar - /dev/ht0
hi ya bob ...beg/borrow/steal a (real) dds1, dds2, dds3 ide tape drive... - hp series, exabyte series, etc and try to read/write to that drive c ya alvin On 11 Aug 2001, Bob Koss wrote: Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin if the device is made properly... it should be like Alvin crw-rw 1 root disk 37, 0 May 5 1998 /dev/ht0 Alvin until ls -la /dev/ht0 looks liek the above line... there Alvin is no point to doing any mt/tar commands.. Okay, a few chgrp's and chmod's later, my ls -al looks like you want it to look. But I still get: mt -f /dev/ht0 rewind mt: /dev/ht0: Input/output error
backups using tar
When this box was running RH, I would backup using my Onstream tape drive thusly: tar cvbf 64 /dev/ht0 /stuff /moreStuff With my recent Debian install, this no longer works, giving me a device full error. But, with the 2.2.19 kernel included with Debian, the Onstream driver is included in the kernel. Looking at dmesg, I see that the Onstream drive is recognized as hdc. Not being all that familiar with /dev, should I now be using /dev/hdc instead of /dev/ht0 ? If so, how would that work with rewind devices? -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar
On 10 Aug 2001 16:39:29 -0400, Bob Koss wrote: When this box was running RH, I would backup using my Onstream tape drive thusly: tar cvbf 64 /dev/ht0 /stuff /moreStuff With my recent Debian install, this no longer works, giving me a device full error. But, with the 2.2.19 kernel included with Debian, the Onstream driver is included in the kernel. Looking at dmesg, I see that the Onstream drive is recognized as hdc. Not being all that familiar with /dev, should I now be using /dev/hdc instead of /dev/ht0 ? If so, how would that work with rewind devices? -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] You may need to install the ide-tape module if it's not in the kernel you are running already. What does df and ls -al /dev/ht0 tell you? I tried to replicate your problem briefly and since ht0 was not a device on my system I just wrote to a normal file. You may have inadvertently done the same. The MAKEDEV script in the dev directory can create the devices for you. --mike
Re: backups using tar
Michael == Michael Heldebrant [EMAIL PROTECTED] writes: Michael You may need to install the ide-tape module if it's not Michael in the kernel you are running already. [EMAIL PROTECTED]:/var/log$ grep OnStream dmesg hdc: OnStream DI-30, ATAPI TAPE drive [EMAIL PROTECTED]:/var/log$ Does that mean that the kernel found it ?? Michael What does df and Michael ls -al /dev/ht0 tell you? [EMAIL PROTECTED]:/var/log$ df /dev/hdc Filesystem 1k-blocks Used Available Use% Mounted on /dev/hdc 69995 69995 0 100% [EMAIL PROTECTED]:/var/log$ [EMAIL PROTECTED]:/var/log$ [EMAIL PROTECTED]:/var/log$ ls -al /dev/ht0 -rw-r--r--1 root root 38121472 Aug 10 16:55 /dev/ht0 [EMAIL PROTECTED]:/var/log$ [EMAIL PROTECTED]:/var/log$ -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar
hi ya bob if the device is full... you have too much data - remove all the junk files... - core, /tmp, /var/log/ files you dont want - use 2 tapes instead for the various stuff - compress it instead tar zcvbf 64 /dev/ht0 /stuff /moreStuff - note the z - to read the compressed tape... tar ztvfbf /dev/ht0 c ya alvin http://www.Linux-Backup.net On 10 Aug 2001, Bob Koss wrote: When this box was running RH, I would backup using my Onstream tape drive thusly: tar cvbf 64 /dev/ht0 /stuff /moreStuff With my recent Debian install, this no longer works, giving me a device full error. But, with the 2.2.19 kernel included with Debian, the Onstream driver is included in the kernel. Looking at dmesg, I see that the Onstream drive is recognized as hdc. Not being all that familiar with /dev, should I now be using /dev/hdc instead of /dev/ht0 ? If so, how would that work with rewind devices?
Re: backups using tar
hi ya bob you need to remove the file called /dev/ht0 that was created by the tar command when trying to write to tape that did not work... you need to create a tape decice called /dev/ht0 and/or ln -s /dev/hdc /dev/ht0 ( donno if it would work ) MAKEDEV /dev/ht0 should work now do your tar commands again to /dev/ht0 have fun alvin On 10 Aug 2001, Bob Koss wrote: Michael == Michael Heldebrant [EMAIL PROTECTED] writes: Michael You may need to install the ide-tape module if it's not Michael in the kernel you are running already. [EMAIL PROTECTED]:/var/log$ grep OnStream dmesg hdc: OnStream DI-30, ATAPI TAPE drive [EMAIL PROTECTED]:/var/log$ Does that mean that the kernel found it ?? Michael What does df and Michael ls -al /dev/ht0 tell you? [EMAIL PROTECTED]:/var/log$ df /dev/hdc Filesystem 1k-blocks Used Available Use% Mounted on /dev/hdc 69995 69995 0 100% [EMAIL PROTECTED]:/var/log$ [EMAIL PROTECTED]:/var/log$ [EMAIL PROTECTED]:/var/log$ ls -al /dev/ht0 -rw-r--r--1 root root 38121472 Aug 10 16:55 /dev/ht0 [EMAIL PROTECTED]:/var/log$ [EMAIL PROTECTED]:/var/log$
Re: backups using tar
Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin if the device is full... you have too much data The device isn't full. When I issued the tar command, it worked for a few seconds and then gave me the error message. Nothing went to tape. -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar
Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin you need to remove the file called /dev/ht0 that was Alvin created by the tar command when trying to write to tape Alvin that did not work... Alvin you need to create a tape decice called /dev/ht0 and/or ln Alvin -s /dev/hdc /dev/ht0 ( donno if it would work ) Alvin MAKEDEV /dev/ht0 should work MAKDEV: don't know hot to make device /dev/ht0 Now I seem to be screwed. -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar
hi ya bob you created a file called /dev/ht0 that filled up the available space in / causes device full to tar c ya alvin On 10 Aug 2001, Bob Koss wrote: Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin if the device is full... you have too much data The device isn't full. When I issued the tar command, it worked for a few seconds and then gave me the error message. Nothing went to tape.
Re: backups using tar - /dev/ht0
Alvin you need to create a tape decice called /dev/ht0 and/or ln Alvin -s /dev/hdc /dev/ht0 ( donno if it would work ) AlvinMAKEDEV /dev/ht0 should work MAKDEV: don't know hot to make device /dev/ht0 Now I seem to be screwed. did you try: cd /dev ./MAKEDEV ht0 = should work, if not... more info http://www-wsg.cso.uiuc.edu/resources/unixguide/devices.html you do it the hard way # crw-rw 1 root disk 37, 0 May 5 1998 /dev/ht0 # # manually create the device that MAKEDEV failed to do.. # donno why it didnt work for you # root# mknod /dev/ht0 c 37 0 when ready... can you access the tape ( stick in a blank tape .. :-) ) mt -f /dev/ht0 rewind mt -f /dev/ht0 eject than try to tar up a file and read it back write# tar zcvf /dev/ht0 /etc -- rewind -- read# tar ztvf /dev/ht0 add more tar options as you like... c ya alvin http://www.Linux-Sec.net
Re: backups using tar
Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin hi ya bob Alvin you created a file called /dev/ht0 that filled up the Alvin available space in / causes device full to tar /dev/ht0 was supposed to go to my tape drive. Why didn't it??? -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: backups using tar - /dev/ht0
Alvin == Alvin Oga [EMAIL PROTECTED] writes: Alvin did you try: cd /dev ./MAKEDEV ht0 That's exactly what I did. Alvin = should work, if not... Alvin more info Alvin http://www-wsg.cso.uiuc.edu/resources/unixguide/devices.html Alvin you do it the hard way # crw-rw 1 root disk 37, 0 May 5 Alvin 1998 /dev/ht0 # # manually create the device that MAKEDEV Alvin failed to do.. # donno why it didnt work for you # root# Alvin mknod /dev/ht0 c 37 0 Alvin when ready... can you access the tape ( stick in a blank Alvin tape .. :-) ) Okay, got /dev/ht0 made again. Alvin mt -f /dev/ht0 rewind mt -f /dev/ht0 eject mt: /dev/ht0: Input/output error -- Robert Koss, Ph.D. | Training, Mentoring, Contract Development Senior Consultant | Object Oriented Design, C++, Java www.objectmentor.com | Extreme Programming
Re: Using tar saving Disk-space [was: apt-get offline]
Thank you, this is exactly what I was looking for. Except the line tar -u $foo -f packages.tar has to be changed into tar uf packages.tar The script I was referring to is the one created by apt-get -qq -print-uris etc. I would have to add the above line to every downloaded package. I think your foreach loop is easier joerg John Galt wrote: On Wed, 30 May 2001, Joerg Johannes wrote: Hi list Now that I can transfer my downloaded .debs in a .tar file, I wonder if I could create this .tar file saving disk space, e.g. in the following way pseudo-code create a tar file (touch packages.tar?) unnecessary, and in fact will break the script... for *.deb in this directory foreach foo (./*.deb) 1.) add it to the tar file tar -u $foo -f packages.tar 2.) rm this .deb rm $foo end end /pseudo-code Is this possible for (non-GNU)-tar? I think that I made it basic enough to be portable... How would this look for the csh? That's what I was writing it for (actually, tcsh, but it should be backwards compatible...) Even better: Could this be included in the wget-script? ?! you have a script already that you want to add this stuff to? That'd be easier by far, because you'd only have to select once and not select, then select on *.deb. thanks joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Using tar saving Disk-space [was: apt-get offline]
Hi list Now that I can transfer my downloaded .debs in a .tar file, I wonder if I could create this .tar file saving disk space, e.g. in the following way pseudo-code create a tar file (touch packages.tar?) for *.deb in this directory 1.) add it to the tar file 2.) rm this .deb end /pseudo-code Is this possible for (non-GNU)-tar? How would this look for the csh? Even better: Could this be included in the wget-script? thanks joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: Using tar saving Disk-space [was: apt-get offline]
You can compress all .deb files into one zipped tar file with only one command. See the manual page of tar. You don't need to write code with a for-loop. I think it's tar czf packages.tar.gz debdir with debdir the directory containing all your .deb files, and packages.tar.gz the target zipped tarfile. On Wed, May 30, 2001 at 10:36:13AM +0200, Joerg Johannes wrote: Hi list Now that I can transfer my downloaded .debs in a .tar file, I wonder if I could create this .tar file saving disk space, e.g. in the following way pseudo-code create a tar file (touch packages.tar?) for *.deb in this directory 1.) add it to the tar file 2.) rm this .deb end /pseudo-code Is this possible for (non-GNU)-tar? How would this look for the csh? Even better: Could this be included in the wget-script? thanks joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: csh [was: Using tar saving Disk-space]
On Wed, May 30, 2001 at 10:36:13AM +0200, Joerg Johannes wrote: How would this look for the csh? I'm going to assume you're just plain unaware of this: csh programming Considered Harmful Somebody can probably provide a link to a copy of the essay. csh scripts are a majorly Bad Idea[tm]. It has been obsolete for years, and may it's fetid corpse never surface again. I suggest you try bash script or perl or something... -- Andrew Suffield [EMAIL PROTECTED] Dept. of Computing, Imperial College, London, UK pgp31JtWvPyKX.pgp Description: PGP signature
Re: csh [was: Using tar saving Disk-space]
Andrew Suffield wrote: On Wed, May 30, 2001 at 10:36:13AM +0200, Joerg Johannes wrote: How would this look for the csh? I'm going to assume you're just plain unaware of this: csh programming Considered Harmful Somebody can probably provide a link to a copy of the essay. csh scripts are a majorly Bad Idea[tm]. It has been obsolete for years, and may it's fetid corpse never surface again. I suggest you try bash script or perl or something... The problem is: this box is not my own, in fact, it is not even a debian one (Sun Solaris) and, the worst of all: It only runs csh because the admin does not like bash (I hate csh, too) joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: Using tar saving Disk-space [was: apt-get offline]
Well, I know how to use tar in general. Zipping the .debs is not necessary because they are already zipped. What I meant is: The .tar file takes the same amount of space as the .debs themselves. So after having tarred them , I need twice the space as before. So I want to delete each .deb after having it added to the .tar archive (to avoid exceeding my disk quota ;-) ) joerg Bart Martens wrote: You can compress all .deb files into one zipped tar file with only one command. See the manual page of tar. You don't need to write code with a for-loop. I think it's tar czf packages.tar.gz debdir with debdir the directory containing all your .deb files, and packages.tar.gz the target zipped tarfile. On Wed, May 30, 2001 at 10:36:13AM +0200, Joerg Johannes wrote: Hi list Now that I can transfer my downloaded .debs in a .tar file, I wonder if I could create this .tar file saving disk space, e.g. in the following way pseudo-code create a tar file (touch packages.tar?) for *.deb in this directory 1.) add it to the tar file 2.) rm this .deb end /pseudo-code Is this possible for (non-GNU)-tar? How would this look for the csh? Even better: Could this be included in the wget-script? thanks joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: csh [was: Using tar saving Disk-space]
Andrew Suffield wrote: On Wed, May 30, 2001 at 10:36:13AM +0200, Joerg Johannes wrote: How would this look for the csh? I'm going to assume you're just plain unaware of this: csh programming Considered Harmful Somebody can probably provide a link to a copy of the essay. csh scripts are a majorly Bad Idea[tm]. http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/
Re: Using tar saving Disk-space [was: apt-get offline]
And yo was Joerg Johannes heard to yodel: Well, I know how to use tar in general. Zipping the .debs is not necessary because they are already zipped. What I meant is: The .tar file takes the same amount of space as the .debs themselves. So after having tarred them , I need twice the space as before. So I want to delete each .deb after having it added to the .tar archive (to avoid exceeding my disk quota ;-) ) It appears that your problem is one of strategy...IIRC the --remove-files option only effects after the archive is completed.. However, you could do incremental additions to the archive. i.e. create an archive that fits on the available space, delete the files used, then add the next lot to the same archive until all files are in the archive. -- I'm not advocating that anyone take up emacs. Not even me: at my age, I'd be more likely to try bungee-jumping. It's easier, and has less risk of causing permanent brain damage. ** A posting on ZDNet forum
Re: Using tar saving Disk-space [was: apt-get offline]
Joerg Johannes [EMAIL PROTECTED] writes: JJ Now that I can transfer my downloaded .debs in a .tar file, I wonder if JJ I could create this .tar file saving disk space, e.g. in the following JJ way JJ JJ pseudo-code JJ create a tar file (touch packages.tar?) JJ for *.deb in this directory JJ1.) add it to the tar file JJ2.) rm this .deb JJ end JJ /pseudo-code JJ JJ Is this possible for (non-GNU)-tar? JJ How would this look for the csh? In any shell, you'd probably want tar cvf deb-packages.tar *.deb rm *.deb I'm curious why you want to do this, though; the amount of lost disk space is negligible (less than 4K per file), and I believe tar effectively adds this back in with per-block padding (remember, it was written to write archives to tapes). So the amount of disk space you'd actually save with this is about zero, give-or-take a little; it's already been noted that compressing the tar file is a lose, since Debian packages are ar archives containing a small indicator file and two gzipped tar files. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Re: csh [was: Using tar saving Disk-space]
Joerg Johannes [EMAIL PROTECTED] writes: The problem is: this box is not my own, in fact, it is not even a debian one (Sun Solaris) and, the worst of all: It only runs csh because the admin does not like bash (I hate csh, too) Solaris boxes have ksh, which is a pretty solid shell. I like bash better, but I would still use ksh over csh. -- Dave Carrigan ([EMAIL PROTECTED])| Yow! I always have fun because UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-DNS | I'm out of my mind!!! Seattle, WA, USA| http://www.rudedog.org/ |
Re: Using tar saving Disk-space [was: apt-get offline]
On Wed, 30 May 2001, Joerg Johannes wrote: Hi list Now that I can transfer my downloaded .debs in a .tar file, I wonder if I could create this .tar file saving disk space, e.g. in the following way pseudo-code create a tar file (touch packages.tar?) unnecessary, and in fact will break the script... for *.deb in this directory foreach foo (./*.deb) 1.) add it to the tar file tar -u $foo -f packages.tar 2.) rm this .deb rm $foo end end /pseudo-code Is this possible for (non-GNU)-tar? I think that I made it basic enough to be portable... How would this look for the csh? That's what I was writing it for (actually, tcsh, but it should be backwards compatible...) Even better: Could this be included in the wget-script? ?! you have a script already that you want to add this stuff to? That'd be easier by far, because you'd only have to select once and not select, then select on *.deb. thanks joerg -- There is an old saying that if a million monkeys typed on a million keyboards for a million years, eventually all the works of Shakespeare would be produced. Now, thanks to Usenet, we know this is not true. Who is John Galt? [EMAIL PROTECTED], that's who!
Re: split archives using tar
You would need to handle this using the -prune option to find. I just wrote a script to do something like what you are talking about, and I *think* that it looks like this: cd /home/howard find . -path .netscape/cache/* -prune -path vmware/* -prune -o -print \ | cpio -ovH crc /mnt/zip/homebackup-`date '+%d-%B-%Y'`.cpio I will have to look at my scripts again to confirm the syntax exactly, but the above is generally correct I think. I think there is an option to find to let you avoid the 'cd' command as I have shown above, but I can't remember it right at the moment. The info pages for GNU find are excellent rainy day reading and using this command well is an art in itself. The find command shown above says: find all filepaths starting in the current directory if the path is like .netscape/cache/* then discard it from the list if the path is like vmware/* then discard it from the list or (-o) else include (-print) the filepath Unlike tar, cpio relies entirely on something else to generate the list of files for archiving. The list can come from anywhere but is very frequently generated by a find command. You can also have the list read from a file or use some other favorite utility to generate it. This makes cpio backups a litle more hassle to set up in the beginning for simple cases, but I think in the long run using find is much more flexible. --- Howard Mann [EMAIL PROTECTED] wrote: What command would one use to _exclude_ certain directories from the archive? Specifically, what would the cpio command be to achieve the following ? : tar -cvpf /mnt/zip/homebackup-`date '+%d-%B-%Y'`.tar \ --directory /home/howard --exclude=vmware --exclude=.netscape/cache . Here I have archived my home directory except for the vmware and .netscape/cache directories. __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com
Re: split archives using tar
On Tue, 4 Jan 2000, John Davis wrote: I have a zip disk which I would like to use for archive in Linux. Can I run tar so that it will take a 500 Meg archive and split it into 5 100 Meg tar files? If so, how do I do this? Have you already tried man tar? To write a tar archive over multiple media use tar cMf /dev/your_zipdrive 500Meg.archive Or use split(1) to split an already existing 500 Meg tar archive in parts and cat(1) to join them again later. Needless to say that this is documented in man split. Good luck, P. *8^) -- If not specific to HP please always reply to Paul Seelig [EMAIL PROTECTED]
Re: split archives using tar
This is not exactly what you were asking for, but you might try something like: tar -cvMf /dev/sdz directories_to_archive where /dev/sdz is replaced by the device for your Zip drive. The 'M' option should (according to the man page) cause tar to prompt you for the next disk when it runs out of space on the first one. You can then extract the 'multi-volume' archive with a command like: tar -xvMf /dev/sdz I highly recommend using cpio in preference to tar if the archives are for your own use and not public distribution to unknown platforms. The command to use cpio would be: find directories_to_archive | cpio -ovH crc /dev/sdz Cpio will automatically span volumes and prompt for the next disk or tape when it runs out of space. The 'H crc' option a causes GNU cpio to create an archive in portable ASCII format with a 32-bit CRC for each file. This allows you to easily verify the archive's integrity and detect errors on restore. Unlike tar, cpio will not puke if it encounters a single error on restore but will continue to restore all undamaged data after the error. To verify with cpio: cpio --only-verify-crc -iv /dev/sdz This will not print any messages except the final block count if all the CRC checks are good. This does not compare files on tape to those on disk but instead reads the file from tape, calculates a CRC, and then compares it with the one stored on the tape at the time of creation to see if they match. To restore with cpio: cpio -imudv /dev/sdz Warning: the 'u' option causes cpio to automatically overwrite existing files on disk with those from the archive. --- John Davis [EMAIL PROTECTED] wrote: run tar so that it will take a 500 Meg archive and split it into 5 100 Meg tar files? If so, how do I do this? __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com
Re: split archives using tar
Michael W. Shaffer wrote: I highly recommend using cpio in preference to tar if the archives are for your own use and not public distribution to unknown platforms. The command to use cpio would be: find directories_to_archive | cpio -ovH crc /dev/sdz Cpio will automatically span volumes and prompt for the next disk or tape when it runs out of space. The 'H crc' option a causes GNU cpio to create an archive in portable ASCII format with a 32-bit CRC for each file. This allows you to easily verify the archive's integrity and detect errors on restore. Unlike tar, cpio will not puke if it encounters a single error on restore but will continue to restore all undamaged data after the error. What command would one use to _exclude_ certain directories from the archive? Specifically, what would the cpio command be to achieve the following ? : tar -cvpf /mnt/zip/homebackup-`date '+%d-%B-%Y'`.tar \ --directory /home/howard --exclude=vmware --exclude=.netscape/cache . Here I have archived my home directory except for the vmware and .netscape/cache directories. Thanks, -- Howard Mann Online Troubleshooting Resources: HOWTO http://www.newbielinux.comhttp://www.xmission.com/~howardm/t1.html
