Re: piping tail -f through cut

Bob van Loosen wrote: > Hi everyone, > > Whenever I do this: > > tail -f /var/log/kern.log | cut -f 8- -d " " | dd bs=1 > > I get no output, but when I do this: > > tail -f /var/log/kern.log | cut -f 8- -d " " > > I do get output, I'm using coreutils 5.97 on Ubuntu 7.10 64 bit. I've documen

Re: piping tail -f through cut

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pádraig Brady wrote: > Bob van Loosen wrote: >> Hi everyone, >> >> Whenever I do this: >> >> tail -f /var/log/kern.log | cut -f 8- -d " " | dd bs=1 >> >> I get no output, but when I do this: >> >> tail -f /var/log/kern.log | cut -f 8- -d " " >> >> I

Re: update fetch

Eric Blake <[EMAIL PROTECTED]> wrote: > [and adding coreutils] > > According to Ralf Wildenhues on 1/22/2008 1:59 PM: > | Hello, > | > | I've started to convert the release rules to git. I'm pretty sure they > | don't work right yet (with Automake I ended up typing them manually), > | but this pat

Re: piping tail -f through cut

On Feb 8, 2008 5:26 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: > It is a very silly idea, considering it would violate the C standard > (§7.19.3#7): > > As initially opened, the standard error stream is not fully buffered; > the standard input and standard output streams are fully buffered if and >

Re: sort --compare-version

Jim Meyering <[EMAIL PROTECTED]> writes: > Andreas Schwab <[EMAIL PROTECTED]> wrote: >> Bruce Korb <[EMAIL PROTECTED]> writes: >> >>> Yep. That's the reason for the "compare-" prefix. I didn't like >>> ``--compare-version-sort'' for some sort of reason, too. Ultimately, >>> someone pick another

"make check" failure

Hi Jim, Building coreutils-6.10 on a Linux/x86 machine fails like this for me: $ ./configure --prefix=/packages/gnu CPPFLAGS=-Wall $ make 2>&1 | tee log1 $ make check 2>&1 | tee log2 ... Making check in misc make[2]: Entering directory `/build/coreutils-6.10/tests/misc' make check-TESTS make[3]:

Re: piping tail -f through cut

James Youngman wrote: > On Feb 8, 2008 5:26 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: >> It is a very silly idea, considering it would violate the C standard >> (§7.19.3#7): >> >> As initially opened, the standard error stream is not fully buffered; >> the standard input and standard output stream