From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 27 Sep 2018 10:23:29 -0400 From: Mike Snitzer Message-ID: <20180927142328.GA4074@redhat.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [linux-lvm] [PATCH 0/2] boot to a mapped device Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Richard Weinberger Cc: Will Drewry , linux-doc@vger.kernel.org, device-mapper development , LKML , helen.koike@collabora.com, linux-lvm@redhat.com, enric.balletbo@collabora.com, kernel@collabora.com, agk@redhat.com On Wed, Sep 26 2018 at 3:16am -0400, Richard Weinberger wrote: > Helen, > > On Wed, Sep 26, 2018 at 7:01 AM Helen Koike 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.