Christine Tran writes: > Cathy has a network service and 2 Sun-delivered manifests are changed to > depend on it. What if I were a 3rd-party device driver whose > load-module scripts lives in rcS.d but milestone/single-user start me > too late?
If you're doing pkgadd on a running system, the manifest will be imported immediately, and the ordering will be correct during the next boot. If your customer's software supports "pkgadd -R" (not all do), it gets a little trickier. I plan to solve the "it gets a little tricker" bit by moving manifest-import to run first thing during boot. If we did that, there'd be nothing additional for your customer to do. I've got a full proposal that needs to be cleaned up and mailed to this alias, but it's honestly on hold for a month or two while we get to completion on the templates project. > As a general question, where should network device driver > manifests go? You mean in the naming scheme? I'd choose something like device/<customer stock symbol or reverse domainname>/<device name> . (At least, if it's just initialization code for that specific device. If it serves a broader function, I'd consider moving into the network heirarchy.) > And is it kosher to for 3rd-party application to reach > out and make a Sun-delivered service a dependent of it? Yes. That's why we created dependents -- so that ISVs and sites can create manifests that declare dependencies on their services without modifying the manifests we deliver. liane -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
