[smf-discuss] Adding a service to run before filesystem/minimal in a ramdisk

[Michael Goff]

Hi,

I'm trying to add a service that has filesystem/minimal as a dependent:

         <dependency
                 name='network'
                 grouping='optional_all'
                 restart_on='none'
                 type='service'>
                 <service_fmri value='svc:/milestone/network' />
         </dependency>

         <dependent
                 name='filesystem'
                 grouping='require_all'
                 restart_on='none'>
                 <service_fmri value='svc:/system/filesystem/minimal' />
         </dependent>

to a ramdisk image, which is something similar to a x86.miniroot. If I
just place the manifest file under /var/svc/manifest/application in the
ramdisk image, it will be loaded too late by svccfg in the boot 
sequence, after filesystem/minimal runs, for the dependency to the 
respected.

I've tried two other methods to directly modify /etc/svc/repository.db 
in the unpacked ramdisk so that it could boot with the correct 
dependencies set:

   HON unknown etc $ svccfg
   svc:> set -v
   svc:> repository /boot/images/0/mnt/etc/svc/repository.db
   svc:> import /var/svc/manifest/application/honeycomb-net-filesystem.xml
   Taking "previous" snapshot for 
svc:/application/honeycomb-net-filesystem:default.
   Upgrading properties of svc:/application/honeycomb-net-filesystem 
according to instance "default".
   Taking "last-import" snapshot for 
svc:/application/honeycomb-net-filesystem:default.
   Could not refresh svc:/application/honeycomb-net-filesystem:default 
(backend access denied).
   Refresh of 
svc:/system/filesystem/minimal:svc:/system/filesystem/minimal:default 
failed: backend refused access.
   Successful import.
   svc:>

   #!/bin/sh
   ROOT=/boot/images/0/mnt
   SVCCFG_REPOSITORY=$ROOT/etc/svc/repository.db
   export SVCCFG_REPOSITORY
   $ROOT/usr/sbin/svccfg import 
$ROOT/var/svc/manifest/application/honeycomb-net-filesystem.xml

But these didn't work either. The node boots and filsystem/minimal runs 
without first waiting for honeycomb-net-filesystem. Also:

   # svcs -d filesystem/minimal

does not show a dependency upon my service.

Does anyone know how I can set the correct dependencies for 
filesystem/minimal upon my own service in a ramdisk environment? The 
service dependencies work properly if I import my service manifest on a 
regular machine, outside of a ramdisk environment, and reboot.

thanks,
Mike