From: Dave Cinege <dcinege@psychosis.com>
To: Alexander Viro <viro@math.psu.edu>,
"Grover, Andrew" <andrew.grover@intel.com>
Cc: "'otto.wyss@bluewin.ch'" <otto.wyss@bluewin.ch>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Booting a modular kernel through a multiple streams file
Date: Sat, 22 Dec 2001 19:28:18 -0500 [thread overview]
Message-ID: <E16HwUt-0001rU-00@schizo.psychosis.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0112172059510.6100-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0112172059510.6100-100000@weyl.math.psu.edu>
On Monday 17 December 2001 21:31, Alexander Viro wrote:
> *shrug* Your "all they have to do" is quite heavy.
Lilo (broken), syslinux (not very difficult), GRUB, (already implemented).
The list is not long. It's little differeent then a boot loader supporting
initrd loading.
> > I don't think this will obsolete any existing boot methods, but it seems
> > like an additional genuinely useful capability for the Linux kernel to
> > have.
>
> I've had a very dubious pleasure of dealing with our boot sequence lately.
Yes the guilty are well known...
> Adding more cruft to it (including in-kernel linker, for fsck sake) is
> _not_ a good idea.
Which is why all of that shit that loads multiple initrd floppies, etc,
etc should be gutting and replaced with a solid initrd system that
can load tar.gz's to tmpfs. Jeez...I happen to have such a patch RIGHT
HERE....for 3 years now. (minix prior to tmpfs existance...)
Loading initrd and boot time kernel modules, from multiple sources,
belongs in 'pre-kernel' (prom/bootloader) land. Most importantly this
boot loader is already implemented for IA32.
> That goes for a _lot_ of code. Mounting root. Detecting the type of
> initrd contents. Loading ramdisk from floppies. Asking to press
> key (you really ought to look what is done for _that_). Speaking
> DHCP - we have a kernel DHCP client, of all things. All that stuff
> can (and should) be done from userland process.
Already done (properly) in GRUB. Userland (after the kernel boots) is
no place for this. It's too late to be done cleanly. I agree the kernel
is no place either.
> Let loader leave an archive to be unpacked into rootfs? Sure. Let kernel
> exec /init on rootfs and leave the rest to it? Absolutely. But let's
> stop adding userland stuff into the kernel. Loading modules _can_ be
> done from userland - insmod does it just fine. And that's where it should
> be done.
This is a very much a failed concept. In theory it sounds nice. My
experience in
1) implementing a Linux OS from scratch
2) administering multiple networks of mission critical servers
says this doesn't work well.
Dave
--
The time is now 22:54 (Totalitarian) - http://www.ccops.org/
next prev parent reply other threads:[~2001-12-23 0:39 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 22:10 Grover, Andrew
2001-12-18 2:31 ` Alexander Viro
2001-12-18 5:46 ` Craig Christophel
2001-12-23 0:28 ` Dave Cinege [this message]
2001-12-23 0:44 ` Dave Cinege
2001-12-23 1:39 ` H. Peter Anvin
2001-12-23 2:10 ` Alexander Viro
2001-12-23 3:00 ` Dave Cinege
2001-12-23 3:52 ` Alexander Viro
2001-12-23 4:41 ` Ryan Cumming
2001-12-23 5:52 ` Dave Cinege
2001-12-23 7:16 ` Bernd Eckenfels
2001-12-23 8:06 ` H. Peter Anvin
2001-12-23 12:22 ` Kai Henningsen
2001-12-23 20:58 ` Erik Mouw
2001-12-23 9:14 ` tar vs cpio (was: Booting a modular kernel through a multiple streams file) H. Peter Anvin
2001-12-22 19:53 ` T. A.
2001-12-23 19:17 ` H. Peter Anvin
2001-12-23 9:51 ` Ryan Cumming
2001-12-23 9:53 ` H. Peter Anvin
2001-12-23 12:01 ` Wichert Akkerman
2001-12-23 14:28 ` Alexander Viro
2001-12-23 19:28 ` H. Peter Anvin
2001-12-23 20:00 ` H. Peter Anvin
2001-12-18 15:26 ` Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time Christian Koenig
2001-12-18 18:32 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2001-12-23 7:20 Booting a modular kernel through a multiple streams file Grover, Andrew
2001-12-23 9:15 ` Eric W. Biederman
2001-12-23 9:47 ` H. Peter Anvin
2001-12-23 21:24 ` Eric W. Biederman
[not found] <Pine.GSO.4.21.0112190313080.9963-100000@weyl.math.psu.edu>
2001-12-19 8:47 ` Eric W. Biederman
2001-12-19 14:55 ` Alexander Viro
2001-12-19 15:49 ` Eric W. Biederman
2001-12-19 17:03 ` Alexander Viro
2001-12-19 19:01 ` Eric W. Biederman
2001-12-20 3:30 ` H. Peter Anvin
2001-12-18 20:35 Torrey Hoffman
2001-12-18 19:50 Grover, Andrew
2001-12-18 20:26 ` Alexander Viro
2001-12-18 20:30 ` M. R. Brown
2001-12-18 20:35 ` H. Peter Anvin
2001-12-19 9:34 ` James A Sutherland
2001-12-23 1:02 ` Dave Cinege
2001-12-23 9:10 ` James A Sutherland
2001-12-19 14:13 ` Erik Mouw
2001-12-18 17:47 Grover, Andrew
2001-12-18 18:53 ` Alexander Viro
2001-12-18 19:43 ` David Weinehall
2001-12-18 17:43 Grover, Andrew
2001-12-18 18:45 ` Alexander Viro
2001-12-18 18:49 ` Greg KH
[not found] <Pine.GSO.4.21.0112180350550.6100-100000@weyl.math.psu.edu>
2001-12-18 11:16 ` James A Sutherland
2001-12-18 19:10 ` H. Peter Anvin
2001-12-19 9:27 ` James A Sutherland
2001-12-19 10:11 ` Erik Andersen
2001-12-23 0:39 ` Dave Cinege
2001-12-23 0:42 ` H. Peter Anvin
2001-12-23 1:15 ` Dave Cinege
2001-12-23 1:35 ` H. Peter Anvin
2001-12-23 2:08 ` Alexander Viro
2001-12-17 19:53 Grover, Andrew
2001-12-17 20:26 ` Alexander Viro
2001-12-16 20:37 Otto Wyss
2001-12-16 20:50 ` Alexander Viro
2001-12-17 18:49 ` Otto Wyss
2001-12-17 19:07 ` Andreas Dilger
2001-12-20 18:47 ` Otto Wyss
2001-12-16 21:06 ` H. Peter Anvin
2001-12-16 22:02 ` antirez
2001-12-16 22:18 ` H. Peter Anvin
2001-12-23 0:08 ` Dave Cinege
2001-12-23 6:26 ` Eric W. Biederman
2001-12-23 13:48 ` Alan Cox
2001-12-23 17:57 ` Dave Cinege
2001-12-23 23:05 ` Marcus Meissner
2001-12-24 2:38 ` Alan Cox
2001-12-27 10:58 ` Wilfried Weissmann
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=E16HwUt-0001rU-00@schizo.psychosis.com \
--to=dcinege@psychosis.com \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=otto.wyss@bluewin.ch \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®