Messages in this thread | | | Date | Fri, 10 Aug 2012 14:56:54 +0200 (CEST) | From | Jan Engelhardt <> | Subject | Re: Regression - /proc/kmsg does not (always) block for 1-byte reads |
| |
On Saturday 2012-07-07 23:19, Kay Sievers wrote: >On Fri, Jul 6, 2012 at 10:30 PM, Linus Torvalds ><torvalds@linux-foundation.org> wrote: >> Kay, this needs to be fixed. >> >> Suggested fix: just use the 'seq_printf()' interfaces, which do the >> proper buffering, and allow any size reads of various packetized data. > >I'll have a look. > >> Of course, I'd also suggest that whoever was the genius who thought it >> was a good idea to read things ONE F*CKING BYTE AT A TIME with system >> calls for each byte should be retroactively aborted. Who the f*ck does >> idiotic things like that? How did they noty die as babies, considering >> that they were likely too stupid to find a tit to suck on? > >Maybe the bs=1 in the dd call stands for bullshit. :)
It seems people need to be taught to use ddrescue, stringently. Having to calculate appropriate values for bs= and count= when you just want to transfer bytes is already a crime, not to mention the problem when you have a prime number of bytes to transfer.
| |