/run pointing to /var/run instead of the opposite
El Viernes, 22 de Julio de 2011, Sven Joachim escribió:
> 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
Ah, nice, it is explained very well there. I looked at the base-files changelog
> > 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.
Ok, since my chroot isn't very used I will probably start from an empty
Thank you very much!
Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2
http://barnacity.net/ | http://disperso.net
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com