Bug#669949: Found the answer

2012-05-13 Thread Roger Leigh
On Sat, May 12, 2012 at 06:10:37PM -0700, Dean Loros wrote:
 Found it---In my system /run was a symlink to /var/run--So my guess is that
 the mount script was going crazy  giving up...I remember about a year or
 so ago there was a problem with /var/run  /run  the fix was linking
 /run to /var/runI wonder how many systems are still running this
 way.  I recreated the /run folder  populated it with the contents of
 /var/run  now things work as expected...  Interesting little puzzle--glad
 to have found the answer.

Thanks for all the investigation.  To be honest, I'm surprised that
this makes a difference.  Though if you had a separately-mounted /var,
I suspect it would have been rather more broken (/run couldn't be
mounted, or it would be later hidden on mounting /var).

I'll take a look and see what might have caused the change in
behaviour, and now you've identified the cause, I'll see if I can
reproduce it on a virtualbox VM.


Thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linuxhttp://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-GPG Public Key  F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#669949: Found the answer

2012-05-12 Thread Dean Loros
Found it---In my system /run was a symlink to /var/run--So my guess is that
the mount script was going crazy  giving up...I remember about a year or
so ago there was a problem with /var/run  /run  the fix was linking
/run to /var/runI wonder how many systems are still running this
way.  I recreated the /run folder  populated it with the contents of
/var/run  now things work as expected...  Interesting little puzzle--glad
to have found the answer.

-- 
Cheers!!!
Dean Loros
Performance by Design Ltd.
autocrosser at http://forums.linuxmint.com