From 937a6c666df68633d8f41054053f7be5c9169a6e Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Mon, 28 Oct 2024 16:58:46 -0400 Subject: [PATCH] docs/install: A separate `/boot` is not required We changed this in the code a while back too. Signed-off-by: Colin Walters --- docs/src/bootc-install.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/bootc-install.md b/docs/src/bootc-install.md index 0ecf04706..e39dd147e 100644 --- a/docs/src/bootc-install.md +++ b/docs/src/bootc-install.md @@ -148,9 +148,9 @@ can be configured off at build time via Cargo features. ### Using `bootc install to-filesystem` The usual expected way for an external storage system to work -is to provide `root=` type kernel arguments. At the current -time a separate `/boot` filesystem is also required (mainly to enable LUKS) -so you will also need to provide e.g. `--boot-mount-spec UUID=...`. +is to provide `root=` type kernel arguments. Note that +if a separate `/boot` is needed (e.g. for LUKS) you will also need to +provide `--boot-mount-spec UUID=...`. The `bootc install to-filesystem` command allows an operating system or distribution to ship a separate installer that creates more complex block