Pre-built binary packages for nosh are available for x86/64 Debian Linux version 7 (or compatible).
You can download the packages from here or configure your machine to use the package repository.
This is the nosh Guide, in HTML. Open it when installed with
or your favourite HTML viewing tool.xdg-open /usr/local/share/doc/nosh/index.html
nosh, and the chain-loading utilities)
service-controland related utilities)
ttylogin-starterand related utilities)
ptyrunand related utilities)
nosh-zsh-completion_1.32_amd64.deb(Z Shell completions for the toolsets)
servicectlshims for systemd compatibility)
chkconfig, and related shims for old-style System 5/BSD compatibility)
initctl, and related shims for upstart compatibility)
update-rc.dshims for Debian compatibility)
fastpoweroffshims for BSD compatibility)
rcctland and related shims for OpenBSD compatibility)
chvtshims for compatibility with the old kbd package)
These install the toolsets under
However, to avert a problem that otherwise makes systems unbootable, they also install a handful of binaries in
This is a suite of service bundles. It comprises:
/etc/service-bundles/targets/, including the
poweroff, and other standard system targets.
You will need this for a working system.
This is an extensive service bundle collection.
There are a lot of service bundles here, including services that conflict (e.g.
exim4-smtp-relay) and services that you probably will not have (e.g.
Installing or upgrading the package will not enable/disable any services or targets. Nor will it start/stop any services. This is a change from prior versions of the package, which used to re-apply preset information and then reset services.
Installation of the various "-run" packages, reliant upon this one, does that and is now the sole way to do that with these binary packages.
Deinstallation will attempt to stop and unload all services in the package. Deinstallation will not disable any services or targets.
Deinstallation of the various "-run" packages, reliant upon this one, does that and is now the sole way to do that with these binary packages.
In an ideal world, the world would ship nosh bundles with its softwares itself, of course. ☺
The "-run" family of packages require the service bundle collection. They employ services in it; which are not started or enabled unless the packages are installed; and which are stopped, disabled, and unloaded from the service manager when the packages are uninstalled.
Rather, they contain preset information in
/usr/local/etc/system-control/presets, and install/deinstall scripts that operate on the relevant services.
Installing a "-run" package presets and resets the relevant services.
Deinstalling a "-run" package disables and stops the relevant services, and unloads them from the service manager.
You can tweak the behaviours with your own local preset information either in
/etc/systemd/system-preset or in
system-manageras process #1
This pre-packages the steps for running a fully nosh-managed system.
It also runs the configuration conversion mechanism in
Note that the default system is fairly minimal.
You'll have to install other -run packages to get things like old-style GNU libc
syslog() service and terminal login services.
In particular, note that you must choose what plug and play device manager (
mdev, and so forth) to run.
Important note: You will need one of these for a working system.
These packages start the several Debian Desktop and Debian Server standard services.
The set of Debian Server services is a strict subset of the Debian Desktop ones, and includes virecover and Debian cron. The set of Debian Desktop services extends that with the likes of CUPS, anacron, and Sun RPC. For D-BUS and other Freedesktop.org services, however, one must install other "-run" packages.
These packages run one of four plug and play managers.
nosh-run-kernel-vt_1.32_amd64.deb(old-style kernel virtual terminals)
nosh-run-user-vt_1.32_amd64.deb(a new-style application-mode virtual terminal)
The old-style kernel virtual terminal system auto-starts a
This monitors the currently active kernel virtual terminal, and auto-starts a
ttylogin@ttyN service on each kernel virtual terminal as it is switched to.
The new-style application-mode virtual terminal auto-starts a
console-fb-realizer@head0 service; the "realizer" service that realizes the multiplex VTs via the (head #0) framebuffer and input event devices.
This connects to the user-mode virtual terminal that is supplied by
which in turn multiplexes the user-mode virtual terminals generated by the
terminal-emulator@vc2 services; whose emulated virtual terminals in their turn are employed by the
The realizer service tells the kernel to disable its built-in terminal emulator program for the duration.
These systems conflict. The head #0 framebuffer and input event device are used by the kernel's virtual terminal emulator. One cannot (without a massive mess of overlapped output and input going to two separate places) realize application-mode virtual terminals onto head #0 whilst simultaneously realizing kernel virtual terminals on the same hardware. So you must only install one of these packages at any one time. The Debian packages are marked so that the package manager will not let you install more than one simultaneously.
This package auto-starts the Freedesktop.org system bus services.
nosh-run-freedesktop-kits_1.32_amd64.deb(Freedesktop.org "kit" services — packagekit, consolekit, policykit, NetworkManager, ModemManager et al.)
This package auto-starts the various Freedesktop.org "kit" services.
Avoid Desktop Bus bus activation.
This package auto-starts the various services that form the VirtualBox Guest Additions:
VBoxService dæmon and the four "vbox" kernel modules.
This package runs the
klogd service, providing logging service to the kernel.
This package runs the
local-syslog-read service, providing old-style logging service to programs that still use
This installs various path, socket, and service unit files for systemd under
/usr/local/lib/systemd/service/, allowing one to use the nosh service management under systemd as the system manager.
- Run a nosh
service-managerdæmon listening on the conventional socket as the nosh
system-control start normal.targetas the nosh
- Run a daemontools-style service scanner monitoring
It also disables the nosh
sysinit standard target, on the basis that systemd handles what that target otherwise handles on a nosh-system-managed system.
Thus, installing this package will break a nosh-system-managed system.
As is the Debian convention installing the package will automatically enable and start all of these systemd units, and removing it will automatically stop and disable them. To set your local preferences in this regard, you can use systemd preset information.