Hello Lori, If the service is marked "offline" it means that it didn't start.
In fact, there is a difference between svc:/system/filesystem/root:default and svc:/system/filesystem/usr:default --> This is the kind of dependencies they have: % svcprop svc:/system/filesystem/root:default | grep group metainit-root/grouping astring optional_all root/grouping astring optional_all (both optional) % svcprop svc:/system/filesystem/usr:default | grep group boot-archive/grouping astring require_all scheduler_usr/grouping astring optional_all (one is required) --> So you can start svc:/system/filesystem/root:default, but you must start svc:/system/boot-archive:default before being allowed to have svc:/system/filesystem/usr:default to start. HTH, William. Lori Alt wrote: > I'm working on modifying the smf methods that > run early in system startup. This is related to booting > from a zfs root file system. I'm trying to modify > the /system/filesystem/usr method, but editing > /lib/svc/method/fs-usr seems to have no effect. I'm booting > to milestone=none, then enabling the > services one by one to start the system. First I do: > > # /sbin/svcadm enable svc:/system/filesystem/root:default > > and that works (and DOES show the effect of changes I've > made to it). Then: > > # /sbin/svcadm enable svc:/system/filesystem/usr:default > > but modifications I've made to the fs-usr method have > no effect. It's as if there's a copy of it stored someplace > (in the repository?) that is running instead. Just to make > sure of this, I edited /lib/svc/method/fs-usr to have > "/sbin/uadmin 1 1" as the first line. So enabling the > filesystem/usr service should have caused the system to > reboot. But no. The service claimed to be "offline". So > what am I missing? Why can I modify the fs-root method, > but not the fs-usr method? > > Lori > > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org
