So, compiled it and it now works. Here is how, version 2.02.167:
# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=x86_64-pc-linux-gnu --disable-udev-systemd-background-jobs --disable-dbus-service --disable-selinux --with-raid=none --with-udev-prefix="" --with-udevdir=/lib/udev/rules.d --with-thin=none --sbindir=/sbin --libdir=/lib
# make device-mapper
# new2dir make install_device-mapper
The website has incorrect instruction for install, my above is correct. Project website:
Comments:Question to dm-devel list Posted on 17 Nov 2016, 17:06 by admin
What I am asking for seems like a reasonable request, not just in the 'table' format in Kees' dm V5 patch, but also using with 'dmsetup create ...'.
Unless I have missed something in my reading of the docs, the device spec is limited to sd* or major:minor numbers, which is surprising.
So, I have raised this question on the 'dm-devel' mail list:
dm kernel boot params Posted on 17 Nov 2016, 14:20 by admin
Yesterday I compiled the 4.8.8 kernel with the device-mapper patches from Kees Cook, and the modules built-in.
However, came to a stop, as I realised the 'table' format only accepts normal device names (sd*) or major:minor numbers.
This is not satisfactory when booting off a removable drive. I need unique persistent naming. This is at the kernel boot parameters, prior to udev running.
I have sent an email to Kees, requesting if the patch could be extended to handle PARTUUIDs.