[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100517094724.48632380.randy.dunlap@oracle.com>
Date: Mon, 17 May 2010 09:47:24 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Will Drewry <wad@...omium.org>
Cc: dm-devel@...hat.com, linux-kernel@...r.kernel.org, agk@...hat.com,
snitzer@...hat.com
Subject: Re: [RFC PATCH v2 2/2] init: boot to device-mapper targets without
an initr*
On Fri, 14 May 2010 20:41:41 -0500 Will Drewry wrote:
> Add a dm= kernel parameter modeled after the md= parameter from
> do_mounts_md. It allows for device-mapper targets to be configured at
> boot time for use early in the boot process (as the root device or
> otherwise).
dm=<blah>
documentation needs to be added to Documentation/kernel-parameters.txt and/or
Documentation/md.txt.
> The format is dm="name uuid ro,table line 1,table line 2,...". The
> parser expects the comma to be safe to use as a newline substitute but,
> otherwise, uses the normal separator of space. Some attempt has been
> made to make it forgiving of additional spaces (using skip_spaces()).
This "space in the arg string" has been tested, right?
It seems a bit odd to me. Most kernel parameter strings that I am familiar with
use punctuation for separating parameter parts.
> A mapped device created during boot will be assigned a minor of 0 and
> may be access via /dev/dm-0.
>
> An example dm-linear root with no uuid may look like:
>
> root=/dev/dm-0 dm="lroot none 0, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0"
>
> Once udev is started, /dev/dm-0 will become /dev/mapper/lroot.
>
> Signed-off-by: Will Drewry <wad@...omium.org>
> ---
> init/Makefile | 1 +
> init/do_mounts.c | 1 +
> init/do_mounts.h | 10 ++
> init/do_mounts_dm.c | 353 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 365 insertions(+), 0 deletions(-)
> create mode 100644 init/do_mounts_dm.c
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists