This case was approved at today's PSARC meeting. I have marked
the IAM file as "closed approved fast-track 03/10/2010".
Brian
On 03/ 2/10 12:13 AM, Qing-Ming Jeff Cai wrote:
>
> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
> This information is Copyright 2010 Sun Microsystems
> 1. Intr
I have placed the updated one-pager here:
http://sac.eng/arc/LSARC/2010/047/libchamplain-one-pager.txt
I have also attached a diff file that shows the differences. The
updated version
+ Adds sections 1.4 through 1.5.4
+ Corrects some grammar issues in sections 2 and 4
+ Makes mention of the
This case was not approved at today's LSARC meeting because it is clear
that the one-pager needs to be updated to reflect the issues highlighted
in the discussion below. Please update the one-pager so the review can
continue.
I extended the timer for this case until 02/24/2010 to give time to
up
This case was approved at the LSARC meeting today.
I marked the IAM file "closed approved fast-track 02/16/2010".
Brian
On 02/03/10 22:17, Jeff Cai wrote:
> Hi,
>
> I'm sponsoring this case for Halton Huo of the Desktop group.
> Since there will be no meeting next week, the timer is set to Feb
This case was approved at the LSARC meeting today.
I marked the IAM file "closed approved fast-track 02/16/2010".
Brian
On 02/04/10 03:13, Qing-Ming Jeff Cai wrote:
> Hi,
>
> I'm sponsoring this case for Sim Jin of Desktop group. The time is set
> 02/17/2010.
>
> Jeff
This case was approved at the LSARC meeting today.
However, I was unable to mark the IAM file "closed approved fast-track
02/16/2010" because the IAM file is write-only by Jeff Cai. Can this
be corrected so the IAM file can be updated? Or, Jeff, can you update
the IAM file?
Jeff, note that yo
J?rg:
On 02/05/10 04:39, Joerg Schilling wrote:
> Halton Huo wrote:
>> For other disabled plugins, they are different story:
>> - CD/DVD Creator
>>Does not work at all, I explain the reason in ARC case and the email
>> to Darren.
>
> It seems that a lot of software developed on Linux since ~
I agree that we should ship plugins if they can build without the
dependencies being present, as long as they are disabled in the user
interface until the user installs the needed dependency. This way
users can add the feature if they want to build the dependency
themselves without needing to reb
With a +1 from Mark Carlson, this was closed approved at today's LSARC
meeting. I marked the IAM file Status as
"closed fast-track 12/01/2009".
Thanks,
Brian
Brian Cameron wrote:
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
GNOME 2.28 Addendum
1.2. Name of Document Author/Supplier:
Author: Brian Cameron
1.3 Date of This Document
This case was approved at the last LSARC meeting on November 10th.
I just updated the IAM file to indicate that this case is
"closed approved fast-track 11/10/2009".
Brian
Brian Cameron wrote:
>
> LSARC:
>
> I am submitting this case for "Fast reboot support of
There have been some minor changes to GDM based on what was approved in
the case, and I wanted to highlight these changs:
- The ARC case suggested that these configuration options would be
managed by the GDM greeter GConf configuration:
- /apps/gdm/simple-greeter/show_last
-
I updated the timeout for this case for November 10, 2009.
This case has been "waiting need spec" for some time. The project
team has provided updated materials which they believe address
the outstanding issues. See attached.
I also updated the case materials directory with the new one-pager
d
Mark:
> I believe this may be the first case that officially refers to (the
> defacto state of) an OpenSolaris distribution and delivery platform
> that's never been fully disclosed to the ARC. While I do not care at
> this time to get into semantics about what that means to the "community"
Note that this case was approved at today's LSARC meeting. It was
agreed that there will be a follow-up case to detail how the Desktop
team is going to address the migration to Perl 5.10. I have marked
the IAM file as "closed approved".
Thanks,
Brian
On 09/02/09 14:47, Bria
Laca/Hugh:
>> A nit: perhaps I'm missing something, but I'm curious why the 2.28
>> release notes point to a page with "seven" in the name and "2.27 release
>> notes" as the page title. Did nothing change in 2.28?
>
> In the GNOME versioning scheme, odd minor versions denote development
> versio
Alan:
>> SUNWperl-authen-pam SUNWperl-authen-pam 0.16
>> 0.16
>> SUNWperl-xml-parser SUNWperl-xml-parser 5.8.4
>> 5.8.4
>
> Which perl version are these provided for? Are they ready to support the
> newly
> delivered perl 5.10? (
Alan:
>> I added the additional-materials/manpage directory in the case directory
>> and provide the manpages in that directory. However, the
>> gtk-docs are over 5,000 files and I thought we were moving away from
>> storing large spews of data files in the case directories.
>
> Okay, so there's
Alan:
>> [5]
>> http://src.opensolaris.org/source/xref/jds/arc-documents/trunk/
>> gnome228/additional-materials/manpages.tar.gz
>> [6]
>> http://src.opensolaris.org/source/xref/jds/arc-documents/trunk/
>> gnome228/additional-materials/gtk
LSARC:
The Desktop team finished the final changes for integrating
GNOME 2.27.92 into build 124 and there were some minor changes
relating to updating our builds to the latest versions of the
upstream modules.
I have updated the materials in the LSARC 2009/475 "GNOME 2.28" case
directory to refl
Note that I changed the IAM file for this case to "waiting need spec"
and I increased the timeout to 09/15/2009.
In what timeframe does the project team plan to provide an updated
one-pager to describe how they plan to address the issues raised in
the discussion so far?
Issues raised in discussi
Jedy:
> Does ConsoleKit support such kind of functionality?
Not yet.
Brian
> On Thu, 2009-09-03 at 02:32 -0500, Brian Cameron wrote:
>> On 09/03/09 02:02, Joerg Barfurth wrote:
>>> Jedy Wang schrieb:
>>>
>>>> For example, ConsoleKit DBus service dae
On 09/03/09 02:02, Joerg Barfurth wrote:
> Jedy Wang schrieb:
>
>> For example, ConsoleKit DBus service daemon currently provides 2 DBus
>> methods, Stop and Restart, to shutdown and reboot the system. We can add
>> 2 new DBus methods, FastRestart and ColdRestart, to support fast reboot
>> and rebo
Jedy:
> I think ConsokeKit provides only one DBus service daemon (It's a
> privileged daemon) which is used to check for the
> solaris.system.shutdown authorization. We can extend this service daemon
> to export a few DBus methods to support fast reboot.
>
> For example, ConsoleKit DBus service d
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
GNOME 2.28
1.2. Name of Document Author/Supplier:
Author: Brian Cameron
1.3 Date of This Document
Sherry:
> Brian, the problem is that, I don't know at this point what the
> feasible solutions and constraints are. Without a better understanding
> of the options I don't see bringing the discussions to the community
> having any value other than a giant mail flood.
I think there are only abou
Sherry:
> The Fast Reboot project team believes and has suggested that the
> simplest way from its perspective (without the new SMF framework) is to
> augment ConsoleKit and associated D-bus messaging system. The Fast
> Reboot project team understands the GDM team's concern regarding having
> to
This case was approved at last Tuesday's LSARC meeting. I marked the
IAM file "closed approved". Sorry for being a bit late on this.
Thanks,
Brian
On 08/18/09 02:04, Brian Cameron wrote:
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This informati
Randy:
>I'll admit I am not that knowlegable on D-Bus API's and
> interactions, but there appears to be a deprecation of HAL in favor of
> new things, including ConsoleKit. And somehow, it appears to not be
> the hardware abstraction which is going away, but a specific set of
> bits (or mayb
Randy:
> On Wed, 26 Aug 2009, Brian Cameron wrote:
>
>>
>> Jedy/Sherry:
>>
>>> Sherry gave us the whole story. The logic you mentioned will be
>>> implemented in ConsoleKit which will be integrated after b128. So
>>> currently, we ha
Jedy/Sherry:
> Sherry gave us the whole story. The logic you mentioned will be
> implemented in ConsoleKit which will be integrated after b128. So
> currently, we have 2 options. The first one is to wait ConsoleKit's
> integration. The second one is to integrate the current fast reboot
> support
This case was approved at today's LSARC meeting. I marked the IAM file
"closed approved".
Brian
> I am submitting this case for "Firefox 3.5.x on S10" by Parthasarathi
> Susarla, and it will timeout on August 27th. See attached onepager.
>
> This case will integrate Firefox 3.5.x into Solaris
This case was approved at today's LSARC meeting. I marked the IAM
file "closed approved".
Brian
On 08/13/09 18:23, Brian Cameron wrote:
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Intro
This case was approved at today's LSARC meeting. I marked the IAM
file "closed approved".
Brian
On 08/11/09 16:19, Brian Cameron wrote:
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Intro
Jedy:
>> I'd also have expected to see a screenshot of the new dialog presented
>> as part of the case material.
>
> A screenshot is attached. Brian, would you please upload the screenshot
> for me?
Done. The fast-reboot.png image is now in the case materials.
Brian
mpact.
Thanks,
Brian
On 07/23/09 08:42, Brian Cameron wrote:
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
> 1.1. Project/Component Working Name:
>WebKit 1.1.x
> 1.2. Name o
Alan:
>>> The following list seem like things needed to build firefox, but which
>>> don't need to be shipped to users of firefox - is there some reason
>>> these are needed, or is it just an artifact of the spec-files build
>>> system? (Though it would seem easy enough to just not deliver the
>
LSARC:
I am submitting this case for "Fast reboot support of GNOME restart
dialog" by Jedy Wang, and it will timeout on September 1st. See
attached onepager.
This case will integrate this new support only into Nevada.
Thanks,
Brian
-- next part --
An embedded and char
The timeout for this case has passed, and no further unresolved issues
were raised. I have marked the case as "closed approved"
I have attached a diff file which shows all the differences to the
onepager since it was first submitted, which reflects the discussion
and agreements made in this revi
The timeout for this case has passed, and no further unresolved issues
were raised. I have marked the case as "closed approved"
I have attached a diff file which shows all the differences to the
onepager since it was first submitted, which reflects the discussion
and agreements made in this revi
Willie:
>> The main reason for integrating WebKit is so that it can be embedded
>> in programs like yelp and devhelp. If WebKit is not usably accessible,
>> then we can continue to deliver older versions of the yelp and devhelp
>> modules which do not use WebKit and not lose any accessibility.
>>
Willie:
> Are you suggesting that WebKit not integrate in Solaris until it is
> more fully accessible? If so, what do you recommend be done instead?
I notice that you raised this issue in the thread "Who is using WebKit
in GNOME 2.28" on the GNOME desktop-devel-list at gnome.org. From that
disc
This case is set to time-out tomorrow as a FastTrack. If there are no
issues raised, then it will be approved as a fasttrack. If people think
there are any remaining issues that require further discussion, then I
have made arrangements for this case to be converted to a full-case and
we can have
This case is set to time-out tomorrow as a FastTrack. If there are no
issues raised, then it will be approved as a fasttrack. If people think
there are any remaining issues that require further discussion, then I
have made arrangements for this case to be converted to a full-case and
we can have
Willie:
> If there is a chance, some clarification should be made about the a11y
> statement. The WebKit team and GNOME teams are working hard to provide
> fundamental a11y support for WebKit, but there is a lot of work to do. See:
>
> http://mail.gnome.org/archives/desktop-devel-list/2009-July/m
Alan:
- Alan Coopersmith asked why some scripts are installed to /usr/lib and
others to /usr/lib/ConsoleKit/scripts.
The difference is that the files installs to /usr/lib are libexec
programs which would normally be installed to /usr/libexec on Linux.
>>>
>>>
Darren:
On 08/19/09 04:08, Darren J Moffat wrote:
> Brian Cameron wrote:
>> The GDM co-maintainers did not like the above proposal. They
>> disagreed strongly with the idea of including or excluding users
>> based on whether they have a face image defined. Remember the
Alan:
>> - Alan Coopersmith asked why some scripts are installed to /usr/lib and
>>others to /usr/lib/ConsoleKit/scripts.
>>
>>The difference is that the files installs to /usr/lib are libexec
>>programs which would normally be installed to /usr/libexec on Linux.
>
> So will you be pu
Nicolas:
> On Tue, Aug 18, 2009 at 06:29:29PM -0500, Brian Cameron wrote:
>>> Provided that it is possible for the installer(s) and user add tools to
>>> edit the configuration, yes. If not then... no.
>>
>> If the installer runs as a user which can modify the G
Based on the discussion so far, I have updated the WebKit onepager
in the case materials. See attached diff file for details of these
changes.
This case was approved at the August 5th meeting, but then was
re-opened when Darren Moffat raised issues with how SSL certificates
are managed.
I belie
Nicolas:
> On Tue, Aug 18, 2009 at 05:44:43PM -0500, Brian Cameron wrote:
>> The GDM co-maintainers did not like the above proposal. They
>> disagreed strongly with the idea of including or excluding users
>> based on whether they have a face image defined. Remember the
the pkgconfig file, thanks, I've just added it.
> Thanks,
> -Justin
>
> Norm Jacobs wrote:
>> Ok, I get the 64-bit libraries, but I have to ask about the 64 bit
>> commands in /usr/bin/... What do they buy us? Are they necessary?
>> Shouldn't you be isaexe
Nicolas:
> On Mon, Aug 17, 2009 at 08:20:14PM -0500, Brian Cameron wrote:
>> - Several people (Joerg Barfurth, Darren Moffat, Nicolas Williams) have
>>highlighted that GDM should not touch the user's $HOME directory
>>before the user authenticates. Current
I just had a two hour discussion about these topics with the upstream
GDM co-maintainers, and want to update the proposal based on what would
be acceptable to get these code changes upstream. Darren Moffat, I also
have some questions about your requirement that the Face Browser support
opt-in/opt
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
I am submitting this case for "Firefox 3.5.x on S10" by Parthasarathi
Susarla, and it will timeout on August 27th. See attached onepager.
This case will integrate Firefox 3.5.x into Solaris 10.
Brian
-- next part --
An embedded and charset-unspecified text was scrubbed..
Thanks to everyone for helping to review the ConsoleKit case. I would
like to summarize the issues raised so far. I think all of these issues
have been answered and resolved. Please let me know if there are any
other remaining issues, or if any of the following items need further
clarification.
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Amendment to sox
1.2. Name of Document Author/Supplier:
Author: Brian Cameron
1.3 Date of This Document
Jason:
> Two questions from the peanut gallery, inline...
>
> On Mon, Aug 17, 2009 at 8:20 PM, Brian Cameron
> wrote:
>> - There are many concerns about the Face Browser and whether it should
>> be turned on by default.
>>
>> - Glenn Faden suggested i
Thanks to everyone for helping to review this GDM case. I would like
to summarize the issues raised so far, and the proposed solutions.
I have not yet updated the case materials to reflect the proposed
solutions, but will do so if the committee is agreeable to approve
this case with these changes
Joerg:
>> - /usr/bin/gdmdynamic [--add=DISPLAY | --delete=DISPLAY | --list ]
>
> This still allows specifying the X server to start when adding a
> display, doesn't it?
Yes, although this is not specified on the gdmdynamic command any
longer. Instead this is specified in the ConsoleKit configur
Mark:
> Why don't you just set a timer on them then and make them fast tracks?
> I don't see any of the discussion so far leaning towards a derail.
>
> Alternatively we could do a pre-inception Tuesday if you feel additional,
> more in-depth review will be warranted later. You really need to get
Joerg:
>> + Also note that GDM has a bug that all GDM login GUI's share the same
>> + GConf settings, so that changing a setting (such as enabling an a11y
>> + feature) will affect logins on all systems. Until this bug is fixed,
>> + it is best to disable GDM a11y in multi-user environments.
>> +
Edward:
On 08/12/09 22:24, Halton Huo wrote:
> On Wed, 2009-08-12 at 17:18 +0800, Edward Shu wrote:
>> What is "session migration" here? Does it mean the session can be
>> migrated from
>> one VT to another VT? With VT, will ConsoleKit be noticed the session
>> switch?
>> Session switch may autom
Joerg:
On 08/14/09 02:31, Joerg Barfurth wrote:
> Brian Cameron schrieb:
> I justed wanted to know (and have recorded in this case) some of the
> architectural gotchas we have to deal with, at least for the transition.
Much appreciated.
>>> Does this mean that PAM is not eve
help focus our discussion during the meeting.
Brian
> Brian Cameron wrote:
>>
>> At last Tuesday's LSARC meeting, I had made arrangements to have
>> a half-hour inception review for ConsoleKit (LSARC 2009/432) and
>> the GDM Rewrite case (LSARC 2009/433). During
At last Tuesday's LSARC meeting, I had made arrangements to have
a half-hour inception review for ConsoleKit (LSARC 2009/432) and
the GDM Rewrite case (LSARC 2009/433). During the meeting, the
LSARC committee said that this would be arranged, but it does not
seem to be on the agenda. Is this an
Michael:
> Brian Cameron wrote:
>> 4.6. L10N Impact:
>>
>> The Desktop team and the G11N team are working together to evaluate
>> and
>> provide I18N/L10N support.
>>
> Really? or is that just boiler plate?
Things are in a bit
I have updated the GDM one-pager with some better examples and some
corrections based on the discussion so far. The diff file showing
these changes, compared to the original materials submitted with the
case, is attached.
Brian
-- next part --
An embedded and charset-unsp
I have updated the ConsoleKit one-pager with some better examples and
some corrections based on the discussion so far. The diff file showing
these changes, compared to the original materials submitted with the
case, is attached.
Brian
-- next part --
An embedded and char
Darren:
I updated the onepager for moovida, and moved the Obsolete/Removed
interfaces to a separate table that lists them as "Removed Interfaces".
Is this okay, then?
Brian
>>> If not then it isn't "Obsolete Volatile" it is actually removed.
>>
>> I thought that when you removed a previously e
Alan:
>> The gobject-introspection module installs:
>> * typelib files to /usr/lib/girepository-1.0
>> * GIR files to /usr/share/gir-1.0
>>
>> for the following modules:
>> * OpenGL
>> * Glib
>> * cairo
>> * fontconfig
>>
Mike:
- If the /var/cache/gdm/user-$uid/dmrc file does not exist, then
GDM will log the user into the default session/language or whichever
ones they selected in the GUI. Then it will save the dmrc file to
the cache with the default settings. On next login, the defaults
w
Nicolas:
>> I thought you were suggesting that the list of users to be shown in the
>> face browser be specified by GDM configuration, rather than using
>> heuristics to decide which users to show. The word "hardcoding" was
>> a poor word choice on my part. What I meant was:
>
> Not configurati
Joerg:
As you probably know, the Desktop team has worked hard over the years
to make sure that GDM works well on Sun Ray. Our plan is to ensure
that the new GDM rewrite also works well on Sun Ray. That said, there
will probably be a few pains in making the transition. However, in the
long run,
Nicolas:
> On Thu, Aug 13, 2009 at 03:08:34PM -0500, Brian Cameron wrote:
>> I am fairly confident that a change to hardcode the list to a
>
>> configuration key would not be accepted upstream. The upstream GDM
>> comm
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
gobject-introspection and gir-repository
1.2. Name of Document Author/Supplier:
Author: Brian Cameron
1.3
Alan:
>> This is probably a good topic for the inception review.
>
> Wait - is this a fasttrack or a full case? Since you sent out the spec
> to LSARC looking like a fasttrack, I think we all assumed this was the
> fasttrack review, but I've just realized you never actually said it was
> a fast
Darren:
>> Correct. The way the code works is that it calls fgetpwent() and if
>> /etc/passwd contains no value, then that account does not show up in the
>> Face Browser. So, users would need to avoid using the shorthand if they
>> want the user to show up in the GDM Face Browser.
>
> Which name
Nicolas:
> This could happen at install time (so the face pic is available on
> first login).
Yes, asking at install time for any users that are added to have a
face pic seems a good idea, though I think this is off-topic for this
case.
> Else it could happen on first login. I don't care so
Nicolas:
> I'd like keyboard A11Y to be enabled, but actual keyboard A11Y features
> disable, with toggle keys enabled. I.e., press and release shift five
> times in a row and get a pop-up asking whether to enable sticky keys,
> for example.
Yes, X server a11y features should work with the new
ort of configuration. If we think
it is needed, we could work with the upstream community to add this
feature back.
Brian
> Brian Cameron wrote:
>>
>> Casper:
>>
>>>>> nobody:x:60001:60001:NFS Anonymous Access User:/:
>>>>> noaccess:x:60002:6000
Darren:
>> Looking more closely at the GDM code, I see that it has a hardcoded list
>> of users to not show in the face browser. These include:
>>
>> "bin"
>> "root"
>> "daemon"
>> "adm"
>> "lp"
>> "sync"
>> "shutdown"
>> "halt"
>> "mail"
>> "news"
>> "uucp"
>> "operator"
>> "nobody"
>> GDM_USERN
Nicolas:
> Any way to make sure that A11Y is enabled by default, with toggle keys
> also enabled by default (but actual A11Y features disabled by default)?
I am not sure what you mean by a11y being enabled but actual features
disabled. If you check "text-to-speech" in the a11y dialog, this
laun
Frank:
>> The new GDM greeter only allows the specification of the background
>> image to be used with the new GDM. Unless the "gdm" user is configured
>> to use a different background image, it will use the same background
>> that is shown by default for a user session. So, without any extra
>>
Alan:
>>> The reason I ask is because the GNOME users and groups tool gets this
>>> wrong on Solaris. It correctly hides by default all those accounts with
>>> a uid< 100 but it doesn't hide the other reserved system accounts:
>>>
>>> nobody:x:60001:60001:NFS Anonymous Access User:/:
>>> noacces
Darren:
>>> 2. Default using face browser
>>>
>>> What is the definition of a system account ?
>>
>> I appreciate your concern about how the Face Browser works, since it
>> never worked very well with the old GDM, especially in environments
>> where NIS/LDAP is used.
>>
>> However, the new face b
Casper:
>>> nobody:x:60001:60001:NFS Anonymous Access User:/:
>>> noaccess:x:60002:60002:No Access User:/:
>>> nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/:
>>
>> Since these users do not have valid shells specified, these would not
>> be shown.
>
> These actually have a valid shel
Joerg:
> This really has two separate parts:
>
> - Ability to select a terminal-only session: This ought be possible by
> putting a suitable 'xterm.desktop' file into the /usr/share/xsessions
> directory. Maybe we should ship such a file, but it should be possible
> to disable it. Which leads to
Darren/Nicolas:
On 08/13/09 02:55, Darren J Moffat wrote:
> Nicolas Williams wrote:
>> On Tue, Aug 11, 2009 at 02:21:31PM -0700, Brian Cameron wrote:
>>> - /usr/lib/gdm-session-worker
>>>
>>> A separate process which handles PAM/audit interactions. The
>&g
Darren:
Thanks for your questions.
> 1. Lack of Failsafe session.
>
> I see this as a major issue. I use the failsafe session more when I'm
> not on the console than when I am. In particular I often use failsafe
> when connecting using VNC or a lot when using Sun Ray. A common use case
> for me
Michael:
>> /usr/bin/moovida Volatile binary
> Is SUNWgnome-media-center removed or present?
It will be removed.
> /usr/bin/moovida is Volatile, not committed?
As we have seen, the binary name has already changed from
/usr/bin/elisa to /usr/bin/moovida. So, it has a history of being
Volatile.
Darren:
>> Exported Interfaces Stability Comments
>> --- -
>>
>> /usr/bin/elisa Obsolete Volatile binary
>
> Is this case still delivering a /usr/bin/elisa ?
No.
> If not then it isn't "Obsolete Volatile" it is actually removed.
I thought th
Alan:
>>> # Boolean. Set to "true" if the active session, "false otherwise"
>>> is_active=false
>>
>> "the" active session? On a multi-seat or Sun Ray system, is it okay that
>> there are multiple active sessions?
I updated the comment in the onepager so it now says:
# Boolean. Set to "tru
Darren and Gary:
>> On some Linux systems, the pam_ck_connector is used to ensure that
>> non-graphical logins (e.g. telnet, ssh, etc.) are registered with
>> ConsoleKit. Thus ConsoleKit can be used as a utmp/wtmp replacement
>> since it stores a superset of the information as in the utmp/wtmp
>>
Margot:
> Do you guys have the contract for HAL interfaces? I didn't
> see it in case directory. Do you need a contract for volatile
> Dbus interfaces?
Here is the Desktop team's contract with HAL:
http://sac.eng.sun.com/arc/LSARC/2006/462/contracts/PSARC-2005-399-Tamarack.txt
D-Bus is a part
Alan:
> Brian Cameron wrote:
>> 4.1.1 Detail About ConsoleKit Database
>> # Device associated with Xserver running session (if any).
>> x11_display_device=/dev/console
>> 4.1.5 Environment Variables
>>CK_SESSION_X11_DISPLAY_DE
Glenn:
>> If configured, GDM can will display "Shutdown" and "Restart" buttons
>> for shutting down and restarting the machine. Refer to section 4.1.9
>> for more information.
> This should not be configured by default if the user is not authenticated.
The "gdm" is not configured to have the sol
Alan:
> I don't see a mention in this case of GDM replacing dtlogin as the
> default login screen, and EOL'ing dtlogin - is that going to be
> handled by this case or are you going to bring LSARC 2005/417 back
> again to do that at the same time as this case integrates?
I would prefer to handle
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
GNOME Display Manager (GDM) Rewrite
1.2. Name of Document Author/Supplier:
Author: Brian Cameron
1.3 Date
1 - 100 of 278 matches
Mail list logo
