Hello Roger, On Sun, Sep 18, 2011 at 07:57:59PM +0100, Roger Leigh wrote: > The problem here is that both are correct--in different circumstances-- > and it's very difficult to know after the fact that it's "wrong", so > you are correct that fixing it is hard. In fact, automated switching > can't be done during an upgrade due to in-use files etc., which is > why initscripts does it early during boot and why it can't be done in > a chroot. > > We could possibly check if /run is a symlink *and* we're not in a chroot > during bootup and print a warning if present. But it will need some > careful consideration--e.g. it might legitimitely be this way on e.g. > GNU/Hurd, and it's not really "wrong" to manually configure it this way > on Linux, either.
Feel free to consider this and either add such a check or close this
bug, depending on what the outcome is. I just wonder why the "other"
way around is not "wrong", since this produced weired effects at least
on my system, like cron not noticing system startup.
Greetings
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
