Ticket #353 (closed enhancement: wontfix)

Opened 15 years ago

Last modified 12 years ago

tty mode login for clusters (a la Ctrl-P)

Reported by: geofft Owned by:
Priority: low Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:


It would eventually be nice to provide a TTY login mode, both because it's probably faster than an X login, and in case your X session or the system's X config is broken.

This should be easy by adding a GDM custom command to essentially openvt schroot -c login getty.

Change History

comment:1 Changed 14 years ago by jdreed

  • Milestone set to Fall 2010

comment:2 Changed 14 years ago by jdreed

  • Status changed from new to committed

IIRC, back in the day, we decided that we didn't really want P anymore, and GDM custom commands are harder now (and we don't need yet another gdm login applet).

I've committed a change to debathena-xsession which does the following:

  • Creates a new session called "Athena TTY Mode" (the name is negotiable)
  • Add /etc/X11/Xsession.d/00debathena-gdm-sucks, which checks for that session type, kills pulseaudio if you're over quota, runs xterm -ls (so you get the Athena tty login sequence), and then exits.

Note that if we change the session name, we need to change it in the message text in 01debathena-quota (see #600)

comment:3 Changed 14 years ago by jdreed

  • Status changed from committed to new
  • Milestone changed from Fall 2010 to The Distant Future

See also #715.

This ticket is for actual tty login on a VT.

comment:4 Changed 13 years ago by jdreed

I'm tempted to wontfix this unless someone can explain to me why this is needed in addition to the existing TTY login. It won't be faster, and if X config is broken, you can't see the login screen to begin with. And anything that's not a GDM session is Effort.

I'll reconsider it if we give up on upstream and bring back dm/xlogin.

comment:5 Changed 12 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to wontfix

So, if we go the openvt route, then we have yet another VT open, and yet another state a machine could be in. There's also the potential for abuse, which is why we disable the VTs.

Note: See TracTickets for help on using tickets.