Hi
On Tue, Dec 16, 2014 at 9:19 AM, Daniel Stone wrote:
>> I reasoned that user access to the tty should be set up by the kernel
>> policies, and we should not enforce the policy at weston level. If the
>> system is configured in this way, then a user with enough permissions can
>> start up westo
Hi,
On 8 December 2014 at 10:34, Damian, Alexandru
wrote:
>
> What annoyed me was weston silently ignoring the tty argument in certain
> conditions (you have to specify a new user argument while being root).
>
Oh, I totally agree. We should have an error message stating that --tty is
not valid w
What annoyed me was weston silently ignoring the tty argument in certain
conditions (you have to specify a new user argument while being root).
I reasoned that user access to the tty should be set up by the kernel
policies, and we should not enforce the policy at weston level. If the
system is con
Hi,
On Wednesday, October 2, 2013, Alex DAMIAN
wrote:
>
> Current behaviour of the tty parameter is to take effect
> only if there is a new user starting up.
>
> Since it is useful to start weston-launch with a command line
> specified tty, I'm changing the semantics of the tty parameter:
>
> * t
From: Alexandru DAMIAN
Current behaviour of the tty parameter is to take effect
only if there is a new user starting up.
Since it is useful to start weston-launch with a command line
specified tty, I'm changing the semantics of the tty parameter:
* the argument to the --tty parameter is now man
