All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Garfield <garfield@irving.iisd.sra.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Query about initramfs and modules
Date: Wed, 16 Jan 2002 11:40:26 -0800	[thread overview]
Message-ID: <20020116194026.GD1964@kroah.com> (raw)
In-Reply-To: <15428.47094.435181.278715@irving.iisd.sra.com> <20020115233437.GC29020@kroah.com> <15428.49056.652466.414438@irving.iisd.sra.com> <20020116000117.GD29020@kroah.com> <20020116202958.E18039@devcon.net>
In-Reply-To: <20020116202958.E18039@devcon.net>

On Wed, Jan 16, 2002 at 08:29:58PM +0100, Andreas Ferber wrote:
> 
> Hmm. AFAICS this also implies that one would have to put /all/ drivers
> for /any/ hardware possibly plugged in at boot time on the initramfs.
> Or will /sbin/hotplug provide the ability to just put requests it
> can't resolve with the modules on the initramfs into some sort of
> queue file, which is read by /sbin/coldplug (or whatever) later on in
> the boot process to load drivers for those from the real root fs?

No, I hadn't thought of doing this.  If someone wants to knock out a
patch, I'd be glad to take a look at it.

> > And this allows lots of horrible "boot over NFS" and other network
> > code/hacks in the kernel to be moved out of kernel space, and into
> > userspace, where it really belongs.
> 
> Having to put all drivers for all PCI/USB/whatever stuff on the
> initramfs will likely be a problem (regarding disk space) for people
> who need to boot the kernel from a floppy disk without having to
> change disks during boot (think of nfsroot without etherboot).

I agree.  It's a lot of drivers (and it's growing.)  It will help out
people booting from a hard disk the most (which happen to be the
majority of people :)

thanks,

greg k-h

  reply	other threads:[~2002-01-16 19:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 23:15 Query about initramfs and modules David Garfield
2002-01-15 23:34 ` Greg KH
2002-01-15 23:47   ` David Garfield
2002-01-16  0:01     ` Greg KH
2002-01-16  0:33       ` David Garfield
2002-01-16  1:16         ` Greg KH
2002-01-16 19:29       ` Andreas Ferber
2002-01-16 19:40         ` Greg KH [this message]
2002-01-16 19:53           ` Jordan Crouse
2002-01-16  2:09 ` 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
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

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=20020116194026.GD1964@kroah.com \
    --to=greg@kroah.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.