f1004dc
From 5a94946cdf38d3574bd32cd3151b32003df60e6a Mon Sep 17 00:00:00 2001
f1004dc
From: Rahul Sundaram <metherid@gmail.com>
f1004dc
Date: Wed, 8 Oct 2014 01:42:59 -0400
f1004dc
Subject: [PATCH] note on relative symlink in os-release
f1004dc
f1004dc
---
f1004dc
 man/os-release.xml | 12 ++++++++----
f1004dc
 1 file changed, 8 insertions(+), 4 deletions(-)
f1004dc
f1004dc
diff --git a/man/os-release.xml b/man/os-release.xml
f1004dc
index 4e02f800b6..b298304943 100644
f1004dc
--- a/man/os-release.xml
f1004dc
+++ b/man/os-release.xml
f1004dc
@@ -90,11 +90,15 @@
f1004dc
                 files at the same
f1004dc
                 time. <filename>/usr/lib/os-release</filename> is the
f1004dc
                 recommended place to store OS release information as
f1004dc
-                part of vendor trees. Frequently,
f1004dc
-                <filename>/etc/os-release</filename> is simply a
f1004dc
-                symlink to <filename>/usr/lib/os-release</filename>,
f1004dc
+                part of vendor trees.
f1004dc
+                <filename>/etc/os-release</filename> should be a
f1004dc
+                relative symlink to
f1004dc
+                <filename>/usr/lib/os-release</filename>,
f1004dc
                 to provide compatibility with applications only
f1004dc
-                looking at <filename>/etc</filename>.</para>
f1004dc
+                looking at <filename>/etc</filename>. A relative
f1004dc
+                symlink instead of an absolute symlink is
f1004dc
+                necessary to avoid breaking the link in a chroot or
f1004dc
+                initrd environment such as dracut.</para>
f1004dc
 
f1004dc
                 <para><filename>os-release</filename> contains data
f1004dc
                 that is defined by the operating system vendor and