On Sat, Jul 23, 2005 at 01:50:10AM +0400, Nikita V. Youshchenko wrote: I had the same bug. It used to happen when you changed inittab to use more than 6 VCs, I had no idea it could race even on lower VCs. > I don't know which is the correct way to fix it. > Possible ways: > > *) ensure that X is never started on vt on which getty is going to be > started - in this case, having default Xservers files to set explicit vtN > is enough, and kdm 3.4 should provide some way to ensure that it will not > choose vt on which getty will be started later, Defining the vtN explicitly makes sense, especially as we seem to have standardised on having X running on vc7. People who change inittab to allocate vc7 for something else, should also change the display manager. A comment in the default inittab reminding of the issue could also help. > *) debian should not treat *dm like other services, and start it after > getty's, not before them I recommend against this one, as there's been quite some talking about invoking *dm earlier in the boot process, to speed up getting to the working environment. > *) some other way? What would be required for getty and X to allocate the vc without messing each other up? The cleaner solution (to me) would be to have getty not run if X is using the vc, or X running on another vc if getty is using it; but I reckon it might not be technically possible, at least judging from the past discussions on bug#116747, bug#47451 and bug#165241, Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <enrico@enricozini.org>
Attachment:
signature.asc
Description: Digital signature