From: Paul Sopka <psopka@sopka.ch>
To: supervision@list.skarnet.org, gdiazhartusch@gmail.com
Subject: Re: Scripting Stage 3 and 4
Date: Sat, 11 Jan 2025 16:29:37 +0100 [thread overview]
Message-ID: <69072b73-e342-44fe-88bd-ff4052bd88ba@sopka.ch> (raw)
In-Reply-To: <CADQ2Nw_oCD=bk__4NezC8SpA=fKUdUNCy5koKECGiz_zykr2dg@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1738 bytes --]
> May I ask if there is a purpose to this other than doing it as a
> learning experience (if so, then by all means carry on)? Do you see a
> problem with just using current s6-linux-init?
Of course you may ask!
Initially I wanted to learn and understand a proper (init/)shutdown
procedure of UNIX like OS's.
But I figured, that if the scripted procedures turn out elegant and
robust enough,
which - in my opinion - seems to be the case (again everybody please
point out any flaws you find),
I would like to use them over s6-linux-init because
a) The scripts are very easy to port to other UNIX like OS's.
b) I am a big fan of 1 tool 1 job combined in a script.
c) The scripts are easier to understand (and modify) for sysadmins with
little programming background.
I see no problem at all in s6-linux-init, it has worked 100% reliable on
my machine for half a year now.
> Perhaps you already know, but if you are interested in comparing, one
> can still download s6-linux-init-0.4.0.1 from the skarnet.org website
> for studying, which is the last version that used an execline stage1
> init, performed the shutdown procedure in .s6-svscan/finish and
> shipped small C programs that probably did the same thing that
> linux-powertool does here, before the change in package design —which
> also surprised me a the time—. Although s6 dropped in version 2.10.0.0
> the functionality that allowed those to work, and you'd need
> skalibs-2.8.0.1 to be able to actually build and run that version of
> s6-linux-init-maker and s6-{halt,poweroff,reboot}.
Thanks for the heads up!
I did not know about that, that was before I discovered skarnet.
I will definitely look into that.
Regards,
Paul
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2025-01-11 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 20:25 Paul Sopka
2025-01-09 23:19 ` Laurent Bercot
2025-01-11 8:30 ` Paul Sopka
2025-01-11 12:21 ` Re[2]: " Laurent Bercot
2025-01-11 15:15 ` Paul Sopka
2025-01-11 13:22 ` Guillermo
2025-01-11 15:29 ` Paul Sopka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69072b73-e342-44fe-88bd-ff4052bd88ba@sopka.ch \
--to=psopka@sopka.ch \
--cc=gdiazhartusch@gmail.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).