public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Nufarul Alb <nufarul.alb@home.ro>
Cc: Jim Carter <jimc@math.ucla.edu>, linux-kernel@vger.kernel.org
Subject: Re: multibooting the linux kernel
Date: Wed, 13 Aug 2003 23:19:26 -0300	[thread overview]
Message-ID: <20030813231926.B8269@almesberger.net> (raw)
In-Reply-To: <3F3A9302.5000806@home.ro>; from nufarul.alb@home.ro on Wed, Aug 13, 2003 at 10:35:30PM +0300

Nufarul Alb wrote:
> the use of initrd is a real pain in the butt.

It's mainly a packaging issue. So far, it seems that nobody has
written a useful set of generic tools to build an initrd. But
the ingredients are there.

> with multibooting GRUB 
> loads the modules into memory and the kernel can take them from there. 

A solution that depends on GRUB and that only works for
modules ? That's not so nice. What if a driver also needs some
setup script, a user-space demon, or has to download a non-GPL
firmware binary ?

If you envision a use where someone would load a set of drivers
from removable media to bring up the system, it would be more
flexible to allow for multiple initrds/initramfs, which then
contain whatever code or data is needed.

And please don't stop there, but also specify what these
additional file systems should contain (e.g. a script
"initializeme" in the top-level directory, or such).

> The MAIN THING  that a multiboot kernel will solve is the problem of 
> module portability. I think that the reason why hardware producers are 
> not making drivers for linux is that they have to make them open source 
> in order to be compiled by every user.

So we're just hallucinating all those binary-only drivers ? :-)

> With multibooting it become 
> possible to make a standard type of the main image of the kernel and all 
> the modules will be built for it.

A developer's dream - the immutable standard kernel with
internal data structures frozen for all eternity ;-))

> AND besides all that you can do many operations before mounting the 
> actual root like, for example, make a module that encapsulates a nice 
> boot animation,

Once kexec makes into the mainstream kernel, I'm sure we won't
have to wait long for such things to show up.

> a progress bar, show the services start in a nice 
> graphical way on top of the framebuffer.

That's entirely a user-space issue.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  reply	other threads:[~2003-08-14  2:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 22:36 multibooting the linux kernel Nufarul Alb
2003-08-13  0:29 ` William Lee Irwin III
2003-08-13  7:18   ` Denis Vlasenko
2003-08-14  6:28     ` William Lee Irwin III
2003-08-13  6:20 ` Christoph Hellwig
2003-08-13 12:23   ` Nufarul Alb
2003-08-13 18:09     ` Wakko Warner
     [not found]     ` <Pine.LNX.4.53.0308130904140.3016@xena.cft.ca.us>
2003-08-13 19:35       ` Nufarul Alb
2003-08-14  2:19         ` Werner Almesberger [this message]
2003-08-14 18:47 ` H. Peter Anvin

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=20030813231926.B8269@almesberger.net \
    --to=wa@almesberger.net \
    --cc=jimc@math.ucla.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nufarul.alb@home.ro \
    /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