Michael Stone <[EMAIL PROTECTED]> writes:
> Yes, but I think it makes more sense to add this into a utility
> designed to make things sparse than to make cp copy stdin to
> stdout. And I'm not sure how well the idea of making output sparse
> would interact with dd, which is designed around the ide
On Sun, Mar 02, 2008 at 09:39:43AM -0800, Rob Browning wrote:
Both of these just don't seem right. Take a look at "zum" in the
perforate package; that's probably a better starting place than either
dd or cp.
Hmm, I hadn't seen perforate, but it appears that zum, like cp,
requires two copies of
[EMAIL PROTECTED] (Bob Proulx) writes:
> In which case it would be best to start a discussion upstream at
> [EMAIL PROTECTED] where it can benefit everyone. Debian is
> trying to avoid patching and forking as much as possible.
That's fine. Forwarding it would be appropriate, but I can also just
Rob Browning wrote:
> It would be nice to have some way to do this without depending on
> bash:
I don't understand why depending upon bash is worse than depending
upon other non-standard options? Isn't it just a matter of one or the
other? They both seem equally good/bad to me.
My question does
Package: coreutils
Severity: wishlist
It would be nice to have some way to do this without depending on
bash:
cp --sparse=always <(zcat foo.img.gz) foo.img
One possibility might be to make it possible to specify standard input
as a source for cp. Another possibility might be to add something
5 matches
Mail list logo
