From: Alasdair G Kergon <agk@redhat.com>
To: Enric Balletbo Serra <eballetbo@gmail.com>
Cc: Kees Cook <keescook@chromium.org>, Will Drewry <wad@chromium.org>,
Guenter Roeck <groeck@google.com>,
Mike Snitzer <snitzer@redhat.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
David Zeuthen <zeuthen@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org, dm-devel@redhat.com,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Shaohua Li <shli@kernel.org>, Alasdair Kergon <agk@redhat.com>
Subject: Re: [dm-devel] [PATCH v6 0/3] dm: boot a mapped device without an initramfs
Date: Thu, 4 May 2017 14:20:07 +0100 [thread overview]
Message-ID: <20170504132007.GG4943@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20170504121452.GF4943@agk-dp.fab.redhat.com>
Some more thoughts with your example, dmsetup might look like:
# dmsetup create --bootformat "lroot:uuid,rw,0 2097152 linear 8:2 0, \
2097152 2097152 linear 8:3 0, 4194304 2097152 linear 8:4 0"
- also supporting creating multiple devices if the semi-colon is used
- colon to separate name from uuid, like we already do major:minor
- colon to separate other flags from rw if we need them in future
- splitting first on a unescaped semi-colons, then on the first two
unescaped commas, and then on unescaped commas and then unescaped spaces
within the table
- backslash escapes the following character so it is never a treated
as a separator
- lroot\:uuid\;\\\ \"\, would be a device with no uuid and the name
lroot:uuid;\ ", (on a non-udev system without name mangling)
# dmsetup ls --bootformat lroot
dm="lroot:uuid,rw,0 2097152 linear 8:2 0, 2097152 2097152 \
linear 8:3 0, 4194304 2097152 linear 8:4 0"
# dmsetup ls --bootformat
(all devices on one output line)
While the code also supports devices in the /dev/sda2 format for
convenience, please use the preferred 8:2 format in any implementation
and documented examples (to avoid the unnecessary dependency on /dev and
its dependencies).
Or with some alternative name for the option
--boot[format|param]
--short[format]
--kernelparam
--condensed
other suggestions?
dmsetup create --condensed
dmsetup ls --condensed
Alasdair
prev parent reply other threads:[~2017-05-04 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 16:42 [PATCH v6 0/3] dm: boot a mapped device without an initramfs Enric Balletbo i Serra
2017-04-18 16:42 ` [PATCH v6 1/3] dm: make some mapped_device functions available Enric Balletbo i Serra
2017-04-18 16:42 ` [PATCH v6 2/3] dm: export a table+mapped device to the ioctl interface Enric Balletbo i Serra
2017-04-18 16:42 ` [PATCH v6 3/3] init: add support to directly boot to a mapped device Enric Balletbo i Serra
2017-04-18 17:37 ` [PATCH v6 0/3] dm: boot a mapped device without an initramfs Kees Cook
2017-05-04 11:18 ` [dm-devel] " Enric Balletbo Serra
2017-05-04 12:14 ` Alasdair G Kergon
2017-05-04 13:20 ` Alasdair G Kergon [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=20170504132007.GG4943@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=eballetbo@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@google.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
--cc=wad@chromium.org \
--cc=zeuthen@google.com \
/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;
as well as URLs for NNTP newsgroup(s).