From: "Casper Ti. Vector" <caspervector@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: s6 usability (was: runit patches to fix compiler warnings on RHEL 7)
Date: Wed, 4 Dec 2019 09:30:52 +0800 [thread overview]
Message-ID: <20191204013052.iimc76r2nehw5qs3@CasperVector> (raw)
In-Reply-To: <20191201214752.2ec0a81b@mydesk.domain.cxm>
On Sun, Dec 01, 2019 at 09:47:52PM -0500, Steve Litt wrote:
> Would it be acceptable to you and them to put the binaries in /bin/s6
> and then very early in the boot add /bin/s6 to the path? This isn't a
> lot different from what djb did with /command, except it's not off the
> root, which everyone seems to hate.
Or can we consider the Plan 9 style [1], which searches all relative
paths (in the broad sense, i.e. all which do not begin with `/', `./' or
`../') from $PATH, so we can install chainloaders into /bin/s6 and then
use `s6/cd' to run `/bin/s6/cd' in execline?
[1] <https://github.com/rakitzis/rc/issues/44>
I fully understand that this convention is not followed in most Unix
shells (except for rc(1) which is from Plan 9, and perhaps some others),
but execline is not a shell, and we can additionally symlink /bin/s6/*
into /bin for backward compatibility.
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19)
7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
next prev parent reply other threads:[~2019-12-04 1:30 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 21:43 runit patches to fix compiler warnings on RHEL 7 J. Lewis Muir
2019-11-27 20:33 ` J. Lewis Muir
2019-11-28 7:59 ` Ben Franksen
[not found] ` <ecdf4d8f-93f6-3f9f-b84c-351fa91c7f02@uni-bremen.de>
2019-11-28 19:04 ` Laurent Bercot
2019-11-28 20:39 ` Steve Litt
2019-11-28 22:17 ` runit or s6 (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-29 14:09 ` runit patches to fix compiler warnings on RHEL 7 Jan Braun
2019-11-29 21:46 ` Dewayne Geraghty
2019-11-30 1:22 ` Colin Booth
2019-11-30 0:21 ` Colin Booth
2019-11-30 3:14 ` Steve Litt
2019-11-30 13:32 ` Jeff
2019-11-30 13:46 ` Jeff
2019-11-30 10:15 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-30 14:32 ` Jeff
2019-11-30 18:58 ` Laurent Bercot
2019-12-02 12:07 ` Jeff
2019-12-02 22:20 ` Laurent Bercot
2019-12-02 2:47 ` Steve Litt
2019-12-02 3:37 ` s6 usability Dewayne Geraghty
2019-12-02 10:24 ` fungal-net
2019-12-02 21:32 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-12-02 23:17 ` s6 usability Samuel Holland
2019-12-03 22:10 ` Steve Litt
2019-12-21 11:49 ` Jan Braun
2019-12-04 12:15 ` Jonathan de Boyne Pollard
2019-12-04 21:02 ` Laurent Bercot
2019-12-04 1:30 ` Casper Ti. Vector [this message]
2019-12-21 9:26 ` Jan Braun
2019-12-21 18:36 ` Guillermo
2019-12-21 21:19 ` Colin Booth
2019-12-22 1:05 ` Jan Braun
2019-12-22 8:30 ` Colin Booth
2019-12-21 23:46 ` Laurent Bercot
2019-12-22 5:53 ` Jan Braun
2019-12-22 20:33 ` Steve Litt
2019-12-22 23:20 ` Laurent Bercot
2019-12-23 1:28 ` Oliver Schad
2019-12-23 9:14 ` Laurent Bercot
2019-12-23 10:15 ` Jonathan de Boyne Pollard
2019-12-24 0:18 ` Oliver Schad
2019-12-23 1:57 ` Steve Litt
2019-12-23 9:00 ` Laurent Bercot
2019-12-22 23:47 ` Dewayne Geraghty
2019-12-04 11:36 ` runit patches to fix compiler warnings on RHEL 7 Jonathan de Boyne Pollard
2019-12-04 16:40 ` J. Lewis Muir
2019-12-04 20:48 ` Laurent Bercot
2019-12-04 21:32 ` J. Lewis Muir
2019-12-04 21:06 ` Steve Litt
2019-12-04 21:50 ` Laurent Bercot
[not found] ` <20191205132736.7f501460@puter>
2019-12-08 19:10 ` Laurent Bercot
2019-12-02 17:57 ` J. Lewis Muir
2019-12-02 21:06 ` J. Lewis Muir
2019-12-02 22:22 ` Laurent Bercot
2019-12-02 21:58 ` Laurent Bercot
2019-12-03 10:57 ` Benjamin Franksen
2019-12-04 10:43 ` Jonathan de Boyne Pollard
2019-12-02 17:13 ` J. Lewis Muir
2019-12-04 11:13 ` Jonathan de Boyne Pollard
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=20191204013052.iimc76r2nehw5qs3@CasperVector \
--to=caspervector@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).