Mike Gerdts writes: > I think that it is likely appropriate for both places, as it would be > a partnership between OpenSolaris and a distributor. As I said > before, I was bringing this particular issue up as something to fix > over the next 2 - 5 years and that pdo.c was likely already a lost > cause. FWIW, I was once again annoyed to read Jonathan's latest blog > entry that referred to Solaris as open source.
In the time scale of 2-5 years, I think pdo.c becomes completely irrelevant. As best I can tell, we'd have to assume that Caiman is a failure for that picture to change. I'm still not quite arguing against release of that source. I'm just pointing out that if you're going to spend limited resources on doing this, you probably have more worthwhile targets available. As for the blog entry, I'm sure that's above my pay grade. > I'll stop annoying install-discuss with this now. As far as I'm > concerned, pdo has officially been put in the same wasteland as LU and > flash. It is abundantly clear that new installation technologies that > are not yet integrated into OpenSolaris are the only things worth > discussing in an OpenSolaris context. It's a very different wasteland from LU. LU is stuck because of licensing issues. We don't own it sufficiently that we can put it under an open license. It doesn't really matter whether we throw resources at it, or if it's good or bad for OpenSolaris; we just can't legally do it. What would help in that case is a project to _replace_ LU with something different -- either a new installer/upgrade tool (as in Caiman) or a clean-room implementation of LU (any takers?). That's quite a different thing than patching, which, as I said before, appears to me to be fairly useless for OpenSolaris participants. It'd be a little like doing the work to hand over the source for "asppp." As for Flash, I don't quite know what's going on there. I assume it's "just" a resource issue. Not at all a good excuse, I know. I think that's a much more worthwhile thing to get vetted and released. -- 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
