From: Theodore Tso <tytso@mit.edu>
To: Juan Quintela <quintela@mandrakesoft.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, felix-dietlibc@fefe.de,
andersen@codepoet.org
Subject: Re: [RFC] klibc requirements, round 2
Date: Mon, 14 Jan 2002 12:54:33 -0500 [thread overview]
Message-ID: <20020114125433.A1357@thunk.org> (raw)
In-Reply-To: <20020110231849.GA28945@kroah.com> <m2r8ovjpey.fsf@trasno.mitica>
In-Reply-To: <m2r8ovjpey.fsf@trasno.mitica>; from quintela@mandrakesoft.com on Sat, Jan 12, 2002 at 09:16:21PM +0100
On Sat, Jan 12, 2002 at 09:16:21PM +0100, Juan Quintela wrote:
> >>>>> "greg" == Greg KH <greg@kroah.com> writes:
>
> Hi
>
> greg> To summarize, here's a partial list of the programs people want to run:
> greg> - mount
> greg> - hotplug
> greg> - busybox
> greg> - dhcpcd
> greg> - image viewer
> greg> - mkreiserfs
> greg> - partition discovery (currently in the kernel)
> greg> - lots of other, existing in kernel code.
>
> I still think that fsck at this point will be great. You will
> minimize the need to have the kernel special case for fsck the root fs
> with respect to the rest of fs.
The development sources for e2fsprogs will already work with diet
libc. Unfortunately, diet libc doesn't do shared libraries, so
resulting binaries are sufficiently big that I doubt they would be
interesting for initrd and rescue floppy applications (which is why I
tried the experiment in the first place).
In any case, given that e2fsprogs is already portable to NetBSD and
Solaris (the latter so I can run purify to catch memory errors), it
shouldn't be particularly difficult to get e2fsprogs to run on some
other alternative libc.
- Ted
next prev parent reply other threads:[~2002-01-14 21:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 23:18 [RFC] klibc requirements, round 2 Greg KH
2002-01-10 22:29 ` Bjorn Wesen
2002-01-11 0:04 ` Greg KH
2002-01-11 0:44 ` Tom Rini
2002-01-11 13:31 ` Felix von Leitner
2002-01-12 12:21 ` Erik Andersen
2002-01-13 1:43 ` Alexander Viro
2002-01-13 2:10 ` Felix von Leitner
2002-01-11 21:46 ` David Lang
2002-01-12 20:16 ` Juan Quintela
2002-01-13 1:38 ` Alexander Viro
2002-01-14 17:54 ` Theodore Tso [this message]
2002-01-14 21:57 ` Oliver Xymoron
2002-01-14 23:58 ` Andreas Dilger
2002-01-15 1:26 ` Oliver Xymoron
2002-01-15 3:48 ` Andreas Dilger
2002-01-15 4:05 ` Oliver Xymoron
2002-01-15 17:28 ` Rob Landley
2002-01-16 4:01 ` Alexander Viro
2002-01-16 17:54 ` Oliver Xymoron
2002-01-15 0:33 ` H. Peter Anvin
2002-01-16 18:40 ` Erik Andersen
2002-01-13 3:58 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 1:50 Torrey Hoffman
2002-01-11 3:32 ` Tom Rini
2002-01-11 6:53 ` 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=20020114125433.A1357@thunk.org \
--to=tytso@mit.edu \
--cc=andersen@codepoet.org \
--cc=felix-dietlibc@fefe.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.com \
/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