Bryan Kadzban wrote:
It actually registers udevsend as the handler, not udev. udevsend
serializes events and then passes them to udev, IIRC. Maybe make the
end of the last sentence look like:
registered udevsend (which runs udev) as this handler.
Yep, I spotted that a couple of weeks ago, but the
I am trying to build a test system from the LFS6 boot cd.
In chapter 5, I can't even get through the 1st binutils:
/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../binutils-2.15.94.0.2.2/bfd -I. -D_GNU_SOURCE -DTRAD_CORE -I.
-I../../binutils-2.15.94.0.2.2/bfd
-I../../binutils
Good grief, I'm replying to myself a lot today!
Anyway, I just saw what I think is a typo in section 7.4 (in the intro):
Device nodes do not require much disk space, so the memory that is
used in negligable.
That should have an 's/ in / is /' done to it, I think.
Also, I missed this in 7.4.2 the fi
Bryan Kadzban wrote:
So when I got to autoconf, it
failed to build, because the chapter 5 Perl did not have Data::Dumper
installed (and /usr/bin/perl was in /tools).
Oops, missed some words:
s/in/looking for it in/
signature.asc
Description: OpenPGP digital signature
--
http://linuxfromscratch.o
Bryan Kadzban wrote:
If I run into other issues, I'll post them then. I've just finished
compiling binutils pass 1 (yes, by hand, I have a whole weekend ;-) ).
Well, I ran into two issues, but both of them seemed to be caused by my
own mistakes (I really should come up with a scripted build syst
Greg Schafer wrote:
> Last time it was a question of attribution. LFS has a
> poor record of crediting contributions.
Well, FWIW I always try and note the bug reporter and fix-provider in
the ChangeLog, and will here as well, of course. If I've previously
missed anything then I apologise and req
