From: Phillip Susi <psusi@cfl.rr.com>
To: Marcin Dalecki <dalecki.marcin@neostrada.pl>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
"Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: C/H/S from user space
Date: Sat, 18 Feb 2006 11:20:57 -0500 [thread overview]
Message-ID: <43F74969.2010500@cfl.rr.com> (raw)
In-Reply-To: <66D6145F-E9F9-4B4F-B06F-3C40018E8F86@neostrada.pl>
Marcin Dalecki wrote:
> It has been already tried years ago to eliminate this ridicle. The
> answer to your
> question is put bluntly: It's like that, because some kernel "prima
> ballerinas",
> whose names "relate to alternating current", will get at you with mock
> up somke
> and mirror woodo examples where it's supposed to be sooo required.
I myself have been trying to show why it is required. Unless I am wrong
about the msdos MBR code passing the CHS partition start values directly
to int 13 rather than computing them based on the LBA in the MBR and the
currently reported geometry from the bios, then fdisk does require the
correct bios geometry to maintain compatibility with msdos/windows.
My original point was that if it is required ( and since it is still in
the kernel, that seems to be the case ) then at least make sure it is
_correct_. Whether it is needed but wrong, or if it is simply not
needed, then it is silly to keep geometry in the kernel.
next prev parent reply other threads:[~2006-02-18 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 17:01 C/H/S from user space linux-os (Dick Johnson)
2006-02-17 18:37 ` Jeff V. Merkey
2006-02-17 19:59 ` Phillip Susi
2006-02-17 20:04 ` linux-os (Dick Johnson)
2006-02-17 20:24 ` Nick Warne
2006-02-17 20:39 ` linux-os (Dick Johnson)
2006-02-17 21:04 ` Phillip Susi
2006-02-17 21:22 ` linux-os (Dick Johnson)
2006-02-17 22:20 ` Phillip Susi
2006-02-18 3:42 ` Marcin Dalecki
2006-02-18 16:20 ` Phillip Susi [this message]
2006-02-17 22:24 ` Jeff V. Merkey
2006-02-17 22:22 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2006-02-17 20:30 Seewer Philippe
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=43F74969.2010500@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dalecki.marcin@neostrada.pl \
--cc=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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