> Imagine a boot disk where ash, busybox, or libc could be upgraded with
> very little effort.... just copy in a new one and run.
I've been wanting to do this for ages (just not enough time), and is what I
mean when I say I want to keep the core system flexible enough to run with
various versions of libc.
IMHO, root.lrp should be renamed to something like bootstrap.lrp (or
similar...please excuse the 9.3 name), and contain only the absolute minimum
required for unpacking the rest of the system. Exactly *what* the bootstrap
system looks like is still up in the air. It could be lua code, busybox sh
compiled against uLibc with a few helper apps, a small Forth program, or
even custom written C code. Whatever it winds up looking like, there's a
big premium on it being as small as possible. <grin>
To still enable a single-disk system, which is obviously quite limited on
space, there are two options:
1) The new bootstrap functions are kept small enough to be added to the
existing LRP files. With things like UPX kernel compression, and some other
space-saving measures, this isn't entirely out of the question.
2) Re-use the bootstrap code in the running LRP system. For instance, if
the bootstrap package had a tar, gzip, and other standard utilities (or
libraries), these could be re-used by a floppy version of root.lrp. Folks
with more space available could still install a "full" system, using none of
the files from the bootstrap package.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
