cvs commit: src/usr.bin/cpio Makefile bsdcpio.1 cmdline.c config_freebsd.h cpio.c cpio.h cpio_platform.h err.c matching.c matching.h pathmatch.c pathmatch.h src/usr.bin/cpio/test Makefile main.c test.h test_0.c test_basic.c test_format_newc.c ...

[Joerg Sonnenberger]

On Wed, May 28, 2008 at 06:58:32AM -0700, David O'Brien wrote:
> Please read this as: "Please don't touch pax".  It works fine as-is, is
> small, is only used by folks that know it exists (many BSD users don't),
> is BSDL'ed, pretty much cause no harm or extra work for us, etc...

It doesn't work as-is. Consider the attached pax archive. I strongly
believe it is a valid "pax Interchange Format" archive as defined by the
Single Unix Specification. FreeBSD's pax can't handle this. NetBSD's pax
is somewhat better as it at least detects that an extended header is
used, but can't deal with it correctly.

Now you might consider long symlinks an obscure edge case, but they
happen in real world situations. Mono f.e. has a number of such long
symlinks.

Joerg