[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dac960 devices on boot-floppies



the kernel is going to grow to a point where having scsi/ide/whatever drivers
in the kernel isn't going to be feasible, but at this stage of the game i
think it's much less of a problem to add a 40k driver to the rescue kernel.

one disadvantage of having the dac960 driver as a module and loading it later
is that you would need more than just the rescue disk to boot the system
should the kerne become corrupted.

are there any other situations like this that would require modules to be
loaded? (nfsroot comes to mind, but i'm not too familiar with that)

On Wed, Nov 10, 1999 at 09:43:18PM -0800, George Bonser wrote:
> An acceptable alternative would be to provide dac960 support as a module.
> Allow the user to load modules BEFORE initializing a hard disk so the
> driver can be loaded. Allow the user to manually specify an install target
> if none are autodetected.
> 
> In this way I could load DAC960 support on the install (loading the driver
> floppy and selecting the dac960 module), then select partition a hard
> disk. When the system returns that it did not find any disk, it should ask
> if I want to specify a device. If it finds that device, it continues as
> normal.
> 
> The part I hate is that debian tries to be smarter than I am and if it
> does not see the disk, it assumes that it can not possibly exist so it
> never gives me a chance to enter a device manually.
> 
> 
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
nathan a ferch
nf@marginal.net
"... and then I opened the door again but it was gone.  There was nothing there." -Dana


Reply to: