Re: elogind status

[Andy Wingo]

On Thu 27 Aug 2015 15:21, address@hidden (Ludovic Courtès) writes:

> Andy Wingo <address@hidden> skribis:
>
>> First of all you need some extra file systems.  These paths provide a
>> documented interface to logind information:
>>
>>   (file-system
>>     (device "systemd")
>>     (mount-point "/run/systemd")
>>     (type "tmpfs")
>>     (check? #f)
>>     (flags '(no-suid no-dev no-exec))
>>     (options "mode=0755")
>>     (create-mount-point? #t))
>>   (file-system
>>     (device "systemd")
>>     (mount-point "/run/user")
>>     (type "tmpfs")
>>     (check? #f)
>>     (flags '(no-suid no-dev no-exec))
>>     (options "mode=0755")
>>     (create-mount-point? #t))
>
> We should add them to %base-file-systems or something.

Could we mount all of /run on a tmpfs?  Maybe that wouldn't work for
some reason.  If it's possible we should do it though.

>>            (mingetty-service "tty1" #:motd motd #:additional-session-modules 
>> (list pam-elogind))
>
> Now I understand; sorry for not reading messages in the right order!
>
> So I think %desktop-services should map over %base-services and simply
> add the session module, as I suggested in the other thread.  WDYT?
>
> If the user adds another login-capable service and forgets to add the
> ‘pam-elogind’ PAM service in there, there’s a problem, but maybe that’s
> acceptable as a first step?

I'll give it a go :)

Andy