| 1 |
On Wed, Feb 06, 2013 at 10:23:06AM -0500, Mike Gilbert wrote: |
| 2 |
> On Wed, Feb 6, 2013 at 10:03 AM, Ian Stakenvicius <axs@g.o> wrote: |
| 3 |
> > -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> > Hash: SHA256 |
| 5 |
> > |
| 6 |
> > On 06/02/13 09:53 AM, Markos Chandras wrote: |
| 7 |
> >> On 6 February 2013 14:18, Ian Stakenvicius <axs@g.o> wrote: |
| 8 |
> >>> |
| 9 |
> >>> So, *my* systems do have /var/run -> /run , which means at some |
| 10 |
> >>> point the /run migration did happen and compatibility symlinks |
| 11 |
> >>> were created. If hwoarang's systems don't have this, there must |
| 12 |
> >>> be an issue somewhere. |
| 13 |
> >>> |
| 14 |
> >> |
| 15 |
> >> My system is a brand new ~testing installation with a |
| 16 |
> >> stage3-amd64-20130110.tar.bz2. I am not sure who is responsible |
| 17 |
> >> for creating this symlink. I see the symlink is present on that |
| 18 |
> >> stage3 tarball so somehow it must have been removed from my system. |
| 19 |
> >> Even if it was a user error, then shouldn't there be a mechanism of |
| 20 |
> >> recreating it on every boot if it's gone missing? At least until |
| 21 |
> >> all init scripts migrate to /run. |
| 22 |
> >> |
| 23 |
> > |
| 24 |
> > ..there was a discussion a week or two back about portage cleaning up |
| 25 |
> > symlinks, or something that needs to be done to keep portage warning |
| 26 |
> > about symlinks, or something. Anyways, I'm wondering if a change was |
| 27 |
> > made related to that and for whatever reason portage is now cleaning |
| 28 |
> > /var/run |
| 29 |
> > |
| 30 |
> |
| 31 |
> Portage will "cleanup" the /var/run symlink after unmerging the last |
| 32 |
> package that installed files under /var/run. |
| 33 |
> |
| 34 |
> I think an early init script (bootmisc?) needs to create the /var/run |
| 35 |
> symlink if it is missing. |
| 36 |
|
| 37 |
The only problem with this approach is it doesn't solve the issue for |
| 38 |
people who are not using OpenRc. |
| 39 |
|
| 40 |
William |
Archives