On 2014-01-09, 11:56 +0200, Jussi Laako wrote: > So you can think of tlm as headless version of login and/or *dm (it can > act in both roles). You can add GUI on top of it, but it is not > necessary. You can ask it to switch the user without having GUI > involved. It works in co-operation with systemd. The model is slightly > difference for Tizen compared traditional X dm's because with X the > Xserver is traditionally restarted between sessions but we expect to > support both models. > > TLM is trying to keep some kind of session alive on all seats (queried > from systemd). Either with default (guest) user or some other specific > user as requested. When session is terminated it falls back to the > default "guest" login. So that is the main difference to *dm's - it > doesn't sit in a login prompt waiting for input. This is the behavior > defined for IVI and I'd expect mobile is also supposed to have a session > always alive, although TLM is not strictly necessary for mobile as long > as it is single user. But it could help solving some of the problems > discussed...
Thanks for the explanation and info. Yeah, (standing in mobile POV) if we are not running a multi-user mobile, I guess most people needs to be convinced what's the value it brings. :) Since in mobile usage, we only need a very light tool (just as what user-session-launch is doing) to trigger the session open and wait for it to close. Yes, it may miss the TTY ownership claim code yet, that's only several lines of code anyway. But if we're planning a multi-user mobile, that's another story. Regards, Kangkai _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
