Date: Tue, 16 Nov 2004 13:35:36 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Andrew Sinclair <syncman@optusnet.com.au> Cc: freebsd-questions@freebsd.org Subject: Re: 5.3-RC2 tar breaks operation with "(null)" Message-ID: <20041116213536.GG17125@xor.obsecurity.org> In-Reply-To: <419A5AAB.7080409@optusnet.com.au> References: <419A5AAB.7080409@optusnet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--eMnpOGXCMazMAbfp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2004 at 07:53:15PM +0000, Andrew Sinclair wrote: > Hi everybodi! >=20 > At work I use a Windows eXPensive machine to gather information and=20 > maintain the web site. I needed to bring some files home and I didn't=20 > have time to setup a proper archiver, so I used cygnus tar to pack them= =20 > uncompressed. > I burned this tar dump onto a CD-RW. I didn't just pack everything=20 > into Nero and let the Toliet^WJoliet file system take care of it because= =20 > neither Joliet or Rock Ridge allow files to use the same name even if=20 > they are in different paths. Besides, there are file name size=20 > limitations... I have not even started yet. don't make me. > I'm using the new tar from 5.3-RC2 to read from the mounted CD-RW.=20 > It seems to have a problem with null blocks, halfway through the archive= =20 > in my case. I got this in the output: >=20 > bash-2.05b$ tar -xvf /dvdrom/20041116.tgz > ... > x Ocean Care Day/OCD website/Website/OCD Photos/mec cam=20 > pictures/000_0075.jpg > x Ocean Care Day/OCD website/Website/OCD Photos/mec cam pictures/Thumbs.db > x Ocean Care Day/OCD website/Website/OCD Photos/Presentation.ppt: (null) > tar: (null) > bash-2.05b$ >=20 > I remembered that tar uses four blocks of 0x00 to indicate the end=20 > of an archive on a sequential device, such as a tape, so I searched the= =20 > man page for an option to bypass it. No luck. Of all the problems people= =20 > have with defacto standard optical media, I had to run into a software=20 > issue :-\ >=20 > I might be able to get around it with another tar but surely the one= =20 > included should be able to work around this. Any ideas? Try an updated version of bsdtar, either by updating to 5.3-STABLE or installing the bsdtar port. Alternatively, use gtar. Kris --eMnpOGXCMazMAbfp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBmnKoWry0BWjoQKURAjwNAKCCvdTfh6d5Wr1RHIglRH9y1c5Z6ACg8jMR l5V+lRkbHaHpKNiXR9nAqzo= =dlmR -----END PGP SIGNATURE----- --eMnpOGXCMazMAbfp--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041116213536.GG17125>