Well, in the future I'll probably end up doing the installer as a
statically linked object; it almost every case, the very first
thing the installer does is set up a working area on the install
media, and I can put libc's and suchlike there. Given the option
between that and a stripped down libc for install disks (I still
have bad dreams about libc-lite), static linking becomes A Good
Thing.
The install floppy really only contains a kernel, libc, and
loadandgo; the rest of the scaffolding on the install floppy is for
a device directory (with 2.2, I can kiss *that* Unix kludge goodbye
and use devfs like G-d Himself Intended), various lilo debris (if
devfs works properly, I can discard lilo in favor of SYSLINUX and
use a MS-DOS format filesystem to boot from), and the terminfo
scaffolding for the ncurses that's statically linked into loadandgo.
If I was ambitious, I could even write a little Windows program that
let me configure specific boot disks, but that's getting Wayyyyyy
off-topic for the Linux kernel mailing list.
____
david parsons \bi/ A linux kernel that only supports MS-DOS and ISO9660
\/ filesystems? Oh, you betcha!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/