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

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

Re: SysVinit vs BSDinit

From Rich <rich@example.invalid>
Newsgroups alt.os.linux.slackware
Subject Re: SysVinit vs BSDinit
Date 2026-08-10 22:14 +0000
Organization A noiseless patient Spider
Message-ID <115digd$3gkf2$2@dont-email.me> (permalink)
References <112o9as$ee8h$1@dont-email.me> <87v79m98cl.fsf@gmail.com> <1153pnt$dcjp$1@dont-email.me> <115bodt$2siu8$1@dont-email.me>

Show all headers | View raw

Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:
> 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"."
> 
> Systemd is not only an init system. It does not only replace /sbin/init, 
> it also replaces /usr/sbin/crond, /usr/sbin/syslogd, /sbin/udevd and /usr/
> sbin/inetd. Systemd is not a bad choice because it is complex, it is 
> complex because it failed to follow the Unix philosopies.

Systemd was concieved and created by a developer who, as it turns out, 
was a closet micro-softie.  He now actually works for Microsoft, so we 
eventually learned where his true allegiances lay.  It is the "do it 
the windows way" init system for Linux, because Lennart Poettering 
apparently was always a microsoft plant all along.

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