Alexander E. Patrakov wrote:
The next pre-release LiveCD will use linux-2.6.16-rc4 unconditionally, unless Linus releases 2.6.16 sooner.
Jumping the gun a bit, aren't we? You haven't waited to hear my reply to your question concerning this. Please don't issue blanket statements like this without waiting to hear my thoughts on the matter.
Alexander, I understand your eager desire and enthusiasm with respect to broadening the support and functionality of the LiveCD. However, you seem to forget that the main purpose of the CD is to provide a proper host for building LFS.
If LFS is broken for a particular user in the way it currently handles devices, or the version of the kernel doesn't work well with their hardware, how is providing them a fixed LiveCD the answer to their problem? Sure the LiveCD will work, but when they 'do the right thing' and FBBG, they'll end up encountering those same problems we sidestepped when they go to boot into their new LFS system, and this without a clue.
If the LiveCD fails to work with their hardware, for a known reason (ie, udev or the kernel) there's a clue right away that the current version of LFS won't work for them. You've said that the udev setup in LFS is broken - so work to fix it. Help on the lists - provide patches. And don't give up. Often, I get the feeling that when certain of your suggestions concerning LFS go ignored, it's either because the devs are busy with other things, or they're having trouble parsing all of the details you provide. ;)
Bottom line, the LiveCD will follow LFS on this. So if you want the changes to happen, get them into LFS.
> This probably
requires returning to shell-based init.
I doubt it *requires* it. In any case, though development on them is slow, the reason for switching back to a C init remains: it works on all architectures. We won't be switching inits again unless we absolutely have to.
-- JH -- http://linuxfromscratch.org/mailman/listinfo/livecd FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
