Jesse Keating wrote:
On Wed, 2005-06-08 at 11:41 -0400, Neal Becker wrote:
If I understand correctly, tar will only handle sparse files properly
if
told to explicitly, using the --sparse flag. Unless tar defaults to
handling sparse intelligently without the flag, 85% of all fedora
sysadmins
are going to be really pissed.
Again, tar won't do ANYTHING unless you pass the right arguments,
whatever they may be. You have to know what you're telling tar to do.
There is no default, other than displaying the usage (which states how
to use --sparse)
Not entirely true.
As you stated, tar (or most commands for that matter) will, by default,
output usage when no options are entered.
When creating a tar, by default, it creates an uncompressed tar rather
than assuming a compression type ... which is a sensible thing to do.
What I think is being asked for here is the default treatment of sparse
files to be changed.
Right now, tar doesn't do anything special to handle sparse files, by
default.
It could, equally as legitimately, have --sparse assumed by default and
require some sort of --nosparse option to be used if you want it to not
handle sparse files.
I don't really see that as being unreasonable. However, I don't have a
lot of experience with using tar to backup though. In your experience,
is there a reason not to use --sparse in most occasions?
Usually sensible defaults are the best way to go and if 99% of the time,
you want your tar to "condense" sparse files, then it is likely best to
make it do that by default.
/Mike