Florian Philipp wrote:
> Am 10.02.2013 17:39, schrieb Dale:
> [...]
>>>
>>
>> Actually, I had something that wouldn't start and said it needed /run.
>> I didn't have one, found references with google that it was the new and
>> upcoming thing, so I created it myself. So, it must have been a bug
>> that should have been reported but I didn't realize that. By creating
>> it myself, I created a bit of a problem. Now what to do about it.
>>
>
> I guess the simplest approach is:
> 1. drop into single user runlevel (`rc single`)
> 2. move the remnants from /var/run to /run
> 3. symlink /var/run to /run
> 4. reboot or go back to default runlevel (`rc default`)
>
> Hope this helps,
> Florian Philipp
>
>


Since you mention rc single.  I did that a good while back.  Afterwards
I went to boot runlevel then to the default runlevel.  When I got to the
default runlevel, it was not working like it should.  I rebooted and
everything was back to normal.  Have you ever ran into that?  It's been
a while, most likely when the openrc change was going on.  Just curious.

I may give that a try.  That sounds like a plan.  I'll be ready for a
reboot tho, just in case.  lol

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!