> You have libc5 versions of dump and restore handy as part of the > add-ons. I'm wondering if you might consider making some other Only if they are directly sensible in the context of recovery. > binaries available. Things like netstat, traceroute, lsmod and so on. I would point you to LRP or Trinux. I definitely won't be spending time putting up libc5 versions of applications. By the way, lsmod is useless given that "cat /proc/modules" gives you the exact same output. > Also, why don't you put /sbin and /usr/sbin into the default path? > Very handy when chroot'ing :) OK, will do. Note, this doesn't even require rebuilding to customize- that is set in the rc.custom.gz file on the main floppy filesystem. > WRT drivers loaded into the default kernel... I know this issue has > been hacked to death before in the mailing list, but I'm wondering of > the wisdom of doing it that way. It's *so* much easier to pass Only the network drivers are in the main kernel, the scsi drivers are not. One issue is that you can't use it for nfsroot without them in there. However, a competing issue is that if you want to use the kernel copied to a hard drive on a scsi system, those drivers have to be compiled in. Unless I go to an initrd/linuxrc setup, which is still on the table. However, ALL of this discussion is overshadowed by the fact that the way it is now is the most space efficient, and I doubt changing it will help enough users to offset the loss in space... > parameters to modules via insmod than to pass them on the lilo boot > line. The rc scripts could just go through and attempt to load them, > if the devices aren't found then they don't get loaded. -Tom
