Re: /run vs /var/run (was: Please test new sysvinit)
Steve Langasek <firstname.lastname@example.org> wrote:
> On Sun, Dec 18, 2005 at 03:57:35AM +0000, Matthew Garrett wrote:
>> Under Linux, can't all of this be done with mount --move anyway? I'm not
>> convinced that we actually need a /run any more.
> So you would have these files stored in /var/run from the beginning, and use
> mount --move to shuffle them around if /var is a separate mount point? I'm
> pretty sure --move is a 2.6-only feature, too, and we haven't yet gotten rid
> of 2.4 for etch; and is there an equivalent solution for non-Linux ports?
Yeah, it's 2.6 only. Are we seriously expecting to ship etch with 2.4
kernels? Is anyone still doing active security support for it?
The linux-onlyness of it is a bit more awkward, but non-Linux OSs tend
to be lacking things like decent ram filesystems anyway, so the
semantics are going to vary in any case. But I guess if it's difficult,
sticking with /run might be easier. Has anyone talked to the FHS guys
about this? (I haven't actually checked whether it's in there, so the
answer may well be "yes" :) )
Matthew Garrett | email@example.com