home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sysv386:17727 comp.unix.pc-clone.32bit:1023
- Path: sparky!uunet!mcsun!sun4nl!tuegate.tue.nl!svin09!wsinis07!debra
- From: debra@wsinis07.info.win.tue.nl (Paul De Bra)
- Newsgroups: comp.unix.sysv386,comp.unix.pc-clone.32bit
- Subject: Re: serious bug in cpio -i -Htar
- Message-ID: <4956@svin09.info.win.tue.nl>
- Date: 11 Jan 93 14:33:03 GMT
- References: <4910@svin09.info.win.tue.nl> <1993Jan7.064311.9540@kilowatt.uucp>
- Sender: news@svin09.info.win.tue.nl
- Reply-To: debra@info.win.tue.nl
- Followup-To: comp.unix.sysv386
- Organization: Eindhoven University of Technology, the Netherlands
- Lines: 19
-
- In article <1993Jan7.064311.9540@kilowatt.uucp> root@kilowatt.UUCP (Kilowatt admin) writes:
- > SVR4 tar has another strange bug. Seems if when restoring files, you
- >restore one file that is a link, say "a ->/a/b/c/d/e" and there is another
- >link just after it called "b ->/a/b/c" tar will restore it as "b ->/a/b/c/d/e"
- >This just seems to be a lack of the NULL at the end of the string, like
- >someone did a memmov or memcpy(dest,src,strlen(src)); where it should be
- >strlen(src)+1 to include the NULL. Sure this is not the same bug in the cpio
- >code?
-
- Probably not the same bug. The bug encountered with cpio -i does not occur
- with tar x.
- The bug is even more serious than i originally posted:
-
- even when you do a 'cpio -ivt', i.e. you just want to look at what's in the
- archive, cpio will *extract* the links from the archive.
- so doing a cpio -ivt is *not* even a safe way to look at tar archives.
-
-
- Paul.
-