It seems now that LFS is ready to go into the world that CLFS has been in for a while. There seems to be a lot of discussions, that are going to be a duplication of work, and no one from LFS reaching out to the CLFS team for input on what issues we have seen and what you will cross. It was proposed a while back to make CLFS the LFS 7, which got rejected, but someone else brings it up something similar, now it's a great idea let's get it done.
As far as udev rules, CLFS has made the move to use the rules that have been included for over a year with no issues at all. The biggest issue when it comes to a 64 bit build is x86 bootloaders, grub still doesn't play nice with 64 bit. The bootloader can be 32 bit, but building it is the issue. There are other choices out there that need to be looked at for bootloaders. Using 64 bit is not mainstream yet, why should LFS go after something that isn't going to be mainstream for at least 2 years or more. Yes we do these builds in CLFS, because we have figured out the way how to do them, but are they usuable, no. There is a lot of work left to get 64 bit working across the board. 64 bit is not ready for primetime, the only safe solution right now is multilib. Even the recommendation from a lot of the experts is to have a 64 bit kernel and tool chain, but the apps as 32 bit. David Miller constantly gets on his soapbox about this on the Sparc Realm of linux. The http://positionrelative.blogspot.com/2008/07/64-bit-linux-desktop.html http://www.osnews.com/story/5447/Running_64-bit_Linux_on_a_G5 http://forums.whirlpool.net.au/forum-replies-archive.cfm/1032065.html If LFS wants to support multiple architectures, I would recommend only supporting x86, x86_64, and powerpc. The others are just too complicated. I also hope anything from what people have done towards the LFS's 7.0 goal, that the appropriate credit is giving. Jim Gifford Lead Developer CLFS [EMAIL PROTECTED] -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
