On Sat, 2017-02-18 at 03:10 +0100, Peter Kjellerstedt wrote: > This allows, e.g., cryptsetup to use libdevmapper without having to > pull in all of lvm2.
I'm experiencing an issue where both kpartx and cryptsetup hang infinitely. For kpartx, I traced it down to the lack of dmsetup udev rules in the rootfs, the same problem as in https://github.com/docker/docker/issues/22025#issuecomment-243943728 Adding lvm2 to my image fixed it, but that defeats the purpose of this patch... ;-} Peter, do you know which parts of lvm2 are needed for kpartx +libdevicemapper to work correctly? My initial attempt with moving just the udev rules to the libdevicemapper packages was either flawed or incomplete. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
