On Sunday 04 July 2010 14:23:45 Julien Cristau wrote: > On Sun, Jul 4, 2010 at 14:11:17 -0500, Raphael Geissert wrote: > > A possible way to implement this state-based policy without relying on > > the underlying boot system would be to require packages and users to > > never call init script directly and to make service(8) the interface to > > init scripts for the user. service(8) and invoke-rc.d(8) would then work > > together to keep a state cache, which would be used by invoke-rc.d. > > > > What do the others think? > > I think such state should be kept by init (which knows, or should know, > which services/processes are running), not by invoke-rc.d(8) and > service(8). And I think we should ditch sysvinit. So I think making > these scripts even more complex is unnecessary in the long run. While I agree this is unnecessarily more complex to achieve with the current and mainline system/design, even if we move to upstart or any other boot system, we must: a) preserve SysV compatibility, and b) for the sake of sanity: provide and use common interfaces that work for all the systems. What seems to concern to Policy here, is that the interfaces and their capabilities must be defined. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net
Attachment:
signature.asc
Description: This is a digitally signed message part.