From: James A Sutherland <james@sutherland.net>
To: "Grover, Andrew" <andrew.grover@intel.com>,
"'Alexander Viro'" <viro@math.psu.edu>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'otto.wyss@bluewin.ch'" <otto.wyss@bluewin.ch>
Subject: Re: Booting a modular kernel through a multiple streams file
Date: Wed, 19 Dec 2001 09:34:49 +0000 [thread overview]
Message-ID: <T57eadc70a6ac1785e2316@pcow024o.blueyonder.co.uk> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C42D804@orsmsx111.jf.intel.com>
In-Reply-To: <59885C5E3098D511AD690002A5072D3C42D804@orsmsx111.jf.intel.com>
On Tuesday 18 December 2001 7:50 pm, Grover, Andrew wrote:
> > From: Alexander Viro [mailto:viro@math.psu.edu]
> >
> > On Tue, 18 Dec 2001, Grover, Andrew wrote:
> > > GRUB 0.90 does this today.
> >
> > ... and I'm quite sure that EMACS could do it easily. Let's not talk
> > about GNU bloatware, OK?
>
> I don't think this is bloatware, especially considering there really isn't
> any cost for having a full-featured bootloader - all its footprint gets
> reclaimed, after all.
Not on disk it doesn't. When you're booting from a floppy (distro
installation, recovery disk, whatever) you only have 1.something Mb to play
with. Or a network. For that matter, you're complicating CD booting too.
> I respect lilo and its cousins, but they make things
> harder than they have to be. Why maintain a reduced level of functionality
> (software emaciation?) when better alternatives are available?
Not "better". More features/bloat - and when they are "features" most of us
neither need nor want, why bother? Lilo does everything most of us need, and
does it better than grub or others: same job with fewer resources.
> > Except that in this case it doesn't make anything simpler.
>
> Implicit in the use of initrd is that you have to *make a ramdisk image*,
> and then tell your bootloader to load it. If you have a bootloader that can
> load multiple images (i.e. the modules themselves) you can skip the first
> step.
Initramfs will do this, it seems. Alternatively, you might have to copy some
files into a tarball - oh, the stress! Oh, wait - you just compiled 100+Mb of
C source to make that kernel and the modules. Somehow, making a tarball out
of the modules doesn't seem too stressful to me.
> > BTW, we don't need a special device to handle initrd after that. Just
> > have your initrd image (gzipped, whatever) in the archive
> > under /initrd.
> > After that /init will have the contents in that file (regular file, at
> > that) and can do whatever it bloody wants.
>
> Again, even the new scheme will still involve the creation of an initrd.
> I'm saying, as a user, it would be easier for me to not do this, and just
> modify a .conf file to have the driver loaded early-on.
OK, make the conf file a shell script which copies the modules into a tarball
or initrd image.
> I'm not arguing that the new initrd won't be better than the old initrd
> (because obviously you are right) I'm arguing that no matter how whizzy
> initrd is, it's still an unnecessary step, and it's one that other OSs
> (e.g. FreeBSD) omit in favor of the approach I'm advocating.
Feeping creaturism in the bootloader, you mean? Great... while we're at it,
how about building gcc, make, tar and gzip into the bootloader, along with an
FTP client, so it can download and compile the kernel to boot? Chuck in a
copy of emacs, too, for any changes you want?
You're already compiling the modules from C into .o files; what's the big
deal with copying them into a tarball?!
> > IOW, we are backwards compatible with old
> > loaders.
>
> No progress will ever be made if we cater to the lowest common denominator.
You're right. Let's drop x86 support, and require everyone to buy a nice new
POWER4 box from IBM.
James.
next prev parent reply other threads:[~2001-12-19 9:34 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-12-23 1:02 ` Dave Cinege
2001-12-23 9:10 ` James A Sutherland
2001-12-19 14:13 ` Erik Mouw
-- strict thread matches above, loose matches on Subject: below --
2001-12-23 7:20 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 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 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
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-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=T57eadc70a6ac1785e2316@pcow024o.blueyonder.co.uk \
--to=james@sutherland.net \
--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®