Alan:
> Brian Cameron wrote:
>> - Alan Coopersmith raised the issue that we need a follow-up case to
>> EOL CDE Login. Personally I think that it would make more sense if
>> the engineers within the Desktop team who are responsible for CDE
>> login were to follow-up with such a case. It would be better, I
>> think, if those people who best understand how CDE login works were
>> to be responsible for such a case and answering questions about
>> how the transition will be managed, etc.
>
> While EOL'ing dtlogin can be a separate case, this case must go forward
> with gdm as default, since we know that has happened without ARC review
> already.
Lin Ma, the engineer on the Desktop team responsible for CDE login has
been assigned the task of EOL'ing dtlogin.
> Things that were treated in previous gdm ARC cases as advice
> of "before gdm becomes the default login screen" must be treated as TCR's
> or TCA's for the "now that gdm is default" get-well plan. Pretending
> that gdm is not default is irresponsible and ignoring the reality of our
> existing OpenSolaris releases, and all Nevada builds 128 and later.
Looking at the mail log of LSARC 2005/417, the only issue raised as a TCR
was the "drop to console" issue. As I have already stated in the ARC case
and this mail thread, this will be addressed by VT. Since build 122, VT will be
available, but not on by default. Users simply need to enable the vtdaemon
service to have this feature. Also, the VT team plans to address the remaining
bugs so the vtdaemon service can be enabled by default, though this probably
will not happen before the end of this year. While there are some issues, this
is a big step forward compared to what exists in OpenSolaris today.
The other issues raised as needing to be done before GDM becomes the
default login program have been addressed. These include:
+ IPv6 support
+ Solaris audit support
+ Solaris logindevperm & fbconsole support
+ accessibility support
+ G11N/I18N/L10N support
+ SunRay support with reasonable performance
+ Support XDMCP Wrappers. This provides XDMCP host allowed access since
CDE login supports this feature via the accessFile /usr/dt/config/Xconfig
resource.
+ Need to be able to launch chooser from login program
+ Support /var/dt/sdtlogin pipe with Xserver
With one exception:
+ Need to be able to launch chooser from login program
Which was listed as a known regression in this ARC case. This will be
treated as a bug and fixed when we have the opportunity.
Also, there were a few other "requirements" that no longer apply to the new
GDM:
+ Specify different gdm.conf configuration file on startup.
+ Support /usr/share/gdm/gdm.conf and /etc/share/gdm/gdm.conf config files
for system-wide and machine-specific configuration support. This is in
GDM CVS head, and the default file is installed to
/usr/share/gdm/gdm.conf.
These are no longer needed because GDM now uses GConf to store its internal
configuration and sysadmins can use normal GConf mechanisms to manage GConf
default/mandatory settings across machines to provide alternative
configurations.
I am not aware of any further issues. If there are any, then please let
me know.
Brian
