| 1 |
On 2013-12-03, at 6:00 PM, William Hubbs <williamh@g.o> wrote: |
| 2 |
|
| 3 |
> On Tue, Dec 03, 2013 at 04:43:28PM -0500, Ian Stakenvicius wrote: |
| 4 |
>> On 2013-12-03, at 4:11 PM, William Hubbs <williamh@g.o> wrote: |
| 5 |
>>> I would like to add a virtual/network-manager package to @system which |
| 6 |
>>> has the following rdepend settings: |
| 7 |
>>> |
| 8 |
>>> RDEPEND=" || ( |
| 9 |
>>> net-misc/netifrc |
| 10 |
>>>> =sys-apps/openrc-0.12[newnet] |
| 11 |
>>> net-misc/badvpn |
| 12 |
>>> net-misc/dhcpcd |
| 13 |
>>> net-misc/netctl |
| 14 |
>>> net-misc/NetworkManager |
| 15 |
>>> net-misc/wicd )" |
| 16 |
>>> |
| 17 |
>>> Does anyone see an issue with setting it up this way? |
| 18 |
>>> |
| 19 |
>>> William |
| 20 |
>> |
| 21 |
>> well, there is the issue where dhcpcd being installed (which is common |
| 22 |
>> for netifrc support) is going to allow netifrc to be cleaned... |
| 23 |
>> similar for NM and Wicd I expect, if those aren't in @world .... |
| 24 |
> |
| 25 |
> Please correct me if I am wrong. You can install NM or wicd and |
| 26 |
> remove netifrc and have a working system, correct? |
| 27 |
> |
| 28 |
> Dhcpcd can be run as a standalone service or per interface. In |
| 29 |
> standalone mode, the default is to automatically configure any unconfigured |
| 30 |
> interfaces it finds on your system, but this can be configured (see |
| 31 |
> dhcpcd.conf (5)). So, I'm wondering what the advantage of running dhcpcd |
| 32 |
> per interface is? |
| 33 |
> |
| 34 |
> William |
| 35 |
> |
| 36 |
|
| 37 |
I'm just referring to issues with selecting the networking stack via a virtual, is all. it'a nice that netifrc is the default due to being on top, but I expect many ppl that run netifrc use dhcp to config at least one iface, and emerging dhcpcd will then bump it out due to it now satisfying the virtual. Maybe a use flag "dhcp-only" that excludes dhcpcd from the virtual list unless set?? |
Archives