linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Tim Fletcher <tim@parrswood.manchester.sch.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Device Numbers, LILO
Date: Tue, 15 May 2001 14:20:10 -0700	[thread overview]
Message-ID: <3B019D8A.86C18D1C@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105152156200.4099-100000@redwood.parrswood.manchester.sch.uk>

Tim Fletcher wrote:
> 
> > It's in, but for some strange reason you have to ask for it explicitly
> > with the "lba32" option.
> 
> Because the 32bit bios calls lilo uses in lba32 mode can cause problems
> with broken or old bios's hence is defaults to a safe option, and if you
> can't boot without it (over 1023 cylinders) then you turn it on at your
> own risk.
> 
> I know this from the experiance of breaking lilo on my workstation :)
> 

The problem is that LILO tries one or the other, instead of dynamically
using whichever one it needs.  Heck, you may not be able to make that
decision until boot time anyway!  You can then either always try LBA
calls and see if they are available, or default to CHS calls unless
cylinder > 1023.

LILO tries to do *way* too much at install time.  The fact that you have
to specify "linear" explicitly is a joke -- there is no excuse for
!linear.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

      reply	other threads:[~2001-05-15 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-15 12:16 Device Numbers, LILO mirabilos
2001-05-15 15:47 ` Nico Schottelius
2001-05-15 16:04 ` H. Peter Anvin
2001-05-15 20:58   ` Tim Fletcher
2001-05-15 21:20     ` H. Peter Anvin [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=3B019D8A.86C18D1C@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@parrswood.manchester.sch.uk \
    /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).