bug#7420: [Feature request]: add option to dd to fsync|fdatasync after each block written

2010-11-17 Thread Марк Коренберг
[Feature request]: add option to dd to fsync|fdatasync after each block written Suppose I want to show progress with: pv image.img | dd bs=16M of=/dev/sdc it will not work, as dd will write to sdc momentarily. dd will hang on close(1) waiting for actual write to complete (tested on USB stick Lin

bug#7421: [Feature request]: add option to dd to issue ioctl(BLKFLSBUF) on output descriptior after each write or at the end

2010-11-17 Thread Марк Коренберг
[Feature request]: add option to dd to issue ioctl(BLKFLSBUF) on output descriptior after each write or at the end I already has sent a message about fsync/fdatasync after each write. It seems that ioctl(BLKFLSBUF) need be implemented in same semantics. in oflags and conv i.e. ioctl after each wr

bug#7424: Tail -n doesn't work on Red-Hat Linux 5.5

2010-11-17 Thread Parsons, Larry
This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intend

bug#7424: Tail -n doesn't work on Red-Hat Linux 5.5

2010-11-17 Thread Eric Blake
On 11/17/2010 07:55 AM, Parsons, Larry wrote: [not much] > > This e-mail and files transmitted with it are confidential, In general, it is considered poor netiquette to send an email to a publicly archived list with a disclaimer that cannot be enforced. Furthermo

bug#7424: Tail -n doesn't work on Red-Hat Linux 5.5

2010-11-17 Thread Parsons, Larry
Eric, All, I just went to another box and entered in the command that you said shouldn't work. It works just the way you said it shouldn't. Oh, and guess what the help page is identical. Oh, and guess what I have never sent an email to this address before, and I didn't realize it was a public f

bug#7424: Tail -n doesn't work on Red-Hat Linux 5.5

2010-11-17 Thread Eric Blake
[as another netiquette tip: please don't top-post on technical lists] On 11/17/2010 12:03 PM, Parsons, Larry wrote: > Eric, All, > > I just went to another box and entered in the command that you said shouldn't > work. It works just the way you said it shouldn't. Please, so that we can have som

bug#7305: sort command not working in version 5.5 as it did in 4.7

2010-11-17 Thread Paul Eggert
On 11/17/10 14:33, Pádraig Brady wrote: > Note it scans command line args twice which > adds some overhead in all cases. > The first scan is to find --debug so we're not > dependent on the position of --debug I have some qualms about that patch. It's not just the extra overhead: the patch causes

bug#7305: sort command not working in version 5.5 as it did in 4.7

2010-11-17 Thread Pádraig Brady
On 17/11/10 23:51, Paul Eggert wrote: > On 11/17/10 14:33, Pádraig Brady wrote: > >> Note it scans command line args twice which >> adds some overhead in all cases. >> The first scan is to find --debug so we're not >> dependent on the position of --debug > > I have some qualms about that patch.

bug#7305: sort command not working in version 5.5 as it did in 4.7

2010-11-17 Thread Paul Eggert
On 11/17/2010 05:41 PM, Pádraig Brady wrote: > Yes that is marginally safer but less useful in the common > case of using an isolated +... > > $ sort --debug +1 > sort: using `en_US.utf8' sorting rules > sort: non-portable file name +1; use ./+1 instead > sort: open failed: +1: No such file or di

bug#7401: [PATCH] split: --chunks option

2010-11-17 Thread Jim Meyering
Pádraig Brady wrote: > On 05/02/10 12:40, Pádraig Brady wrote: >> I got a bit of time for the review last night... ... >> Here is stuff I intend TODO before checking in: >> s/pread()/dd::skip()/ or at least add pread to bootstrap.conf >> fix info docs for reworked interface >> try to refactor du