mirror of
https://github.com/ostreedev/ostree.git
synced 2025-01-25 10:04:14 +03:00
doc: Update links to Continuous
This commit is contained in:
parent
1b1e3a592e
commit
ec56e1ca8b
@ -177,9 +177,10 @@ d /run/media 0755 root root -
|
||||
</para>
|
||||
<para>
|
||||
The solution chosen for the <ulink
|
||||
url="https://wiki.gnome.org/GnomeOSTree">gnome-ostree</ulink>
|
||||
operating system is to create <filename>/lib/passwd</filename>,
|
||||
and to include a NSS module <ulink
|
||||
url="https://live.gnome.org/Projects/GnomeContinuous">gnome-continuous</ulink>
|
||||
operating system is to create
|
||||
<filename>/usr/lib/passwd</filename>, and to include a NSS
|
||||
module <ulink
|
||||
url="https://github.com/aperezdc/nss-altfiles">nss-altfiles</ulink>
|
||||
which instructs glibc to read from it. Then, the build system places
|
||||
all system users there, freeing up <filename>/etc/passwd</filename>
|
||||
|
@ -40,9 +40,9 @@
|
||||
<para>
|
||||
To begin a simple upgrade, OSTree fetches the contents of the
|
||||
ref from the remote server. Suppose we're tracking a ref named
|
||||
<literal>gnome-ostree/buildmaster/x86_64-runtime</literal>.
|
||||
<literal>exampleos/buildmaster/x86_64-runtime</literal>.
|
||||
OSTree fetches the URL
|
||||
<literal>http://<replaceable>example.com</replaceable>/repo/refs/gnome-ostree/buildmaster/x86_64-runtime</literal>,
|
||||
<literal>http://<replaceable>example.com</replaceable>/repo/refs/exampleos/buildmaster/x86_64-runtime</literal>,
|
||||
which contains a SHA256 checksum. This determines the tree to
|
||||
deploy, and <filename class='directory'>/etc</filename> will be
|
||||
merged from currently booted tree.
|
||||
|
Loading…
x
Reference in New Issue
Block a user