From: Farley Flud <ff@linux.rocks>
Subject: Re: Shutdown - 25 Years Later
Newsgroups: comp.os.linux.advocacy,comp.os.linux.misc
Followup-To: comp.os.linux.advocacy
References: <pan$1c8bb$619a6b57$40e9fbf7$742927fd@linux.rocks> <vtt9ee$heug$1@news1.tnib.de>
Mime-Version: 1.0
Message-Id: <pan$55efe$f03dde5d$5d3bc1ca$18cd8169@linux.rocks>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Lines: 42
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!news.usenetexpress.com!not-for-mail
Date: Fri, 18 Apr 2025 19:02:08 +0000
Nntp-Posting-Date: Fri, 18 Apr 2025 19:02:08 +0000
X-Received-Bytes: 2242
Organization: UsenetExpress - www.usenetexpress.com
X-Complaints-To: abuse@usenetexpress.com

On Fri, 18 Apr 2025 12:27:25 +0200, Marc Haber wrote:

> Farley Flud <ff@linux.rocks> wrote:
>>Note: the "shutdown" command belongs the package "sysvinit"
>>and probably has been replaced within the junk Systemd that
>>has grabbed the balls of most, but not all (and certainly
>>not mine), GNU/Linux distros.
> 
> Surprisingly, in Debian the shutdown binary is in the systemd-sysv
> package and will thus vanish as soon as we¹ eventually get rid of the
> last init script, but I am pretty sure that shutdown nowadays just
> issues a command to systemd like the appropriate systemctl reboot or
> systemctl halt.
> 

So too does the sysvinit version of shutdown, but the command (or signal)
is sent to the program "init", which is the program called by the kernel
on boot (but that also can be overridden).

Init then consults the file "/etc/inittab" which then determines the
next course of action.

In former/current distros the init program will execute a script
that was/is supplied by the distro maintainers, but any user can
easily substitute his own script.

But even with sysvinit, the distro-supplied scripts were oriented
toward multi-user, server environments which is totally ridiculous
for a stand-alone, desktop workstation.

Sysvinit, in contrast to that abomination known as systemd, is
simplicity and elegance in the flesh.  I, and anyone, can supply
my own boot and shutdown scripts that will conform to the specific
purpose of the machine.

GNU/Linux is far more flexible and adaptable than even the lackey
distro maintainers could ever realize.



-- 
Systemd: solving all the problems that you never knew you had.