On 7/24/05, Jeremy Huntwork <[EMAIL PROTECTED]> wrote: > Alexander E. Patrakov wrote:
<snip> > > it is hard to do so with the unknown future RedHat extensions in mind, > > but it either has to be done or too-new hosts should be blacklisted > > (thus making LFS live CD the only officially supported host - but that's > > against the spirit of LFS). > > To some extent, I agree with your suggestion here, Alexander. Since FC > came out, there's been several run-ins with LFS. I think, to a large > extent, simply because FC is too bleeding-edge. And though LFS trunk > tries to stay up-to-speed, it takes longer for us to successfully > incorporate new technology than it does for a project like FC to produce > and release (for several reasons). So, at the least, I think it might > be a good idea to discourage using the latest version of FC somewhere in > the book. Another option is to apply the FC2\3 workaround permanently - change the book instructions to download, compile and use e2fsprogs from LFS to create the LFS partition always, and never use the host tools. Although that would work for all e2fs problems, I can forsee other FC related tool issues, so might not be as useful as it could be. Yet Another Option: Have a "Host Quirks" page - document known Host based issues and suggested workarounds - we could maintain that as an online only page referred to in the book (Check the <host> page for known issues with your Host system before building) - this would be fairly easy to maintain, since the number of quirks is not high, and we could test and update relatively easily when a new host OS is released. -- - Steve Crosby -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
