Christian Weisgerber writes:
> Both OpenBSD's and FreeBSD's pax(1) go back to the one in 4.4BSD,
> but they have diverged since. In particular, OpenBSD uses pax as
> the base for tar and cpio--they're just different frontends for the
> same program--but FreeBSD doesn't, so pax is a bit neglected
Robert B. Carleton:
> I see FreeBSD tar(1) does support pax. I hadn't caught that yet... I
> guess I need to catch up on my FreeBSD reading.
FreeBSD uses tar(1) and cpio(1) from the libarchive project.
You can get those on OpenBSD by installing the libarchive package,
the utilities are called bs
"Robert B. Carleton" writes:
> Christian Weisgerber writes:
[...]
>> Those are similarly obsolete as ustar. libarchive-formats(5)
>> on FreeBSD mentions limitations:
>> "The SVR4 format uses eight-digit hexadecimal values for all
>> header fields. This limits file size to 4GB, and also limits
Christian Weisgerber writes:
> "Robert B. Carleton":
>
>> Unfortunately, the FreeBSD pax command lacks the pax format supported by
>> OpenBSD. I'm backing up paths that exceed the limits of ustar, so I'm
>> looking at alternatives.
>
> Use FreeBSD's tar(1).
>
I see FreeBSD tar(1) does support pa
"Robert B. Carleton":
> Unfortunately, the FreeBSD pax command lacks the pax format supported by
> OpenBSD. I'm backing up paths that exceed the limits of ustar, so I'm
> looking at alternatives.
Use FreeBSD's tar(1).
> I realize I could just use the various versions of tar or cpio, but I
> pref
v4cpio formats as an alternative that is supported by
both OpenBSD and FreeBSD.
Does anyone have anecdotes, or caveats to share about sv4crc and sv4cpio
pax formats?
The man pages on OpenBSD, and FreeBSD don't seem to indicate any
issues. I'm also doing some testing for my use ca
6 matches
Mail list logo
