On Sat, 20 Sep 2014 08:34:02 +0900 Joel Rees <joel.r...@gmail.com> wrote:
> On Sat, Sep 20, 2014 at 1:36 AM, T.J. Duchene <t.j.duch...@gmail.com> > wrote: > > What systemd does is basically a generic process of reading > > parameters from a file and using them to start a service. > > If that were true, I don't think anyone would be fussing about > systemd at all. I would. I'm a big believer in modularity, encapsulation, and programs/processes minding their own business unless they have a true need to know. I seldom use global variables in my code, and I try to keep classes as separated as possible, with as thin interfaces between them a possible. I don't hold these views out of some sense of aesthetics: I've been burned by my own code when I failed to exercise these principles, and I've seen whole projects stall when the project's code doesn't follow these principles, because only the original author(s), if him(them), can modify the code. Everyone else's eyes just cross and they say "no thanks". Now of course, unlike me, some people write bug-free code and never need to maintain their code. Others, unlike me, can remember a complex and convoluted bunch of codependent processes months later. But such people are rare, and heaven help the project if they're not available. > > That is, if systemd were just a generic service starter, it would be > keeping its fingers out of login, file permissions, and all sorts of > other stuff that it gets itself entangled with. It would be properly > delegating, as the pid 1 process must, if you want to keep a system > stable and secure in the long term. Pre-cisely! SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140919212149.33c88...@mydesq2.domain.cxm
