2. Nov 2015 14:17 by [email protected]:
> Under "Command Explanations" it reads "--with-capabilities: This > option enables libcap2 support". > > May we have a health warning here because if this option is enabled, > and the user goes on to build and install cryptsetup, they will find > that their cryptsetup build is completely broken. > > Result:- > > device-mapper: version ioctl on failed: Permission denied > Incompatible libdevmapper (unknown version) and kernel driver (unknown > version). > > I know that cryptsetup is not in the book, but I'm sure that I'm not > the only one that sees it as an essential tool for encrypting block > devices. Building libgcrypt with the "capabilities" option gave me > two days of building, rebuilding and testing other packages until I > discovered the cause of the problem. > > Richard > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: > http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page Thanks for the info! I use cryptsetup extensively and although I only use "prefix=/usr" when compiling, these things are often hard to find. BTW I use these custom init scripts (shameless plug) on LFS with builtin encryption support if you're interested: https://github.com/williex/init.bsd
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
