[lxc-devel] For some reason tty1 is always bound to host's tty1
Andrian Nord
nightnord at gmail.com
Tue Nov 24 19:31:55 UTC 2009
On Tue, Nov 24, 2009 at 09:51:28PM +0300, Michael Tokarev wrote:
> It's the way how devices works. In container you've the same /dev/tty1
> as in host. Ditto for /dev/tty2, /dev/tty3 and so on.
Hm, you are right, my mistake, sorry - it was only /dev/tty1 as real device
others was just files, so only tty1 was working. Thanks for
clarification.
> You can:
>
> a) revoke access to tty devices using cgroup device access methods
Yes, yes, that's also my mistake - there is no need for ttys in cgroup
allow as 'lxc.tty' makes pty's
But I'm woundering if there is a good behaviour - if I hadn't configured
lxc.tty I still have ttys but from host. This is confusing, as man
lxc.conf says, that lxc.tty sets a number of existing ttys, and if you
will not set it - agetty will fail, while it does not.
Probably it should be changed into man lxc.conf than (some clarification
about devices) =)
Actually until now I haven't reasised that devices (except ptys) actually are
not virtualised, maybe it also should be noted into man lxc as a big fat
warning - for someone with openvz background it may be very confusing.
What do you thinK?
(And as now i've realized this, it opens some nice advantages =))
More information about the lxc-devel
mailing list