public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initramfs programs (was [RFC] klibc requirements)
Date: Wed, 9 Jan 2002 03:00:13 -0700	[thread overview]
Message-ID: <20020109100013.GB8743@codepoet.org> (raw)
In-Reply-To: <20020108192450.GA14734@kroah.com> <20020109042331.GB31644@codeblau.de> <20020109043446.GB17655@kroah.com>
In-Reply-To: <20020109043446.GB17655@kroah.com>

On Tue Jan 08, 2002 at 08:34:47PM -0800, Greg KH wrote:
> On Wed, Jan 09, 2002 at 05:23:31AM +0100, Felix von Leitner wrote:
> > 
> > How many programs are we talking about here?  And what should they do?
> 
> Very good question that we should probably answer first (I'll follow up
> to your other points in a separate message).
> 
> Here's what I want to have in my initramfs:
> 	- /sbin/hotplug
> 	- /sbin/modprobe
> 	- modules.dep (needed for modprobe, but is a text file)
> 
> What does everyone else need/want there?

I think you want a staticly linked multi-call binary, a 
trivial shell, and some kernel modules...
    http://www.uwsg.indiana.edu/hypermail/linux/kernel/0112.2/0681.html

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  parent reply	other threads:[~2002-01-09 10:00 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 19:24 [RFC] klibc requirements Greg KH
2002-01-08 20:37 ` Erik Andersen
2002-01-09  4:23 ` Felix von Leitner
2002-01-09  4:34   ` initramfs programs (was [RFC] klibc requirements) Greg KH
2002-01-09  6:10     ` Greg KH
2002-01-09  7:23       ` H. Peter Anvin
2002-01-09  9:33     ` Kai Germaschewski
2002-01-09 10:00     ` Erik Andersen [this message]
2002-01-09  4:51   ` [RFC] klibc requirements Greg KH
2002-01-09  5:01     ` H. Peter Anvin
2002-01-09  6:09       ` Greg KH
2002-01-09  7:26         ` H. Peter Anvin
2002-01-10  6:30           ` Rusty Russell
2002-01-10 18:41             ` H. Peter Anvin
2002-01-10 15:24           ` Matthias Kilian
2002-01-10 17:13             ` H. Peter Anvin
2002-01-09 14:15     ` Felix von Leitner
2002-01-09 14:30       ` Lars Brinkhoff
2002-01-09 14:51       ` Erik Andersen
2002-01-09 10:38   ` initramfs programs (was [RFC] klibc requirements) Anton Altaparmakov
2002-01-09 15:56     ` Pavel Machek
2002-01-09 16:04       ` Patrick Mochel
2002-01-09 16:26         ` Greg KH
2002-01-09 16:29         ` Pavel Machek
2002-01-09 16:48           ` Andreas Ferber
2002-01-09 21:15     ` Alex Bligh - linux-kernel
2002-01-09 21:34     ` Anton Altaparmakov
2002-01-09 21:40       ` Greg KH
2002-01-09 21:55       ` Anton Altaparmakov
2002-01-09 22:15         ` Andreas Ferber
2002-01-10  0:25           ` Tom Rini
2002-01-10  0:38             ` Andreas Ferber
2002-01-10  2:42               ` Tom Rini
2002-01-10 14:09                 ` Rob Landley
2002-01-10 22:24                   ` Tom Rini
2002-01-11  0:15                   ` H. Peter Anvin
2002-01-09 22:12       ` Alex Bligh - linux-kernel
2002-01-09 13:23   ` [RFC] klibc requirements Juan Quintela
2002-01-09 14:57     ` Erik Andersen
2002-01-15  3:08   ` Albert D. Cahalan
2002-01-15 11:55     ` Felix von Leitner
2002-01-15 14:54       ` David Lang
2002-01-15 16:15         ` Doug McNaught
2002-01-15 18:06           ` David Lang
2002-01-15 18:36             ` Doug McNaught
2002-01-16 18:36         ` Erik Andersen
2002-01-16  7:50       ` Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2002-01-09 17:54 initramfs programs (was [RFC] klibc requirements) Torrey Hoffman
2002-01-09 18:06 ` Tom Rini
2002-01-09 18:28 ` Greg KH
2002-01-09 18:49   ` Tom Rini
2002-01-09 20:05 Eric S. Raymond
2002-01-09 20:43 ` Doug McNaught
2002-01-09 20:44   ` Eric S. Raymond
2002-01-09 21:01     ` Doug McNaught
2002-01-09 22:07     ` Andreas Ferber
2002-01-09 21:56       ` Eric S. Raymond
2002-01-09 23:26         ` H. Peter Anvin
2002-01-09 23:30         ` Andreas Ferber
2002-01-12  5:31     ` Pavel Machek
2002-01-09 20:55 ` Patrick Mochel
2002-01-09 20:47   ` Eric S. Raymond
2002-01-09 22:41     ` Matthew Kirkwood
2002-01-09 22:46       ` Eric S. Raymond
2002-01-09 23:28         ` H. Peter Anvin
2002-01-10  0:21           ` Alan Cox
2002-01-10 11:21             ` Dave Jones
2002-01-09 23:29         ` Matthew Kirkwood
2002-01-09 23:29           ` Eric S. Raymond
2002-01-09 23:54             ` H. Peter Anvin
2002-01-10 10:35             ` Matthew Kirkwood
2002-01-12  5:36             ` Pavel Machek
2002-01-12 18:11 ` Oliver Xymoron
2002-01-09 20:25 Torrey Hoffman
2002-01-10  0:02 ` Tom Rini
     [not found] <fa.d7rnnnv.1l1gnri@ifi.uio.no>
     [not found] ` <fa.p5gg3pv.1iiscrg@ifi.uio.no>
2002-01-10 11:22   ` Giacomo Catenazzi
     [not found] <fa.gs2ktfv.1r00h12@ifi.uio.no>
     [not found] ` <fa.kj79fuv.1angmqd@ifi.uio.no>
2002-01-10 17:13   ` Giacomo Catenazzi
2002-01-10 17:28     ` Dave Jones
2002-01-10 17:32       ` H. Peter Anvin
2002-01-10 17:43         ` Dave Jones
2002-01-10 17:44           ` H. Peter Anvin
2002-01-10 17:47             ` Dave Jones
2002-01-10 17:37     ` Alan Cox
2002-01-10 17:27       ` 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=20020109100013.GB8743@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=greg@kroah.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