On Sat, Jul 27, 2013 at 8:03 PM, Oleksii Shevchuk wrote:
>> For most other things: there are actually very few things that should
>> use the environment as a data store and to pass around
>> config/policy/runtime information; it's just a too broken and static
>> model that should no be used in thi
> For most other things: there are actually very few things that should
> use the environment as a data store and to pass around
> config/policy/runtime information; it's just a too broken and static
> model that should no be used in this century.
Probably yes. But who and when will reimplement al
On Sat, Jul 27, 2013 at 7:30 PM, Oleksii Shevchuk wrote:
>> It is, and always was, designed as a --user daemon, just like the name
>> suggests, not as a session daemon. With the upcoming kdbus work,
>> systemd --user will be the creator and owner of the user's bus, and
>> there can and should only
> It is, and always was, designed as a --user daemon, just like the name
> suggests, not as a session daemon. With the upcoming kdbus work,
> systemd --user will be the creator and owner of the user's bus, and
> there can and should only be one per user and no per session.
I understand this. But..
On Sat, Jul 27, 2013 at 6:24 PM, Oleksii Shevchuk wrote:
>
>> It all needs still some work how things should work in the end
>
> Unfortunately, with shared session daemon
It is, and always was, designed as a --user daemon, just like the name
suggests, not as a session daemon. With the upcoming kd
> It all needs still some work how things should work in the end
Unfortunately, with shared session daemon there is no way to have
display session managed by systemd -- too many problems should be
solved. Mainly with attaching services to active seat/session (for
polkit), environment propagation
On Sat, Jul 27, 2013 at 4:50 PM, Léo Gillot-Lamure
wrote:
> All these big changes from systemd 205 seem good and yummy, but how do this
> relates to the systemd --user sessions ?
>
> I used to launch all my desktop components (WM, panel, applets,
> pulseaudio...) using systemd user units, systemd
Hi.
All these big changes from systemd 205 seem good and yummy, but how do this
relates to the systemd --user sessions ?
I used to launch all my desktop components (WM, panel, applets,
pulseaudio...) using systemd user units, systemd --user itself being
launched by my display manager, but now it
