On Fri, Jan 03, 2014 at 10:06:44PM +0800, Yin Kangkai wrote:
> Hi,
>
> We're trying to bring up Tizen 3.0 mobile on IA devices. We're at a
> state that can barely boot into the menu screen. Lots of issues need
> to be addressed (these will be tracked soon in jira), among which 2
> biggest ones are SMACK and systemd, I will try to bring some systemd
> discussion in this thread.
>
> As we know, we're now running systemd v208 in 3.0
>
> systemd since v205 has its own user session implementation:
> user@.service. This is conflicting with our user-session@.service
> solution (which was patched into Tizen by Auke's team).
>
> Align and adopting the upstream user@.service seems a reasonable
> choice, at least to me. After I patched the vanilla user@.service with
> adding the missing "Environment=", seems the systemd user session can
> successfully bring up Tizen UI.
>
> Environment=DISPLAY=:0
> Environment=XDG_RUNTIME_DIR=/run/user/%U
> EnvironmentFile=/etc/sysconfig/tizen-mobile-ui
>
> However things seems not that simple...
>
> systemd user session ("systemd --user" in user@.service) is run
> through systemd-logind, which in turn is triggered each time a user
> login.
>
> Combine the user session setup currently in Tizen mobile: most
> middle-ware services including X and enlightenment are launched though
> user session. This leads to a annoy effect: if you open a sdb
> connection, those user session services will be triggered to run again
> (yes including the X and e17).So as the ssh login? -- Thanks, Chengwei > > So in short, the Tizen mobile user session setup need to be refactor > carefully. > > Auke and Patrick, do you already have any plan here? > > At the same time, I am trying to understand more about the systemd > upstream user session code and plan, any comments and suggestions are > welcomed. > > Thanks, > Kangkai
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
