From 4ce1cee76d0a2773ea5d05234b968893082d7b4f Mon Sep 17 00:00:00 2001 From: Jax Calder Date: Sun, 25 Oct 2026 19:39:03 +0000 Subject: [PATCH] libsystemd: load the configuration directory of a mount point by itself libsystemd already hears every mount and unmount (dmfsi's _mount_changed dif), so the loading of /cfg/services and cfg/rules is its own business again, not an API for a service to call: on a mount it adds the units, templates and rules to what is loaded and starts the units (dependency order, first definition of a name stays, %m = the mount point), on an unmount it runs the rules' `remove` units, then stops and drops exactly what came from there. A full reload keeps them; the units directory of libsystemd_scan() is never loaded twice. The module search path is invalidated before the units start: the new file system may hold their modules (/mnt/