From: Phillip Susi <psusi@cfl.rr.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Seewer Philippe <philippe.seewer@bfh.ch>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: disk geometry via sysfs
Date: Wed, 15 Feb 2006 10:20:58 -0500 [thread overview]
Message-ID: <43F346DA.4020404@cfl.rr.com> (raw)
In-Reply-To: <1140012392.14831.13.camel@localhost.localdomain>
Alan Cox wrote:
> On Mer, 2006-02-15 at 10:01 +0100, Seewer Philippe wrote:
>
>> This would mean dropping the HDIO_GETGEO ioctl completely and force
>> applications such as fdisk/sfdisk and even dosemu to determine disk
>> geometry for themselves. Which I think actually would be the most
>> correct approach.
>>
>
> In the IDE case the drive geometry has meaning in certain cases,
> specifically the C/H/S drive addressing case with old old drives.
I thought that C/H/S addressing was purely a function of int 13, not the
hardware interface? If it is a function of some older hardware
interfaces, then we are still talking about two different, and likely
incompatible geometries: the one the disk reports, and the one the bios
reports. The values in the MBR must be the values the bios reports.
next prev parent reply other threads:[~2006-02-15 15:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 13:06 RFC: disk geometry via sysfs Seewer Philippe
2006-02-13 9:56 ` Bartlomiej Zolnierkiewicz
2006-02-15 7:57 ` Seewer Philippe
2006-02-13 16:32 ` Phillip Susi
2006-02-13 19:02 ` Seewer Philippe
2006-02-13 19:22 ` linux-os (Dick Johnson)
2006-02-13 19:36 ` Phillip Susi
2006-02-14 16:35 ` Seewer Philippe
2006-02-13 19:34 ` Phillip Susi
[not found] ` <43F206E7.70601@bfh.ch>
2006-02-14 18:19 ` Phillip Susi
2006-02-15 8:39 ` Seewer Philippe
2006-02-15 8:51 ` Bartlomiej Zolnierkiewicz
2006-02-15 9:01 ` Seewer Philippe
2006-02-15 14:06 ` Alan Cox
2006-02-15 14:11 ` Seewer Philippe
2006-02-15 15:15 ` Alan Cox
2006-02-15 15:29 ` Phillip Susi
2006-02-16 8:12 ` Seewer Philippe
2006-02-16 15:36 ` Phillip Susi
2006-02-16 15:41 ` Seewer Philippe
2006-02-16 16:15 ` Phillip Susi
2006-02-15 15:20 ` Phillip Susi [this message]
2006-02-15 16:06 ` Alan Cox
2006-02-15 16:20 ` Phillip Susi
2006-02-15 17:32 ` Alan Cox
2006-02-15 18:43 ` Phillip Susi
2006-02-15 19:23 ` linux-os (Dick Johnson)
2006-02-15 20:54 ` Phillip Susi
2006-02-15 21:41 ` linux-os (Dick Johnson)
2006-02-15 22:43 ` Phillip Susi
2006-02-16 12:33 ` linux-os (Dick Johnson)
2006-02-16 15:26 ` Phillip Susi
2006-02-16 16:15 ` Seewer Philippe
2006-02-16 17:01 ` Phillip Susi
2006-02-16 16:39 ` linux-os (Dick Johnson)
2006-02-16 17:09 ` Phillip Susi
2006-02-16 19:01 ` linux-os (Dick Johnson)
2006-02-16 19:55 ` Phillip Susi
2006-02-16 8:18 ` Seewer Philippe
2006-02-16 18:14 ` Matt Domsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F346DA.4020404@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.seewer@bfh.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.