David Bustos writes: > Quoth James Carlson on Fri, May 18, 2007 at 03:47:52PM -0400: > > Doing this seems like the simplest and easiest to defend > > implementation. The problem, of course, is that it's an undocumented > > interface, and it could be ripped out from under me. I thus need to > > make it Stable. > > I don't recall the particulars of how inetd upgrade works, but can you > delay the conditional work to after boot?
I suspect the answer is "no," because then I need to know what version of Solaris I came _from_. If I'm coming from S9 or older, then the upgrade works one way (inetd.conf is authoritative about the intended state) and if I'm coming from S10 or newer it works another (SMF is authoritative). As with the other solution, doing that also means detecting whether the import has ever happened before, but means doing so in the context of the new system -- while the import is in fact in progress. I suppose it's plausible, and (even though I've now put a couple of weeks work into setting up various test scenarios; upgrade testing is a bear) I can give it a try to see if there's something workable there, but I don't see how it's any easier or safer. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
