[systemd-devel] New mount restriction? -- from Systemd policy?
Linda Walsh
suse at tlinx.org
Mon Apr 8 15:45:31 PDT 2013
Andrey Borzenkov wrote:
> This seems to be yest another fallout of changed systemd policy - it
> now makes / shared mount.
>
> bor at opensuse:~> sudo mount --move /tmp/old /tmp/new
> mount: wrong fs type, bad option, bad superblock on /tmp/old,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
> bor at opensuse:~> sudo mount --make-private /
> bor at opensuse:~> sudo mount --move /tmp/old /tmp/new
> bor at opensuse:~> cd
----
Is that another systemd change, really? Aren't fs's mounted
on initrd before systemd is invoked?
Is it something that systemd needed to have? I.e. if it is made
private would systemd care? If not, why would it have
been made shared?
Maybe a default in mount for root changed?
More information about the systemd-devel
mailing list