Okay, I'm on the job. Since I've been playing with the systemd branch I need to compile vanilla 32-bit and 64-bit releases, which I'm currently doing using jhalfs. I just realised I chose the development branch without much consideration, when the stable version my be more appropriate. If only for the convenience of release cycle guidelines. I focus on making a bootable CD and USB image for now using the vanilla-SVN build and replace it with a release build later if it's more appropriate. i686 and x86_64 on the same image, like Arch, is a good idea isn't it? It becomes complicated to build twice if things such as X are expected to be included as standard though, and space becomes tight having to have two builds of everything on the same disk. The Arch disk splits the filesystem off into SquashFS (or similar) files for i686, x86_64, and architecture independent files. This could also allow for additional archives (such as BLFS software) to extend the bootdisk, much like Puppy. To be honest, I'm not prepared to commit to maintaining non-essential software such as X for now. My ambition is a terminal environment with the tools to build LFS, SSH, screen, jhalfs, and build the book. Any bells and whistles can be added by anyone through some sort of SquashFS or UnionFS shenanigans (or perhaps BLFS using jhalfs). If users feel more comfortable using a GUI then they should be encouraged to use a virtual machine or SSH into a dedicated box.
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
