From: Peter Samuelson <peter@cadcamlab.org>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: Jeremy <prrthd25@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: VFS: Cannot open root device
Date: Tue, 6 Mar 2001 14:22:32 -0600 [thread overview]
Message-ID: <20010306142232.C28368@cadcamlab.org> (raw)
In-Reply-To: <20010303011000.1832.qmail@web4203.mail.yahoo.com> <3AA04B88.9B4E5AF8@coplanar.net>
In-Reply-To: <3AA04B88.9B4E5AF8@coplanar.net>; from jerj@coplanar.net on Fri, Mar 02, 2001 at 08:40:24PM -0500
[Jeremy Jackson]
> try command 'man mkinitrd' under redhat for hints about initial
> ramdisk.
I have been puzzled about this for quite some time. Why exactly does
everyone always recommend using 'mkinitrd' on Red Hat systems? It
seems to me that if you are compiling a kernel for a specific server
anyway, it is a much more reliable proposition to just compile in
whatever drivers you need to boot.
initrd's are inherently clumsy and fragile, to my way of thinking.
I've always thought they should only be used to support diverse or
unknown hardware, or odd cases like crypto loopback root. Are there
other advantages to 'mkinitrd' in the case of a custom kernel for a
single machine?
Peter
next prev parent reply other threads:[~2001-03-06 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 1:10 Jeremy
2001-03-03 1:40 ` Jeremy Jackson
2001-03-06 20:22 ` Peter Samuelson [this message]
2001-03-06 21:04 ` Jeremy Jackson
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=20010306142232.C28368@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=jerj@coplanar.net \
--cc=linux-kernel@vger.kernel.org \
--cc=prrthd25@yahoo.com \
/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®