[7778] in linux-scsi channel archive
Clarification (was: Re: Convincing the aic7xxx driver that it's scsi1)
daemon@ATHENA.MIT.EDU (ken@seefried.com)
Fri Dec 31 19:12:03 1999
To: linux-scsi@vger.rutgers.edu
From: ken@seefried.com
Date: Fri, 31 Dec 1999 19:04:27 -0500
Message-ID: <OF27241738.BA01F2A4-ON05256859.00006841@seefried.com>
MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<P>Perhaps a bit of clarification is in order.</P><P>I understand that I ca=
n manipulate the order of module loads once I've got a booting a machine. &=
nbsp;The point is that loading Linux (Redhat in this case) in the configura=
tion in question results in a machine that will not boot, due to the device=
names are not the same as when the box was installed. Therefore, I c=
an't make new kernels, edit files, etc. </P><P>I suppose I should loo=
k at a stand-alone boot floppy or some such.</P><P>I also have found a few =
places where changing the source code could produce the desired result, alt=
hough on this machine changing drivers/scsi/hosts.c results in a kernel tha=
t panics. I think that this also precludes building a non-modules ver=
sion of the kernel.</P><P>The point is that there should be a simple way fo=
r the average joe to specify these sorts of details about the boot proceedu=
re without resulting to editing kernel sources and/or having a second machi=
ne to build kernels for a non-working machine. I suppose what I *real=
ly* want is a way to specify the controller order from the LILO prompt, or =
at least during the install.</P><P>- Ken</P><P></P>=
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
