From: Guest section DW <dwguest@win.tue.nl>
To: Wakko Warner <wakko@animx.eu.org>, Aaron Lehmann <aaronl@vitelus.com>
Cc: Stephen C Burns <sburns@farpointer.net>,
linux-kernel@vger.kernel.org, 83710@bugs.debian.org
Subject: Re: [OT] Re: LILO calling modprobe?
Date: Fri, 6 Jul 2001 01:01:07 +0200 [thread overview]
Message-ID: <20010706010107.A1956@win.tue.nl> (raw)
In-Reply-To: <20010705224245.A1789@win.tue.nl> <20010705140330.C22723@vitelus.com> <20010705180331.A10315@animx.eu.org>
In-Reply-To: <20010705180331.A10315@animx.eu.org>; from Wakko Warner on Thu, Jul 05, 2001 at 06:03:31PM -0400
On Thu, Jul 05, 2001 at 06:03:31PM -0400, Wakko Warner wrote:
> > > Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
> > > There is no problem, certainly no kernel problem.
> >
> > Sure it isn't a problem, but it's really annoying if it won't need to
> > touch hda anyway.
> >
> > Is there a reason that it does this?
>
> I believe there is. It wants to find what drive is bios drive 80h.
Yes.
> I had a machine at work with both ide and scsi. ide hdd was hdc and ide
> cdrom was hda just to keep lilo from thinking hdc is the first bios drive
> which infact sda was
But why don't you use the bios keyword? From lilo.conf(5):
For example,
disk=/dev/sda
bios=0x80
disk=/dev/hda
bios=0x81
would say that your SCSI disk is the first BIOS
disk, and your (primary master) IDE disk is the
second BIOS disk.
next prev parent reply other threads:[~2001-07-05 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 19:58 LILO calling modprobe? Stephen C Burns
2001-07-05 20:14 ` Aaron Lehmann
2001-07-05 20:42 ` Guest section DW
2001-07-05 21:03 ` [OT] " Aaron Lehmann
2001-07-05 22:03 ` Wakko Warner
2001-07-05 22:14 ` Albert D. Cahalan
2001-07-05 23:01 ` Guest section DW [this message]
2001-07-05 23:03 ` Aaron Lehmann
2001-07-05 23:08 ` Guest section DW
2001-07-05 23:29 ` Aaron Lehmann
2001-07-06 0:14 ` Wakko Warner
2001-07-05 20:57 ` Russell King
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=20010706010107.A1956@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=83710@bugs.debian.org \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sburns@farpointer.net \
--cc=wakko@animx.eu.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).