Bart Smaalders wrote: > Kyle McDonald wrote: >> I only meant to state that I've been given the impression fro >> comments users make, that the public perception is that Solaris has >> 'moved on', and that all interest and development is on the new way. >> That for now (since no ARC case has yet been filed.) it's still >> there, but it seems like people have gotten the impression that it's >> not that smart to write new things the 'old way' since you can't >> depend on it being there forever. > > Yes, as developers most of us _have_ moved on. The advantages of > using SMF > are pretty clear, and for new daemons, etc, being introduced into Solaris > there isn't even a "we've always done it this way" argument to make. > If I hear > of a new service in Solaris, I _expect_ to be able to enable/disable, > examine > status, etc w/o having to read man pages. > Which is great for new things being developed *in* solaris.
I was discussing this from the view point of an admin building or installing some outside software package that doesn't have a solaris SMF manifest already created for his/fer use. There's a decision to make there. It's not always cut and dry. -Kyle > - Bart > >
