From: Jeff Garzik <jgarzik@pobox.com>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: gkajmowi@tbaytel.net, linux-kernel@vger.kernel.org
Subject: Re: Initramfs
Date: Thu, 21 Aug 2003 10:19:48 -0400 [thread overview]
Message-ID: <3F44D504.7060909@pobox.com> (raw)
In-Reply-To: <1061447419.19503.20.camel@camp4.serpentine.com>
Bryan O'Sullivan wrote:
> No. initramfs is stuck in limbo at the moment, and early userspace is
> unlikely to see any real work until 2.7. Feel free to ask questions,
> but don't expect them to result in anything actually happening.
>
> If you want to do real work in this area, the klibc mailing list is the
> place to go: http://www.zytor.com/mailman/listinfo/klibc
Correct, though there is one thing I am thinking about adding to 2.6:
Support replacing "initrd=" with "initramfs=", so that bootloaders can
pass a cpio image into the standard initrd memory space.
Jeff
next prev parent reply other threads:[~2003-08-21 14:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 4:44 Initramfs Garrett Kajmowicz
2003-08-21 6:30 ` Initramfs Bryan O'Sullivan
2003-08-21 14:19 ` Jeff Garzik [this message]
2003-08-21 18:28 ` Initramfs Bryan O'Sullivan
2003-08-21 19:03 ` Initramfs viro
2003-08-21 19:57 ` Initramfs Bryan O'Sullivan
2003-08-21 20:22 ` Initramfs Willy Tarreau
2003-08-21 20:56 ` Initramfs viro
2003-08-21 22:34 ` Initramfs H. Peter Anvin
2003-08-21 22:31 ` Initramfs Werner Almesberger
2003-08-21 22:41 ` Initramfs Jeff Garzik
2003-08-21 23:15 ` Initramfs Werner Almesberger
2003-08-28 20:07 ` Initramfs H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 17:41 initramfs Wakko Warner
2005-05-25 18:26 ` initramfs Lennart Sorensen
2005-05-25 18:45 ` initramfs Wakko Warner
2005-05-25 19:54 ` initramfs Wakko Warner
2005-05-25 18:54 ` initramfs Wakko Warner
2005-07-13 10:06 initramfs Jacek Jabłoński
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=3F44D504.7060909@pobox.com \
--to=jgarzik@pobox.com \
--cc=bos@serpentine.com \
--cc=gkajmowi@tbaytel.net \
--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