All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Again Multiboot-Standard for Linux ?
Date: 21 Nov 2001 15:07:16 -0800	[thread overview]
Message-ID: <9thc34$8lb$1@cesium.transmeta.com> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C42D772@orsmsx111.jf.intel.com> <166g3I-0ksq00C@fwd06.sul.t-online.com>

Followup to:  <166g3I-0ksq00C@fwd06.sul.t-online.com>
By author:    "ChristianK."@t-online.de (Christian Koenig)
In newsgroup: linux.dev.kernel
> 
> Beside that, this it is a very nice feature for making an Installation Disk / 
> Distributions.
> AFAIK the newest RedHat distribution use grub as standard Linux Loader,
> if the Linux Kernel is able to load modules before mounting root, you can 
> make a Kernel without any block/bus driver compiled in.
> 

That's already what initrd does.  What would make this interesting --
and why, at least in my opinion, Multiboot is the wrong solution -- is
to make the bootloader smarter about what it loads.  If the boot
loader can *probe* for the device- and filesystem drivers it needs and
thus dynamically compose the kernel in a dynamic manner, then it is
suddenly a win; not sooner.  Multiboot doesn't do that, although it
might be possible to build on top of it to get there.

	-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	<amsp@zytor.com>

  reply	other threads:[~2001-11-21 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 22:43 Again Multiboot-Standard for Linux ? Grover, Andrew
2001-11-21 22:41 ` Christian Koenig
2001-11-21 23:07   ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-20 21:29 Christian Koenig
2001-11-20 21:19 Christian Koenig

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='9thc34$8lb$1@cesium.transmeta.com' \
    --to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.