I don't think it's good enough to simply disable the GDM2 service - what
if you happen to have people connected to the machine via XDMCP, or 
worse SunRay,
doing a disable, will effectively kill all GDM2 services, including 
these clients!

Not really realistic for that case, but maybe instead, if it was 
possible to disable only
the console's X display, leaving the main GDM2 daemon process running 
(to handle
other clients) then we could have a compromise in that... This could be 
as simple as
GDM2 looking for a file (eg /etc/gdm_disable_console) [1] and while that 
file
exists, don't start a console session. But that's really an 
implementation detail,
you would need a CLI tools to do the disable / enable of the console 
GDM2 session...

Darren.

[1] Only an example please don't take literally

Moinak Ghosh wrote:

> Ivan Wang wrote:
>
>>> Jake Hamby wrote:
>>>   
>>>
>>>> One feature that is currently missing from the gdm2
>>>>     
>>>
>>> login service compared to "dtlogin" is being able to
>>> drop down to a console login, do some work (for
>>> example on the Xserver configuration), and then have
>>> X restart when I log out.  In the Linux world, this
>>> isn't really necessary since you can always hit
>>> CTRL-ALT-F1 to jump to a virtual console, although in
>>> this case you might have to manually shut down gdm
>>> and restart it.
>>>
>> [snipped ...]
>>  Since virtual terminal is not available long ago in Solaris, to gain 
>> access to system console, dtlogin "Command line login" is the only 
>> way I can tell.. Any better way doing that? network login requires a 
>> working network connection, which is not always available when doing 
>> system administration work.
>>
>>  I am all for having a command line login no matter what display 
>> manager will be adopted in the future.  
>>
>   One inelegant way to go to console from GDM would be to disable it
>   from the failsafe terminal.
>
>   In GDM screen select Failsafe Terminal
>   Login as root
>   Execute:   svcadm disable gdm2-login
>   Window system exits and you are dropped onto system console login
>     Later when you are done, login to console as root and execute:
>
>   ((sleep 5 && svcadm enable -s gdm2-login)&) ; exit
>
>   The above is copied out of Darren Moffat's blog.
>   Though the following simpler code also works for me:
>
>   svcadm enable -s gdm2-login; exit
>
> Regards,
> Moinak.
>
> _______________________________________________
> Desktop-discuss mailing list
> Desktop-discuss at opensolaris.org


Reply via email to