public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to do with /var/run?
Date: Sun, 10 Feb 2013 09:28:25 +0100	[thread overview]
Message-ID: <51175A29.3090002@binarywings.net> (raw)
In-Reply-To: <CAN0CFw15FF-FaPrUehXdPE_+42s7voKNGj4jz_O1aoCMGHrfvw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

Am 10.02.2013 06:11, schrieb Grant:
> I received the following ELOG message after an emerge:
> 
>  * One or more symlinks to directories have been preserved in order to
>  * ensure that files installed via these symlinks remain accessible. This
>  * indicates that the mentioned symlink(s) may be obsolete remnants of an
>  * old install, and it may be appropriate to replace a given symlink with
>  * the directory that it points to.
>  *
>  * /var/run
> 
> Should I change anything?
> 
> - Grant
> 

If my understanding of the situation is correct, we see this message
whenever a package is updated that in the old version installed to
/var/run and now has migrated to /run.

Even if I'm wrong, there is nothing to be done. /var/run is intended to
be a symlink to /run. If it is, then all is fine.

Regards,
Florian Philipp



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  parent reply	other threads:[~2013-02-10  8:28 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 [this message]
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
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=51175A29.3090002@binarywings.net \
    --to=lists@binarywings.net \
    --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