Bug#191036: create /run for programs that run before /var is mounted
On Mon, 28 Apr 2003, Bas Zoetekouw wrote:
> Hi Bill!
> You wrote:
> > Thanks a lot! I will try to improve it again:
> > As an extension to the FHS, the Debian filesystem has a /run directory
> > intended to hold program state file for programs that run early during
> > the boot process when /var is not yet mounted.
> > /run must be in the root filesystem, or it must be made available at the
> > time the root filesystem would be mounted in read-write mode. It must be
> > writeable. It is not required that its content survives system reboot.
> Should't the distinction between /run and /var/run be made more
> explicit? Something like:
> State files must go into /var/run unless they are needed/created before
> /var is mounted rw, in which case they must go into /run.
Well, /run is completely ephemeral as specified so far, while /var/run
*might* retain directories across reboots. Do we want a fully ephemeral
/var/run (this *will* break most packages that have subdirs in there, I have
already fixed mine to recreate the dirs in the initscripts due to user
If we do want an ephermeral /var/run, just symlink it to /run and be done
with it ;-)
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot