From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2848 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: mobinmob@disroot.org Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: State of skarnet.org projects Date: Mon, 03 Feb 2020 21:28:42 +0200 Message-ID: <1580758123.3822.3@disroot.org> References: <1760736f-f479-4fc3-256d-a4cad4d5772f@obarun.org> <20200202090725.5a7d837c@mydesk.domain.cxm> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=-eOOxYVLFc4hStn7XM/DF" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="58918"; mail-complaints-to="usenet@ciao.gmane.io" Cc: supervision@list.skarnet.org To: Steve Litt Original-X-From: supervision-return-2437-gcsg-supervision=m.gmane-mx.org@list.skarnet.org Mon Feb 03 20:28:55 2020 Return-path: Envelope-to: gcsg-supervision@m.gmane-mx.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by ciao.gmane.io with smtp (Exim 4.92) (envelope-from ) id 1iyhOx-000F4S-K0 for gcsg-supervision@m.gmane-mx.org; Mon, 03 Feb 2020 20:28:55 +0100 Original-Received: (qmail 24995 invoked by uid 89); 3 Feb 2020 19:29:16 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 24988 invoked from network); 3 Feb 2020 19:29:16 -0000 X-Virus-Scanned: Debian amavisd-new at disroot.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1580758126; bh=aB24gOd6aEQAoaL2oh513hyWcWr+3AbA9DDdnXm1gB4=; h=Date:From:Subject:To:Cc:In-Reply-To:References; b=JmwqSzG3ifEQKZqD1tJC30SelDE/spWEnid6liCtO5Pms1WXpOVM8SY5428d+IUON c6E+PDCA7LzNt9LQFqOgXP11QssqNPmuwxHjLhDz3gz9rCvO1YA8HVMn4uBnllVdJA Z40eqzu2X84Wh0Gvq7qQ3XJm6cw2lY5s2UHr6kLzB7XMQkUtOqOMu/u8mPUS6vX97P XSu6lrdivoHNE2118t3EqVjgSC7IpwsxgNzFan0Afk7FJEXtV+T5BJE7OIa6DfVADz RuWStRSpN0W47EryERBEfzZLTmOvjvXwPt7Z7iB5aW3kv+Kv4YDEoA20JX+uKR3Scg e89DSnfhN5Izw== In-Reply-To: <20200202090725.5a7d837c@mydesk.domain.cxm> Xref: news.gmane.io gmane.comp.sysutils.supervision.general:2848 Archived-At: --=-eOOxYVLFc4hStn7XM/DF Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable =CE=A3=CF=84=CE=B9=CF=82 =CE=9A=CF=85=CF=81, =CE=A6=CE=B5=CE=B2 2, 2020 at = 09:07, =CE=BF/=CE=B7 Steve Litt=20 =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > On Sun, 2 Feb 2020 12:34:05 +0200 > fungal-net > wrote: >=20 >> Void is also >> very close, I for one use it with s6 and 66 for a while now and in >> many ways being more carefree than obarun having fast balls thrown=20 >> by >> arch daily. >=20 > Have you, or are you going to, write documentation on how to install > and maintain s6 (and presumably s6-rc) on Void? Are you using Void's > s6* packages, or do you compile the stuff yourself? If you install > Void's s6* packages, does that remove runit? I'd like to have both, to > a/b them against each other and to more quickly learn s6*. I am the maintainer of 66/66-tools and oblibs templates/packages in=20 voidlinux. The 66/s6/s6-rc packages contain only what is provided by the upstream=20 projects or compiled with the projects build systems. The scripts for runit stage 1 and some relevant utilities are developed=20 in the void-runit gh repo [1] and packaged in the runit-void package [2]. Currently there is no package that does the same for 66. I plan to=20 build one once I have enough time for testing. I will accomplish this by=20 modifying the boot-66serv [3] project already used by obarun. I am going to create=20 both a '66-void' package that will be rougly analogous to the runit-void one and a base-system-66 package that will replace base-system. I plan to=20 use the same basic configuration file (/etc/rc.conf) and follow existing=20 (and mostly unwritten/assumed) void policies regarding the basic system=20 functionality. Switching from one init system to the other should require no more than=20 installing the new base system and doing basic configuration (once). >=20 > It seems trivial to me to deploy s6 stage 2 and migrate all my runit > stage2 to s6 stage 2. However, migrating stage 1 sounds to me like an > Einsteinian task. Runit's stage 1 repeatedly loops through .d > directories in what I find to be an unobvious way. boot-66serv works fine with void [4]-[5], but I want to make (and test)=20 certain changes in order to package it properly. You will need 66 and 66-tools=20 packages installed. That being said, 66 is not just s6-rc and s6. It uses an ini-based=20 format for services [6] and has some simple but powerfull utilities. It=20 organises services in trees [7] - obarun has (ootb) a boot tree (provided by boot-66serv)=20 and a root tree populated by service frontend files packaged seperately. >=20 > It seems to me that Void is getting more popular every day, and Void > could serve as a Rosetta Stone between runit and s6. I'd appreciate=20 > any > documentation you have or will write in the future concerning your use > of s6* on Void. >=20 > Thanks, >=20 > SteveT >=20 > Steve Litt > February 2020 featured book: Thriving in Tough Times > >=20 ___________________________________________________________________ [1] https://github.com/void-linux/void-runit [2]=20 https://github.com/void-linux/void-packages/blob/a71b0a458be6ae5d095dc94aa4= f2983acc0796db/srcpkgs/runit-void/template [3] https://framagit.org/Obarun/boot-66serv [4] https://forum.obarun.org/viewtopic.php?id=3D957 [5]=20 https://www.reddit.com/r/voidlinux/comments/cqck5d/change_runit_to_s6_is_po= ssible/f75neth/ [6] https://web.obarun.org/software/66/frontend.html [7] https://web.obarun.org/software/66/66-tree.html = --=-eOOxYVLFc4hStn7XM/DF--