mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Garfield <garfield@irving.iisd.sra.com>
To: linux-kernel@vger.kernel.org
Subject: Query about initramfs and modules
Date: Tue, 15 Jan 2002 18:15:02 -0500	[thread overview]
Message-ID: <15428.47094.435181.278715@irving.iisd.sra.com> (raw)

Hearing all this talk about initramfs and eliminating hardwired
drivers, it occurs to me to ask:



Can/will the initramfs mechanism be made to implicitly load into the
kernel the modules (or some of the modules) in the image?



Doing so would allow the initramfs image to be composed solely of the
modules to be loaded, which would reduce the need for the "klibc".  It
would also eliminate the need for any sort of control script to be in
the image.

The only difficulty that I perceive in doing this is that the modules
in question might need to be appropriately resolved and relocated
before being put into the file image.  I think this is a solvable
problem, given that the kernel and its System.map should be available
when building the image.

--David Garfield

             reply	other threads:[~2002-01-15 23:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 23:15 David Garfield [this message]
2002-01-15 23:34 ` Greg KH
2002-01-15 23:47 ` David Garfield
2002-01-16  0:01   ` Greg KH
2002-01-16 19:29     ` Andreas Ferber
2002-01-16 19:40       ` Greg KH
2002-01-16 19:53         ` Jordan Crouse
2002-01-16  0:33   ` David Garfield
2002-01-16  1:16     ` Greg KH
2002-01-16  2:09 ` H. Peter Anvin
2002-01-16  3:29 ` Alexander Viro
2002-01-16 19:41   ` Erik Andersen
2002-01-16 19:56     ` H. Peter Anvin
2002-01-16 20:18       ` Erik Andersen
2002-01-16 20:23         ` H. Peter Anvin
2002-01-16 17:53 ` David Garfield
2002-01-16 18:13   ` H. Peter Anvin
2002-01-16 19:04   ` David Garfield

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=15428.47094.435181.278715@irving.iisd.sra.com \
    --to=garfield@irving.iisd.sra.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 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®