Wrong

Post #71,146 by kmself 12/27/02 7:05:36 PM Reply	Wrong You're confusing IFS with the OS's inherent ability to manipulate files with spaces. When working through the shell, these names need to be quoted. Tar handles 'em fine: \r\n\r\n \r\n \r\n[karsten@academy:karsten]$ cd tmp\r\n[karsten@academy:tmp]$ mkdir boxley\r\n[karsten@academy:tmp]$ cd boxley\r\n[karsten@academy:boxley]$ touch "a file with spaces"\r\n[karsten@academy:boxley]$ touch "another of the same"\r\n[karsten@academy:boxley]$ ls \r\na file with spaces another of the same\r\n[karsten@academy:boxley]$ cd ..\r\n[karsten@academy:tmp]$ tar czvf boxley.tar.gz boxley/\r\nboxley/\r\nboxley/a file with spaces\r\nboxley/another of the same\r\n[karsten@academy:tmp]$ mkdir untar\r\n[karsten@academy:tmp]$ cd untar \r\n[karsten@academy:untar]$ tar xzvf ../boxley.tar.gz \r\nboxley/\r\nboxley/a file with spaces\r\nboxley/another of the same\r\n[karsten@academy:untar]$ ll\r\ntotal 1\r\ndrwxr-sr-x 2 karsten karsten 128 Dec 27 18:02 boxley\r\n[karsten@academy:untar]$ ll boxley/\r\ntotal 0\r\n-rw-r--r-- 1 karsten karsten 0 Dec 27 18:02 a file with spaces\r\n-rw-r--r-- 1 karsten karsten 0 Dec 27 18:02 another of the same\r\n \r\n --\r\n Karsten M. Self [link\|mailto:kmself@ix.netcom.com\|kmself@ix.netcom.com]\r\n [link\|http://kmself.home.netcom.com/\|http://kmself.home.netcom.com/]\r\n What part of "gestalt" don't you understand?\r\n [link\|http://twiki.iwethey.org/twiki/bin/view/Main/\|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n \r\n Keep software free. Oppose the CBDTPA. Kill S.2048 dead.\r\n[link\|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html\|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
Post #71,152 by boxley 12/27/02 8:09:51 PM Reply	The reason I brought this upo was recovering files from a doze box to a linux box running rhat 7.0. Mounted a NT drive from the linux box and tarred about a gig onto the linux box tarball.tar. I ftp'd the file to a second linux box running 7.0 and untarred the file. On extraction it had problems with the type of file naming convention with spaces. I manually had to crawl thru the doze box directory by directory to get the files. That is why I brought it up. It appears to not be a problem as shown by your post. hanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/resume/Resume.html\|skill set] You think that you can trust the government to look after your rights? ask an Indian
Post #71,167 by kmself 12/27/02 10:15:59 PM Reply	Two possible issues I can think of... ...barring your posting commands used. \r\n\r\n Some tars have an absolute cap on filename length. I'm not sure what this is with GNU tar, but recursing long names into a directory should identify whether this exists at any of the likely intervals (256, 512, 1024, 2048, 4096 characters, etc.). I have encountered this problem, possibly on either tar, CD ROM (the iso9660 format also has a total name length cap), or NTFS. \r\n\r\n Depending on how you were selecting files for inclusion in your tar archive, you may have run into the shell quoting issues mentioned earlier. You'll find that GNU tar does allow for null-terminated filenames, to work around the problem of embedded whitespace. Some folks feed `find` output to tar, in which case the problem can crop up. One of the reasons I prefer tar over such alternatives as cpio and afio is that tar will handle directory recursion itself while the other tools want input fed from stdin, by means that always require heavy manpage decoding by me. Note that there are some commendable advantages to the filestructures used by cpio & afio, I'm not criticising these. \r\n\r\n Bill, you made an absolute statement of what tar could or couldn't do. It's demonstrably wrong for GNU tar. If you care to show methods, we might be able to identify the source of the problem. It's not what you've represented it to be. --\r\n Karsten M. Self [link\|mailto:kmself@ix.netcom.com\|kmself@ix.netcom.com]\r\n [link\|http://kmself.home.netcom.com/\|http://kmself.home.netcom.com/]\r\n What part of "gestalt" don't you understand?\r\n [link\|http://twiki.iwethey.org/twiki/bin/view/Main/\|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n \r\n Keep software free. Oppose the CBDTPA. Kill S.2048 dead.\r\n[link\|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html\|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
Post #71,180 by boxley 12/27/02 10:43:35 PM Reply	It was over a year ago so bear with me had a NTFS box with a crossover cable connected to a linux laptop. The Drive was mounted via NFS to the /mnt mount point. Used SOSNT (son of sam nt a nfs server for nt) at the command line in bsh from the root directory used "tar cvf tarball.tar mnt" . after creating the file I disconnected the NT box and using the regular network ftp'd the tar file to a third linux box. Ran the command "tar xvf tarball.tar" I noticed the ocassional error at that point "foo file name" cannot extract file cannot extract name. So assumed it had a problem writing so went back to the source to get the files that wernt untarred manually. Now from your example it works just fine. I was using ext2 file systems on both linux boxes and RH 7.0 . Apparently what I saw belonged to another issue because as you have shown he it works just fine. Also works on darwin when I retested after your post. So I saw an abberation? thanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/resume/Resume.html\|skill set] You think that you can trust the government to look after your rights? ask an Indian

Welcome to IWETHEY!