From: Andreas Dilger <adilger@turbolabs.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Russell Coker'" <russell@coker.com.au>,
"Acpi-linux (E-mail)" <acpi@phobos.fachschaften.tu-muenchen.de>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: lilo vs other OS bootloaders was: FreeBSD makes progress
Date: Fri, 31 Aug 2001 16:40:28 -0600 [thread overview]
Message-ID: <20010831164028.I541@turbolinux.com> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0DB@orsmsx35.jf.intel.com>
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0DB@orsmsx35.jf.intel.com>
On Aug 31, 2001 14:49 -0700, Grover, Andrew wrote:
> Just for discussion's sake, I would like to point out that other OSs do have
> loaders that can load boot drivers, and they can use this to increase the
> modularity of their kernel. FreeBSD's and Win2k's bootloaders are examples.
> Win2K even abstracts all SMP/UP code into a module (the HAL) and loads this
> at boot, thus using the same kernel for both.
Just FYI, this is just around the corner. Al Viro has made it mandatory
(I believe) to have a very simple initramfs, for doing things like mounting
the root filesystem and setting up other services which are now done in
the kernel at boot time. This initramfs (very similar to initrd) is at
the end of the kernel image, so it can't get lost and doesn't require
sending a separate file (i.e. for network booting, etc).
> possibly abstracting SMP/UP from the kernel proper?
Will never happen, as there would probably be overhead for both UP and SMP
to do this. If you want something like this (for ease of admin or so),
you can generally run the SMP kernel on UP systems and take the performance
hit, but not everyone will do that.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-08-31 22:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 21:49 lilo vs other OS bootloaders was: FreeBSD makes progress Grover, Andrew
2001-08-31 22:40 ` Andreas Dilger [this message]
2001-08-31 22:50 ` Alan Cox
2001-09-01 15:50 ` Jamie Lokier
2001-09-08 17:55 ` Eric W. Biederman
2001-09-08 18:55 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 14:55 Samium Gromoff
2001-09-01 12:03 ` Peter Wächtler
2001-09-01 12:39 ` Alan Cox
2001-09-01 14:10 ` Rik van Riel
2001-09-04 21:52 Grover, Andrew
2001-09-05 1:51 ` David S. Miller
2001-09-05 8:03 ` Helge Hafting
2001-09-05 14:26 ` Horst von Brand
2001-09-11 22:48 ` Pavel Machek
2001-09-05 21:18 Grover, Andrew
2001-09-05 22:11 ` Alan Cox
2001-09-05 22:13 ` Tim Hockin
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=20010831164028.I541@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=russell@coker.com.au \
/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