From: Dave Cinege <dcinege@psychosis.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>,
landley@trommello.org, linux-kernel@vger.kernel.org,
reiser@namesys.com, alan@lxorguk.ukuu.org.uk, davem@redhat.com,
boissiere@adiglobal.com
Subject: Re: Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list.
Date: Wed, 30 Oct 2002 04:32:23 -0500 [thread overview]
Message-ID: <200210300432.23107.dcinege@psychosis.com> (raw)
In-Reply-To: <20021030083751.A25178@flint.arm.linux.org.uk>
On Wednesday 30 October 2002 3:37, Russell King wrote:
> On Wed, Oct 30, 2002 at 03:22:17AM -0500, Dave Cinege wrote:
> > Do you have any serious sysadmin, clustering, or emebedded system
> > IMPLEMENTATION experience?
>
> Please don't get personal, or you'll end up in peoples kill files.
It's not personal. He made a wild 'No one needs any of this[initrd]'
statement. Is he coming from 'this looks like a good idea'(coder) or
'I can prove this is a good idea through experience examples.'
(systems engineer)
I can prove to you (for one thing) that when the shit hits the
fan (disaster recovery) initrd is a good option to have.
> ARM is basically embedded today, and I support initramfs. I don't
> believe your "embedded system" argument holds any water. Yes, it
High level embedded systems...low level systems could care less.
> is a different way of doing things, but it can (and does here)
> support initrd images.
The point to this is:
Linking an image into the kernel LOOKS nice, but I would sure not
want to deploy it because it becomes an adminstation nightmare.
Even with initrd, a single file can be a problem...this is why my
patch supports extracting multiple tar.gz archives....to maintain
configuration modularity.
Having an image in the kernel is not a bad thing...making it the
only option is.
Dave
--
The time is now 22:48 (Totalitarian) - http://www.ccops.org/
next prev parent reply other threads:[~2002-10-30 9:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 2:17 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 [this message]
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
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=200210300432.23107.dcinege@psychosis.com \
--to=dcinege@psychosis.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=boissiere@adiglobal.com \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®