12216 2017-10-11 00:52:46 +0000 dm-verity boot support 2017-10-12 09:20:34 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.5 x86 Multiple RESOLVED NOTABUG Undecided enhancement --- 0 jonathan.yong ross.burton meta.mr.watcher meta.watcher --- --- Yes (doc changes required) oldest_to_newest 77509 0 jonathan.yong 2017-10-11 00:52:46 +0000 dm-verity is a platform independent way of verifying the root filesystem at the block level, but consequently, the filesystem is read-only. So far, one of the notable issues found is pulseaudio failing because /home is read-only. 77513 1 ross.burton 2017-10-11 09:07:03 +0000 I'd always expected /home would be a separate mount point under dm-verity so that the system is actually useful. 77514 2 ross.burton 2017-10-11 09:46:18 +0000 Pulseaudio wants to write state to $HOME. So will others. You either need to have a tmpfs for state/sockets/etc (in /run or similar) which you can configure pulseaudio to use, or put $HOME in a separate read/write partition. I've also a hunch that you may be using sysv and switching to systemd will make pulse use /run, but then again there may be a hard-coded $HOME in Pulseaudio somewhere. I'm going to close this as it's too vague, as you said dm-verity works and RefKit also use it to validate the installer media. Please open specific bugs for specific issues that are not just integration issues in your system. 77529 3 jonathan.yong 2017-10-11 23:44:33 +0000 We're using systemd, and yes, we're already aware of the need for writeable /home. I am not aware of the refkit, is that a layer to enable dm-verity support? 77539 4 ross.burton 2017-10-12 09:20:34 +0000 refkit is a distro that targets IoT (hosted on git.yoctoproject.org). Reclosing, please file concrete bugs for concrete problems.