>-----Original Message----- >From: [email protected] [mailto:[email protected]] On >Behalf Of Yin Kangkai >Sent: Thursday, January 09, 2014 11:02 AM >To: Jussi Laako >Cc: [email protected] >Subject: Re: [Dev] systemd user session in Tizen 3.0 mobile > >On 2014-01-08, 11:38 +0200, Jussi Laako wrote: >> On 6.1.2014 10:30, Yin Kangkai wrote: >> > We can fiddle with PAM configurations (/etc/pam.d) to work around >> > this. >> >> Just a short note, partially related to this is that we have our >> ongoing work of tlm (Tizen Login Manager) here: >> https://github.com/01org/tlm >> >> It is still very much work-in-progress with lot of things missing, but >> we have some PAM configs and code ready and it auto-creates sessions >> for each seat presented by systemd. >> >> Some of the environment setup is done as part of session creation, >> similar way as login/gdm/kdb/lightdm do. >> >> So some of the session related environment setup is supposed to happen >> there (as planned earler for the multiuser support). > >Some basic questions: > >once this is ready, it is replacing the user-session-launch that we're using >now in >[email protected]? > >And it is responsible of claiming the TTY ownership for the login user? as I >asked >in systemd mailing list: >http://lists.freedesktop.org/archives/systemd-devel/2014-January/016079.html >
[ Wu, Zhiwen] We met the same problem when bring up mobile wayland image. See https://lists.tizen.org/pipermail/dev/2014-January/001440.html Currently, we used an udev rule to work around this issue like what IVI did (see https://review.tizen.org/gerrit/gitweb?p=profile/ivi/udev-rules.git;a=commit;h=6d1a6add2492f618412b8646d39c017e09fb5332). But it is expected that the "login manager" to prepare the TTY for login user. >Thanks, >Kangkai >_______________________________________________ >Dev mailing list >[email protected] >https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
