Re: Masking mount units

[Phillip Susi <phill@xxxxxxxxxxxx>]

Lennart Poettering <lennart@xxxxxxxxxxxxxx> writes:

> Huh? Even after? Like, *forever*??? What's the point of that? Is
> gparted supposed to break your system for good and render your block
> devices unusable?
>
> I thought it was a partitioner, but I might have gotten that wrong?

Just because you move or resize a partition does not mean that it should
be auto mounted, even if it is delayed until after you close gparted.
That is just terrible UX.

Over the years gparted has gone through many different things to disable
auto mounting while it runs; hal-lock, udisks-inhibit, and currently it
masks all mount units.

Furthermore, it seems that the undesirable auto mounting behavior only
happens with systemd-239 and lower.  Newer versions of systemd seem to
have dropped this behavior by not setting the WantedBy=foo.device on the
mount point.  I assume this change was intentional?  I am a bit confused
as to why systemd no longer does auto mount yet you are shocked that
anyone would not want systemd to auto mount.

I would say that gparted should just drop the masking of mounts and be
done with it since it is no longer an issue, but they still wish to
support even older distros that are still supported, which right now
means Rocky Linux 8, which still has systemd-239, and still tries to
auto mount a moved partition unless gparted masks the mounts.