Alan Cox wrote:
The tools need to know the C/H/S drive addressing data for old drives
because it is used to determine partition tables. That doesn't have to
be GETGEO but it does need to exist somewhere.
Currently GETGEO very often does not report the same values of the bios
doesn't it? For some disks it's completely made up, and for others it
is the value returned by the drive itself, which often differs from the
bios values. If this is the case, and it is the bios values that must
be stored in the MBR, then it makes little sense to have GETGEO seeing
as how it often provides incorrect information.
Wouldn't it be better then, to clean up GETGEO everywhere so that unless
it has correct values from the bios, it should just fail? And leave it
up to fdisk and friends to inform the user of that failure, choose
default values, and allow the user to override those defaults should
they need to?
The only time they would even have to worry about it is if they are
installing linux on a blank disk, and then want to install windows to
dual boot with it. In that case they might have to correct the CHS
values in the MBR to match the values the bios provides.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
