From: Richard Weinberger <richard.weinberger@gmail.com>
To: helen.koike@collabora.com
Cc: Will Drewry <wad@chromium.org>,
snitzer@redhat.com, linux-doc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
device-mapper development <dm-devel@redhat.com>,
linux-lvm@redhat.com, enric.balletbo@collabora.com,
kernel@collabora.com, agk@redhat.com
Subject: Re: [linux-lvm] [PATCH 0/2] boot to a mapped device
Date: Wed, 26 Sep 2018 09:16:57 +0200 [thread overview]
Message-ID: <CAFLxGvzCDOTR4stPmp1TTLkQ39x3e8MQuL=AR754abKc5skhpA@mail.gmail.com> (raw)
In-Reply-To: <cover.1537936397.git.helen.koike@collabora.com>
Helen,
On Wed, Sep 26, 2018 at 7:01 AM Helen Koike <helen.koike@collabora.com> wrote:
>
> This series is reviving an old patchwork.
> Booting from a mapped device requires an initramfs. This series is
> allows for device-mapper targets to be configured at boot time for
> use early in the boot process (as the root device or otherwise).
What is the reason for this patch series?
Setting up non-trivial root filesystems/storage always requires an
initramfs, there is nothing
wrong about this.
> Example, the following could be added in the boot parameters.
> dm="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
Hmmm, the new dm= parameter is anything but easy to get right.
--
Thanks,
//richard
next prev parent reply other threads:[~2018-09-26 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 5:00 [linux-lvm] [PATCH 0/2] boot to a mapped device Helen Koike
2018-09-26 5:00 ` [linux-lvm] [PATCH 1/2] dm ioctl: add a device mapper ioctl function Helen Koike
2018-09-26 5:00 ` [linux-lvm] [PATCH 2/2] init: add support to directly boot to a mapped device Helen Koike
2018-09-26 16:09 ` Randy Dunlap
2018-09-26 5:02 ` [linux-lvm] [PATCH 0/2] " Helen Koike
2018-09-26 7:16 ` Richard Weinberger [this message]
2018-09-27 14:23 ` Mike Snitzer
2018-09-27 16:36 ` Kees Cook
2018-09-27 18:31 ` Mike Snitzer
2018-10-19 16:27 ` Helen Koike
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='CAFLxGvzCDOTR4stPmp1TTLkQ39x3e8MQuL=AR754abKc5skhpA@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=enric.balletbo@collabora.com \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=snitzer@redhat.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 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).