Contents
Summary
There are two fundamental modes of a linux install: text and graphical. Linux also supports virtual consoles: the ability to switch to different screens via <ctrl>+<alt>+Fn.
In text mode, currently VT1 through 6 all provide text prompts to allow users to login (agetty). In graphical mode the first VT is transitioned into a graphical login prompt (gdm, kdm etc.) but VT2 through 6 are still "reserved" for text logins should the user switch to them.
We should instead provide graphical login screens on VT2 through 6 should the user switch to them.
Owner
- Name: Colin Guthrie
- Email: colin@mageia.org
Resources
Nothing specific, just regular testing.
Current status
- Targeted release: Mageia 3
- Last updated: 2012/06/05
- Percentage of completion: 0%
Detailed Description
If a user has opted for a graphical system, login prompts should reflect this choice for the most part. Multi-user systems should then become more natural to use. One text login screen should be reserved even in graphical mode such that any fundamental problem with graphical logins are easily worked around (without the need to isolate to a text target).
(alien) WISH: keep VT12 for kernel messages, have VT11 as a forced textonly login, in case of emergency. but have VT1-VT10 identical consistent setup.
Why it would be good for Mageia to include it
It brings a degree of consistency to how graphic and text modes operate: In text mode, VT 1 through 6 will display text login prompts, in graphical mode, VT 1 through 6 will display graphical login prompts. If a shared computer in a multi-user household is rebooted, particular users may become used to using a particular VT for their login. If the machine is rebooted, the user who "normally" uses VT2 may be the first to try and login. They can simply switch to VT2 and login there and leave VT1 for the other user.
Test case
Switch VTs in graphical mode and in text mode.
Software / Packages Dependencies
- gdm: Support needs to be added to tell it to activate on a given VT. Ideally a dbus protocol should be defined that can be implemented by all DMs to tell them to start themselves on a particular VT.
- systemd: autovt@.service should no longer point unconditionally to getty@.service. It should instead be a wrapper utility that will attempt the starting of a login screen via the afore mentioned dbus protocol and if that fails, it will revert back to getty, thus proving the required functionality.
- $DM: Other DMs (kdm, lxdm etc.) should also then be updated to support this approach.
What could disrupt development of this new feature
Upstream support for such a feature will be required. Preliminary talks with gdm upstream suggest this would be a generally desired feature overall.
Planning
Discussions with upstream have already taken place, but more general planning of the required changes are still needed.
Contingency
Keep the current setup.
