On Wed, Jun 12, 2013 at 04:40:22PM +0800, Chow Loong Jin wrote: > Bitrot doesn't happen immediately, and even when it does happen, it will > take time before its rate reaches an unmanageable state. Plenty of time > to test a solution in the meantime I say. Basic autogeneration of > sysvinit and upstart init scripts from systemd unit files perhaps?
None of upstart jobs, systemd units, and init scripts are homologous to one another. You can't generate one set from another set without including additional metadata that's not being used by the "native" system you're writing for - which means you haven't actually solved the problem of leaving the users of the other systems with untested implementations. For a concrete example, if we assume systemd units are the base and using socket-based activation as the primary convention, you will have none of the information here about what events the upstart job should start on; and for init scripts, you'll have neither this information, nor information about how to track the processes (pidfiles, etc). Remember that the appeal of upstart jobs or systemd units over init scripts is that we're removing *unnecessary complexity*. Once you've removed that complexity, you can't re-synthesize it from thin air in order to autogenerate init scripts; you have to maintain it somewhere. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
