Phi Tran wrote:
Name: Solaris ATCA IPMI Driver
Submitter: Kevin Song
Owner: Garrett D'Amore
Intern: Jim Walker
Interest: kevin.s...@sun.com
Status: waiting need draft opinion 11/25/2009
Exposure: open
Comment:
OK, PSARC 2009/467 is not approved
On 07/ 1/10 01:58 PM, Kevin Song wrote:
Jim,
Please derail PSARC 2009/467 with a note of PSARC 2010/252.
Two things:
1. 2009/467 was already approved, and so it cannot be derailed.
2. 2009/467 was a full case, and so it cannot be derailed (derailing is
only for fast-tracks that need a full r
On 07/ 1/10 02:43 PM, Kevin Song wrote:
On 07/01/10 11:31 AM, Sebastien Roy wrote:
On 07/ 1/10 01:58 PM, Kevin Song wrote:
Jim,
Please derail PSARC 2009/467 with a note of PSARC 2010/252.
Two things:
1. 2009/467 was already approved, and so it cannot be derailed.
2. 2009/467 was a full case
On 07/01/10 11:55, Garrett D'Amore wrote:
On Thu, 2010-07-01 at 11:43 -0700, Kevin Song wrote:
On 07/01/10 11:31 AM, Sebastien Roy wrote:
On 07/ 1/10 01:58 PM, Kevin Song wrote:
Jim,
Please derail PSARC 2009/467 with a note of PSARC 2010/252.
Two things:
1. 2009/467 was already approved, an
Kevin Song wrote:
> Name: Solaris ATCA IPMI Driver
> Submitter: Kevin Song
> Owner: Garrett D'Amore
> Intern: Jim Walker
> Interest: kevin.s...@sun.com
> Status: waiting need draft opinion 11/25/2009
> Exposure: open
> Comment:
>
> OK, PSARC 2009
On Thu, 2010-07-01 at 11:43 -0700, Kevin Song wrote:
> On 07/01/10 11:31 AM, Sebastien Roy wrote:
> > On 07/ 1/10 01:58 PM, Kevin Song wrote:
> >> Jim,
> >>
> >> Please derail PSARC 2009/467 with a note of PSARC 2010/252.
> >
> > Two things:
> >
> > 1. 2009/467 was already approved, and so it canno
On 07/01/10 11:31 AM, Sebastien Roy wrote:
On 07/ 1/10 01:58 PM, Kevin Song wrote:
Jim,
Please derail PSARC 2009/467 with a note of PSARC 2010/252.
Two things:
1. 2009/467 was already approved, and so it cannot be derailed.
2. 2009/467 was a full case, and so it cannot be derailed (derailing
Don Cragun wrote:
This might be ignorance on my part, but shouldn't the code be
using wchar instead of char in order to be CSI enabled?
The latest version of expr.c is at:
http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/expr/expr.c
There is no use of wchar.
If you look a
Jim,
Please derail PSARC 2009/467 with a note of PSARC 2010/252.
Thanks,
kevin
On 06/30/10 05:33 PM, Barry Harding wrote:
Kevin,
Since our new project will support the functionality covered by the
other case (PSARC 2009/467),
I think it does obsolete that other case and that it could/should
On Jul 1, 2010, at 8:32 AM, Rich Burridge wrote:
Please find comments in-line below...
>> Don Cragun wrote:
> The expr(1) man page has:
>
> index string character-list
>
> Report the first position in which any one of the bytes
> in character-list ma
Rich,
Sounds good. You still have my +1.
John
On 07/ 1/10 08:39 AM, Rich Burridge wrote:
What sort of announcement will be made in a Patch release
of Solaris? Will this be release noted? Will the man pages
be updated to include a warning? Other?
It will be documented via a release note
On 06/30/10 08:33 PM, Barry Harding wrote:
Since our new project will support the functionality covered by the
other case (PSARC 2009/467),
I think it does obsolete that other case and that it could/should get
withdrawn...
You cannot withdraw an approved case, but it can be superseded. Please
On 06/30/10 06:29 PM, Shawn Emery wrote:
On Jun 30, 2010, at 12:19 PM, Sebastien Roy wrote:
A couple of quick questions:
1. What is the release binding?
It follows the CIFS project, which I don't know off the top of my head.
I don't see how CIFS is relevant to the release binding of this
What sort of announcement will be made in a Patch release
of Solaris? Will this be release noted? Will the man pages
be updated to include a warning? Other?
It will be documented via a release note in a Patch release of Solaris.
The P-Team and marketing will help craft the wording. It wi
Don Cragun wrote:
The expr(1) man page has:
index string character-list
Report the first position in which any one of the bytes
in character-list matches a byte in string.
This is terrible! The man page you included below says that expr
is CSI enabled.
On Thu, 2010-07-01 at 09:58 +0100, Darren J Moffat wrote:
> On 30/06/2010 23:47, Ted H. Kim wrote:
> > I think this is where things are ending up.
> >
> > umad to use protection 666 and PRIV_SYS_NET_CONFIG
> > ucma reserved ports uses PRIV_NET_PRIVADDR
> > uverbs privileged Q_Keys uses PRIV_NET_PRI
On Jul 1, 2010, at 7:06 AM, Rich Burridge wrote:
Hi Rich,
Please find comments in-ilne below...
>
> > Don Cragun wrote:
> > ...
> >
> >> The expr(1) man page has:
> >>
> >> length string
> >>
> >> Return the length (that is, the number of bytes) of
> >> string.
> >>
> >>
On 6/30/10 3:53 PM, Nicolas Williams wrote:
Are you adding new profiles or adding to existing profiles? (or both?)
If you're adding profiles you should list them.
(Note: I'm not an ARC member, so I can't give you the +1 that you need.)
It seems to me the project team has a new spec.
> Don Cragun wrote:
> ...
>
>> The expr(1) man page has:
>>
>> length string
>>
>> Return the length (that is, the number of bytes) of
>> string.
>>
>> The length does not include the terminating nul character.
> The original case materials for this case said:
> len s
On 30/06/2010 23:47, Ted H. Kim wrote:
I think this is where things are ending up.
umad to use protection 666 and PRIV_SYS_NET_CONFIG
ucma reserved ports uses PRIV_NET_PRIVADDR
uverbs privileged Q_Keys uses PRIV_NET_PRIVADDR except for
the ones which might be used to spoof MADs (x8001, x8001
20 matches
Mail list logo
