![]() | |||||||||||||
Messages in this thread |
On Tue, Jan 15, 2002 at 07:33:17PM -0500, David Garfield wrote: > > Except that what you have just proposed requires that you "build in > _all possible_ SCSI PCI drivers" as modules in the initramfs. Little > gain, except that some things won't be retained. Little gain? You don't waste kernel space for SCSI drivers that are not being used. > Further, I don't thing I would expect a system with a changed SCSI PCI > controller to boot on a kernel specifically built for the previous > controller. I don't think I would even want it to boot. Better I > think to get out a rescue disk of some sort, boot from that, > reconfigure a built kernel for the new hardware (in the new case, > simply reconstructing the initramfs), and reboot from that. Each to their own. > What I am worried about is not *allowing* user mode code in the > initramfs, but *requiring* it. Why? What are you afraid of? :) If you want the boot process to be just like it is today, and you don't require any network boot stuff, I think no userspace code will be needed. But I can't guess the future... greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:23 [W:0.702 / U:0.030 seconds] ©2003-2008 Jasper Spaans | |||||||||||||