COME FROM
COME FROM
Posted Feb 11, 2014 12:46 UTC (Tue) by cesarb (subscriber, #6266)Parent article: Systemd programming part 2: activation and language issues
Let's see if I understood this correctly. Upstart's behavior is like COME FROM, while systemd's is more like GO TO.
Posted Feb 11, 2014 13:34 UTC (Tue)
by hummassa (subscriber, #307)
[Link] (1 responses)
Not that COME FROM is totally useless (no GUI-based programming without it).
Posted Feb 14, 2014 21:15 UTC (Fri)
by giraffedata (guest, #1954)
[Link]
The Upstart philosophy is the "multiuser" unit means the user has authorized or requested multiuser service. NFS is appropriate only in multiuser service, so NFS depends upon multiuser. The Systemd philosophy is that the multiuser unit refers to the system providing the multiuser service. You can't claim to providing multiuser service if you aren't providing NFS, so multiuser depends upon NFS.
The Systemd definition of multiuser seems more useful and easy to understand to me.
Here's an analogy: a house is inhabitable only if the heat is on, but it's wasteful to heat an uninhabited house. So you could say inhabitability depends upon the heat being on and therefore the landlord should turn on the heat before signing a lease. Or you could say the appropriateness of the heat being on depends upon the house being inhabited, so the furnace should turn on only when it detects that a lease has been signed.
COME FROM
The dependency declaration looks backwards only if you look at the meaning of "multiuser" backwards.
COME FROM