Am 21.04.20 um 15:26 Uhr schrieb Wieschke, Thomas:
> I'm writing on a RH 7 system to an automounted FS and get an disruption
> because systemd (??) is,
> besides working in this directory, obviously trying an umount in the
> background.
> The umount doesn't work because the FS is in use (returned
Am 27.12.19 um 19:08 Uhr schrieb Jeffrey Walton:
I have three services I need to automatically start sometime around
boot in a mostly unattended environment. My services depend on other
services, like the USB bus and GUI environment.
My question is, how can I list the various service units to de
pshot contains everything which is relevant for a
complete rollback of the system including /boot and /.snapshots
(containing snapper metadata). Splitting this up into three (or more)
separate subvolumes would be a major architectural change. I'll think
about this over the weekend, but I don&
Am 27.06.2018 um 16:34 schrieb Lennart Poettering:
On Mi, 27.06.18 15:50, Ignaz Forster ([email protected]) wrote:
By recursive snaphots I really mean recursive snapshots, i.e. if you
have a subvolume called `/foobar` and there's a subvolume below it
called `/foobar/var`, and you
Am 27.06.2018 um 15:37 schrieb Lennart Poettering:
On Mi, 27.06.18 15:09, Ignaz Forster ([email protected]) wrote:
Am 27.06.2018 um 13:39 schrieb Lennart Poettering:
On Mi, 27.06.18 13:02, Ignaz Forster ([email protected]) wrote:
Hello,
when using systemd-tmpfiles' feature to c
Am 27.06.2018 um 13:39 schrieb Lennart Poettering:
On Mi, 27.06.18 13:02, Ignaz Forster ([email protected]) wrote:
Hello,
when using systemd-tmpfiles' feature to create subvolumes it will always
create the new subvolume as a child of the subvolume of the given path. This
however may not a
In any case a corresponding implementation would mean additional
handling for generating an fstab entry and mounting the subvolume if the
subvolume is not created as a subdirectory of an existing subvolume.
Would this be an approach that would be acceptable upstream? Please note
that I'
