[Dev] Tizen 3 services: use case for multi user

Jussi Laako jussi.laako at linux.intel.com
Tue Sep 9 07:58:12 GMT 2014


On 8.9.2014 15:55, Dominig ar Foll wrote:
> The concept of seat represent a display.
> display may or may not have a dedicated input device.
> (typically the driver and passenger seat display shares same input
> devices while the back seat have their dedicated control.

No, seat may have one or more displays. Seat is group of displays and 
input devices that belong together (as already defined by 
udev/systemd/weston).

> In  the model use for defining Tizen 3 :
>
>   - User session are not allocated to a given seat.

Yes they are, unless you plan to completely change logind or switch away 
from systemd in general.

>   - An application is started on a given seat and later can be reseated.

You re-seat entire sessions, not single applications.

> The set of application run by one user can be shared between multiple
> seats while applications from various users can run on he same seat.

This sounds insane. You cannot share applications across user sessions. 
When you store data from the application, who's home directory it will 
end up in?



More information about the Dev mailing list