Frans de Boer wrote:
On 07/10/2015 12:16 AM, Bruce Dubbs wrote:
Frans de Boer wrote:
I found - in the meantime - that using 'seq 1.1 inf | head -n2' also
does stop it. Somehow, 'inf' does not trigger the right response on my
machine and head does nothing to stop it. My question to you: do you use
'head' from chapter 5 (TC-phase) or the completed chapter 6 (BSS-phase)?
I think I will rebuild from scratch again (2e time) and start fresh
tomorrow to dig into this deeper.
For now, good night, Frans.
I get the same results in chroot with
$ /tools/bin/seq 999999 inf | head -n2
$ seq 999999 inf | head -n2
-- Bruce
Well, I rebuild everything again with the same bad results.
Whatever I do, seq does not handle the argument inf well.
Normally the '| head -n2' would break the pipe where thereafter the
feeding side would terminate because of a broken pipe. No such thing
here as seq keeps on running without any output anymore.
I tried to make a new tar file from git, but I lack the knowledge of how
to make a usable archive from a git directory. When I try, it ends up
being 72+ MB instead of 5+ MB.
I also re-downloaded the tar file, but that was no solution either.
It seems to work elsewhere, but not on my builds/machine.
Just a thought. Do you have the virtual file systems mounted when you
are doing these tests? I'm not sure if that would affect things or not.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
