On Sat, 20 Oct 2007, Scott Long wrote: > > Although I agree, it would be nice if you could more easily load > > vendor drivers.. (ie if the module overrode the kernel code) > > 1. Modifying the install disk is not trivial to most people, > especially ones who just want to install the damn OS and use it, not > hack it. Pfft, weaklings! :) > 2. Modifying the install disk doesn't do a damn thing to make the > driver work after the install is done and the computer is rebooted. > Sure, you can drop a new 3ware driver onto the install disk and > install to your new 3ware-enabled computer just fine. But then you > reboot, and the stock GENERIC kernel has no idea how to talk to that > device, and the driver that you dropped onto the CD is now no where > to be found, leaving your fresh install stuck at the mountroot > prompt. \o/ > > =-) Yeah I know, there needs to be some work on it that's for sure! I would be interesting in doing the sysinstall work, although unless the kernel can cope with (and prefer) modules then there isn't a huge point IMO. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:19 UTC