[systemd-devel] Graphical session targets as standard

Currently many Linux Distributions don't activate graphical-session.target and graphical-session-pre.target during login. I liked to know which software should ideally be in charge of that. So I can inform their developers about it, and have that behavior widely adopted. Alberto

Re: [systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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'd make a snapsh

Re: [systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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'd make a snapshot of `/foobar` and call > > it `/foobar2`

Re: [systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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 create subvolume

Re: [systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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 create subvolumes it will always > > > creat

Re: [systemd-devel] Starting an unit in user mode for all users

I think I'll leave the service like this: [Unit] Description=Xiccd Screen Color Profiler [Service] type=dbus ExecStart=/bin/xiccd Restart=always [Install] WantedBy=graphical-session.target dbus.service # Check on 2019-July if having graphical-session.target started on boot is standard for desk

Re: [systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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 always

Re: [systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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 always be the expected parent, especially when usin

Re: [systemd-devel] Starting an unit in user mode for all users

Well, that really isn't needed actually in this situation. I can just make the service wanted by the default.target and wait for dbus to start, as it is required. Alberto smime.p7s Description: S/MIME Cryptographic Signature ___

Re: [systemd-devel] Starting an unit in user mode for all users

What if before making the service I enabled the graphical-session.target? What do you think would be the proper way to do that? Alberto smime.p7s Description: S/MIME Cryptographic Signature ___ systemd-devel mail

[systemd-devel] systemd-tmpfiles subvolume handling vs. changing default btrfs root

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 always be the expected parent, especially when using btrfs snapshots to switch between various system states. Example l