You are not logged in.
I was looking over the setup scripts for schroot to get a better sense for how the system works, when I stumbled across this comment in the file /etc/schroot/setup.d/10mount:
# Work around systemd insanity.
#
# Mark this mountpoint as private; some systems have / as a shared mountpoint.
# As an example, assume /home/m/ch is the chroot directory.
# schroot will mount -o bind /home/m/ch to /var/lib/schroot/mount/ch-123
# Afterwards, it will bind-mount /dev to /var/lib/schroot/mount/ch-123.
# With shared mountpoints, that mount will also show up in the original
# /home/m/ch. This is a problem once schroot mounted /home: the following
# mount of /tmp will show up in /var/lib/schroot/mount/ch-123/tmp,
# /home/m/ch/tmp and /home/m/ch/home/m/ch/tmp (!), which leads to failure
# on unmounting.
if [ "$(uname -s)" = "Linux" ]; then
mount --make-private "$3"
fi
I had no idea systemd made everything a shared mount by default, but now I'm wondering if it could have been the cause of some weird issues I had in the past. I guess it's another reason to be grateful I'm not using systemd anymore.
Offline
Systemd is such a disaster in so many ways, I'm also very grateful Devuan exists.
Offline