Re: /run pointing to /var/run instead of the opposite

[Sven Joachim <svenjoac@gmx.de>]

On 2011-07-22 16:44 +0200, Alejandro Exojo wrote:

> I'm running Debian unstable, and I have a chroot environment where I have 
> another Debian unstable installation. Today I've updated the chroot 
> environment because it was very dated, and I've noticed that /run is a 
> symbolic link pointing to /var/run, instead of the other way round:
>
> In the chroot:
> $ file /run /var/run/
> /run:      symbolic link to `/var/run'
> /var/run/: directory
>
> In the true system:
> $ file /run/ /var/run
> /run/:    directory
> /var/run: symbolic link to `/run'
>
> I think I can do the changes myself by hand, but I wonder if it will be 
> appropriate (maybe is that way for a reason), or if I have hit a bug that I 
> should report.

This is intentional, read the sysvinit 2.88dsf-13.3 changelog entry for
explanations.

> I need to change it because I need an application in the chroot to connect to 
> CUPS from outside the chroot, and this is done through a socket on 
> (/var)/run/cups. And schroot can't do the bind mount if the chroot /run is a 
> link.

I guess you need to do the changes yourself then.  Note that the problem
does not exist in freshly debootstrapped chroots.

Sven