For Solaris 10 (and later, unless the service names have changed): svcadm enable svc:/system/filesystem/volfs:default
svcadm disable svc:/network/ipfilter:default Prior to Solaris 10, most things weren't started directly from inittab, but rather inittab started /sbin/rc? scripts corresponding to the run-level, which in turn ran the scripts in the corresponding /etc/rc?.d directory with a "start" argument if they began with an "S" or a "stop" argument if they began with a "K". Solaris 10 and later, inittab just runs svc.startd, which does everything else, and while rc scripts are still possible, SMF services (that can be listed with the svcs command, enabled or disabled with the svcadm command, and imported with the svccfg command after creating suitable manifests and method scripts) are the preferred way of doing things. SMF is smarter about starting as much as dependencies allow in parallel, will also automatically restart anything that dies, and can separate configuration properties out so one doesn't have to edit startup scripts in most cases. Run levels correspond to SMF "milestones", which services can have a dependency on to determine under which they should be active. For versions earlier than Solaris 10, IIRC ipfilter was not bundled (although one could build it oneself), there was SunScreen as an optional item; offhand, I don't know what the startup for that was, although I assume there were probably rc scripts. (I always used ipfilter even back then, since earlier, SunScreen was extra-cost.) But for volume management, there should have been hard links to /etc/init.d/volmgt as can be discovered with grep /etc/init.d/volmgt /var/sadm/install/contents If those links are missing, they need to be re-created for volume management to start automatically on systems earlier than Solaris 10; in particular, the S??volmgt link needs to be there. This message posted from opensolaris.org
