Bug#620870: debian-policy: Please add /run as FHS exception
On Wed, Jun 15, 2011 at 05:50:52PM +0200, Michael Biebl wrote:
> Am 08.06.2011 23:22, schrieb Bill Allombert:
> > Hello Cyril and Michael,
> >
> > Are you willing to resecond this as the final version ?
>
>
> At the current state, I'm not for adding /run/shm to debian-policy.
> If we can get wider acceptance of this feature (cross-distro), then my position
> on this might change. Atm this looks like a Debian-only feature with no real
> use-case why we need that.
Do you still hold that opinion ?
Would anybody object to Roger patch being applied without the reference to /run/shm,
and leave this particular topic to another bug report ?
Beside, I attach an alternative patch by Thomas Hood that I found in the log
but which was not send to the list.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
--- policy.sgml_ORIG 2010-07-26 06:44:57.000000000 +0200
+++ policy.sgml 2011-06-21 13:10:15.815787305 +0200
@@ -5987,11 +5987,30 @@
<item>
<p>
The following directories in the root filesystem are
- additionally allowed: <file>/sys</file> and
- <file>/selinux</file>. <footnote>These directories
- are used as mount points to mount virtual filesystems
- to get access to kernel information.</footnote>
- </p>
+ additionally allowed: <file>/run</file>,
+ <footnote>
+ The purpose of the /run hierarchy is storage of ephemeral
+ system state, that is, state information that should
+ not be preserved across a reboot.
+ Files and directories residing in <file>/run</file>
+ should be stored on a temporary filesystem.
+ The <file>/run</file> directory is a
+ replacement for <file>/var/run</file>; its
+ subdirectory <file>/run/lock</file> is a replacement for
+ <file>/var/lock</file>.
+ /run/ and /run/lock/ have been introduced
+ by most distributions and are on track to be
+ endorsed by the FHS.
+ Additionally, the subdirectory <file>/run/shm</file>
+ is a replacement for <file>/dev/shm</file>.
+ </footnote>
+ <file>/sys</file> and <file>/selinux</file>.
+ <footnote>
+ The <file>/sys</file> and <file>/selinux</file>
+ directories are mount points where
+ virtual filesystems are mounted which provide access
+ to kernel information.
+ </footnote>
</item>
</enumlist>
@@ -6489,15 +6508,17 @@
</p>
<p>
- <file>/var/run</file> and <file>/var/lock</file> may be mounted
- as temporary filesystems<footnote>
- For example, using the <tt>RAMRUN</tt> and <tt>RAMLOCK</tt>
- options in <file>/etc/default/rcS</file>.
- </footnote>, so the <file>init.d</file> scripts must handle this
- correctly. This will typically amount to creating any required
- subdirectories dynamically when the <file>init.d</file> script
- is run, rather than including them in the package and relying on
- <prgn>dpkg</prgn> to create them.
+ Files and directories under <file>/run</file>, including those
+ in directories <file>/var/run</file> and <file>/var/lock</file>
+ which are symlinks or bind mounts to subdirectories of
+ <file>/run</file>, are normally stored on a temporary
+ filesystem and are normally not persistent across a reboot.
+ Consequently, packages cannot assume that these files or
+ directories are present at system boot time.
+ Files and directories under <file>/run</file> must not be
+ included in packages; such files or directories
+ must be created dynamically, for example, in the
+ <file>init.d</file> script.
</p>
</sect1>
Reply to: