Bug#514326: debian-policy: fhs-2.3 doesn't specify that /var/run and /var/lock may be volatile ref rcS(5)

[Tim Small <tim@buttersideup.com>]

Package: debian-policy
Version: 3.8.0.1
Severity: wishlist
Tags: patch

The requirements for /var/run and var/lock don't specify that the
contents of these directories may be volatile (e.g. ramdisk based,
as happens if you enable the RAMRUN option in /etc/default/rcS).

Some packages assume that sub-directory structures in these directories
will persist, and fail if this isn't the case (e.g bug #349830 ).

Same goes for var/lock.

I think a sentence should be added to the "requirement" statement for
each which states that:

"
It should not be assumed that the contents of this directory will
persist after a system reboot.
"


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

-- no debconf information