Enda O'Connor ( Sun Micro Systems Ireland) wrote: > Casper.Dik at Sun.COM wrote: >>> Hi >>> I guess setting start/exec for the service:instance in question to a >>> startup script other than say fs-user would do ( just in the >>> miniroot repository ), but again this is messy I guess. >> >> >> How is the repository build for the miniroot. >> >> If you think that that is messy, I think it's much cleaner than >> the current situation. >> >> Casper >> > To be honest I have no idea how the repository is built in the > miniroot, I don't disagree that it is probably a beter idea that we > have currently have ( which would not be hard ) :-) > > Would we then need to ship a dummy file to cover all the exit 0 cases, > or is their a better way of manipulating the svc stuff to just have > fs-usr not do anything, just return 0? Enda,
I am not clear as to what you are proposing. Once the patches are applied these files get overwritten. So, we would have to modify the files for all of the services to know when running in the miniroot they should simply exit 0. That way when and if they are patched in the miniroot we do the right thing still. However, today there is no standard way that we export from the miniroot to know if you are running in the miniroot. Applications that need this data find ways to get this data. In the case of the customer issue I was dealing with it wasn't fs-usr, it was devices-local. sarah **** > > Enda > > > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/install-discuss >
