Administration
--------------

GPM sets defaults using GConf.  GConf was introduced in LSARC/2002/146
Gnome 2.0 Configuration - GConf.  GConf is a system for storing application
preferences which would allow GPM to start according to a user's preference. 
Any changes that a user makes to the GPM graphical user interface preferences
are stored in the GConf database and persists across reboots.
 
GPM Defaults
------------

What happens on a freshly installed system with GPM?

For any user who is logged into an X session, GPM will by default
have these actions:

Lid - When a user closes the lid, the system will by default suspend if
supported.  If suspend is not supported, the action will be to do nothing
by default.  One can change the default to blank screen or do nothing. 
Power button - Pressing the power button will by default open a GUI that allows
the user to choose actions such as shutdown, suspend, or hibernate.  One can
change the default to immediately shutdown, suspend, or hibernate without
a GUI prompt.  Suspend and hibernate are only available if the system
supports these actions. 
LCD Brightness - On AC power, there is no change in brightness.  On
battery power, the brightness reduces to 50% by default.  One can adjust
the default brightness level. 
Screen Lock - The screen will lock by default if the user returns from
actions such as suspend, hibernate, or blank screen.  This action can be
disabled. 
CPU frequency - By default, there is no change in CPU frequency handling.
One can change the default to either a "On Demand" or Performance
governor.

If no one is logged into an X session, the defaults above will be true
except for the following:

Lid - When a user closes the lid, the system will by default suspend if
supported.  If suspend is not supported, the action will be to do nothing
by default.  One can change the default to do nothing.
Power button - Pressing the power button will by default shutdown the
system.  This default is not configurable.
LCD Brightness - There is no change in brightness.  This default is not
configurable.
Screen Lock - There is no screen lock action since no one is logged
into an X session.

Auditing
--------

The project team will work with the audit team to enable auditing 
in accordance to the Solaris Auditing Policy.  However, any issues
with auditing in the current power management interfaces will be
considered a bug. 

Security
--------

The requirement is that we cannot have two security policies in Solaris so
the security policy we implement will be RBAC.  By porting any security
policies to RBAC, we can then have one picture on how to administer
the security policies.  This requirement will allow one to only need the 
RBAC administration tools.

PolicyKit is a security policy on Linux similar to RBAC.  The plan has
been to port the pieces that are needed into RBAC.  libpolkit is a 
small piece of PolicyKit that has been ported to use RBAC since its
introduction in PSARC/2005/399 Tamarack: Removable Media Enhancements.  So 
far, projects will only port the piece of PolicyKit that is needed.  What
about the rest of PolicyKit?  Any piece of PolicyKit used by a project team
would be required to port to RBAC and thus keep with the requirement
of having only one security policy and administration.