packaging
/
ostree
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc/adapting-existing: Elaborate a bit more on FS layout and links

This commit is contained in:
Colin Walters 2013-08-25 10:23:19 -04:00
parent 1ab01a6b35
commit b06e10ebf9
1 changed files with 37 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
doc/adapting-existing.xml
View File

@ -37,11 +37,15 @@
<para> <para>
Because OSTree only preserves <filename Because OSTree only preserves <filename
class='directory'>/var</filename> across upgrades, it is very class='directory'>/var</filename> across upgrades (each
strongly recommended for systems which want to preserve deployment's chroot directory will be garbage collected
compatibility with the <ulink eventually), you will need to choose how to handle other
toplevel writable directories specified by the <ulink
url="http://www.pathname.com/fhs/">Filesystem Hierarchy url="http://www.pathname.com/fhs/">Filesystem Hierarchy
Standard</ulink> to create the following symbolic links: Standard</ulink>. Your operating system may of course choose
not to support some of these such as <filename
class='directory'>/usr/local</filename>, but following is the
recommended set:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
@ -53,6 +57,16 @@
<filename class='directory'>/opt</filename> to <filename class='directory'>/var/opt</filename> <filename class='directory'>/opt</filename> to <filename class='directory'>/var/opt</filename>
</para> </para>
</listitem> </listitem>
<listitem>
<para>
<filename class='directory'>/srv</filename> to <filename class='directory'>/var/srv</filename>
</para>
</listitem>
<listitem>
<para>
<filename class='directory'>/root</filename> to <filename class='directory'>/var/roothome</filename>
</para>
</listitem>
<listitem> <listitem>
<para> <para>
<filename class='directory'>/usr/local</filename> to <filename class='directory'>/var/local</filename> <filename class='directory'>/usr/local</filename> to <filename class='directory'>/var/local</filename>
@ -74,9 +88,10 @@
<para> <para>
Furthermore, since <filename class='directory'>/var</filename> Furthermore, since <filename class='directory'>/var</filename>
is empty by default, your operating system will need to is empty by default, your operating system will need to
dynamically create these directories at boot. A good way to do dynamically create the <emphasis>targets</emphasis> of these at
this is using <command>systemd-tmpfiles</command>, if your OS boot. A good way to do this is using
uses systemd. For example: <command>systemd-tmpfiles</command>, if your OS uses systemd.
For example:
</para> </para>
<programlisting> <programlisting>
@ -100,6 +115,21 @@ d /var/mnt 0755 root root -
d /run/media 0755 root root - d /run/media 0755 root root -
]]> ]]>
</programlisting> </programlisting>
<para>
Particularly note here the double indirection of <filename
class='directory'>/home</filename>. By default, each
deployment will share the global toplevel <filename
class='directory'>/home</filename> directory on the physical
root filesystem. It is then up to higher levels of management
tools to keep <filename>/etc/passwd</filename> or equivalent
synchronized between operating systems.
</para>
<para>
Each deployment can easily be reconfigured to have its own home
directory set simply by making <filename
class='directory'>/var/home</filename> a real directory.
</para>
</chapter> </chapter>
<chapter id="booting"> <chapter id="booting">