From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: 66-boot-0.1.2.1
Date: Tue, 16 Feb 2021 07:00:51 +0100 [thread overview]
Message-ID: <20210216060051.IUhA3xQqyKfM_iQwfNQiX65YcZ_xNNUZDa5pikwNURE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21142@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
There's a closed pull request on the void-packages repository
New package: 66-boot-0.1.2.1
https://github.com/void-linux/void-packages/pull/21142
Description:
66-boot packages obarun's boot-66serv, which, as its author puts it, is a portable set of 66 services that can boot unix machines successfully. The packaging just helps with transitioning from runit to s6/66. The package in itself does not replace any of /bin/init, /bin/reboot, /bin/poweroff, etc... It merely installs another shell script that servces as init at /bin/66-bootstart which can be used with an alternative init=/bin/66-bootstart kernel command line argument. The user is left with the responsability to organize its machine as he sees fit and should find the shutdown, reboot and halt scripts in the /etc/66/ directory. Symbolic links to those scripts could be added to the package's INSTALL.
66-boot doesn't offer any service frontend files either (with the exception of tty@ which is necessary and the boot bundle directory which 66-boot's init binary (which is called by the 66-bootstart script) uses.
Another package named 66-services should package a compilation of possible 66 frontend service files for most daemons, as it seems rather difficult to put each daemon's frontend file in its corresponding package.
prev parent reply other threads:[~2021-02-16 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 4:44 [PR PATCH] " zenfailure
2020-04-19 12:08 ` [PR PATCH] [Updated] " zenfailure
2020-04-20 5:11 ` zenfailure
2020-12-20 1:49 ` ericonr
2021-02-16 6:00 ` ericonr
2021-02-16 6:00 ` ericonr [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=20210216060051.IUhA3xQqyKfM_iQwfNQiX65YcZ_xNNUZDa5pikwNURE@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).