FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 07-22-2011, 02:44 PM
Alejandro Exojo
 
Default /run pointing to /var/run instead of the opposite

Hi.

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.

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.

Thank you.

--
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 listmaster@lists.debian.org
Archive: 201107221644.06343.suy@badopi.org">http://lists.debian.org/201107221644.06343.suy@badopi.org
 
Old 07-22-2011, 04:18 PM
Sven Joachim
 
Default /run pointing to /var/run instead of the opposite

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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 8739hyuw5c.fsf@turtle.gmx.de">http://lists.debian.org/8739hyuw5c.fsf@turtle.gmx.de
 
Old 07-23-2011, 03:40 PM
Alejandro Exojo
 
Default /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
> explanations.

Ah, nice, it is explained very well there. I looked at the base-files changelog
only.

> > 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
installation.

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 listmaster@lists.debian.org
Archive: 201107231740.29305.suy@badopi.org">http://lists.debian.org/201107231740.29305.suy@badopi.org
 

Thread Tools




All times are GMT. The time now is 06:00 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org