From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to do with /var/run?
Date: Sun, 10 Feb 2013 11:39:51 -0600 [thread overview]
Message-ID: <5117DB67.8090808@gmail.com> (raw)
In-Reply-To: <5117D14D.8070501@binarywings.net>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
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!
[-- Attachment #2: Type: text/html, Size: 1977 bytes --]
next prev parent reply other threads:[~2013-02-10 17:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 5:11 [gentoo-user] What to do with /var/run? Grant
2013-02-10 6:47 ` J. Roeleveld
2013-02-10 7:04 ` J. Roeleveld
2013-02-10 8:28 ` Florian Philipp
2013-02-10 11:49 ` Michael Mol
2013-02-10 12:40 ` Alan McKinnon
2013-02-10 13:14 ` Michael Mol
2013-02-10 13:33 ` Alan McKinnon
2013-02-10 13:42 ` Florian Philipp
2013-02-10 17:58 ` Neil Bothwick
2013-02-10 15:29 ` covici
2013-02-10 15:55 ` Alan McKinnon
2013-02-10 16:46 ` covici
2013-02-10 17:03 ` Florian Philipp
2013-02-10 18:01 ` covici
2013-02-10 18:41 ` Florian Philipp
2013-02-10 19:14 ` covici
2013-02-10 20:54 ` Alan McKinnon
2013-02-10 21:41 ` covici
2013-02-10 15:53 ` Dale
2013-02-10 15:56 ` Alan McKinnon
2013-02-10 16:39 ` Dale
2013-02-10 16:56 ` Florian Philipp
2013-02-10 17:39 ` Dale [this message]
2013-02-10 17:56 ` Neil Bothwick
2013-02-10 18:00 ` Florian Philipp
2013-02-10 19:17 ` Grant
2013-02-10 19:42 ` Florian Philipp
2013-02-16 20:08 ` Grant
2013-02-16 23:28 ` Florian Philipp
2013-02-10 13:14 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5117DB67.8090808@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox