diff options
| author | Rahul Sundaram <metherid@gmail.com> | 2014-10-08 01:42:59 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-10-08 08:30:22 -0400 |
| commit | 5a94946cdf38d3574bd32cd3151b32003df60e6a (patch) | |
| tree | 320f79b405d8ae3a6640036bdb3c5325e085d1ad | |
| parent | e94937df954451eb4aa63573f0d7404ed2db987e (diff) | |
note on relative symlink in os-release
| -rw-r--r-- | man/os-release.xml | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/man/os-release.xml b/man/os-release.xml index 4e02f800b6..b298304943 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -90,11 +90,15 @@ 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 |