linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mirabilos <eccesys@topmail.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Device Numbers, LILO
Date: Tue, 15 May 2001 14:16:35 +0200 (MET DST)	[thread overview]
Message-ID: <20010515121635.B5C402F84AC@www.topmail.de> (raw)

>That's not the issue.  LILO takes whatever you pass to root= and converts
>it to a device number at /sbin/lilo time.  An idiotic practice on the
>part of LILO, in my opinion, that ought to have been fixed a long time
>ago.

That's why you have to use append="root=blah" for devfs :)
Really it should have been in IMO. Btw, is LBA support in?
Last time I saw a LILO manpage it stated that "linear" still
is restricted to 16bit (65535 sectors) which normally is much
less than 1k cylinders...

-mirabilos
-- 
by telnet

             reply	other threads:[~2001-05-15 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-15 12:16 mirabilos [this message]
2001-05-15 15:47 ` Device Numbers, LILO 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

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=20010515121635.B5C402F84AC@www.topmail.de \
    --to=eccesys@topmail.de \
    --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).