diff options
author | Brian Cameron <brian.cameron@sun.com> | 2007-03-26 11:10:28 +0000 |
---|---|---|
committer | Brian Cameron <bcameron@src.gnome.org> | 2007-03-26 11:10:28 +0000 |
commit | 96afc4f0e235acd7a600e46816b3e92d0d86be82 (patch) | |
tree | 59823f2351a511e2b3206fe1c03a996fff5572be /docs/C | |
parent | 64dd36406041549cf9772b6a7d9c478ddb44eca7 (diff) | |
download | gdm-96afc4f0e235acd7a600e46816b3e92d0d86be82.tar.gz |
A little more information added to Solaris and Accessibility sections.
2006-03-23 Brian Cameron <brian.cameron@sun.com>
* docs/C/gdm.xml: A little more information added to Solaris
and Accessibility sections.
svn path=/trunk/; revision=4710
Diffstat (limited to 'docs/C')
-rw-r--r-- | docs/C/gdm.xml | 60 |
1 files changed, 59 insertions, 1 deletions
diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml index 1a23b163..c4830974 100644 --- a/docs/C/gdm.xml +++ b/docs/C/gdm.xml @@ -6917,13 +6917,19 @@ custom-config=foo <para> The GDM greeter programs support the ability to launch AT's at login - time via configurable "gestures". These gestures can be + time via configurable "gestures". These gestures can be defined to be standard keyboard hotkeys, switch device event, or mouse motion events. When using the "Standard Greeter", the user may also change the visual appearance of the login UI. For example, to use a higher-contrast color scheme for better visibility. </para> + <para> + Note that <command>gdmsetup</command> does not yet work with + accessibility, so that users who require AT programs should only + configure GDM by editing the ASCII files directly. + </para> + <sect2 id="accessibilityconfig"> <title>Accessibility Configuration</title> @@ -7141,6 +7147,58 @@ GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/u <sect1 id="solaris"> <title>Solaris Specific Features</title> + <sect2 id="solarisusing"> + <title>Using GDM on Solaris</title> + + <para> + GDM is not yet the default login program on Solaris. If you wish + to switch to using GDM, then you need to turn off CDE login and + start the GDM service. Note that turning off or disabiling CDE + login will cause any running sessions to immediately exit, and any + unsaved data will be lost. Only run these commands if you are + sure there is no unsaved data in your running sessions. It would + be best to run these commands from console login, or a Failsafe + Terminal rather than from a running GUI session. The first step + is to run the following command to see if CDE login is running as + an SMF service. + </para> + +<screen> +svcs cde-login +</screen> + + <para> + If the <command>svcs</command> command responds that this + service is enabled, then run this command to disable CDE login: + </para> + +<screen> +svcadm disable cde-login +</screen> + + <para> + If the <command>svcs</command> command responds that this pattern + doesn't match any instances, then run these commands to stop + CDE login: + </para> + +<screen> +/usr/dt/config/dtconfig -d +Either reboot, or kill any running dtlogin processes. +</screen> + + <para> + At this point you will be presented with a console login. Login + as root, and run the following command. If on Solaris 10 the + servicename is "gdm2-login", if on Solaris Nevada the + servicename is "gdm". + </para> + +<screen> +svcadm enable servicename +</screen> + </sect2> + <sect2 id="solarisconfiguration"> <title>Solaris Configuration</title> <para> |