On Fri, 6 Apr 2001 [EMAIL PROTECTED] wrote:
> No. A new patch would be required, or the root archive would
> need to be in gzip instead of bzip2 format; but much/most of
> the root stuff might be able to be moved into a root2 package
> that is bzipped...
(Clears throat, steps forward)
ACTUALLY, David and I had a long discussion in regards to a bunch of
stuff, and this is one of the things that came up along the way. In the
course of stuff, I went and puzzled through the 2.9.8 linuxrc script to
try and find PRECISELY what was done to get to the point where the first
package was loaded, and I came up with the following list. Please note
that this is cut & pasted from an outline for a project idea that I've
been semi-working on. The project would, in the end, allow for move to a
boot floppy with CD-ROM/HDD packages, as well as a move to glibc 2.1.x and
easier upgradeability of the various core parts of a system.
1. Busybox compiled with cat, ln, tar(if we can get scripts working to use
it correctly for replacing ctar), makedevs, mknod, mkdir, mount, and
gunzip ONLY.
2. sed.
3. ash.
4. ctar - assuming we can't get a functioning script for BB tar.
5. Required libs, unless they're statically linked to the binaries - not
recommended.
6. Possibly POSIXness scripts.
This is based on the boot sequence in initrd archive, to the point of
loading packages, as follows:
1. Creates links to busybox for ln, cat, and mkdir.
2. Creates the base directory structure with the above.
3. Creates busybox and POSIXness links.
4. Makes the dev files
5. chmod's /var/lock and /tmp, mounts proc, updates mtab
6. Checks for boot= and makes the mount dir, then mounts the boot device
specified.
7. Begins to install packages.
Please, someone who's monkeyed with the default 2.9.8 Linuxrc script,
doublecheck me on that.
Thought here is to get a bootstrap initrd archive up and running first,
then use what it contains to load System packages, then addon packages,
from a significantly larger medium than a floppy disk. In this case, if
we're using bzip2, we can still load off the floppy disk, and just add in
bzip2 and libbz2 to the boot.lrp package, and away we go.
I THINK I can get a default boot.lrp together in the next few days, but
I'm weak on scripting, and this may take a bit of scripting skill. If
anyone can make a couple of modifications for me to Linuxrc, please offer.
Overall, I'd prefer not, since this might be the kick I need to figure out
shell scripts and the like, but if you like the idea and want it done in
less than a week or two, then modify linuxrc to load a set list of System
packages that are constant-named. I was thinking lib, modules, root, etc,
and local could be static packages, whereas everything that ISN'T a
system-required package such as dnscache, sshd, weblet, etc. could remain
configured via the "LRP=" parameter - or whatever happens to be used by a
given distro.
Understand also that the intent of the above is to use a BB that ONLY does
what's absolutely necessary in the scripts to load the first packages. The
original intent was to have a BB in the root.lrp that would overwrite the
bootstrap BB, so as to provide full functionality. This would be done so
that ALL the configureable files - and even files such as the portsentry
files that you've built up over time that you want to keep so that you're
blocking the same idjits - can be stored on a single, base-format 1.44M
floppy. If this isn't feasible, or the savings don't necessitate the
effort, then a full BB in the boot package would work just fine.
Thoughts? Questions? Insults? =)
--
George Metz
Commercial Routing Engineer
[EMAIL PROTECTED]
"We know what deterrence was with 'mutually assured destruction' during
the Cold War. But what is deterrence in information warfare?" -- Brigadier
General Douglas Richardson, USAF, Commander - Space Warfare Center
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
