From: Raz Ben Yehuda <rbenyehuda@manz.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "wad@chromium.org" <wad@chromium.org>,
"kay.sievers@vrfy.org" <kay.sievers@vrfy.org>,
Rasty Slutsker <RSlutsker@manz.com>,
Lior Brafman <LBrafman@manz.com>, <raziebe@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: Subject:[PATCH 1:1] boot paramer "root=" gets a list of devices
Date: Thu, 15 Dec 2011 17:19:58 +0200 [thread overview]
Message-ID: <1323962398.11872.3.camel@raz> (raw)
In-Reply-To: <4EEA0C05.4030907@zytor.com>
On Thu, 2011-12-15 at 16:02 +0100, H. Peter Anvin wrote:
> On 12/15/2011 01:13 AM, Raz Ben Yehuda wrote:
> > From: Raz ben yehuda<rbenyehuda@manz.com>
> >
> > Patch is aimed to bypass the need for initramfs when it is not
> > known which disk has the root file system.
> >
> > Example: The kernel boot parameter "root=/dev/sda1,/dev/sdc1,/dev/sdb4".
> > Check if /dev/sda1 exists ,if /dev/sda1 does not exist then try
> > /dev/sdc1 an so on upto the first a device that exists ( ROOT_DEV != 0 ),
> > else use the last device as the mount device.
> >
> > patch is on top of 3.2-rc5.
> >
> > Signed-off-by: Raz Ben Yehuda<rbenyehuda@manz.com>
> >
>
> To which point I have to ask, once again, at which point we stop putting
> this stuff in the kernel to "bypass the need for initramfs"...
because there are times where we cannot use initramfs. is this a problem
with way i phrase or with with the whole idea ?
> -hpa
next parent reply other threads:[~2011-12-15 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1323940396.16032.2.camel@raz>
[not found] ` <4EEA0C05.4030907@zytor.com>
2011-12-15 15:19 ` Raz Ben Yehuda [this message]
2011-12-15 15:22 ` Subject:[PATCH 1:1] boot paramer "root=" gets a list of devices H. Peter Anvin
2011-12-15 18:11 ` Kay Sievers
2011-12-18 8:54 ` Raz Ben Yehuda
2012-01-04 17:48 ` Will Drewry
2011-12-15 9:17 Raz Ben Yehuda
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=1323962398.11872.3.camel@raz \
--to=rbenyehuda@manz.com \
--cc=LBrafman@manz.com \
--cc=RSlutsker@manz.com \
--cc=hpa@zytor.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raziebe@gmail.com \
--cc=wad@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.