So, here at UBports we’re still using system-image with read-only rootfs - much like Ubuntu Core. As we’re transitioning our base to Ubuntu 20.04, we’re also (finally) transitioning to systemd, and that means adding more paths to
Upon studying, I’ve found that the
core snap (16.04 one) defines the directory as
synced (i.e. new files will be copied on every boot)
core18, this path is instead re-defined as
persistent transition (i.e. files are copied only on the first boot).
What I don’t understand is, when e.g. upgrade from
core18, won’t the newly-shipped units become not-enabled by default? I think that it was a problem before in
core which prompts the change from
persistent transition to
Isn’t it also a problem in core18+?
And, BTW: since Ubuntu Touch is special-purpose, personally I don’t really want the
/etc/systemd to be completely writable, but we need it so that a few selected units can be disabled (e.g.
ssh.service). Maybe there’s a better way to achieve this?