From ff010dea445e959da8704090a977f85421c9453c Mon Sep 17 00:00:00 2001 From: Matthias Braun Date: Sat, 25 May 2024 23:25:14 +0200 Subject: [PATCH] Update 6-lets-talk-about-forks-and-cows.mdx fix grammar --- src/content/chapters/6-lets-talk-about-forks-and-cows.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/chapters/6-lets-talk-about-forks-and-cows.mdx b/src/content/chapters/6-lets-talk-about-forks-and-cows.mdx index 0f06e7c..2e3b653 100644 --- a/src/content/chapters/6-lets-talk-about-forks-and-cows.mdx +++ b/src/content/chapters/6-lets-talk-about-forks-and-cows.mdx @@ -214,7 +214,7 @@ Now the kernel can find a suitable init program to run: On Linux, the init program is almost always located at or symbolic-linked to `/sbin/init`. Common inits include [systemd](https://systemd.io/) (which has an abnormally good website), [OpenRC](https://wiki.gentoo.org/wiki/OpenRC/openrc-init), and [runit](http://smarden.org/runit/). `kernel_init` will default to `/bin/sh` if it can't find anything else — and if it can't find `/bin/sh`, something is TERRIBLY wrong. -*MacOS has an init program, too! It's called launchd and is located at `/sbin/launchd`. Try running that in a terminal to get yelled for not being a kernel.* +*MacOS has an init program, too! It's called launchd and is located at `/sbin/launchd`. Try running that in a terminal to get yelled at for not being a kernel.* From this point on, we're at step 4 in the boot process: the init process is running in userland and begins launching various programs using the fork-exec pattern.