[Clfs-dev] Boot Method rather than chroot steps of the Cross-LFS book

[Grail Dane]

Hi William
I think I follow what you are saying but wouldn't this be better left to CBLFS?
Like the original LFS, the base system is only designed to create a minimal systemwhich then can be extended as the user sees fit.  I personally like the idea of giving the usera good base from which to start but then leave the decision of net access and compressedmodules to be something the user can decide on after they have a working system.
For example, I have converted my CLFS Pure 64 to systemd for init and would also like to see it adopted but the tried and true SysV just works so we let the user decide after they have completedthe base system.
Regardsgrail

> To: clfs-dev at lists.cross-lfs.org
> From: berzerkula at cox.net
> Date: Mon, 13 Aug 2012 15:53:56 -0500
> Subject: [Clfs-dev] Boot Method rather than chroot steps of the Cross-LFS	book
> 
> Hello everybody,
> 
> 
> Been working on the boot method of the book, but mostly with powerpc  
> for now.
> 
> I've come across some issues we need to discuss.
> 
> When we boot, it is a very minimal system. Really, only the extra  
> program installed is VIM.
> We tell the user to build a minimal kernel to mount the rootfs and  
> that is about it, and to not include audio and all that jazz. That is  
> fine.
> 
> Although, I think the user may need network access. For example,  
> maybe they want to build the system by running an openssh daemon in  
> the booted temp system. That is fine. Since we install minimal boot  
> scripts, the kernel can use ip autolevel configuration via dhcp,  
> rarp, or some other method or the user can pass the kernel paramaters  
> of the boot line to configure the network, and not even use  
> bootscripts, don't need to install iproute2 in the temp system before  
> booting. I think that may be the best way and we would not need to  
> install ethernet configuration programs for the boot method.
> 
> Next up, we discourage the use of modules for the boot method, but if  
> someone does and they decide to compress them for whatever reason,  
> kmod will not load them as xz and zlib aren't enabled by default. We  
> can enable those options for kmod during the boot method section and  
> that will fix that. I know we want to keep the boot method minimal,  
> and I want to know what the community has to say about the above  
> issues I am raising.
> 
> Sincerely,
> 
> William Harrington
> _______________________________________________
> Clfs-dev mailing list
> Clfs-dev at lists.cross-lfs.org
> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clfs.org/pipermail/clfs-dev-clfs.org/attachments/20120814/d9e4cdb5/attachment-0001.htm>