lkml.org 
[lkml]   [2001]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Linux not adhering to BIOS Drive boot order?
Date
Guys,

> And this is a problem that has plagues all PC operating systems, but has
never
> been a problem on the Macintosh. Why? Because the Mac was designed to
handle
> this problem, but the PC never was.

Quite true on this point.

> The Mac never enumerates its devices like the PC does (no C: D: etc, no
> /dev/sda, /dev/sdb, or anything like that). It also remembers the boot
device
> in its EEPROM (the Startup Disk Control Panel handles this).

For ATA drives the bios handles this.

> The only way to solve this problem is the DESIGN IT INTO THE OS! Someone
needs
> to stand up and say, "This is a problem, and I'm going to fix it." There
needs
> to be a "device mount order database" or some kind, and all the disk
drivers
> need to access that database to determine where to put the devices it
finds.

NO! What needs to happen is:
1) the person who installs a second scsi card should read the manual BEFORE
installing it so they know how to disable the boot features if they aren't
needed,

or

2) install only one bootable scsi card, period.

Anything else is a useless kludge that will come back and bite us in the
ass.


> The only problem is BIOS boot. That information is, I believe, stored in
the
> ESCD, but I don't know if it's reliable enough and complete enough to be
usable
> by Linux.

It seems to work well enough.

Matthew D. Pitts
mpitts@suite224.net



-
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/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.064 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site