From: Pete Zaitcev <zaitcev@redhat.com>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB HardDisk Booting 2.4.20
Date: Thu, 30 Jan 2003 20:28:51 -0500 [thread overview]
Message-ID: <200301310128.h0V1SpL00558@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1043967125.21672.linux-kernel2news@redhat.com>
>> Is there a reason for not using initrd for this. That should let you
>> use any kind of root device even ones requiring user space work before
>> the real root is mounted.
>
> Yes, I believe there is. IMO initrd is too much of an annoyance to setup.
I believe it's going to be mandatory anyway, perhaps not as initrd,
but as initfs, but the result is the same. Besides, it's not
that big a deal if rpm -i makes initrd for you automagically.
-- Pete
prev parent reply other threads:[~2003-01-31 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 17:27 [PATCH] USB HardDisk Booting 2.4.20 Wesley Wright
2003-01-30 18:47 ` Alan Cox
2003-01-30 22:35 ` Samuel Flory
2003-01-31 2:21 ` Willy Tarreau
2003-02-01 15:00 ` Wesley Wright
2003-01-30 22:51 ` Wakko Warner
[not found] ` <mailman.1043967125.21672.linux-kernel2news@redhat.com>
2003-01-31 1:28 ` Pete Zaitcev [this message]
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=200301310128.h0V1SpL00558@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wakko@animx.eu.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