lianep at eng.sun.com wrote: > >> 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.)
It's an ATM card driver. Apparently network-physical will fail if this service isn't ready. I have to at least wait for filesystems to be mounted to read the module. The FAQ says: filesystem/root : /usr is mounted filesystem/usr : / and /usr is read-write f/usr is indirectly dependent on f/root, but up this dependency chain, f/root depends on network/physical, which will be waiting for the driver. So I lose either way. What's the minimum system service I should wait for before trying to load the driver? BTW this is still in rcS.d in form of a script. I'm trying to convert this into an SMF service. CT
