[lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
When building and installing (6.9) the glibc ... what test errors are acceptable? What are the guidelines for determining quirkiness vs. woops, I screwed up ? For example, the following error (and a refusal to finish the make) .. I assume to be bad: make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 Scratch I am in the process of doing it again (re-patch/etc..) and see what happens. I am building on a 2.6.32 kernel, and I might very well have left the 2.6.25 in the copied shell command... However, I was just wondering what tests, when they fail, are FAIL rather than fail;) :) ? -- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
Actually, this is my entire list: make[2]: *** [/sources/glibc-build/libio/tst-fopenloc.check] Error 127 make[1]: *** [libio/tests] Error 2 make[2]: *** [/sources/glibc-build/posix/bug-regex32.out] Error 1 make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored) make[2]: *** [/sources/glibc-build/posix/bug-regex2-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex14-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex21-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex31-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-rxspencer-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-pcre-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-boost-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-glob2-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-vfork3-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-fnmatch-mem] Error 127 make[1]: *** [posix/tests] Error 2 make[2]: *** [/sources/glibc-build/misc/tst-error1-mem] Error 127 make[1]: *** [misc/tests] Error 2 make[2]: *** [/sources/glibc-build/nptl/tst-stack3-mem] Error 127 make[1]: *** [nptl/tests] Error 2 make[2]: *** [/sources/glibc-build/elf/tst-leaks1-mem] Error 127 make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 make[1]: *** [elf/tests] Error 2 make: *** [check] Error 2 I assume I have failed? --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 09:28, David Scott Williams wrote: When building and installing (6.9) the glibc ... what test errors are acceptable? What are the guidelines for determining quirkiness vs. woops, I screwed up ? For example, the following error (and a refusal to finish the make) .. I assume to be bad: make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 Scratch I am in the process of doing it again (re-patch/etc..) and see what happens. I am building on a 2.6.32 kernel, and I might very well have left the 2.6.25 in the copied shell command... However, I was just wondering what tests, when they fail, are FAIL rather than fail;) :) ? -- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
Now -- this is funny, I re-ran: === I have no name!:/sources/glibc-build# make -k check 21 | tee glibc-check-log And it seems to have done OK on the second run... I have no name!:/sources/glibc-build# grep Error glibc-check-log I have no name!:/sources/glibc-build# = Weird. --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 09:49, David Scott Williams wrote: Actually, this is my entire list: make[2]: *** [/sources/glibc-build/libio/tst-fopenloc.check] Error 127 make[1]: *** [libio/tests] Error 2 make[2]: *** [/sources/glibc-build/posix/bug-regex32.out] Error 1 make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored) make[2]: *** [/sources/glibc-build/posix/bug-regex2-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex14-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex21-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex31-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-rxspencer-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-pcre-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-boost-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-glob2-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-vfork3-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-fnmatch-mem] Error 127 make[1]: *** [posix/tests] Error 2 make[2]: *** [/sources/glibc-build/misc/tst-error1-mem] Error 127 make[1]: *** [misc/tests] Error 2 make[2]: *** [/sources/glibc-build/nptl/tst-stack3-mem] Error 127 make[1]: *** [nptl/tests] Error 2 make[2]: *** [/sources/glibc-build/elf/tst-leaks1-mem] Error 127 make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 make[1]: *** [elf/tests] Error 2 make: *** [check] Error 2 I assume I have failed? --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 09:28, David Scott Williams wrote: When building and installing (6.9) the glibc ... what test errors are acceptable? What are the guidelines for determining quirkiness vs. woops, I screwed up ? For example, the following error (and a refusal to finish the make) .. I assume to be bad: make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 Scratch I am in the process of doing it again (re-patch/etc..) and see what happens. I am building on a 2.6.32 kernel, and I might very well have left the 2.6.25 in the copied shell command... However, I was just wondering what tests, when they fail, are FAIL rather than fail;) :) ? -- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
I feel silly replying to myself again -- but...after re-running the check, and it coming up OK... I went ahead and went to install this glibc... the tail end of the error message (I assume this is relating to a manual//info?) is as follows. Not sure if this is OK/normal/whatever. make[2]: Entering directory `/sources/glibc-2.14.1/manual' pwd=`pwd`; \ no libm-err-tab.pl $pwd/.. libm-err-tmp /bin/sh: line 1: no: command not found make[2]: *** [stamp-libm-err] Error 127 make[2]: Leaving directory `/sources/glibc-2.14.1/manual' make[1]: *** [manual/subdir_install] Error 2 make[1]: Leaving directory `/sources/glibc-2.14.1' make: *** [install] Error 2 I have no name!:/sources/glibc-build# --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 09:58, David Scott Williams wrote: Now -- this is funny, I re-ran: === I have no name!:/sources/glibc-build# make -k check 21 | tee glibc-check-log And it seems to have done OK on the second run... I have no name!:/sources/glibc-build# grep Error glibc-check-log I have no name!:/sources/glibc-build# = Weird. --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 09:49, David Scott Williams wrote: Actually, this is my entire list: make[2]: *** [/sources/glibc-build/libio/tst-fopenloc.check] Error 127 make[1]: *** [libio/tests] Error 2 make[2]: *** [/sources/glibc-build/posix/bug-regex32.out] Error 1 make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored) make[2]: *** [/sources/glibc-build/posix/bug-regex2-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex14-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex21-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-regex31-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-rxspencer-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-pcre-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-boost-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/bug-glob2-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-vfork3-mem] Error 127 make[2]: *** [/sources/glibc-build/posix/tst-fnmatch-mem] Error 127 make[1]: *** [posix/tests] Error 2 make[2]: *** [/sources/glibc-build/misc/tst-error1-mem] Error 127 make[1]: *** [misc/tests] Error 2 make[2]: *** [/sources/glibc-build/nptl/tst-stack3-mem] Error 127 make[1]: *** [nptl/tests] Error 2 make[2]: *** [/sources/glibc-build/elf/tst-leaks1-mem] Error 127 make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 make[1]: *** [elf/tests] Error 2 make: *** [check] Error 2 I assume I have failed? --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 09:28, David Scott Williams wrote: When building and installing (6.9) the glibc ... what test errors are acceptable? What are the guidelines for determining quirkiness vs. woops, I screwed up ? For example, the following error (and a refusal to finish the make) .. I assume to be bad: make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 Scratch I am in the process of doing it again (re-patch/etc..) and see what happens. I am building on a 2.6.32 kernel, and I might very well have left the 2.6.25 in the copied shell command... However, I was just wondering what tests, when they fail, are FAIL rather than fail;) :) ? -- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
Hi David, On 29/11/2011 10:13, David Scott Williams wrote: I feel silly replying to myself again -- but...after re-running the check, and it coming up OK... I went ahead and went to install this glibc... the tail end of the error message (I assume this is relating to a manual//info?) is as follows. Not sure if this is OK/normal/whatever. make[2]: Entering directory `/sources/glibc-2.14.1/manual' pwd=`pwd`; \ no libm-err-tab.pl $pwd/.. libm-err-tmp /bin/sh: line 1: no: command not found make[2]: *** [stamp-libm-err] Error 127 make[2]: Leaving directory `/sources/glibc-2.14.1/manual' make[1]: *** [manual/subdir_install] Error 2 make[1]: Leaving directory `/sources/glibc-2.14.1' make: *** [install] Error 2 I have no name!:/sources/glibc-build# I just checked through the section of Glibc source code and I believe glibc-2.14.1/manual/Makefile line 110 is where it goes wrong for you. The line in question contains: $(PERL) $ $$pwd/.. libm-err-tmp The $(PERL) variable seems to have expanded into no which likely will be traced back during an error encountered during the configure script where it tried to detect perl and failed. There is a second issue: notice the last line in your output: I have no name!:/sources/glibc-build# I have no name! is significant here. This is caused by the system not knowing who you are - usually because of a missing /etc/passwd file. This step is handled in Section 6.6 of the book Creating Essential Files and Symlinks. If this step was missed, perhaps you missed a couple of other steps in the same beginnings of Chapter 6 that led to Glibc's failure. Some of those core system files will definitely trip up a configure script. The files are simply assumed to always exist without exception and error checking for their absence often doesn't exist or is poorly done. If in doubt, perhaps start Chapter 6 from the beginning again assuming Chapter 5 was done correctly. Gerard -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Bug in latest kernel releases (3.1.0 ... 3.1.4)
Nov 29, 2011 02:09:37 AM, Simon wrote: A little dramatic, don't you think? The world isn't going to end, just because you've found a bug in a video driver... In the KERNEL Simon, in the KERNEL, NOT the driver. Also, come to think of it, I didn't find the BUG, it found me! :) Speaking of drama, don't you think that for a KERNEL to mess up the return from graphics, so badly and inexcusably as of 3.x and end of 2011, that's pretty dramatic (and sad)? Thank you for your comments. Keep the faith. Only 14 more years. (BTW, if the world is to end at all, that would be in a little over a year or so - according to the Mayans). -- Alex -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
Here is the section I did not do. I did not realize that it was mandatory (I thought it was cosmetic ;)) == To remove the “I have no name!” prompt, start a new shell. Since a full Glibc was installed in Chapter 5 and the / etc/passwd and /etc/group files have been created, user name and group name resolution will now work: exec /tools/bin/bash --login +h = Also, it seems that while I built perl in 5.x, I neglected the copy part at the end. Teaches me to rush this along... Thanks for the help Dave --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 10:27, Gerard Beekmans wrote: Hi David, On 29/11/2011 10:13, David Scott Williams wrote: I feel silly replying to myself again -- but...after re-running the check, and it coming up OK... I went ahead and went to install this glibc... the tail end of the error message (I assume this is relating to a manual//info?) is as follows. Not sure if this is OK/normal/whatever. make[2]: Entering directory `/sources/glibc-2.14.1/manual' pwd=`pwd`; \ no libm-err-tab.pl $pwd/.. libm-err-tmp /bin/sh: line 1: no: command not found make[2]: *** [stamp-libm-err] Error 127 make[2]: Leaving directory `/sources/glibc-2.14.1/manual' make[1]: *** [manual/subdir_install] Error 2 make[1]: Leaving directory `/sources/glibc-2.14.1' make: *** [install] Error 2 I have no name!:/sources/glibc-build# I just checked through the section of Glibc source code and I believe glibc-2.14.1/manual/Makefile line 110 is where it goes wrong for you. The line in question contains: $(PERL) $ $$pwd/.. libm-err-tmp The $(PERL) variable seems to have expanded into no which likely will be traced back during an error encountered during the configure script where it tried to detect perl and failed. There is a second issue: notice the last line in your output: I have no name!:/sources/glibc-build# I have no name! is significant here. This is caused by the system not knowing who you are - usually because of a missing /etc/passwd file. This step is handled in Section 6.6 of the book Creating Essential Files and Symlinks. If this step was missed, perhaps you missed a couple of other steps in the same beginnings of Chapter 6 that led to Glibc's failure. Some of those core system files will definitely trip up a configure script. The files are simply assumed to always exist without exception and error checking for their absence often doesn't exist or is poorly done. If in doubt, perhaps start Chapter 6 from the beginning again assuming Chapter 5 was done correctly. Gerard -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] It's baaaaack! Libmpfr not found in gcc make.
Christian Gardner wrote: So the last time I had this problem a couple of weeks ago, it occurred only in the second pass of the gcc build. Now it occurs in the first pass. And unlike last time, it hasn't magically disappeared. Having trashed the partition with my host LFS system on it, I'm using Xubuntu 11.04 as the host this time. But that's unlikely to be the problem given this occurred back with LFS 6.8 as host too. To recap: I can create the filesystem okay and install the binutils tool (first pass). Doing gcc, the configure appears to go okay but then the make quits after a while, with configure: error: libmpfr not found or uses a different ABI. Follow the book: These are from 5.3. General Compilation Instructions tar -xf gcc.tarball cd gcc-4.6.2 -- you probably missed this. # From 5.5.1. Installation of Cross GCC tar -jxf ../mpfr-3.1.0.tar.bz2 mv -v mpfr-3.1.0 mpfr tar -jxf ../gmp-5.0.2.tar.bz2 mv -v gmp-5.0.2 gmp tar -zxf ../mpc-0.9.tar.gz mv -v mpc-0.9 mpc ... -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
David Scott Williams wrote: Here is the section I did not do. I did not realize that it was mandatory (I thought it was cosmetic ;)) Building an OS is complicated. Don't assume. There are a couple of places where we say an item is optional, but not many. The most general recommendation for the first few times is do things *exactly* as specified in the book. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
On 29/11/2011 11:04, Bruce Dubbs wrote: David Scott Williams wrote: Here is the section I did not do. I did not realize that it was mandatory (I thought it was cosmetic ;)) Building an OS is complicated. Don't assume. There are a couple of places where we say an item is optional, but not many. The most general recommendation for the first few times is do things *exactly* as specified in the book. In David's defense I can understand his point too. If all the book says is to remove the I have no name! prompt then I can see where that sounds like it's not all that significant. In our defense, passwd and group files are core/essential Linux files that no *NIX system lives without so we also make our assumptions that certain things are just understood by Linux users. It's definitely a bit of a grey area. Cleaning up the text a bit would not necessarily be a bad thing either (not to be confused with excessive hand-holding but have it be more correct as there are additional reasons beyond that I have no name prompt although that's probably the most visible of reasons). Gerard -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
BTW-- now that I have done what the book told me to do, CC=gcc /usr/bin/perl scripts/test-installation.pl /sources/glibc-build/ Your new glibc installation seems to be ok. make[1]: Leaving directory `/sources/glibc-2.14.1' root:/sources/glibc-build# :) Joy. --- David Scott Williams twitter: @dscott_williams blog: http://deadpenguinsociety.org On 29.11.2011 11:10, Gerard Beekmans wrote: On 29/11/2011 11:04, Bruce Dubbs wrote: David Scott Williams wrote: Here is the section I did not do. I did not realize that it was mandatory (I thought it was cosmetic ;)) Building an OS is complicated. Don't assume. There are a couple of places where we say an item is optional, but not many. The most general recommendation for the first few times is do things *exactly* as specified in the book. In David's defense I can understand his point too. If all the book says is to remove the I have no name! prompt then I can see where that sounds like it's not all that significant. In our defense, passwd and group files are core/essential Linux files that no *NIX system lives without so we also make our assumptions that certain things are just understood by Linux users. It's definitely a bit of a grey area. Cleaning up the text a bit would not necessarily be a bad thing either (not to be confused with excessive hand-holding but have it be more correct as there are additional reasons beyond that I have no name prompt although that's probably the most visible of reasons). Gerard -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
On 29/11/2011 11:21, David Scott Williams wrote: BTW-- now that I have done what the book told me to do, CC=gcc /usr/bin/perl scripts/test-installation.pl /sources/glibc-build/ Your new glibc installation seems to be ok. make[1]: Leaving directory `/sources/glibc-2.14.1' root:/sources/glibc-build# :) Joy. Awesome, glad you got it working. In the end no harm done and tons learned, which is exactly what we aim to provide with the LFS project. In the end all these seemingly frustrating issues just helped you accomplish the larger goal. And it helps validate that the book's instructions remain valid and correct which is always a good peer-review in a way. Gerard -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
On Tue, Nov 29, 2011 at 10:49:56AM -0600, David Scott Williams wrote: Here is the section I did not do. I did not realize that it was mandatory (I thought it was cosmetic ;)) == To remove the “I have no name!” prompt, start a new shell. Since a full Glibc was installed in Chapter 5 and the / etc/passwd and /etc/group files have been created, user name and group name resolution will now work: exec /tools/bin/bash --login +h = Technically, it *is* cosmetic - I don't do it within my own chroot script. Anyway, you've found the reason for your perl error. But, for glibc (and many other packages) it is worth remarking that 'make check' creates files along the way (its dependencies) which prevent the tests that have run from rerunning when you next invoke it. And *please* don't top post. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.0 release, Building on Debian 5 host build system...
On Tue, Nov 29, 2011 at 11:10:49AM -0600, Gerard Beekmans wrote: In David's defense I can understand his point too. If all the book says is to remove the I have no name! prompt then I can see where that sounds like it's not all that significant. In our defense, passwd and group files are core/essential Linux files that no *NIX system lives without so we also make our assumptions that certain things are just understood by Linux users. It's definitely a bit of a grey area. Cleaning up the text a bit would not necessarily be a bad thing either (not to be confused with excessive hand-holding but have it be more correct as there are additional reasons beyond that I have no name prompt although that's probably the most visible of reasons). Gerard To clarify my response just now - starting a new shell is optional, clearly the passwd and group files are required. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] bind problems
On Tue, Nov 29, 2011 at 4:10 PM, Danny Vukobratovich dvukobratov...@marianinc.com wrote: loading configuration from ‘/etc/bind/named.conf’ /etc/bind/rndc.key:1: key ‘rndc-key’: already exists previous definition: /etc/bind/rndc.key:1 It seems like rndc.key is included twice? Here is my configuration from my named.conf file: Include “/etc/bind/named.conf.options”; Include “/etc/bind/named.conf.local”; Include “/etc/bind/named.conf.default-zones”; Perhaps rndc.key is included by one of the above config files too? Include “/etc/bind/rndc.key”; Cheers, Matijn -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] bind problems
On Tue, 29 Nov 2011 10:10:53 -0500 Danny Vukobratovich dvukobratov...@marianinc.com wrote: /etc/bind/rndc.key:1: key 'rndc-key': already exists previous definition: /etc/bind/rndc.key:1 Here is my configuration from my named.conf file: It looks like the problem is in /etc/bind/rndc.key. Can we see that? (obscure the secret). Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
