On Fri, 19 Sep 2014 11:36:58 -0500 "T.J. Duchene" <t.j.duch...@gmail.com> wrote:
> Why is it not possible to create a completely generic shell script - > basically ala SysV that can parse systemd config files for those use cases > where Systemd is undesirable? Everything is possible. Yet your question brings bunch of another, much more important ones: 1) What's the point of re-implementing systemd in shell? What about other programming languages, why they're unsuitable for this? 2) Who will implement it? 3) Who will support it? 4) Why re-implementing systemd? Writing your own init is much more fun, as [1] shows to us. > What systemd does is basically a generic process of reading parameters from > a file and using them to start a service. That's one thing of many that systemd actually does, moreover, the list of such things changes constantly. Some call it a 'feature creep', others call it a 'development'. > Granted, this approach would > have the benefits that systemd has, but the concerns about systemd being > too opaque or monolithic could be almost mitigated. Whenever systemd is 'opaque' or not is in the eye of the beholder. Systemd is not monolithic, and that's the main obstacle to anyone who's willing to re-implement it. The best description of systemd would be 'a bunch of small parts each one depending on several others parts'. > The remaining concerns such as login and so on can be addressed separately. I don't intend to sound harsh, but - there's no known working 'e-mail wishes → actual code' generator. So, if you believe that you idea is worth something, why don't you show a shell script that implements your idea on some level? [1] http://wiki.openwrt.org/doc/techref/procd Reco -- 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/20140919210845.f38426d48dd520401cc7b...@gmail.com
