[systemd-devel] systemd vs udev automount

[Paul D. DeRocco]

I've got a system (actually two similar systems) built with Yocto that use
systemd, but also have the udev-extraconf package, which includes a udev
rule and associated mount.sh script for automounting. It's doing strange
things, like mounting an additional partition on my main disk (which is
good), and then quietly unmounting it unless it is also listed in
/etc/fstab (which is bad). When it works, I see systemd messages in
journalctl about automounting, in addition to the messages generated by
the udev mount.sh, making me think these two systems are fighting with
each other. Is it possible that after mount.sh mounts it, systemd kicks
in, finds it's not in fstab, and unmounts it without logging anything?

But if I have systemd, should I even be using the udev automount rules in
the first place, or should I just create mount and automount units and
ditch udev-extraconf entirely? (Or are the autonet rules important?) My
ultimate goal is to have this additional partition on my main disk to be
automounted as early in the boot process as possible. I don't need (or
want) removable drives to be automounted anyway.

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco at ix.netcom.com