From 1e710cc9d8dfcf2472f54cdb1bbc9aa916cdd893 Mon Sep 17 00:00:00 2001 From: Neale Pickett Date: Wed, 5 Dec 2012 17:36:21 -0600 Subject: [PATCH] runit is not a command --- papers/arch-runit.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/papers/arch-runit.mdwn b/papers/arch-runit.mdwn index b6d8c67..d71ec9d 100644 --- a/papers/arch-runit.mdwn +++ b/papers/arch-runit.mdwn @@ -105,7 +105,7 @@ let's make a copy. ln -s busybox.static /usr/local/sbin/sv -We also need to create a new `/sbin/init` to replace `systemd` (or sysvinit) and launch `runit`. +We also need to create a new `/sbin/init` to replace `systemd` (or sysvinit) and launch `runsvdir`. Arch actually has a pretty nice init setup, almost as though they had this use case in mind when they were designing it. The early userspace init sets up /, pivots root, and runs /sbin/init. @@ -301,7 +301,7 @@ Nothing in this page will destroy the old bootup process If it does work --------------- -Congratulations, you're now using `runit`. +Congratulations, you're now using runit. You now need to write startup scripts for things you like to run, like `dhcpcd`, `ntpd`, maybe `xdm`. You're an Arch Linux sysadmin,