<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hi William<div><br></div><div>I think I follow what you are saying but wouldn't this be better left to CBLFS?</div><div><br></div><div>Like the original LFS, the base system is only designed to create a minimal system</div><div>which then can be extended as the user sees fit. I personally like the idea of giving the user</div><div>a good base from which to start but then leave the decision of net access and compressed</div><div>modules to be something the user can decide on after they have a working system.</div><div><br></div><div>For example, I have converted my CLFS Pure 64 to systemd for init and would also like to see it </div><div>adopted but the tried and true SysV just works so we let the user decide after they have completed</div><div>the base system.</div><div><br></div><div>Regards</div><div>grail<br><br><div><div id="SkyDrivePlaceholder"></div>> To: clfs-dev@lists.cross-lfs.org<br>> From: berzerkula@cox.net<br>> Date: Mon, 13 Aug 2012 15:53:56 -0500<br>> Subject: [Clfs-dev] Boot Method rather than chroot steps of the Cross-LFS book<br>> <br>> Hello everybody,<br>> <br>> <br>> Been working on the boot method of the book, but mostly with powerpc <br>> for now.<br>> <br>> I've come across some issues we need to discuss.<br>> <br>> When we boot, it is a very minimal system. Really, only the extra <br>> program installed is VIM.<br>> We tell the user to build a minimal kernel to mount the rootfs and <br>> that is about it, and to not include audio and all that jazz. That is <br>> fine.<br>> <br>> Although, I think the user may need network access. For example, <br>> maybe they want to build the system by running an openssh daemon in <br>> the booted temp system. That is fine. Since we install minimal boot <br>> scripts, the kernel can use ip autolevel configuration via dhcp, <br>> rarp, or some other method or the user can pass the kernel paramaters <br>> of the boot line to configure the network, and not even use <br>> bootscripts, don't need to install iproute2 in the temp system before <br>> booting. I think that may be the best way and we would not need to <br>> install ethernet configuration programs for the boot method.<br>> <br>> Next up, we discourage the use of modules for the boot method, but if <br>> someone does and they decide to compress them for whatever reason, <br>> kmod will not load them as xz and zlib aren't enabled by default. We <br>> can enable those options for kmod during the boot method section and <br>> that will fix that. I know we want to keep the boot method minimal, <br>> and I want to know what the community has to say about the above <br>> issues I am raising.<br>> <br>> Sincerely,<br>> <br>> William Harrington<br>> _______________________________________________<br>> Clfs-dev mailing list<br>> Clfs-dev@lists.cross-lfs.org<br>> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org<br></div></div> </div></body>
</html>