From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Chris McDermott <lcm@us.ibm.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [dm-devel] Re: [PATCH] User-configurable HDIO_GETGEO for dm volumes
Date: Thu, 23 Feb 2006 10:16:24 -0800 [thread overview]
Message-ID: <1140718584.10148.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20060223135639.GK31641@agk.surrey.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Thu, 2006-02-23 at 13:56 +0000, Alasdair G Kergon wrote:
> My copy of the sd(4) man page says of that ioctl:
>
> The information returned in the parameter is the disk
> geometry of the drive as understood by DOS! This geometry is not
> the physical geometry of the drive. It is used when constructing the
> drive's partition table, however, and is needed for convenient
> operation of fdisk(1), efdisk(1), and lilo(1). If the geometry
> information is not available, zero will be returned for all of the
> parameters.
>
> Is there a preferred alternative specification?
Hm... in light of that, I'll acquiesce that 0/0/0 is fine by me, and no
other behavior is necessary.
--D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-02-23 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 20:22 Darrick J. Wong
2006-02-16 3:05 ` Andrew Morton
2006-02-17 1:31 ` Darrick J. Wong
2006-02-17 1:49 ` Andrew Morton
2006-02-17 15:16 ` Alasdair G Kergon
2006-02-17 15:21 ` [dm-devel] " Alasdair G Kergon
2006-02-18 0:59 ` Darrick J. Wong
2006-02-19 1:25 ` [dm-devel] " Alasdair G Kergon
2006-02-22 22:32 ` Alasdair G Kergon
2006-02-23 0:46 ` Darrick J. Wong
2006-02-23 13:56 ` Alasdair G Kergon
2006-02-23 18:16 ` Darrick J. Wong [this message]
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=1140718584.10148.2.camel@localhost.localdomain \
--to=djwong@us.ibm.com \
--cc=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=dm-devel@redhat.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®