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 10:39:46 -0600 [thread overview]
Message-ID: <5117CD52.8080708@gmail.com> (raw)
In-Reply-To: <5117C334.1080805@gmail.com>
Alan McKinnon wrote:
> On 10/02/2013 17:53, Dale wrote:
>> Alan McKinnon wrote:
>>> It's probably better to leave the symlink in place for now. What
>>> happens when the user installs a package they have never had before
>>> and that package uses /var/run? It will make a directory which isn't
>>> what you want. Better to leave the symlink in place and train your
>>> eyes to ignore the elogs (something we humans are extremely good at)
>> I have a question. On my rig, /var/run does not appear to be a link to
>> /run. For giggles:
>
>
>
> You should re-read the elog you got when /run was created and do what it
> says
>
> :-)
>
>
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 don't see any news item or anything on it. I generally look at elogs
but we know how that works. lol I guess I missed that one.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2013-02-10 16:39 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 [this message]
2013-02-10 16:56 ` Florian Philipp
2013-02-10 17:39 ` Dale
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=5117CD52.8080708@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