public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 and IDE "geometry"
Date: Wed, 17 Dec 2003 10:40:36 -0500	[thread overview]
Message-ID: <20031217104036.A13292@animx.eu.org> (raw)
In-Reply-To: <200312161717.hBGHH0kX000201@81-2-122-30.bradfords.org.uk>; from John Bradford on Tue, Dec 16, 2003 at 05:17:00PM +0000

> > I believe parted does not. Nor any of the libparted frontends. I may be
> > wrong though.
> 
> If so, I consider it a missing feature in parted - why should the BIOS
> geometry resemble the disk it describes at all?  Some machines have no
> user-definable drive types, forcing you to use an incorrect geometry
> if you install a disk which is not in the table of supported drives.
> 
> This is no problem for recent Linux kernels, and doesn't even prevent
> you booting from that disk.

I think noone has really understood why I want it.  The machines in question
will not ever boot linux from the hard disk.  Only from the CD that I built. 
The OS that is installed from the CD is one of the windows OSs which depend
on the bios geometry definition to boot properly.  The kernel doesn't care
about the geometry, that's all well and good except when I create the
partitions.  Most of the pcs I work with use */255/63 notation,
occasionally, I'll come across one that uses */128/63 notation.  Never one
with */16/63 notation.  The smallest disk I work with would be a 1.2gb disk.

I have tried to make this CD as simple to use as possible, which means
passing the geometry on the command line is out of the question and setting
it for every invocation of *fdisk is pretty much out as well.  I liked the
"bogus bios"geometry the kernel was able to get from the bios.  Out of the
hundreds of PCs I've used this on, not one has ever failed me.

I have stuck with 2.4.x for now, but at some point, it'll have to be
upgraded due to hardware support.  2.4 will eventtually become with 2.0 is
now, stable, no new drives, only critial bug fixes.  As time progresses, the
kernel will not support newer hardware (For instance network drivers which
is used havily in this CD as well).

All I really want is to beable to get the kernel to get the bios parameters
for me.  If this means a patch or something, that's fine.  (I don't know
anything about the ide drivers to do this)

This CD has made my life easier at my job and it's not something I want to
give up while I still have this job =)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2003-12-17 15:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 18:17 2.6 and IDE "geometry" Wakko Warner
2003-12-12 19:44 ` Andries Brouwer
2003-12-12 21:35   ` Wakko Warner
2003-12-13 13:22     ` Andries Brouwer
2003-12-13 22:18       ` Wakko Warner
2003-12-14 14:40         ` Andries Brouwer
2003-12-14 16:27           ` Wakko Warner
2003-12-14 20:27             ` Andries Brouwer
2003-12-14 21:23               ` Wakko Warner
2003-12-14 22:03                 ` Andries Brouwer
2003-12-15 20:02                   ` Wakko Warner
2003-12-16 20:55               ` bill davidsen
2003-12-17 15:42                 ` Wakko Warner
2003-12-16 13:53   ` Sven Luther
2003-12-16 17:17     ` John Bradford
2003-12-17 15:40       ` Wakko Warner [this message]
2003-12-17 16:16         ` Richard B. Johnson

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=20031217104036.A13292@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=john@grabjohn.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