[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180927142328.GA4074@redhat.com>
Date: Thu, 27 Sep 2018 10:23:29 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: Richard Weinberger <richard.weinberger@...il.com>
Cc: helen.koike@...labora.com,
device-mapper development <dm-devel@...hat.com>,
agk@...hat.com, LKML <linux-kernel@...r.kernel.org>,
enric.balletbo@...labora.com, Will Drewry <wad@...omium.org>,
linux-doc@...r.kernel.org, linux-lvm@...hat.com,
kernel@...labora.com
Subject: Re: [PATCH 0/2] boot to a mapped device
On Wed, Sep 26 2018 at 3:16am -0400,
Richard Weinberger <richard.weinberger@...il.com> wrote:
> Helen,
>
> On Wed, Sep 26, 2018 at 7:01 AM Helen Koike <helen.koike@...labora.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.
Exactly. If phones or whatever would benefit from this patchset then
say as much.
I will not accept this patchset at this time.
> > 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.
No, it isn't.. exposes way too much potential for users hanging
themselves.
Powered by blists - more mailing lists