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 idea of working > a block at a time and which has very strict requirements about how > to handle and report errors.
Sure. I only mentioned those as possibilities, in part to get the idea across. I'm definitely not trying to claim those are the best options, and I don't disagree with your concerns. A separate executable would be perfectly fine as far as I'm concerned. In any case, if this bug doesn't end up forwarded upstream (which is fine), I'll probably just mention it there myself when I get a chance. In the interim, since I use bash, I can just use "cp --sparse=always <(zcat foo.gz) bar". Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
