On 08/05/2010 06:12 AM, J. Greenlees wrote:
> Um, my comment / question was about making the livecd multi lib.
> a pure64 livecd would be useless on 32 bit hardware.
>
> a 32 bit cd would mean the shortcut bootstrapping would be needed for a
> 64 bit build.
>
> and one multi lib cd is easier than one of each.
>
"To multi-lib or not to multi-lib" seems, IMO, to be way beyond the
purpose of the livecd not to mention the state of the current
discussion. This is LFS and not CLFS. Currently, LFS is non-multi-lib
it's either pure 32 or 64, which ever the builder wants to do. There are
two concepts.
First, the livecd project became dormant--died (?)--because of the
difficulty in maintaining into what it had morphed and the small
numbers--2 (?)--of those who were willing to work at maintaining it.
Therefore, I think the goal is to keep it as simple as possible while
meeting the purpose of it.
The second concept is the purpose and intended function of the livecd.
As it currently stands, I believe this purpose is to automatically build
a {,B}LFS system and create an image that the user can burn and then
from which to boot. The cd then becomes a host system so that the user
has all the tools to build LFS through Chapter 9 of the book.
The resulting image would be either 32 or 64 bit depending on the
hardware. The user can then either use LFS or CLFS depending on desires.
If someone wanted a multi-lib livecd, that person could remaster what
now exists or whatever is produced as the project becomes more current.
I agree with Andy. I don't even really see the need for an X
environment. The only thing that sways me to X right now is the problems
with links, gpm and utf-8. I know nothing about the availability of
other text based browsers, I just know I made that choice from what's
available in BLFS. I think that the livecd needs to be as "light weight"
as possible. OK, let's put in an X environment. There's really no *need*
for any connectivity. The livecd provides all the packges necessary to
build LFS and a copy of "the book." The only need for connectivity is if
the user were building against SVN and it changed. I think it is
*convenient* to have the other "bells and whistles." I don't think it's
necessary to put all of that in the livecd.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
