> > Maybe the item was just referring to the extra > security features > > rolled in, like access to ipfilters and such? > > You're probably thinking of the > generic_limited_net.xml profile in > /var/svc/profile, which you can use to disable most > services on the > system. This is not the default, and there are still > a few services > which remain exposed to the network (like rpcbind). > The project > mentioned aims to fix those, and make this setup the > default for > evada.
Nope never read that file. I think it's from all the presentation slides, as Christine says. > I think it's more likely that you were equating > "multi-user milestone" > with "runlevel 3". Yep, I was. > It's true that if you boot a > system normally (the > "all" milestone), and then you enable a service, and > you reboot > normally, the service will still be enabled and will > be started. It's > not true that if you boot to a specific milestone > (either by booting to, > say, *runlevel* s or with "-m milestone=", or by > using > svcadm milestone -d) and you enable a service which > was disabled and > then you boot the same way, the service will be > started. If the service > was disabled the first time, then the milestone > doesn't depend on it, so > it was temporarily disabled. Without changing the > dependencies, > svc.startd will still temporarily disable it the > second time. Hmm. OK, that clarifies things a lot. And yes, I equated milestone multi-user with runlevel 3. Thanks for the good description. I think I've got a better handle on it now (and will need to excise the incorrect analogies from my brain). I definitely had it all turned around. Rainer This message posted from opensolaris.org
