doc/adapting-existing: A bit more elaboration and a typo fix
This commit is contained in:
parent
84f2cd249a
commit
1ab01a6b35
|
|
@ -4,7 +4,7 @@
|
||||||
<!ENTITY version SYSTEM "../version.xml">
|
<!ENTITY version SYSTEM "../version.xml">
|
||||||
]>
|
]>
|
||||||
<part id="adapting-existing">
|
<part id="adapting-existing">
|
||||||
<title>Adapating existing mainstream distributions</title>
|
<title>Adapting existing mainstream distributions</title>
|
||||||
<chapter id="layout">
|
<chapter id="layout">
|
||||||
<title>System layout</title>
|
<title>System layout</title>
|
||||||
<para>
|
<para>
|
||||||
|
|
@ -20,18 +20,19 @@
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The <filename class='directory'>/sysroot</filename> directory is
|
Remember, because by default the system is booted into a
|
||||||
a new OS-level directory that OSTree expects to use as a bind
|
|
||||||
mount target to the physical <filename
|
|
||||||
class='directory'>/</filename> root directory. Remember,
|
|
||||||
because by default the system is booted into a
|
|
||||||
<literal>chroot</literal> equivalent, there has to be some way
|
<literal>chroot</literal> equivalent, there has to be some way
|
||||||
to refer to the actual physical root filesystem, and there is
|
to refer to the actual physical root filesystem. Therefore,
|
||||||
precedent for this name in the initramfs context. This
|
your operating system tree should contain an empty <filename
|
||||||
directory must exist; for example, the OSTree tool at runtime
|
class='directory'>/sysroot</filename> directory; at boot time,
|
||||||
expects that <filename
|
OSTree will make this a bind mount to the physical / root
|
||||||
class='directory'>/sysroot/ostree/repo</filename> refers to the
|
directory. There is precedent for this name in the initramfs
|
||||||
system repository.
|
context. You should furthermore make a toplevel symbolic link
|
||||||
|
<filename class='directory'>/ostree</filename> which points to
|
||||||
|
<filename class='directory'>/sysroot/ostree</filename>, 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.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue