linux fan wrote:
On 3/19/10, Mike McCarty mike.mcca...@sbcglobal.net wrote:
I wonder if head is closing the input pipe when it has read
all it needs, and that's causing the error. I can't reproduce
that problem with my host system, however.
It is tar-1.23 and not head
Umm, I didn't mean
I started a new build of current dev LFS, and noticed some strange
behavior from tar once inside chroot. Using tar 1.23, attempting to pipe
its tf output through head results in a tar: write error. In other
words...
tar -tjf /home/sources/glibc-2.11.1.tar.bz2 | head -n1
glibc-2.11.1/
Chris Staub wrote:
I started a new build of current dev LFS, and noticed some strange
behavior from tar once inside chroot. Using tar 1.23, attempting to pipe
its tf output through head results in a tar: write error. In other
words...
tar -tjf /home/sources/glibc-2.11.1.tar.bz2 | head
Bruce Dubbs wrote:
Chris Staub wrote:
[...]
I do not get any kind of error message when just using tar -tf by
itself, only when piping through head. Also, I tried piping through
various other programs (grep, sed...) and got nothing.
I get the same error message with head:
./configure
On 3/19/10, Mike McCarty mike.mcca...@sbcglobal.net wrote:
I wonder if head is closing the input pipe when it has read
all it needs, and that's causing the error. I can't reproduce
that problem with my host system, however.
It is tar-1.23 and not head
head --version
head (GNU coreutils) 8.4
linux fan wrote:
On 3/19/10, Mike McCarty mike.mcca...@sbcglobal.net wrote:
I wonder if head is closing the input pipe when it has read
all it needs, and that's causing the error. I can't reproduce
that problem with my host system, however.
It is tar-1.23 and not head
head --version
On Fri, 19 Mar 2010 14:21:29 -0600
Mike McCarty mike.mcca...@sbcglobal.net wrote:
Bruce Dubbs wrote:
Chris Staub wrote:
[...]
I do not get any kind of error message when just using tar -tf
by itself, only when piping through head. Also, I tried piping
through various other programs
