keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

man: A bit more fleshed out explanation of semantics, link to docker(1)

Browse Source
This commit is contained in:
Colin Walters 2014-06-17 16:42:30 -04:00
parent 3fae1238c0
commit c23e0a9c37
1 changed files with 18 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
man/rpm-ostree.xml
View File

@ -66,13 +66,24 @@ Boston, MA 02111-1307, USA.
<para> <para>
On an rpm-ostree managed system, the traditional On an rpm-ostree managed system, the traditional
<literal>yum</literal> and <literal>rpm</literal> <literal>yum</literal> (if installed) and <literal>rpm</literal>
tools operate in a read-only state. Instead, the tools operate in a read-only state; the RPM database is stored
underlying OSTree layer replicates a filesystem tree in <literal>/usr/share/rpm</literal> which is underneath a
from a compose server. In this "pure replication" read-only bind mount.
model, there is no dependency resolution on the </para>
client machines, nor any ability to add or remove <para>
packages. Instead of live package-by-package upgrades, the underlying
OSTree layer replicates a complete filesystem tree from a
compose server into a new deployment, available on the next
reboot. One benefit of this is that there will always be a
previous deployment, available for rollback.
</para>
<para>
Note in this "pure replication" model, at present there is no
dependency resolution on the client machines, nor any ability to
add or remove packages. You may however use /usr/local/bin, or
an application mechanism such as
<citerefentry><refentrytitle>docker</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
</para> </para>
</refsect1> </refsect1>