From: Thomas Caravia <taca@kadisius.eu>
To: arch-general@archlinux.org
Cc: Supervision <supervision@list.skarnet.org>,
Jonathan de Boyne Pollard
<j.deboynepollard-newsgroups@ntlworld.com>
Subject: Archnosh - the nosh toolset packaged for Archlinux
Date: Tue, 11 Apr 2017 15:15:30 +0200 [thread overview]
Message-ID: <20170410215726.0904d9db@kadisius> (raw)
Hello,
The archnosh repository[1] provides the build files necessary to
integrate the nosh[2] system and service manager with Archlinux package
management, as of version 1.33[3].
The nosh toolset is part of the daemontools family of managers, several
of which are already packaged[4] for Archlinux: runit, s6, daemontools,
perp...
The packages generated via archnosh follow the Debian packaging[5]
provided by the author of nosh and allow for two major setups:
1. Running the nosh service manager under systemd
Here systemd remains the default system and service manager but
migrating a service to nosh supervision is just a matter of
disabling it from systemd and enabling its equivalent with nosh.
2. Running nosh as both system and service manager
This is a fully nosh-managed system, the nosh system manager runs
as init.
Various packages provide simple utilities which may be of interest in
themselves, in particular the eponymous nosh script processor.
The nosh toolset has currently been tested for the x86_64 architecture
on qemu/kvm virtual machines and non-virtualised on a laptop with
minimal installs of early 2017 Archlinux releases. Although further
testing is of course ongoing, obtaining a useful working system is made
relatively easy by the comprehensive collection of service bundles
--the native service configuration and control mechanism-- packaged
with the toolset.
Pointers for installing on Archlinux are available in the repository
README.
A guide[6] is available for further information about nosh.
The latest repository archive is available here:
https://framagit.org/taca/archnosh/repository/archive.tar.gz?ref=v1.33-1
It follows the Arch packaging standards as much as possible but can no
doubt be improved.
Regards,
[1] mirrors:
https://framagit.org/taca/archnosh
https://repo.or.cz/archnosh.git
https://github.com/tacatac/archnosh
[2] https://jdebp.eu/Softwares/nosh/
[3] http://www.mail-archive.com/supervision@list.skarnet.org/msg01659.html
[4] https://wiki.archlinux.org/index.php/Init#Service_managers
[5] https://jdebp.eu/Softwares/nosh/debian-binary-packages.html
[6] https://jdebp.eu/Softwares/nosh/guide/
reply other threads:[~2017-04-11 13:15 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=20170410215726.0904d9db@kadisius \
--to=taca@kadisius.eu \
--cc=arch-general@archlinux.org \
--cc=j.deboynepollard-newsgroups@ntlworld.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).