Matthew Jacob writes: > But the ARC process is of necessity a somewhat heavyweight process (when > it suits it- look at the automatic closed approved for the IOMMU case > for the opposite). This means that people have to be fairly strongly > motivated to do the right thing and use that process. Obvious changes > and integrations that would make Solaris a developer's favorite didn't > necessarily find a champion within Sun because it does and takes real > work to think these things through. This does now seem to be changing, > but there is perhaps more tension between ARC and getting things "into" > Solaris (for some measure of "into") than still should be.
That seems silly. I fear C-teams and the general wrath of my fellow developers for having broken something much more than I do any open review in the ARC. If "obvious" integrations aren't happening because the ARC is too "heavy," then I think that's actually a symptom of a different set of linked problems: we've got too many system-wide features in Solaris that are (a) implemented differently from other operating systems (aka "innovative") and (b) not supported by much existing open source software. There's a price to pay for being different, and this is it. Those aren't problems we can wave a wand to remove or just wish away. -- 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
