Garrett D'Amore wrote:
Thanks for clarifying this. IIUC, the key issue here is:
This project makes new access control decisions (within hald).
So its the decisions which need to be audited.Given that, I agree
that the gap here needs to be closed.
I agree with that, however
Gary Winiger wrote:
The kernel was suspended, so on a resume like any suspended process
would start running again. That's my simplified answer :), but the
power management group would have more details if needed.
Not really. When the kernel resumes, I would presume it stats
at
The architectural point is how does the project team expect to
meet the requirements? I don't believe existing interfaces
implementations are sufficient. IMO this is not, the (non-existant)
Audit project team will do it for us. This actually requires some
Gary Winiger wrote:
I understand it's waiting need spec -- for different reasons.
My motivation for posting was to add to the new specs completeness
for whatever audit architecture was needed.
Darren says this has nothing to do with this project. I disagree,
audit being directly introduced by this project, it is appropriate
to extend this cooperation to resolve the past architectural
oversites. IMO, they are likely to add very little additional
project team work beyond fleshing out the ignorance.
Gary,
I'm a little
Gary:
Do you believe that a different kind of audit trail should be recorded
by this project than if, for example, the sysadmin just types the uadmin
command with the magic number arguments?
This project makes new access control decisions (within hald).
Are you referring to the
Gary Winiger wrote:
audit being directly introduced by this project, it is appropriate
to extend this cooperation to resolve the past architectural
oversites. IMO, they are likely to add very little additional
project team work beyond fleshing out the ignorance.
Lid
---
GPM allows the user to set actions for lid close such as suspend,
hibernate, and shutdown. Suspend and hibernate actions will be
Power Button
GPM allows for the configuration of power button actions such as
shutdown, suspend, and hibernate. These actions will
Gary Winiger wrote:
Lid
---
GPM allows the user to set actions for lid close such as suspend,
hibernate, and shutdown. Suspend and hibernate actions will be
Power Button
GPM allows for the configuration of power button actions such as
shutdown, suspend, and hibernate. These
From Phi.Tran at sun.com Wed Feb 13 12:34:52 2008
Date: Wed, 13 Feb 2008 12:44:12 -0800
From: Phi Tran Phi.Tran at sun.com
Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout
01/23/2008]
To: Gary Winiger gww at eng.sun.com
Cc: PSARC-ext at sun.com, dchieu
Gary Winiger wrote:
From Phi.Tran at sun.com Wed Feb 13 12:34:52 2008
Date: Wed, 13 Feb 2008 12:44:12 -0800
From: Phi Tran Phi.Tran at sun.com
Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout
01/23/2008]
To: Gary Winiger gww at eng.sun.com
Cc: PSARC-ext at sun.com
How does this project meet the audit requirements for
auditing a system discontinuity?
Before this project, when the system is shutdown (halt(1M),
reboot(1M), uadmin(1M)), an audit record is written indicating
the start of a discontinuity, the audit trail is flushed to
Gary Winiger wrote:
How does this project meet the audit requirements for
auditing a system discontinuity?
Before this project, when the system is shutdown (halt(1M),
reboot(1M), uadmin(1M)), an audit record is written indicating
the start of a discontinuity, the audit trail is
Phi Tran wrote:
Gary Winiger wrote:
How does this project meet the audit requirements for
auditing a system discontinuity?
Before this project, when the system is shutdown (halt(1M),
reboot(1M), uadmin(1M)), an audit record is written indicating
the start of a
The auditing of suspend is handled by the uadmin.c code. It creates an
audit record and the ends the auditing session before the actual
This should say it ends the auditing not the ends like some bad movie.
suspend.
Phi
Not really. When the kernel resumes, I would presume it stats
at the next kernel instruction following the instruction that
caused it to go into suspended animation. I would presume it
does not run genuinx:main() again that starts the system fresh
in a reboot, so
Not really. When the kernel resumes, I would presume it stats
at the next kernel instruction following the instruction that
caused it to go into suspended animation. I would presume it
does not run genuinx:main() again that starts the system fresh
in a reboot,
Gary Winiger wrote:
Not really. When the kernel resumes, I would presume it stats
at the next kernel instruction following the instruction that
caused it to go into suspended animation. I would presume it
does not run genuinx:main() again that starts the system fresh
in
I'm confused by the statement of console owner or RBAC auth.
Will libpolkit enforce this policy? Why should it be either
rather than just RBAC auth?
As stated above, the Workstation Owner role is just being defined and we
did not want to depend on it. We would like to use
Gary,
Based on your comments, the project team has an updated spec.txt (v2) at
the material directory. Please see
http://sac.eng.sun.com/Archives/CaseLog/arc/PSARC/2008/021/material/spec_v2.txt
and a diff is provided at
Irene Huang Irene.Huang at sun.com wrote:
Gary Winiger wrote:
libpolkit interfaces
Interface level: Volatile
Why are these Volatile? If they remain Volatile,
won't any consuming case need a contract? I presume
LSARC/2007/702 GPM to
Gary Winiger wrote:
4. Technical Description
I see a number of cases referred to but no case dependencies.
Is that because all the referred to cases are either integrated
or dependent on this case?
Yes and yes.
For all of these actions, what is the default
P.SIIRC Randy was talikng about CLIs with me. Is that a different
case?
I think it is the poweradm tool that will use these RBAC authorizations.
It's not part of this case.
Phi
Randy Fishel wrote:
On Thu, 17 Jan 2008, Darren J Moffat wrote:
I like your rationale for why there are multiple authorisations. I'd
recommend though that it be three not two, ie:
solaris.system.power.suspend.disk
solaris.system.power.suspend.ram
We came to the
Gary..
P.S IIRC Randy was talikng about CLIs with me. Is that a different
case?
I think it is the poweradm tool that will use these RBAC authorizations.
Phi
New or updated CLI's (including the soon to be 'poweradm', to which
Gary and Phi refer) will be dependant on this
Gary Winiger wrote:
libpolkit interfaces
Interface level: Volatile
Why are these Volatile? If they remain Volatile,
won't any consuming case need a contract? I presume
LSARC/2007/702 GPM to be a consumer. Shouldn't there
be a
I see. Then we'll wait until solaris power management team decides the
final stability level of libpolkit, before we continue with the contract
(if needed).
Regards.
--Irene
Gary Winiger wrote:
Gary Winiger wrote:
libpolkit interfaces
Interface level: Volatile
Gary
Just sent the wrong link of contract, in fact, the contract about
libpolkit is
http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/contracts/contract-hal.txt
However, Contact along is not the issue that you concern about. Let's
wait for the power management team's response about the
Gary Winiger wrote:
Just sent the wrong link of contract, in fact, the contract about
libpolkit is
http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/contracts/contract-hal.txt
And I read the wrong contract. For not being clear and the case
materials, I read the
4. Technical Description
I see a number of cases referred to but no case dependencies.
Is that because all the referred to cases are either integrated
or dependent on this case?
For all of these actions, what is the default value?
For all of these
Gary Winiger wrote:
libpolkit interfaces
Interface level: Volatile
Why are these Volatile? If they remain Volatile,
won't any consuming case need a contract? I presume
LSARC/2007/702 GPM to be a consumer. Shouldn't there
be a
Randy Fishel wrote:
On Thu, 17 Jan 2008, Darren J Moffat wrote:
I like your rationale for why there are multiple authorisations. I'd
recommend though that it be three not two, ie:
solaris.system.power.suspend.disk
solaris.system.power.suspend.ram
We came to the proposed
On 18 Jan 2008, at 11:38, Darren J Moffat wrote:
Randy Fishel wrote:
On Thu, 17 Jan 2008, Darren J Moffat wrote:
I like your rationale for why there are multiple authorisations.
I'd
recommend though that it be three not two, ie:
solaris.system.power.suspend.disk
I like your rationale for why there are multiple authorisations. I'd
recommend though that it be three not two, ie:
solaris.system.power.suspend.disk
solaris.system.power.suspend.ram
Or if disk is the wrong word maybe hibernate is better.
--
Darren J Moffat
On Thu, 17 Jan 2008, Darren J Moffat wrote:
I like your rationale for why there are multiple authorisations. I'd
recommend though that it be three not two, ie:
solaris.system.power.suspend.disk
solaris.system.power.suspend.ram
We came to the proposed choice after a fair bit
Another comments:
- some laptops do not allow changing LCD brightness via ACPI in graphics
mode (e.g. due to graphics driver). So I wonder if you could provide
some command line API to do this? Gnome applet will not save a user of
such laptop.
- on some laptops, you need to do various
Vita Batrla wrote:
Another comments:
- some laptops do not allow changing LCD brightness via ACPI in graphics
mode (e.g. due to graphics driver). So I wonder if you could provide
some command line API to do this? Gnome applet will not save a user of
such laptop.
This case is for
David Chieu wrote:
InterfaceTypeComments
--
can.suspendbool The ability to suspend as determined
by uadmin(2).
can.hibernate bool The
Hi David,
please see comments inline.
On Mon, 2008-01-14 at 15:00 -0800, David Chieu wrote:
I am sponsoring this FastTrack for Phi Tran.
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component
On Tue, 15 Jan 2008, Darren J Moffat wrote:
David Chieu wrote:
InterfaceTypeComments
--
can.suspend bool The ability to suspend as determined
by
On Tue, 15 Jan 2008, Randy Fishel wrote:
On Tue, 15 Jan 2008, Darren J Moffat wrote:
David Chieu wrote:
InterfaceTypeComments
--
can.suspendbool The ability
Marcel Telka wrote:
Hi David,
please see comments inline.
On Mon, 2008-01-14 at 15:00 -0800, David Chieu wrote:
I am sponsoring this FastTrack for Phi Tran.
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1.
This sounds a bit strange for me. The battery driver will change LCD
brightness. Why the battery driver? What is the relation between battery
driver and LCD brightness? What will happen if you will run your laptop
without a battery? Maybe I do not understand the battery driver
concept...
A better name would be acpipower or somesuch. But that's a minor detail.
-- Garrett
Phi Tran wrote:
This sounds a bit strange for me. The battery driver will change LCD
brightness. Why the battery driver? What is the relation between
battery
driver and LCD brightness? What will happen
I am sponsoring this FastTrack for Phi Tran.
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
GNOME Power Management Support
1.2. Name of Document Author/Supplier:
45 matches
Mail list logo
