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

Re: dac960 devices on boot-floppies



are there any alternatives to the initrd approach? i'm fairly certain redhat
uses initrd for it's install disks (as well as the normal booting, ick), so
investigating that might be of some interest.

building rescue/drivers disks can be a real pain, especially whe you don't
have a current installation of the distribution to build it on.

might providing a simpler means to replace kernel/drivers on the
rescue/drivers disks without rebuilding the entire boot-floppies be an avenue
we can persue? i think joe debian user who has this kind of specialized
hardware would be familiar with building kernel/kernel packages, but i don't
think they should necessarily have to be involved with boot-floppies just to
replace the kernel.

just my two cents,

On Thu, Nov 11, 1999 at 01:35:15AM -0500, Adam Di Carlo wrote:
> nf <nf@marginal.net> writes:
> 
> > 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)
> 
> Yes -- installation via PCMICA floppy for instance.
> 
> It requires initrd, which is *not* going to be a feature for potato.
> 
> Again, the only solution is a custom rescue/drivers disks for your HBA.
--
nathan a ferch
nf@marginal.net
"Are you all right?" -Venkman


Reply to: