Re: Linux not adhering to BIOS Drive boot order?

From: Brian Gerst <bgerst@didntduck.org>
To: Venkatesh Ramamurthy <Venkateshr@ami.com>
Cc: "'David Woodhouse'" <dwmw2@infradead.org>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux not adhering to BIOS Drive boot order?
Date: Tue, 16 Jan 2001 12:04:57 -0500	[thread overview]
Message-ID: <3A647F39.EC62BB81@didntduck.org> (raw)
In-Reply-To: <1355693A51C0D211B55A00105ACCFE64E95190@ATL_MS1>

Venkatesh Ramamurthy wrote:
> 
> > When the cards are of different make the order is solely dependent on
> > the order that the drivers are initialized in the kernel.  If you have
> > modules enabled, only build the driver for your root device into the
> > kernel image and have the other modular.  This lets you control the
> > initialization order to your liking.
>         [Venkatesh Ramamurthy]  I think there should be a better way to
> handle this , compiling is one of the options, but an end-user should not
> think of compiling. The end user needs to put an another card and connect
> drives and get his system up and running. He should not think of compiling
> the drivers, if it is already part of the kernel / initrd to get his system
> running.

Why does the end-user have to compile the kernel?  Most distributions
provide a kernel with no SCSI drivers in it, but use an initrd to get
the root SCSI driver in (man mkinitrd on any Redhat box).  Just
distribute all SCSI drivers as modules and you won't have any problems.

--

				Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/