From: Alessandro DE LAURENZIS <just22.adl@gmail.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up
Date: Sun, 1 Dec 2013 11:20:15 +0100 [thread overview]
Message-ID: <20131201102015.GA1219@egeo> (raw)
I've just upgraded to the latest openrc version; I was aware of the
netifrc USE flag introduction
(http://www.gossamer-threads.com/lists/gentoo/user/275748). But so far
the presence of the newnet flag was actually a "switch" between the old
and the new network stack, given that one of the two should (must?) be
added in any case.
Now the presence of both netifrc and newnet could make a bit of
confusion, particularly from a user perspective. We have of course 4
cases; two of them are clear:
1) netifrc -newnet: "legacy" network stack;
2) -netifrc newnet: "new" network stack.
The other two cases need a clarification:
3) -netifrc -newnet: no network stack?!?
4) netifrc newnet: ???
This should be definitely documented somewhere (I didn't find anything).
And, the last question: what's the point to have two flags instead the
good old one?
Thanks for any clarification.
--
Alessandro DE LAURENZIS
[mailto:just22.adl@gmail.com]
LinkedIn: http://it.linkedin.com/in/delaurenzis
next reply other threads:[~2013-12-01 10:20 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 10:20 Alessandro DE LAURENZIS [this message]
2013-12-01 10:36 ` [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up Alexander V Vershilov
2013-12-02 20:28 ` William Hubbs
2013-12-02 21:19 ` Rick "Zero_Chaos" Farina
2013-12-02 21:24 ` Ian Stakenvicius
2013-12-03 17:32 ` Alexander V Vershilov
2013-12-03 21:11 ` William Hubbs
2013-12-03 21:43 ` Ian Stakenvicius
2013-12-03 23:00 ` William Hubbs
2013-12-03 23:29 ` Ian Stakenvicius
2013-12-04 1:14 ` mingdao
2013-12-04 15:57 ` William Hubbs
2013-12-04 16:46 ` Samuli Suominen
2013-12-04 21:25 ` William Hubbs
2013-12-04 21:30 ` Mike Gilbert
2013-12-04 22:31 ` William Hubbs
2013-12-04 22:36 ` Mike Gilbert
2013-12-04 23:42 ` William Hubbs
2013-12-05 17:03 ` Samuli Suominen
2013-12-05 8:01 ` Martin Gysel
2013-12-05 9:23 ` Steev Klimaszewski
2013-12-04 23:45 ` Patrick Lauer
2013-12-05 0:13 ` William Hubbs
2013-12-05 0:20 ` Patrick Lauer
2013-12-05 0:17 ` Mike Gilbert
2013-12-05 1:56 ` William Hubbs
2013-12-06 15:26 ` Ian Stakenvicius
2013-12-06 15:38 ` Ben Kohler
2013-12-05 7:39 ` Alan McKinnon
2013-12-05 12:30 ` Rich Freeman
2013-12-05 17:01 ` Samuli Suominen
2013-12-07 5:52 ` Rick "Zero_Chaos" Farina
2013-12-07 12:42 ` Rich Freeman
2013-12-07 14:22 ` Rick "Zero_Chaos" Farina
2013-12-07 23:25 ` Rich Freeman
2013-12-08 2:34 ` Peter Stuge
2013-12-08 22:31 ` William Hubbs
2013-12-14 6:22 ` Jorge Manuel B. S. Vicetto
2013-12-14 17:18 ` Jeroen Roovers
2013-12-07 15:04 ` Peter Stuge
2013-12-08 22:25 ` William Hubbs
2013-12-09 14:50 ` Rick "Zero_Chaos" Farina
2013-12-09 15:28 ` Rich Freeman
2013-12-09 18:47 ` Steev Klimaszewski
2013-12-09 19:56 ` Rick "Zero_Chaos" Farina
2013-12-10 1:33 ` Rich Freeman
2013-12-10 10:31 ` Steev Klimaszewski
2013-12-10 11:23 ` Rich Freeman
2013-12-10 18:46 ` Steev Klimaszewski
2013-12-11 17:51 ` [gentoo-dev] " Steven J. Long
2013-12-16 22:33 ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-12-11 2:57 ` William Hubbs
2013-12-14 5:56 ` Jorge Manuel B. S. Vicetto
2013-12-14 20:13 ` William Hubbs
2013-12-14 20:47 ` Jorge Manuel B. S. Vicetto
2013-12-14 21:57 ` William Hubbs
2013-12-14 22:22 ` Luis Ressel
2013-12-16 22:38 ` Rick "Zero_Chaos" Farina
2013-12-14 17:24 ` mingdao
2013-12-15 0:59 ` William Hubbs
2013-12-15 1:37 ` mingdao
2013-12-16 22:41 ` Rick "Zero_Chaos" Farina
2013-12-09 23:30 ` Patrick Lauer
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=20131201102015.GA1219@egeo \
--to=just22.adl@gmail.com \
--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