March 28, 2025 at 12:39 PM, "João" <phlogis...@sapo.pt mailto:phlogis...@sapo.pt?to=%22Jo%C3%A3o%22%20%3Cphlogiston%40sapo.pt%3E > wrote:
> > Hello everyone, > > Now that runit works on the Hurd, I tried to use it as init system and it > worked. The output of ps is attached. This is super cool! Congrats on getting it to work! > If you want to try it you need to set the profs translator by adding > > mount -t proc none /proc -ocompatible > > towards the top of /etc/runit/1. > > To get a getty on the mach-console, I needed to set a run script and > explicitly > set the translator on /dev/console. It looks like this: > > #!/bin/sh > settrans -a /dev/console /hurd/term --type=device console --name=console > exec /sbin/getty 38400 console > > I have not yet tried to get the hurd-console working, but this will probably > involve starting the console server (under runit supervision?), setting the > translators for the different tty and running getty on them? > > Then replace init in /etc/hurd/runsystem.sysv with /sbin/runit-init (or write > an > equivalent /etc/hurd/runsystem.runit and point to it using the > /etc/alternatives > system). > > On the topic of init systems, many will know that GNU Shepher 1.0 has been > released > (https://www.gnu.org/software/shepherd/news/2024/12/the-shepherd-1.0.0-released/), > and it is in Debian but not yet building on the hurd > (https://buildd.debian.org/status/package.php?p=shepherd). > Shepherd was initially designed as the init system for the Hurd. Any design > features that make such association advantageous? > > Best regards, > João >
