Re: [gdm-list] List of useful GDM features/config options

[Brian Cameron <Brian Cameron Sun COM>]

Hans:

- DefaultPath/RootPath are probably desirable.  I'd say users/sysadmins
  would want to have the freedom to configure this, not just at
  distro compile time.

- User/Group are also desirable.  While not necessary, I think
  users/sysadmins should have the freedom to configure what users
  and groups exist on their systems.

- Ability to configure the Xserver command.  It's probably necessary
  to have the ability to configure different Xserver commands on
  a per-display basis.

- FlexibleXservers is probably also needed, as well as a configuration
  option that turns on/off VT support (something like VTallocation, in
  other words)

- RetryDelay

- Perhaps DisallowTCP?

- Probably still need most XDMCP chooser configuration options
  (e.g. the [chooser] section).

- The ability to configure if you want the Face Browser or not.
  Some users will not want it.

> We had a discussion the other day about what options need to be
> re-implemented in the upcoming GDM.
>
> Here's a list of GDM features/configurable options I think we need,
> based on bugzilla.novell.com and experience with SLED customers. I've tried
> to keep it short:
>
>   * XDMCP options (as yippi says, all of them).
>
>   * Accessibility (AddGtkModules, GtkModulesList were used for this).
> This means we need sound support too. Screen reader and screen magnifier
> most requested.

I'm not attached to the AddGtkModules or GtkModulesList configuration
options, but it probably is a requirement to be able to turn on/off
a11y support as needed.  Users without a11y needs probably don't want
the extra programs running at login time.

Also, probably need some mechanism to allow the user to change to
a11y themes (such as GTK+ high/low contrast themes) via hotkey.
gdmlogin managed this via menus and mnemonics.  This was handled in
the old GDM via AllowGtkThemeChange and GtkThemesToAllow.  Probably
could do it differently in the new GDM.

>   * Automatic login (GUI configurable would be nice...). We can do
> without timed login and remote auto login.

I suspect lots of users will scream if we remove Timed Login.  Lots
of users seem to be asking for the ability to configure Autologin
and Timedlogin to work on multiple displays.

Note that the old GDM supports the ability to specify a script as
the "user".  I think this feature is used by a lot of people.

>   * Presession/postsession script control for distro and sysadmin.
>
>   * FirstVT, because you want GDM to start up early without landing in
> VT2.
>
>   * Configurable reboot, halt, shutdown system commands.

Suspend also.  Halt/Shutdown are really the same.

>   * A way to require authentication for - or at least prevent - reboot,
> halt, shutdown from user sessions and login screen (AllowLogoutActions,
> SystemCommandsInMenu).
>
>   * PamStack.

PamStack is one of those configuration options that makes a lot of
sense to work in a per-display fashion.

>   * Ability to set gdm user/group acct for sysadmins.
>
> Also, this would be nice:
>
>   * XKeepsCrashing script control.
>   * Debug output to syslog.
>
> Long term:
>
>   * Framework for pluggable modules that can add extra widgets to login
> manager - or otherwise request extra information, like login domain -
> for Active Directory and similar setups, and optionally perform their
> own authentication. See [1].
>
> [1] http://bugzilla.gnome.org/show_bug.cgi?id=354567