From: Andre Hedrick <andre@linux-ide.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Allan Duncan <allan.d@bigpond.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.40 etc and IDE HDisk geometry
Date: Sat, 5 Oct 2002 12:30:18 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10210051228080.21833-100000@master.linux-ide.org> (raw)
In-Reply-To: <20021004215049.GA20192@win.tue.nl>
Andries,
If CHS is truly meaningless (less drives smaller than 8.4GB) why can we
not specify forced LBA geometry reporting? Also any drive supporting
48-bit feature sets are forbidden to use CHS.
Just a comment, not bait for a lesson or lecture :-)
On Fri, 4 Oct 2002, Andries Brouwer wrote:
> On Fri, Oct 04, 2002 at 11:47:16PM +1000, Allan Duncan wrote:
>
> > Question is - what is determining that initial value that becomes the "logical"
> > CHS, and does it matter?
>
> No, it does not matter at all.
> CHS are meaningless numbers not used anywhere anymore in Linux.
>
> If you want to influence what geometry *fdisk will use, give it
> the appropriate options or commands. No need to go via the kernel.
> But only in rare cases is it necessary to worry about geometry.
>
> Andries
>
> > Aside - RedHat has dropped cfdisk from util-linux in their distro versions 7.2 ff.
> > Given the bad words said about fdisk, what did cfdisk do to be ostracised?
>
> RedHat thought cfdisk is buggy.
> They were mistaken.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
LAD Storage Consulting Group
next prev parent reply other threads:[~2002-10-05 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 13:47 2.5.40 etc and IDE HDisk geometry Allan Duncan
2002-10-04 21:50 ` Andries Brouwer
2002-10-05 19:30 ` Andre Hedrick [this message]
2002-10-06 21:48 ` Allan Duncan
2002-10-06 23:28 ` Andries Brouwer
2002-10-07 0:19 ` Werner Almesberger
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=Pine.LNX.4.10.10210051228080.21833-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=aebr@win.tue.nl \
--cc=allan.d@bigpond.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;
as well as URLs for NNTP newsgroup(s).