Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Kevin Chadwick Newsgroups: comp.lang.ada Subject: Re: systemd controversy Date: Wed, 20 Mar 2024 09:56:18 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Wed, 20 Mar 2024 09:56:18 -0000 (UTC) Injection-Info: dont-email.me; posting-host="826ba427a20a622cbb06bd21c2d6bba4"; logging-data="1511754"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/hSRR+MgRqnuRuPJjzsu6uOwTc9oCYDO0=" User-Agent: PhoNews/3.13.3 (Android/13) Cancel-Lock: sha1:FfDAvrBTuWW9aYq4jitGYk7V2xA= In-Reply-To: Bytes: 2219 >That’s purely down to how you choose to implement it--it has nothing to do >with the format--and meaning--of those unit files themselves. Nobody can >stop you from writing bad code to parse a good format. > I'm skeptical of the flexibility being lost. Perhaps it is possible but Ada was specified competitively. Had Linux init been handled competitively then I doubt they would have attempted and failed to move away from scripts entirely. Likely openrc, runit or a new init system would have succeeded. >> In my experience init scripts are made entirely of simple commands that >> are documented and editable, piece by piece. > >sysvinit scripts are full of boilerplate sections that users regularly >copy and paste from one to the next, without thinking too much about what >they do. SysV init scripts are quite horrid but OpenBSDs rc system is far more transparent, flexible and nicer to work with than systemd. -- Regards, Kc