Defining seats

Fabian Steiner lists at fabis-site.net
Sun Jan 28 12:00:59 PST 2007


Hello!

Sorry for the lag, but I am quite busy with some exams these days ...

William Jon McCann schrieb:
> Hi,
>
> On 1/18/07, William Jon McCann <mccann at jhu.edu> wrote:
> ...
>> Another question we need to answer is:
>> "Where and how are Sessions associated with a Seat?"
>>
>> At the moment, all locally attached sessions (ie. not XDMCP) are
>> assigned to Seat1.  So, we haven't really tried to answer this yet.

First of all, I will probably have to ask a rather stupid question: How 
do you define a "session"? Do you mean that a session can be regarded as 
a user who is currently working on one display (among three or four in 
multiseat environments)?

If yes, why can't we simply associate display :0 with seat1 and seat1, 
on the other hand, possesses a usb hub whose device permissions are set 
to the user who owns display :0? Or does this setup involve any 
shortcomings I did not think of?

>
> Here's an idea that is essentially an amalgam of the techniques used
> in menu spec, fdi files, and pam-console's console.perms.
>
> What if we just statically define each seat and use matching criteria
> to add new sessions to them?  The definition file might look something
> like the attached file.  Possible problems with this are a) what if a
> session matches the criteria for more than one seat b) what if a
> session doesn't match any seats.
>
> Not sure if this is a good idea yet.  What do you think?
>
Generally speaking, I like the idea of defining a seat in a format 
similar to the one you have proposed. As far as your questions are 
concerned, I would need more input (see my questions above).

Thanks,
Fabian





More information about the hal mailing list