Matthew Jacob writes:
> + Is it worth including at all?
> + Is it worth including even incomplete wrt RBAC?
> + Is it worth including if it takes a year to sort out RBAC and other
> issues?
I think you might be assuming that we'll see this project team again
and that they'll improve things. No offense intended towards the
project team, but history teaches us otherwise: we either get all of
our issues out on the table and dealt with in some manner, or we
forever hold our piece. Once they integrate, project teams tend to
fall under a bus. (For that matter, the same holds true for design,
code, and C-team reviews.)
So, add to that list:
+ Is it worthwhile giving ARC approval to an incomplete project when
there's no demonstrable commitment to improving things later?
(And I'd give the length of this email thread as pretty good evidence
of a lack of commitment.)
> it anyway. Perhaps another thing to make the inclusion of these packages
> easier is a "optional but unsupported because...." category which is
> just a documentation exercise. Like, we could say "sg3_utils is
> something you can add, but it doesn't meet the Solaris criteria of a, b,
> c which is why it's not part of the default release. You have been warned".
That's basically what /opt/sfw (Companion CD) used to be. Just
compile, toss it in, and hope it sticks. It wasn't exactly a popular
solution -- in part because we're not known for being particularly
spry in fetching new sources and recompiling, even the process barrier
is reduced effectively to zero.
We've had our run of experiments with software ghettos, and it doesn't
seem to end well, so I'd suggest not going there again. We know how
the story ends.
Since you seem to be leaning on the Linux side of things, I think the
best answer might be the earlier suggestion I made (and seconded by
Garrett, Casper, and Darren, though we haven't heard from Gary) to
avoid an RBAC profile entirely and let the user play "invent an
architecture" with it. Document what privileges are needed, and wish
them luck.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
