Re: fileutils can now replace perforate...
> But --sparse=auto is impossible to implement correctly on many
> systems, and filesystem-dependent on others !
Depends on what you mean by sparse... the trick is that you can use
stat() to determine if the file has *any* holes. If it has none, you
don't try to make new ones; if it already has some, you produce the
maximal amount. You may produce more sparseness than before -- but it
isn't like the application has any way to tell *where* the holes
are...
Reply to: