Hi Bas! On Mon, Apr 28, 2003 at 10:24:27PM +0200, Bas Zoetekouw wrote: > You wrote: > > 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.
I am not sure about that yet. In some border line case, files that would be in /var but not /var/run if /var was mounted will end in /run (or maybe not). As Manoj say, it is too soon to write a policy about it. I am rather interested at solving the chicken and egg problem base-files <--> debian-policy and going forward. So it is sufficient for now to define /run at the system level, not the application level. (At the instant the directory is added, no application use it). Whether or not this go to policy, we cannot add a new top-level directory without a proper definition at the system level. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here.
