I've been in discussion with upstream OpenHPI, so that what goes into Debian can go into upstream as well. In this discussion, we have questions regarding the interpretation of the LSB in this area. Please provide input to this discussion, as I've been told you are the veritable expert in this area.
My proposed LSB block is: ### BEGIN INIT INFO # Provides: openhpid # Required-Start: $network $named $remote_fs $syslog # Required-Stop: $network $named $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start OpenHPI daemon at boot time # Description: Enable OpenHPI service which is provided by openhpid. ### END INIT INFO We question $named and $remote_fs. Upstream doesn't want to put anything into the block that might preclude starting the daemon. The argument goes like, "If there is no name service, that shouldn't preclude starting our daemon since it can run without it." They don't want to get into the situation where the LSB block has precluded running the daemon because of the capabilities of the underlying OS. My reason for putting it there is that the daemon has a config file, and in the config file, the user can put IP addresses or hostnames. If the user puts in hostnames, I argue that some sort of name service must exist before the daemon starts. I don't want to see users trying to debug a situation where the daemon doesn't work at boot, but works later when they run it by hand. Note that the user could put in only IP addresses, and then wouldn't need $named. Matt Taggart provided the opinion that this is only for LSB-compliant platforms, and those are required to supply some sort of name service, even if only an /etc/hosts file. Upstream's major concern is to avoid precluding small, ROM-based systems that may not have all the bells and whistles of complete OS's. What would you recommend? The situation with $remote_fs is similar. The spec says that /usr may be remote-mounted, and if you require /usr to run, then use $remote_fs. Our daemon loads plugin libraries dynamically, after it starts running, based on the config file. Those libraries are typically under /usr. Hence, I think we need $remote_fs. Again, upstream's concern is whether we're saying that we need remote filesystem capability in order to run. We don't. In fact, we could care less. What we want is $usr, but that doesn't exist. :-) Again, we'd really appreciate any clarification or pointers to further information. -- Bryan Sutula <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
