From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: OpenRC Networking Scripts
Date: Sun, 27 May 2012 09:56:56 -0500 [thread overview]
Message-ID: <20120527145656.GA5206@linux1> (raw)
In-Reply-To: <4FC23EE3.4060208@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
On Sun, May 27, 2012 at 10:49:07AM -0400, Ian Stakenvicius wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 26/05/12 03:40 PM, William Hubbs wrote:
> > All,
> >
> > I realize this has been discussed and there are definite opinions
> > about which method works well. So, I want to take a different
> > approach.
> >
> > Is there any interest in documenting and supporting newnet along
> > side oldnet as opposed to killing newnet?
> >
> > Newnet would consist of the "network" init script to set up your
> > loopback interface along with something like dhcpcd,
> > networkmanager, or wicd (and wpa_supplicant for wireless
> > interfaces) running in standalone mode to manage your other
> > interfaces.
> >
> > My understanding of the way newnet works is that the big advantage
> > would come for workstations that have a simple network setup and
> > where users would want hotplugged interfaces to just work.
> >
> > Any thoughts?
> >
> > William
> >
>
>
> Just want to point out that my hotplugged interfaces work great with
> oldnet.
Actually they don't, because we don't make or remove the net.* symlinks
in /etc/init.d for the hotplugged interfaces when the interfaces are
added or removed.
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-27 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 19:40 [gentoo-dev] rfc: OpenRC Networking Scripts William Hubbs
2012-05-27 14:49 ` Ian Stakenvicius
2012-05-27 14:56 ` William Hubbs [this message]
2012-05-28 15:57 ` Ian Stakenvicius
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=20120527145656.GA5206@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@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