>> Since there is nothing in Linux that ensures that devices are
>> numbered according to the _actual_ BIOSes order, any tool based on
>> such an assumption is essentially broken.
>> LILO works most of the time because most of users only have IDE
>> only or IDE and a single SCSI adapter.
> Hmmm... not mentioned in the man page. Also, we're straying from
> the charter of the kernel newsgroup a bit. It would be interesting
> to have a parameter known to lilo (and the kernel?) that could be
> used to override the device order if you are planning to, say,
> reorder your SCSI drives, including your boot drive.
I'm not sure whether this will help, but my $0.02's worth here is my
understanding of the steps involved in booting up an IBM PC clone...
1. Power arrives at PC.
2. BIOS performs various tests, then recognises drives attached to
the system in whatever order it chooses.
3. BIOS uses its internal code to select a drive to be the boot
drive. This may have been set as one of the ROM BIOS options.
4. BIOS loads head 0, track 0, sector 1 into memory and runs whatever
it finds there. This is presumably LILO.
If this is the case, then all that's required is for LILO to know
which disk it was loaded off, and label that disk as being the boot
disk...
Since this is so simple, I'm obviously missing something, so please
tell me what - I hate it when I do...
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu