All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: rbenyehuda@manz.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 07:22:36 -0800	[thread overview]
Message-ID: <4EEA10BC.3000906@zytor.com> (raw)
In-Reply-To: <1323962398.11872.3.camel@raz>

On 12/15/2011 07:19 AM, Raz Ben Yehuda wrote:
>>
>> 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 ?
>

There are problems with the whole concept of "cannot use initramfs".  We 
allow the initramfs to be integrated with the kernel image for a reason, 
for example.

I'm obviously ranting on this in part to make people think about what 
they are doing, and partly to remind that the more complex the in-kernel 
root-mounting code get, the more it might be worth reconsidering klibc 
in the kernel build tree.

	-hpa


  reply	other threads:[~2011-12-15 15:22 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   ` Subject:[PATCH 1:1] boot paramer "root=" gets a list of devices Raz Ben Yehuda
2011-12-15 15:22     ` H. Peter Anvin [this message]
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=4EEA10BC.3000906@zytor.com \
    --to=hpa@zytor.com \
    --cc=LBrafman@manz.com \
    --cc=RSlutsker@manz.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raziebe@gmail.com \
    --cc=rbenyehuda@manz.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.