Closes: #3586
Signed-off-by: Micah Abbott <miabbott@redhat.com>
files via hardlinks, and they thus need to be immutable to prevent corruption.
Therefore, another way to think of OSTree is that it's just a more polished
version of
-[Linux VServer hardlinks](http://linux-vserver.org/index.php?title=util-vserver:Vhashify&oldid=2285).
+[Linux VServer hardlinks](http://linux-vserver.at/util-vserver:Vhashify).
**Features:**
files via hardlinks, and they thus need to be immutable to prevent corruption.
Therefore, another way to think of OSTree is that it's just a more polished
version of
-[Linux VServer hardlinks](http://linux-vserver.org/index.php?title=util-vserver:Vhashify&oldid=2285).
+[Linux VServer hardlinks](http://linux-vserver.at/util-vserver:Vhashify).
**Features:**
[Chromium Autoupdate](http://dev.chromium.org/chromium-os/chromiumos-design-docs/filesystem-autoupdate),
the much older
[Fedora/Red Hat Stateless Project](https://fedoraproject.org/wiki/StatelessLinux),
-[Linux VServer](http://linux-vserver.org/index.php?title=util-vserver:Vhashify&oldid=2285)
+[Linux VServer](http://linux-vserver.at/util-vserver:Vhashify)
and many more.
As mentioned elsewhere, OSTree is strongly influenced by package