This is weird ...
My /home directory is set up somewhat strangely, as in I've got two raw
partitions, I've put dm-integrity on them, raided them together, then
put lvm on top of that.
Which got me into a bind with fstab. I've created a systemd service,
which fires up dm-integrity on those two partitions. But I get the
impression it doesn't run until fstab completes. Catch-22 - fstab tries
to mount /home, but it can't until dm-integrity has made the volume appear!
So I created a systemd mount unit for /home, which only runs after
dm-integrity. Great - I enabled it and it appeared to work!
Only problem, startplasma-wayland now dumped me at a blank screen.
Now for the weirdo. I disabled it, thinking I would have to log in as
root, mount /home, and go from there. Except that, when I logged in,
/home was mounted and startplasma-wayland worked!
systemctl tells me mount.home is disabled, but also tells me that it ran
and mounted the drive.
So what on earth is going on, and more importantly, what am I
misunderstanding or doing wrong. I would very much like to know why it's
working, when I think it shouldn't be!
Cheers,
Wol
