Bug#43486: getty/init/X locking issues

2005-09-06 Thread Samuel Thibault
LaMont Jones, le Tue 06 Sep 2005 08:35:19 -0600, a écrit : > On Tue, Sep 06, 2005 at 04:28:28PM +0200, Samuel Thibault wrote: > > LaMont Jones, le Tue 06 Sep 2005 08:26:27 -0600, a écrit : > > > And vt 2-15 when opened to check them, are also busy... > > No: vt_1_ is opened to check them. > > And

Bug#43486: getty/init/X locking issues

2005-09-06 Thread Samuel Thibault
LaMont Jones, le Tue 06 Sep 2005 08:26:27 -0600, a écrit : > On Mon, Sep 05, 2005 at 10:26:09PM +0200, Samuel Thibault wrote: > > I hope to have found some correct fix, please see patch. Yes, linux has > > been providing VT_GETSTATE since something like 1.0. > > > > Only vt 2-15 can be checked: 1

Bug#43486: getty/init/X locking issues

2005-09-06 Thread LaMont Jones
On Mon, Sep 05, 2005 at 10:26:09PM +0200, Samuel Thibault wrote: > I hope to have found some correct fix, please see patch. Yes, linux has > been providing VT_GETSTATE since something like 1.0. > > Only vt 2-15 can be checked: 1 is always busy, and the size of the mask > is limited. But that shoul

Bug#43486: getty/init/X locking issues

2005-09-06 Thread LaMont Jones
On Tue, Sep 06, 2005 at 04:28:28PM +0200, Samuel Thibault wrote: > LaMont Jones, le Tue 06 Sep 2005 08:26:27 -0600, a écrit : > > And vt 2-15 when opened to check them, are also busy... > No: vt_1_ is opened to check them. And _WE_ have them open as stdin. lamont

Bug#43486: getty/init/X locking issues

2005-09-05 Thread Samuel Thibault
Hi, Apparently, this bug is a duplicate of 216658, for which a patch was submitted, then corrected because of 224028/224067/226443/229788/257487, and then dropped because of 272689. I hope to have found some correct fix, please see patch. Yes, linux has been providing VT_GETSTATE since something