From: Erik Andersen <andersen@codepoet.org>
To: Dave Cinege <dcinege@psychosis.com>
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 01:51:49 -0700 [thread overview]
Message-ID: <20021030085149.GA7919@codepoet.org> (raw)
In-Reply-To: <200210300322.17933.dcinege@psychosis.com>
On Wed Oct 30, 2002 at 03:22:17AM -0500, Dave Cinege wrote:
> On Wednesday 30 October 2002 2:40, Jeff Garzik wrote:
>
> > untar - cpio is better.
>
> CPIO is commonly used and supported by NO ONE. (rpm, whoppee)
> Kernels even come tar'ed. KISS....
Both formats are simple. But cpio is simpler.
> > initrd - 99% moved out of the kernel
>
> Great...you just killed the high level embedded linux market, and
> the ability to play boot games from GRUB. (Network, etc)
> Initrd is a good **OPTION* to have to fall back on...
Umm. No. See initramfs below. initrds have always been an
evil abomination. They do things terribly wrong and eliminating
them will _save_ space in embedded linux system. When busybox is
compiled without the special-case initrd workarounds, it does get
a bit smaller...
> > do_mounts - moved out of the kernel completely
>
> And he's willing to completely purge initrd and do_mounts NOW???
>
> > initramfs - should be ready for Linus in the next day or so.
>
> Fire away with the 100K+ bloated POS. I'm backwards compatible,
> could easily add 'linked kernel image' support, and only increase
> the current code by 20K.
Perhaps you have misunderstood. initramfs is simply an initrd
infrastructure that is done right. You don't need to use klibc
in your initramfs if you don't want to. Its just a piece of
normal unhosed-up userspace. Populate it as you see fit.
> Do you have any serious sysadmin, clustering, or emebedded system
> IMPLEMENTATION experience?
Yes he has plenty of experience. He also has good taste. IMHO
the embedded world (as well as everyone else) wants initramfs --
it is a major improvement.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-10-30 8:45 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 [this message]
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
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=20021030085149.GA7919@codepoet.org \
--to=andersen@codepoet.org \
--cc=dcinege@psychosis.com \
--cc=jgarzik@pobox.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