On Thu, 13 May 2010 04:28:27 +0400, sergio <mail...@sergio.spb.ru> wrote:
> On 05/13/2010 04:05 AM, Bdale Garbee wrote:
> 
> > You assert that there is a policy violation where there is none, and
> > I've already explained how you can achieve a trivial resolution of the
> > behavior that bothers you with the existing packages.
> 
> In the Debian policy I see:
> /var/run and /var/lock may be mounted as temporary filesystems[59], so 
> the init.d scripts must handle this correctly.
> 
> "... _must_ handle ..."
> 
> And sudo doesn't handle this correctly. So it's policy violation.
> Where I'm wrong?

Our difference of opinion is over whether showing the lecture every time
is a failure or just an expected behavior when choosing to use RAMRUN.

However, after re-reading the FHS sections on the various /var subdirs,
I now believe that /var/lib may be a better location for the state
information to reside in than /var/run.  I'll raise this question with
sudo upstream.

Bdale

Attachment: pgpWOJdGWj9bU.pgp
Description: PGP signature

Reply via email to