From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7028 invoked from network); 21 Dec 2021 23:54:25 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 21 Dec 2021 23:54:25 -0000 Received: (qmail 21793 invoked by uid 89); 21 Dec 2021 23:54:50 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 21786 invoked from network); 21 Dec 2021 23:54:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; h=X-Originating-IP:Date:From:To:Subject:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; s=default; d=troubleshooters.com; b=hfxY8GREw2Tg2FWnjtpvdf2mQKJ20nqAa7CH34jA4bPmF70+CrQq826XaAG8c3agBXpFD5LqEuMQPCQ8vB0aS91gjsJS89ywlO4KLOruinHCoK1Kz60pmUuXSFRaEK2IO3Y1LXUzopmMhpVHb9Wnhdd0Oscql88hjND2UA+Xmzg=; DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=troubleshooters.com; s=default; t=1640130858; bh=dS17sT8QanOKEWp2JYAQVnMNNGU=; l=4795; h=X-Originating-IP:Date:From:To:Subject:Message-ID:In-Reply-To: References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=mWImhRhgnWunY3dvUnrzxF55OOOFGsCE4qWyKvZ+sEGFTzjIGEYgxKwUBb8M/ags1 1klKzHusL5AVLITuIfY5S9wBtdGLRtQIwMrBDRF9OHsGIuVUjTDY8j3VpYSUoju3PG p0k+bFKmByo5Nz7/QXsCWlgbxOvTVnQpJqJnjnLg= X-Originating-IP: [184.90.157.212] Date: Tue, 21 Dec 2021 18:54:17 -0500 From: Steve Litt To: supervision@list.skarnet.org Subject: Re: [announce] skarnet.org Winter 2021-2022 release Message-ID: <20211221185417.120f440f@mydesk.domain.cxm> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi Laurent, Congratulations on your updated software! I searched through my execline documentation page ( http://troubleshooters.com/linux/execline.htm ) to see whether revisions were needed. They weren't, but I found and fixed several errors on that page. I've been doing other things and haven't paid much attention to the progress of s6. I haven't found any simple documentation on it. Let me see if I understand... * Before first installation, back up /sbin/init so if things go wrong it's easy to boot with your prior init * Before running any s6 components, do all the correct config so that the s6-rc-compile program to produce a proper s6-rc. Do this every time you add or subtract services * Grub boots to s6-linux-init-maker, which creates several things, including a new /sbin/init, and then execs /sbin/init * /sbin/init does the necessary stuff about signals and the like, and then forks the stage1 script * When the stage 1 script completes, /sbin/init execs the stage 2 script, so the stage 2 script is PID1 now * The stage 2 script forks s6-rc-init * When s6-rc-init completes, the stage 2 script execs s6-rc, so s6-rc is PID1 * s6-rc supervises s6-svscan, which supervises all the other services, both longrun and shortrun. The preceding is the best interpretation I could put together from https://skarnet.org/software/s6-rc/overview.html, https://skarnet.org/software/s6-rc/s6-rc.html, and discussions with you. What do I need to do to make the preceding sequence accurate? Thanks, SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques Laurent Bercot said on Tue, 21 Dec 2021 08:19:38 +0000 > Hello, > > New versions of all the skarnet.org packages are available. > > The changes are, for the most part, minimal: essentially, the new >versions fix a bug in the build system that made cross-building under >slashpackage more difficult than intended. Very few people should >have been impacted by this bug. > Some packages had a few more bugfixes; and some packages have >additional functionality. No major update; no compatibility break. > > The new versions are the following: > >skalibs-2.11.1.0 (minor) >nsss-0.2.0.1 (release) >utmps-0.1.1.0 (minor) >execline-2.8.2.0 (minor) >s6-2.11.0.1 (release) >s6-rc-0.5.3.0 (minor) >s6-portable-utils-2.2.3.4 (release) >s6-linux-utils-2.5.1.7 (release) >s6-linux-init-1.0.7.0 (minor) >s6-dns-2.3.5.3 (release) >s6-networking-2.5.1.0 (minor) >mdevd-0.1.5.1 (release) >bcnm-0.0.1.5 (release) >dnsfunnel-0.0.1.3 (release) >smtpd-starttls-proxy-0.0.1.1 (release) > > Dependencies have all been updated to the latest versions. They are > not >strict: libraries and binaries may build with older releases of their >dependencies, although this is not guaranteed. > > You do not need to recompile your s6-rc service databases. To make > use >of the new s6-linux-init functionality, however, you will have to >recreate your run-image. > You do not need to restart your supervision tree, unless you're >deleting >your old s6 binaries. > > Details of minor package changes follow. > >* skalibs-2.11.1.0 > ---------------- > > - New function: opendir_at() > > >* utmps-0.1.1.0 > ------------ > > - New binary: utmps-write, a generic utmp client that can write >user-crafted records to the utmp and/or wtmp databases. > > >* execline-2.8.2.0 > ---------------- > > - New -s option to the case binary, enabling fnmatch() (shell) >expression matching instead of regular expression matching. > > >* s6-rc-0.5.3.0 > ------------- > > - Bundle contents are now read in a "contents.d/" subdirectory, one >file per content, instead of one per line in a "contents" file. In >the same way, service dependencies are now read in a "dependencies.d/" >subdirectory, one file per dependency. Old "contents" and >"dependencies" files are still supported, but deprecated. This change >allows better integration of s6-rc service definitions with package >managers. > > >* s6-linux-init-1.0.7.0 > --------------------- > > - New -S option to s6-linux-init-maker, forcing a sync on halt even >in a container. > > >* s6-networking-2.5.1.0 > --------------------- > > - SNI wildcarding is implemented, as well as a workaround for a >bearssl bug causing errors on certificate signatures in certain cases. > > > Enjoy, > Bug-reports welcome. > And happy holidays to you all! > >-- > Laurent >