mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Felix von Leitner <felix-dietlibc@fefe.de>
Cc: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, andersen@codepoet.org
Subject: Re: [RFC] klibc requirements
Date: 09 Jan 2002 14:23:46 +0100	[thread overview]
Message-ID: <m2elkzslnh.fsf@trasno.mitica> (raw)
In-Reply-To: <20020108192450.GA14734@kroah.com> <20020109042331.GB31644@codeblau.de>
In-Reply-To: <20020109042331.GB31644@codeblau.de>

>>>>> "felix" == Felix von Leitner <felix-dietlibc@fefe.de> writes:

Hi

>> Comments from the various libc authors?  Comments from other kernel
>> developers about requirements and goals they would like to see from such
>> a libc?

felix> I think you need to ask initrd users.
felix> My understanding was that people want to use the IP autoconfiguration
felix> stuff from the kernel to initrd.  Is that still so?  What other programs
felix> are needed?

I can think of that in a fast thought:

- if fsck.* can be there, it will make fs nice, just now they have to
  be able to fsck a ro root fs.
- I suppose that you can put here also the raid autodetect code and
  things like that.
- you also need a very small minishell, something like nash (that
  cames with mkinitrd will suffice).
  Basic utility here is that you want to have several small programs
  and have a small shell script to configure them (a distribution
  dont' want to recompile all its boot programs for each target
  configuration).
- as I suppose that you have supposed insmod is essential :)
- you already put there IP autoconfiguration.

Later, Juan.



-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  parent reply	other threads:[~2002-01-09 13:27 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 19:24 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
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 15:24           ` Matthias Kilian
2002-01-10 17:13             ` H. Peter Anvin
2002-01-10  6:30         ` Rusty Russell
2002-01-10 18:41           ` 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 13:23   ` Juan Quintela [this message]
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
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 22:12     ` Alex Bligh - linux-kernel
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

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=m2elkzslnh.fsf@trasno.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=andersen@codepoet.org \
    --cc=felix-dietlibc@fefe.de \
    --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

all inboxes | Powered by JetHome®