From: "Laurent Bercot" <ska-skaware@skarnet.org>
To: "skaware@list.skarnet.org" <skaware@list.skarnet.org>,
"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: [announce] s6-linux-init-1.0.1.0
Date: Mon, 20 May 2019 14:17:56 +0000 [thread overview]
Message-ID: <emd9724382-5ed3-4f73-b4bf-091619e5d623@elzian> (raw)
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Hello,
Following some UX reports in the #s6 IRC channel, a new version of
the s6-linux-init package is out.
* s6-linux-init-1.0.1.0
---------------------
- Binaries have less restrictive permissions. Root-only binaries
are now readable (though still not executable) by normal users.
- A generated /run/uncaught-logs now has 02750 permissions.
- The runlevel skeleton script now includes a guard to avoid
calling the service manager without an argument.
- A new option to s6-linux-init-maker, -f, allows the user to specify
the skeldir to copy scripts from, which is useful in packaging scripts
(common in distributions) where the skeldir is in a staging directory
instead of the final installation directory.
https://skarnet.org/software/s6-linux-init/
git://git.skarnet.org/s6-linux-init
Enjoy,
Bug-reports welcome.
--
Laurent
reply other threads:[~2019-05-20 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=emd9724382-5ed3-4f73-b4bf-091619e5d623@elzian \
--to=ska-skaware@skarnet.org \
--cc=skaware@list.skarnet.org \
--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).