From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd
Date: Mon, 21 Dec 2015 22:37:38 +0000 [thread overview]
Message-ID: <201512212237.56009.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20151221224300.313ce5d0@jupiter.sol.kaishome.de>
[-- Attachment #1: Type: Text/Plain, Size: 1515 bytes --]
On Monday 21 Dec 2015 21:43:00 Kai Krakow wrote:
> Am Mon, 21 Dec 2015 16:25:34 -0500
>
> schrieb waltdnes@waltdnes.org:
> > On Mon, Dec 21, 2015 at 02:06:25PM +0000, James wrote
> >
> > > From what I read/understand openrc is in the process of removal from
> > > @system, for all profiles?
> > >
> > In Lennart's dreams... and many peoples' nightmares.
>
> Haters gonna hate...
>
> If I look at the virtual/service-manager ebuild, openrc probably in
> the process of being removed from the system set and replaced by this
> virtual. In that way you can more easily replace openrc with a service
> manager of your choice.
>
> The upgrade path will be straight forward: It doesn't affect your openrc
> installation at all because through the service-manager deps openrc is
> still pulled into the system set - simply by the fact that it is
> installed.
Nevertheless, virtual options to make it easier to use alternatives to the
current stable version of openrc are not my problem at this stage. I can't
get ifplugd to work, unless I start up net.<iface> first and I am getting no
/var/log/rc.log to see what's gone sideways. Regardless of these problems I
am getting warnings on the console during boot time as posted initially.
Am I alone in experiencing this? Any ideas for fixing it? Should I post a
bug and if so where? I'm thinking that asking Lennart to fix ifplugd so that
it works with openrc would be taking it a step too far. :p
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-21 22:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 18:26 [gentoo-user] Problem with openrc-0.18.4 and ifplugd Mick
2015-12-21 1:29 ` thelma
2015-12-21 6:15 ` Mick
2015-12-21 14:06 ` [gentoo-user] " James
2015-12-21 17:21 ` Peter Humphrey
2015-12-21 20:33 ` Alan McKinnon
2015-12-21 20:30 ` Alan McKinnon
2015-12-21 21:25 ` waltdnes
2015-12-21 21:40 ` Neil Bothwick
2015-12-21 22:59 ` »Q«
2015-12-21 23:18 ` Kai Krakow
2015-12-21 21:43 ` Kai Krakow
2015-12-21 22:37 ` Mick [this message]
2015-12-21 22:38 ` Alan McKinnon
2015-12-21 23:20 ` Mick
2015-12-21 23:35 ` Neil Bothwick
2015-12-21 23:55 ` Mick
2015-12-22 0:48 ` Neil Bothwick
2015-12-22 0:54 ` Mick
2015-12-22 1:12 ` Kai Krakow
2015-12-22 14:04 ` Mick
2015-12-22 14:20 ` Kai Krakow
2015-12-22 15:15 ` Mick
2015-12-22 23:32 ` Neil Bothwick
2015-12-23 10:58 ` Mick
2015-12-21 23:41 ` Mick
2015-12-21 23:54 ` Kai Krakow
2015-12-21 23:49 ` Kai Krakow
2015-12-22 0:50 ` Mick
2015-12-22 1:12 ` Kai Krakow
2015-12-21 22:54 ` Kai Krakow
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=201512212237.56009.michaelkintzios@gmail.com \
--to=michaelkintzios@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