From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-58259-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 3F1A31388B6
	for <garchives@archives.gentoo.org>; Wed,  6 Feb 2013 15:30:51 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E7419E057F;
	Wed,  6 Feb 2013 15:30:47 +0000 (UTC)
Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id EC69BE0384
	for <gentoo-dev@lists.gentoo.org>; Wed,  6 Feb 2013 15:30:46 +0000 (UTC)
Received: by mail-oa0-f43.google.com with SMTP id l10so1619009oag.30
        for <gentoo-dev@lists.gentoo.org>; Wed, 06 Feb 2013 07:30:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:sender:date:from:to:subject:message-id:mail-followup-to
         :references:mime-version:content-type:content-disposition
         :in-reply-to:user-agent;
        bh=B/tfDIW9wTvypxZ64mQMQSvpxOZjR6ut/F1kc4wLIxI=;
        b=idyVJkcttw/UtMegaqgtJ5rX8+NURHE9NvwpxIdSLTbk2IsXPfEieaj/SSAHjiKOgC
         uRHJPBz+bKJH04iulFuju4r0duYpTKlupMgoCzCBYNC7FzUaU4vtqg15Wz2kiAErBctT
         1obEr2K20xN+iSHsFLvZS7ZyYwZ6hXAFnc7XEgCg7rYqku22B6DhGkDm8qlcucvGvCBI
         kaKzZVXf16Z9Swa/PshbXrDRETct3nFRLrieyNQwaKrOSmXWlri0OPvph2JmN5YkkUQE
         iAVzwE2qp4sxdUHEEAhDDjCFRNkmevCRYAR2torIsTAERCFjt837feLuPUkM5uodPAI/
         sAWg==
X-Received: by 10.60.24.201 with SMTP id w9mr22917528oef.73.1360164646045;
        Wed, 06 Feb 2013 07:30:46 -0800 (PST)
Received: from linux1 (cpe-76-187-88-199.tx.res.rr.com. [76.187.88.199])
        by mx.google.com with ESMTPS id w10sm30342136oeg.2.2013.02.06.07.30.42
        (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 06 Feb 2013 07:30:44 -0800 (PST)
Sender: William Hubbs <w.d.hubbs@gmail.com>
Received: by linux1 (sSMTP sendmail emulation); Wed, 06 Feb 2013 09:30:41 -0600
Date: Wed, 6 Feb 2013 09:30:41 -0600
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The /run migration
Message-ID: <20130206153041.GA30148@linux1>
Mail-Followup-To: gentoo-dev@lists.gentoo.org
References: <CAG2jQ8jRxhMXgpMiLvSv5MngZwVMJwDSjp2W-52UjawO=tk1sg@mail.gmail.com>
 <511260D8.8070606@flameeyes.eu>
 <CAG2jQ8iAjUEpx6KDJnwgeJQVnog6b6adw3ooC+YLM3Hrp88sAA@mail.gmail.com>
 <51126285.7000905@flameeyes.eu>
 <5112661B.4030307@gentoo.org>
 <CAG2jQ8ibdw2USYTp-hxswjTDSapeJWRy0KmWcbAUYWz+Ga_f5g@mail.gmail.com>
 <511270C8.9050901@gentoo.org>
 <CAJ0EP43P2NQza3SocoOoFjz_R3tkTQB1BCHkZGXKzWpw50UVCA@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE"
Content-Disposition: inline
In-Reply-To: <CAJ0EP43P2NQza3SocoOoFjz_R3tkTQB1BCHkZGXKzWpw50UVCA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Archives-Salt: 13a77b5e-b887-450d-9a2b-aec4e43d6036
X-Archives-Hash: 52369c7ac191b0e272036c92af78c39d


--Kj7319i9nmIyA2yE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 06, 2013 at 10:23:06AM -0500, Mike Gilbert wrote:
> On Wed, Feb 6, 2013 at 10:03 AM, Ian Stakenvicius <axs@gentoo.org> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On 06/02/13 09:53 AM, Markos Chandras wrote:
> >> On 6 February 2013 14:18, Ian Stakenvicius <axs@gentoo.org> wrote:
> >>>
> >>> So, *my* systems do have /var/run -> /run , which means at some
> >>> point the /run migration did happen and compatibility symlinks
> >>> were created. If hwoarang's systems don't have this, there must
> >>> be an issue somewhere.
> >>>
> >>
> >> My system is a brand new ~testing installation with a
> >> stage3-amd64-20130110.tar.bz2. I am not sure who is responsible
> >> for creating this symlink. I see the symlink is present on that
> >> stage3 tarball so somehow it must have been removed from my system.
> >> Even if it was a user error, then shouldn't there be a mechanism of
> >> recreating it on every boot if it's gone missing? At least until
> >> all init scripts migrate to /run.
> >>
> >
> > ..there was a discussion a week or two back about portage cleaning up
> > symlinks, or something that needs to be done to keep portage warning
> > about symlinks, or something.  Anyways, I'm wondering if a change was
> > made related to that and for whatever reason portage is now cleaning
> > /var/run
> >
>=20
> Portage will "cleanup" the /var/run symlink after unmerging the last
> package that installed files under /var/run.
>=20
> I think an early init script (bootmisc?) needs to create the /var/run
> symlink if it is missing.

The only problem with this approach is it doesn't solve the issue for
people who are not using OpenRc.

William


--Kj7319i9nmIyA2yE
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlESdyEACgkQblQW9DDEZTjoigCfTJP3z0bse5NkYh3akZVWdqin
RBwAoI8k2klHKOYD9HBBvNh4loBFZzBf
=WSTi
-----END PGP SIGNATURE-----

--Kj7319i9nmIyA2yE--