On May 07, Grant Bowman wrote: > There's a discussion going on right now over on the > [email protected] mail list. I am looking for validation > in the specification itself that the LSB applies to systems as a whole > and not to only *.lsb packages. This seems like a crazy premise to me, > but I'm having trouble finding justifications in the specification to > clearly demonstrate otherwise. Any suggestions?
Just to be clear, the debate is over whether distribution-provided init scripts must comply with the Init Scripts section of the specification. My and others' position is that there is no such requirement, since LSB-conformant applications (as of LSB 1.1) cannot depend on the presence or absence of any particular init script on the system, so (a) they shouldn't care what command line arguments they accept and (b) they shouldn't care what exit codes they return. Now, I don't think there is any disagreement that init scripts provided by LSB-conformant applications must comply with the spec, as the spec provides an interoperable subset of capabilities for init scripts to use and an interoperable superset of command line arguments for init scripts to function normally. (Having said that, I wouldn't be opposed to a requirement in the future, if the interfaces were clearly defined and there was some good reason for LSB applications to be mucking with init scripts provided by the system... for now, though, that seems rather unlikely.) Chris -- Chris Lawrence <[EMAIL PROTECTED]> - http://www.lordsutch.com/chris/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with subject of "unsubscribe". Trouble? Email [EMAIL PROTECTED]
