From a8cd654f55faf51b3bb707f4a56757e452d99da3 Mon Sep 17 00:00:00 2001 From: Yusef Aslam Date: Mon, 25 Apr 2022 21:43:40 +0100 Subject: [PATCH] Fix typo --- markdown/0.7/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/markdown/0.7/debugging.md b/markdown/0.7/debugging.md index e39fd6a..f871fda 100644 --- a/markdown/0.7/debugging.md +++ b/markdown/0.7/debugging.md @@ -41,7 +41,7 @@ Many bootloaders allow users to alter the kernel line for a session. Bedrock is dependent on various runtime items being in placed, and thus one may not simply mount a Bedrock partition and `chroot` into it. -One common need to `choot` into some system is to fix a broken `/boot`. While a generalized `chroot` is not available, a limited one for this purpose is. There are three main differences from a typical rescue `chroot`: +One common need to `chroot` into some system is to fix a broken `/boot`. While a generalized `chroot` is not available, a limited one for this purpose is. There are three main differences from a typical rescue `chroot`: - Instead of setting up and `chroot`'ing directly into the mount, setup and `chroot` into `~(mount~)/bedrock/strata/~(stratum~)` for some ~{stratum~} which will perform the repair operation. - In addition to the typical `proc`, `dev`, etc setup, also bind-mount `~(mount~)/boot` to `~(mount~)/bedrock/strata/~(stratum~)/boot`. This will make the ~{global~} `/boot` accessible for manipulation by the given ~{stratum~}.