[MeeGo-SDK] running startmeego as root?
haitao.feng at intel.com
Tue Sep 14 09:09:12 UTC 2010
Before we release, I have done two things,
1. Run this script as a normal user, the result is Xephyr is running with software rendering and the performance is very slow.
2. After starting this script, switch to a normal user, Xephyr is running with gl acceleration and there is no permission problem.
So for your case, it is possible to split the startmeego-debug into two parts, use root to start Xephyr, and use the others to run /etc/xdg/autostart.
The general question is how to make Chroot+Xephyr more like a real machine. If we could achieve that, the permission problem could be solved automatically. Currently we use startmeego to start MeeGo UX, if it is a real machine, we should start MeeGo UX from init process and start all the MeeGo services and then startmeego.
From: meego-sdk-bounces at meego.com [mailto:meego-sdk-bounces at meego.com] On Behalf Of Patrick Ohly
Sent: 2010年9月14日 16:54
To: MeeGo SDK
Subject: [MeeGo-SDK] running startmeego as root?
Why is it necessary to run the "startmeego" script as root
This hides permission issues as they'll occur on real devices where apps
and most /etc/xdg/autostart session daemons run as a normal user.
What would it take to run the script as a normal user, or start it as
root and then become a normal user before running the session?
Normally I would now run some experiments, but I guess it is more
time-efficient to ask the authors of the script first ;-)
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
MeeGo-sdk mailing list
MeeGo-sdk at meego.com
More information about the MeeGo-sdk