Re: Request for Comments: libarchive, bsdtar
From: Don Lewis (truckman_at_FreeBSD.org)
Date: 01/15/04
- Previous message: Tim Kientzle: "Re: Request for Comments: libarchive, bsdtar"
- In reply to: Tim Robbins: "Re: Request for Comments: libarchive, bsdtar"
- Next in thread: Tim Kientzle: "Re: Request for Comments: libarchive, bsdtar"
- Reply: Tim Kientzle: "Re: Request for Comments: libarchive, bsdtar"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 14 Jan 2004 21:37:50 -0800 (PST) To: tjr@FreeBSD.org
On 15 Jan, Tim Robbins wrote:
> - Padding gzip'd tar archives (with bsdtar czf) causes gzip to report
> "trailing garbage" and fail, and in turn this causes GNU tar to fail.
> BSD pax (-wzf) and GNU tar (czf) do not pad compressed archives.
In the case of GNU tar, it depends on where it is writing. It pads when
writing to stdout, but does not pad when writing to a file. I would
hope that it pads when writing to a tape device, since many tapes
require writing to some multiple of their native block size.
% tar cfz /tmp/printcap.tgz /etc/printcap
tar: Removing leading `/' from member names
% ls -l /tmp/printcap.tgz
-rw-r--r-- 1 dl wheel 1216 Jan 14 21:28 /tmp/printcap.tgz
% tar cfz - /etc/printcap > /tmp/printcap.tgz
tar: Removing leading `/' from member names
% ls -l /tmp/printcap.tgz
-rw-r--r-- 1 dl wheel 10240 Jan 14 21:28 /tmp/printcap.tgz
I would prefer to have explicit control of this behavior.
BTW, on a Unix variant that I used many years ago, there was an enhanced
version of dd, called ddx, which had the useful option "mobs", which was
used to specify a minimum output block size. You could run something
like
ddx obs=10k mobs=1k ...
to cause all writes to be blocked to 10k except for the last partial
write which would be padded out to at least 1k. I don't remember what
it did if there was 1025 bytes left over for the last write ...
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Tim Kientzle: "Re: Request for Comments: libarchive, bsdtar"
- In reply to: Tim Robbins: "Re: Request for Comments: libarchive, bsdtar"
- Next in thread: Tim Kientzle: "Re: Request for Comments: libarchive, bsdtar"
- Reply: Tim Kientzle: "Re: Request for Comments: libarchive, bsdtar"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: [opensuse] Split command to burn DVD+R (file size)
... multi-volume tar to work in the same way as it would with a tape device ...
DVD media as read write filestore but I have never suceeded with my ... Packet writing
would be really nice, but again not all hardware has ... I do get an I/O error on retrieving
data that looks like it is probably ... (SuSE) - Re: Tar error code
... that's what the documentation says and the absence of any diagnostic info is why I suspected
a tar bug. ... or ENOSPC or even ERANGE, but not EPIPE, at least if tar were writing
... no pipes involved unless the USB connection magic approximates some sort of pipe. ...
martin@ | Martin Gregorie ... (uk.comp.os.linux) - Re: this is not a specific linux question but more of just UNIX - tar, dump, restore command questio
... The 2GiB issue is not a tar issue. ... Dittos for cpio. ... I
think, GNU tar has some issues with long filenames, when reading non-GNU ... I am covered
with pure vegetable oil and I am writing a best seller! ... (comp.os.linux.misc) - Re: Tar error code
... Code 141 isn't listed in either the man page or the info documentation ... Exit
codes above 128 being signals are a Unix de-facto standard ... fundamental tar limit.
... or ENOSPC or even ERANGE, but not EPIPE, at least if tar were writing ... (uk.comp.os.linux) - Re: Question about General Relativity
... My vision is, you are writing a post, you click "insert sketch", you ... Classroom
writing screens. ... That certainly is a closely related technology, ... I hadn't
seen the laptops with scratch pads. ... (sci.physics)