Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.slackware > #35732

Re: SysVinit vs BSDinit

Show all headers | View raw

Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> writes:

> On Fri, 07 Aug 2026 07:16:45 +0200, Marco Moock wrote:
>
>> Am 07.08.26 um 00:45 schrieb steve g:
>>> The basic idea these days is systemd. Slackware doesn't use systemd. it
>>> uses run levels. Slackware is easier to use for me.
>> 
>> systemd has targets that behave very similar.
>> 
>> Although, systemd is much more complex regarding what it does, where it
>> is being configured and which unit triggers another one.
>
> IMHO, the biggest disadvantage of systemd is not that it is more complex. 
> The biggest disadvantage of systemd is that it deviates from the number 
> one of the Unix philosopies: "Make each program do one thing well. To do 
> a new job, build afresh rather than complicate old programs by adding new 
> "features"."

That is certainly part of it. But for me -- my personal preference I
mean -- as much of an annoyance is the replacement of what was "just a
matter of coding" -- in terms of your system start being decided by
whatever is in your init scripts -- with configuration files. So they
have this rigid set of files in "ini" format instead of a true
programming language. Maybe bourne shell (plus extensions) isn't the
finest programming language out there, but any programming language is
better than a configuration language designed for non-programming
sysadmins.

Falling out of that decision they get this endless proliferation of
keywords and concepts (wants, upholds, requires, requisite, bindsto,
wants-with-chocolate-sprinkles-on-top, passive-aggressively-suggests,
etc. etc.).

As a consequence of this view I don't share the common opinion that systemd
wouldn't be that bad if it had only confined itself to replacing init.

I have a similar beef with udevd (and eudevd), its use of "udev rules"
in place of a proper embedded programming language.  Now, I don't
dislike so called little languages, purpose drawn languages like expect
or awk. But udev-rule format can't hold a candle to those. It's just an
awkward configuration format and with a nasty feature of sharing some
special characters with bourne shell in unintuitive and error prone
ways.

Regards,
Mike Sm.

Back to alt.os.linux.slackware | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-07-09 15:56 +0200
  Re: SysVinit vs BSDinit Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-07-09 14:25 +0000
    Re: SysVinit vs BSDinit Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-07-09 14:27 +0000
  Re: SysVinit vs BSDinit Rich <rich@example.invalid> - 2026-07-09 15:16 +0000
    Re: SysVinit vs BSDinit Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-07-09 15:46 +0000
      Re: SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-07-10 07:01 +0200
    Re: SysVinit vs BSDinit jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-07-10 13:16 -0400
      Re: SysVinit vs BSDinit Rich <rich@example.invalid> - 2026-07-11 01:22 +0000
        Re: SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-07-11 07:26 +0200
  Re: SysVinit vs BSDinit John McCue <jmclnx@gmail.com.invalid> - 2026-07-11 15:16 +0000
    Re: SysVinit vs BSDinit Mike Small <smallm@panix.com> - 2026-07-23 13:27 -0400
      Re: SysVinit vs BSDinit John McCue <jmclnx@gmail.com.invalid> - 2026-07-23 23:36 +0000
  Re: SysVinit vs BSDinit steve g <Sgonedes1977@gmail.com> - 2026-08-06 18:45 -0400
    Re: SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-08-07 07:16 +0200
      Re: SysVinit vs BSDinit Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2026-08-10 05:43 +0000
        Re: SysVinit vs BSDinit Rich <rich@example.invalid> - 2026-08-10 22:14 +0000
        Re: SysVinit vs BSDinit Mike Small <smallm@panix.com> - 2026-08-15 00:15 -0400
          Re: SysVinit vs BSDinit Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2026-08-16 11:06 +0000

csiph-web