From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to do with /var/run?
Date: Sun, 17 Feb 2013 00:28:37 +0100 [thread overview]
Message-ID: <51201625.1050609@binarywings.net> (raw)
In-Reply-To: <CAN0CFw1=EMVXguPKDWvVS-icBH_jSWE8E2ENkLsaec9jm6ig5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Am 16.02.2013 21:08, schrieb Grant:
>>>>> 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`)
>>>>
>>>> /run is a tmpfs mounted at boot time, so anything you copy in there
>>>> before rebooting will disappear.
>>>
>>> Ah that makes sense. /run/openerp/ disappears after a reboot and
>>> re-emerging openerp brings it back. Should that be an ebuild bug?
>>>
>>> - Grant
>>>
>>
>> Flameeyes was faster:
>> https://bugs.gentoo.org/show_bug.cgi?id=451764
>>
>> There is a blocker bug for the migration:
>> https://bugs.gentoo.org/show_bug.cgi?id=332633
>
> Diego is using openerp-server and I'm using openerp. So I'm sure I
> understand, does this mean I should file a "keepdirs /var/run" bug for
> openerp?
>
> - Grant
>
If there is no bug referenced as a dependency of the blocker bug I
linked, by all means, do it (and reference the blocker bug).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-02-16 23:29 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
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 [this message]
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=51201625.1050609@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