From: "Kevin P. Fleming" <kpfleming@cox.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.68 kernel no initrd
Date: Wed, 23 Apr 2003 09:36:09 -0700 [thread overview]
Message-ID: <3EA6C0F9.1010406@cox.net> (raw)
In-Reply-To: <200304231600.h3NG0aCs019316@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 23 Apr 2003 15:49:54 +0200, =?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?= said:
>
>>initrd gives much more flexibility.
>>I can make one kernel and use it on _all_ of my mashines, just change
>>initrd. quick, nice and flexible with proper initrd tools set.
>
>
> Amen. initrd isn't just for modules - I'd not need an initrd at all if I could
> figure out how to start up an LVM volume group from kernelspace - I suspect
> people with / on a RAID disk have similar issues...
>
Well, even though I'm working on a solution to that, it still involves
early userspace, just not the heavyweight "fake root" userspace that an
initrd represents. This is what the initramfs technology in 2.5.X is
for, so eventually (soon, hopefully) you'll be able to start md devices,
LVM volume groups, etc. from early userspace and not have to have any
autostart logic in the kernel nor will you have build and maintain an
initrd separate from the kernel.
next prev parent reply other threads:[~2003-04-23 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 4:39 2.5.68 kernel no initrd Dave Mehler
2003-04-20 17:24 ` Felipe Alfaro Solana
2003-04-22 21:58 ` Bill Davidsen
2003-04-23 13:49 ` Paweł Gołaszewski
2003-04-23 16:00 ` Valdis.Kletnieks
2003-04-23 16:36 ` Kevin P. Fleming [this message]
2003-04-23 21:54 ` Felipe Alfaro Solana
2003-04-24 20:19 ` Bill Davidsen
2003-04-24 21:54 ` Felipe Alfaro Solana
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=3EA6C0F9.1010406@cox.net \
--to=kpfleming@cox.net \
--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