chiark / gitweb /
note on relative symlink in os-release
authorRahul Sundaram <metherid@gmail.com>
Wed, 8 Oct 2014 05:42:59 +0000 (01:42 -0400)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Wed, 8 Oct 2014 12:30:22 +0000 (08:30 -0400)
man/os-release.xml

index 4e02f800b63d19cc9c754eb5c35df7a258796596..b2983049432bbb29f2fcac14f0b433ceb192b9f3 100644 (file)
                 files at the same
                 time. <filename>/usr/lib/os-release</filename> is the
                 recommended place to store OS release information as
-                part of vendor trees. Frequently,
-                <filename>/etc/os-release</filename> is simply a
-                symlink to <filename>/usr/lib/os-release</filename>,
+                part of vendor trees.
+                <filename>/etc/os-release</filename> should be a
+                relative symlink to
+                <filename>/usr/lib/os-release</filename>,
                 to provide compatibility with applications only
-                looking at <filename>/etc</filename>.</para>
+                looking at <filename>/etc</filename>. A relative
+                symlink instead of an absolute symlink is
+                necessary to avoid breaking the link in a chroot or
+                initrd environment such as dracut.</para>
 
                 <para><filename>os-release</filename> contains data
                 that is defined by the operating system vendor and