From 1ab01a6b35db9001ef9bbc41c0d97118f83a9b47 Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Sat, 24 Aug 2013 19:18:57 -0400 Subject: [PATCH] doc/adapting-existing: A bit more elaboration and a typo fix --- doc/adapting-existing.xml | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/doc/adapting-existing.xml b/doc/adapting-existing.xml index f6514791..d02e70b3 100644 --- a/doc/adapting-existing.xml +++ b/doc/adapting-existing.xml @@ -4,7 +4,7 @@ ]> - Adapating existing mainstream distributions + Adapting existing mainstream distributions System layout @@ -20,18 +20,19 @@ - The /sysroot directory is - a new OS-level directory that OSTree expects to use as a bind - mount target to the physical / root directory. Remember, - because by default the system is booted into a + Remember, because by default the system is booted into a chroot equivalent, there has to be some way - to refer to the actual physical root filesystem, and there is - precedent for this name in the initramfs context. This - directory must exist; for example, the OSTree tool at runtime - expects that /sysroot/ostree/repo refers to the - system repository. + to refer to the actual physical root filesystem. Therefore, + your operating system tree should contain an empty /sysroot directory; at boot time, + OSTree will make this a bind mount to the physical / root + directory. There is precedent for this name in the initramfs + context. You should furthermore make a toplevel symbolic link + /ostree which points to + /sysroot/ostree, so that + the OSTree tool at runtime can consistently find the system data + regardless of whether it's operating on a physical root or + inside a deployment.