From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc requirements, round 2
Date: 10 Jan 2002 22:53:14 -0800 [thread overview]
Message-ID: <a1m24q$qrd$1@cesium.transmeta.com> (raw)
In-Reply-To: <D52B19A7284D32459CF20D579C4B0C0211CB2C@mail0.myrio.com>
Followup to: <D52B19A7284D32459CF20D579C4B0C0211CB2C@mail0.myrio.com>
By author: "Torrey Hoffman" <torrey.hoffman@myrio.com>
In newsgroup: linux.dev.kernel
>
> My concern is with the minority who are using initrd, and in
> some cases a very customized initrd.
>
They can presumably use whatever they already do, except they'll make
it into a .cpio.gz file instead of an .img.gz file.
> The important thing, I think, is that it should be easy for
> less-than-guru level hackers to add programs to the initramfs,
> even if the program they want can't be linked with klibc.
>
> This really comes down to: What will the build process be for
> these initramfs images?
>
> By the way, is initramfs intended to supercede initrd, or will
> they co-exist?
Eventually supercede; it will let us pull out an amazing amount of
crud.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-11 6:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 1:50 [RFC] klibc requirements, round 2 Torrey Hoffman
2002-01-11 3:32 ` Tom Rini
2002-01-11 6:53 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-10 23:18 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
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
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='a1m24q$qrd$1@cesium.transmeta.com' \
--to=hpa@zytor.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.