/opensolaris-arc/attachments/20090914/c75bb1c0/attachment-0004.ksh
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: committed-API-changes.diff
URL:
http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090914/c75bb1c0/attachment-0005.ksh
Jack Meng wrote:
1. Store the bootpath in firmware (OBP).
Details:
This approach needs to create a dedicated option value in OBP space to
store the bootpath,
and then let Solaris kernel read it during booting.
ISSUES:
Negative opinion is received from firmware team for the bootpath of
Brian Cameron wrote:
[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/
Manjunath Basappa wrote:
Danek,
Thanks for your feedback.
One thing, I just installed latest OSOL (2009.06) and it does
have cherrypy! And it does appear in the /release repository
as well
(http://pkg.opensolaris.org/release/en/search.shtml?token=pythonaction=Search).
Wonder how it
I'm submitting the following self review case which records yet another
audio driver. As this driver follows established architecture for audio
devices, I think this fits well within self-review guidelines. The only
possible complaint here would be lack of SPARC support, but the hardware
simply
On Fri, Sep 11, 2009 at 11:31:10PM +0800, Jack Meng wrote:
The project team has been trying different approaches to solve the
'bootpath' issue,
2. Store the bootpath in boot_archive as the existing mechanism to
support UFS booting in x86.
3. Dynamically build the bootpath before
On Mon, Sep 14, 2009 at 02:51:35PM -0400, Tarl Neustaedter wrote:
Nicolas Williams wrote:
[...]
Er, how can the OBP not know about TPGT?
It's provided by the target during the login sequence. Potentially we
should have an RFE for OBP to specify TPGT rather than accepting what
the target
On Mon, Sep 14, 2009 at 03:27:45PM -0400, Tarl Neustaedter wrote:
Nicolas Williams wrote:
[...]
If it's provided by the target then the OBP should pass it to the OS.
If that's the consensus, we'll modify FWARC 2008/466 to accommodate -
probably create a new chosen property to export
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-doc.tar.gz
Brian Cameron wrote:
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
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 little
Victor Latushkin wrote:
On 10.09.09 07:40, Tim Haley wrote:
I am sponsoring the following fast-track for myself. This case
introduces additional zpool sub-command options to support pool
recovery. The case is requesting micro/patch binding. Timeout is
09/16/2009.
Template Version:
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? (PSARC
Brian Cameron wrote:
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?
On 14/09/09 03:03 PM, Tim Haley wrote:
Victor Latushkin wrote:
On 10.09.09 07:40, Tim Haley wrote:
I am sponsoring the following fast-track for myself. This case
introduces additional zpool sub-command options to support pool
recovery. The case is requesting micro/patch binding. Timeout is
I am sponsoring this case for Stuart Kreitman of the X team.
The timeout is set for next Monday, Sept. 21, 2009.
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
FCL--FOSS Check List
0. Introduction
0.1 Document
I'm not really sure what the history of this is, but OBP
supports native iscsi boot with a FWARC case. In that caae,
all the arguments are provided for and we can boot directly
from an iscsi target.
What else does the firmware need to support besides what it
already does support, and why?
Darren J Moffat wrote:
[...]
OBP already stores Solaris specific properties and has Sun system and
Solaris specific code and properties [at the very least for WAN boot
but there was E10k specific stuff there too in the past and I'm sure
there is more]. So I really don't see why this is an
Nicolas Williams wrote:
[...]
Er, how can the OBP not know about TPGT?
It's provided by the target during the login sequence. Potentially we
should have an RFE for OBP to specify TPGT rather than accepting what
the target tells us, but that's how it currently works.
Nicolas Williams wrote:
[...]
If it's provided by the target then the OBP should pass it to the OS.
If that's the consensus, we'll modify FWARC 2008/466 to accommodate -
probably create a new chosen property to export it. Or Solaris could
fetch the information by itself.
That leaves the
Tarl Neustaedter wrote:
The knowledge of which driver to use within Solaris
isn't needed until after this stage - so I don't think it belongs in the
boot command in the first place.
This is correct... and storing such driver info somewhere where a
special program needs to update it is just
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:
flowadm(1m) remote_port flow attribute
1.2. Name of Document Author/Supplier:
Author: Kais Belgaied
1.3
22 matches
Mail list logo
