From a8cd654f55faf51b3bb707f4a56757e452d99da3 Mon Sep 17 00:00:00 2001 From: Yusef Aslam Date: Mon, 25 Apr 2022 21:43:40 +0100 Subject: [PATCH 1/3] 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~}. From bf46bee86b94a2d424e94b840e49f1743f6a2d9e Mon Sep 17 00:00:00 2001 From: pave Date: Thu, 12 May 2022 17:46:59 +1000 Subject: [PATCH 2/3] Use less clunky pronouns idk it just.. sounds better? --- markdown/0.7/distro-compatibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/markdown/0.7/distro-compatibility.md b/markdown/0.7/distro-compatibility.md index 76b6e07..e49cbd0 100644 --- a/markdown/0.7/distro-compatibility.md +++ b/markdown/0.7/distro-compatibility.md @@ -61,7 +61,7 @@ non-local components, such as `/etc` files, changing out from under it. over `/etc` file changes. ~+Solus~x _does_ provide default versions of these files, but outside of -`/etc`. The expectation might be that the user copies them over at his/her +`/etc`. The expectation might be that the user copies them over at their whim. This is likely removable with adequate effort. ~+Bedrock~x could be configured From 32843550f342d46ff8877777313148c6216270c0 Mon Sep 17 00:00:00 2001 From: Brahad <94699627+brahad316@users.noreply.github.com> Date: Tue, 12 Jul 2022 01:31:51 +0530 Subject: [PATCH 3/3] Update faq.md Fixed a basic repetition error (of word "can" in line 68). --- markdown/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/markdown/faq.md b/markdown/faq.md index e6432cf..c440007 100644 --- a/markdown/faq.md +++ b/markdown/faq.md @@ -65,7 +65,7 @@ This process is referred to as ~{hijacking~} to emphasize the forceful way Whichever offers the install process you like the most. Once you've had ~+Bedrock~x hijack the install, you're no longer running that -distro - you're running ~+Bedrock~x. You can then can swap out everything +distro - you're running ~+Bedrock~x. You can then swap out everything specific to the hijacked distro with parts from other distros. Once you've configured the system to your liking, the result is functionally the same irrelevant of which install process you happened to use to get there.