The nosh FreeBSD binary packages

nosh pages:

Pre-built binary packages for nosh are available for x86/64 FreeBSD version 10 (or compatible).

You can download the packages from here or configure your machine to use the package repository.

You can view a list of the packages in the repository via GOPHER or via FTP in EPLF.

Doco

This is the nosh Guide, in HTML. Open it when installed with

xdg-open /usr/local/share/doc/nosh/index.html
or your favourite HTML viewing tool.

Toolsets

These install the toolsets under /usr/local. However, to avert a problem that otherwise makes systems unbootable, they also install a handful of binaries in /bin: /bin/nosh, /bin/exec, /bin/cyclog, /bin/system-manager, and /bin/system-control.

Service bundles

This is a suite of service bundles. It comprises:

Important notes:

In an ideal world, the world would ship nosh bundles with its softwares itself, of course. ☺

-run packages

The "-run" family of packages require the service bundle collection. They employ service bundles in it; and do not themselves contain any service bundles.

Rather, they contain preset information in /etc/system-control/presets and /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 /etc/system-control/presets.

Running a fully nosh-managed system with system-manager as process #1

This pre-packages the steps for running a fully nosh-managed system. It adjusts init_path in /boot/loader.conf to point to /sbin/system-manager. It also runs the configuration conversion mechanism in /etc/system-control/convert.

Note that the default system enables no services at all. You'll have to install other -run packages to get things like old-style BSD libc syslog() service and terminal login services.

Running FreeBSD and TrueOS/PC-BSD base services

Important note: You will need one of these for a working system.

These packages start the several FreeBSD/TrueOS Desktop and FreeBSD/TrueOS Server standard services.

The set of TrueOS Server services is a strict subset of the TrueOS Desktop ones, and includes the AppCafe ngnix server, ipfw, openntpd, devd, virecover, and Vixie cron. The set of TrueOS Desktop services extends that with the likes of powerd, CUPS, anacron, and Sun RPC. For D-BUS and other Freedesktop.org services, however, one must install other "-run" packages.

The set of FreeBSD Server services is similarly a strict subset of the FreeBSD Desktop ones, and includes ipfw, openntpd, devd, virecover, and Vixie cron. The set of FreeBSD Desktop services extends that with the likes of powerd, CUPS, anacron, and Sun RPC.

Virtual terminal services

The old-style kernel virtual terminal system auto-starts a ttylogin@ttyN service on each kernel virtual terminal at startup, as configured by /etc/ttys.

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 console-multiplexor@head0; which in turn multiplexes the user-mode virtual terminals generated by the terminal-emulator@vc0, terminal-emulator@vc1, and terminal-emulator@vc2 services; whose emulated virtual terminals in their turn are employed by the ttylogin@vc0-tty, ttylogin@vc1-tty, and ttylogin@vc2-tty services. 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 BSD package manager does not provide an easy means of enforcing this, unfortunately.

OpenSSH server

This package auto-starts the OpenSSH server.

Freedesktop.org system bus services

This package auto-starts the Freedesktop.org system bus services.

Freedesktop.org "kit" services

This package auto-starts the various Freedesktop.org "kit" services.

Avoid Desktop Bus bus activation.

VirtualBox Guest Additions

This package auto-starts the various services that form the VirtualBox Guest Additions: the VBoxService dæmon and the four "vbox" kernel modules.

kernel log service

This package runs the klogd service, providing logging service to the kernel.

local syslog() service

This package runs the local-syslog-read service, providing old-style logging service to programs that still use /run/log.

bcron

This package auto-starts the services for Bruce Guenter's bcron.

Running nosh service management under Mewburn rc

This installs various rc.d scripts for running allowing one to use the nosh service management under Mewburn rc (the rc system used on FreeBSD, DragonFly BSD, PC-BSD, et al.).

It also disables the nosh sysinit standard target, on the basis that rc handles what that target otherwise handles on a nosh-system-managed system. Thus, installing this package will break a nosh-system-managed system.

Running nosh service management under OpenRC

This installs various init.d scripts for running allowing one to use the nosh service management under OpenRC (the rc system used on Gentoo, TrueOS, et al.).

It also disables the nosh sysinit standard target, on the basis that rc handles what that target otherwise handles on a nosh-system-managed system. Thus, installing this package will break a nosh-system-managed system.


© Copyright 2015,2016,2018 Jonathan de Boyne Pollard. "Moral" rights asserted.
Permission is hereby granted to copy and to distribute this WWW page in its original, unmodified form as long as its last modification datestamp information is preserved.