From: Dave Cinege <dcinege@psychosis.com>
To: Miles Bader <miles@gnu.org>, Miles Bader <miles@lsi.nec.co.jp>,
andersen@codepoet.org
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list.
Date: Wed, 30 Oct 2002 04:55:20 -0500 [thread overview]
Message-ID: <200210300455.20883.dcinege@psychosis.com> (raw)
In-Reply-To: <buofzuogv31.fsf@mcspd15.ucom.lsi.nec.co.jp>
On Wednesday 30 October 2002 4:00, Miles Bader wrote:
> Erik Andersen <andersen@codepoet.org> writes:
> > IMHO the embedded world (as well as everyone else) wants initramfs --
> > it is a major improvement.
Erik
#1 I'll be reviewing initramfs and adding loading image from
the kernel support. I don't deny it's a godo thig to have.
#2 My main bitch at jeff was he said if initramfs goes in
initrd comes out. initrd shodul not come out.
My patch is the best of both because
> I guess I'm part of the `embedded world,' and I don't want _either_
> because they _both use RAM_!
My patch supports this (well it can be in about 5 lines of code)
Right now for backwards compatiblity I have a
initrd_from_floppy option (which replaces load_ramdisk=).
I was debating changing that to initrd_from= and then you can
spec /dev/fd0, /dev/fd1, or in your case a memory device linux
understandings.
But I mostly dimissed it because that is the job of the
boot loader....but you bring up a good point where it
could be used.
--
The time is now 22:48 (Totalitarian) - http://www.ccops.org/
next prev parent reply other threads:[~2002-10-30 9:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 2:17 Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Rob Landley
2002-10-28 8:25 ` Vamsi Krishna S .
2002-10-28 9:55 ` Skip Ford
2002-10-28 10:35 ` Vamsi Krishna S .
2002-10-28 10:29 ` Andrew Walrond
2002-10-28 10:40 ` Rob Landley
2002-10-28 12:15 ` Nicholas Wourms
2002-10-28 13:31 ` Dave Jones
2002-10-28 14:05 ` Andrew Walrond
2002-10-28 14:42 ` Andrew Walrond
2002-10-28 15:02 ` Alan Cox
2002-10-30 7:29 ` Dave Cinege
2002-10-30 7:40 ` Jeff Garzik
2002-10-30 8:22 ` Dave Cinege
2002-10-30 8:37 ` Russell King
2002-10-30 9:32 ` Dave Cinege
2002-10-30 8:41 ` Jeff Garzik
2002-10-30 8:51 ` Erik Andersen
2002-10-30 9:00 ` Miles Bader
2002-10-30 9:06 ` Jeff Garzik
2002-10-30 9:19 ` Miles Bader
2002-10-30 9:26 ` Jeff Garzik
2002-10-30 9:38 ` Miles Bader
2002-10-30 9:42 ` Erik Andersen
2002-10-30 10:50 ` Jeff Garzik
2002-10-30 9:34 ` Russell King
2002-10-30 10:07 ` Dave Cinege
2002-10-30 9:36 ` Erik Andersen
2002-10-30 10:52 ` Jeff Garzik
2002-10-30 9:55 ` Dave Cinege [this message]
2002-10-30 9:59 ` Miles Bader
2002-10-30 10:24 ` Dave Cinege
2002-10-30 10:05 ` Jeff Garzik
2002-10-30 10:14 ` Dave Cinege
2002-10-30 10:24 ` Jeff Garzik
2002-10-30 10:42 ` Dave Cinege
2002-10-30 11:06 ` Jeff Garzik
2002-10-30 9:55 ` Dave Cinege
2002-10-30 10:29 ` Jeff Garzik
2002-11-04 2:13 ` Rob Landley
2002-11-04 7:39 ` Help needed with IRQ on Ali chipset Jacek Pliszka
2002-11-04 13:10 ` Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Alan Cox
2002-11-04 22:52 ` Werner Almesberger
2002-11-04 23:02 ` Jeff Garzik
2002-11-04 18:16 ` Rob Landley
2002-11-04 23:22 ` Werner Almesberger
2002-10-30 14:32 ` Alan Cox
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=200210300455.20883.dcinege@psychosis.com \
--to=dcinege@psychosis.com \
--cc=andersen@codepoet.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=miles@lsi.nec.co.jp \
/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