Peter Jeremy wrote:
> Note that it isn's possible to accurately distinguish between a block
> of NULs and a hole in the file through the filesystem. The only way
> to accurately copy a sparse file is with dump/restore.
Hence the need for an explicit switch.
> This is true in the desktop and server market but is not true in the
> embedded market and only marginally true for laptops.
I don't know about embedded markets (do they need cp, or it's simply
kernel+dedicated application?) but I've recently bought a 60GB laptop
drive for ~~ $120 (converted back from my currency, may be cheaper in
other parts of the world) - that's $2/GB.