C. Bergstr?m wrote: > <snip /> >> >> I'm guessing you'll care about console-login and network-service. I >> can't be sure we're resilient to an absent restarter service, but it's >> at least possible. >> >>> 2) Where does common.db/global.db go after after the build or >>> where/how does the initial database get built/populated? >> >> Currently, the installer places the appropriate seed into >> /etc/svc/repository.db. Then svc:/system/manifest-import takes care >> of importing the rest. > By appropriate you mean either common.db or global.db..
global.db (a normal system), or nonglobal.db (a zone). We don't use common.db to deploy anything. >> It'd be ideal if when repository.db was missing, configd attempted to >> populate it from one of the well-known seeds in /lib/svc/seed, but >> it's a bit tricky and we haven't prioritized that enhancement yet. >> > Right now I'm in maintenance mode and ifconfig hangs if I ifconfig bge0 > plumb.. (Which I assumed was because some service hasn't started yet) I'm not so convinced. I don't know of any services that need to be running in order to do ifconfig plumb. > I'll try to debug the problem and get things rolling so this is less of > a hassle, but wanted to understand precisely what was going on. One of > the nice things/benefits to a script based init system is that I can > always just look at the script and pick it apart when things fail.. That's basically what you have to do here too. svcprop -p start/exec <fmri> is your friend. > This was also pointed out to me.. > http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/apps/belenix_constructor/src/mkrepo?revision=61&view=markup > That looks a lot like usr/src/cmd/svc/milestone/manifest-import from ON. (/lib/svc/method/manifest-import on an installed system.) liane
