Re: [dm-devel] [PATCH v5 0/3] init: add support to directly boot to a mapped device

Barry Kauler wrote: > However, it seems that the 'table' format when using 'dmsetup create', > and also in the kernel boot params, that devices can only be specified > by the normal name (/dev/sd*) or by major:minor numbers. > basically, my question is, could the 'table' format be extended to >

Re: [dm-devel] [PATCH v5 0/3] init: add support to directly boot to a mapped device

Hi, I have just joined this list. I am a newcomer to using device-mapper. I currently maintain Quirky Linux, prior to that, Puppy Linux. Puppy uses overlay filesystems, usually aufs, to achieve what could also be done, partly, with device-mapper. Puppy has a initramfs, however, Quirky is a

Re: [dm-devel] [PATCH v5 0/3] init: add support to directly boot to a mapped device

On Fri, Feb 26 2016 at 2:59pm -0500, Kees Cook wrote: > On Fri, Feb 26, 2016 at 11:21 AM, Mike Snitzer wrote: > > On Fri, Feb 26 2016 at 1:52pm -0500, > > Kees Cook wrote: > > > >> On Fri, Feb 26, 2016 at 8:53 AM, Mike Snitzer

Re: [dm-devel] [PATCH v5 0/3] init: add support to directly boot to a mapped device

On Fri, Feb 26, 2016 at 11:21 AM, Mike Snitzer wrote: > On Fri, Feb 26 2016 at 1:52pm -0500, > Kees Cook wrote: > >> On Fri, Feb 26, 2016 at 8:53 AM, Mike Snitzer wrote: >> > On Mon, Feb 22 2016 at 1:55pm -0500, >> > Kees Cook

Re: [dm-devel] [PATCH v5 0/3] init: add support to directly boot to a mapped device

On Fri, Feb 26 2016 at 1:52pm -0500, Kees Cook wrote: > On Fri, Feb 26, 2016 at 8:53 AM, Mike Snitzer wrote: > > On Mon, Feb 22 2016 at 1:55pm -0500, > > Kees Cook wrote: > > > >> On Sun, Feb 21, 2016 at 2:08 PM, Alasdair G

Re: [dm-devel] [PATCH v5 0/3] init: add support to directly boot to a mapped device

On Mon, Feb 22 2016 at 1:55pm -0500, Kees Cook wrote: > On Sun, Feb 21, 2016 at 2:08 PM, Alasdair G Kergon wrote: > > On Sat, Feb 20, 2016 at 10:13:49AM -0800, Kees Cook wrote: > >> This is a resurrection of a patch series from a few years back, first >