1 |
On 04/24/2013 06:39 PM, Ian Stakenvicius wrote: |
2 |
> On 24/04/13 09:10 PM, William Hubbs wrote: |
3 |
>> On Wed, Apr 24, 2013 at 07:32:44PM -0400, Rick "Zero_Chaos" Farina |
4 |
>> wrote: |
5 |
>>> On 04/24/2013 07:17 PM, William Hubbs wrote: |
6 |
>>>> |
7 |
>>>> This would actually be cleaner than a bogus dependency in |
8 |
>>>> OpenRC. I would probably call it virtual/network-manager |
9 |
>>>> though. |
10 |
>>>> |
11 |
>>> You can't call it virtual/network-manager, that calls to mind, |
12 |
>>> you know, net-misc/networkmanager. That's just too confusing |
13 |
>>> imho. I wouldn't object to virtual/net, or pretty much anything |
14 |
>>> else that isn't confusing. The net scripts are not a network |
15 |
>>> manager, networkmanager, wicd, even wpa_supplicant would be |
16 |
>>> things I would consider to be network managers. |
17 |
> |
18 |
>> But the oldnet scripts do run wpa_supplicant, dhcp clients, etc, |
19 |
>> for each interface they manage. |
20 |
> |
21 |
>> Newnet doesn't even try that, it just manages static interfaces |
22 |
>> and assumes that you will use a dhcp client or something like |
23 |
>> wpa_supplicant in standalone mode to control your interfaces. |
24 |
> |
25 |
> |
26 |
> virtual/network-init ? |
27 |
|
28 |
Sounds about right. Also, rather than "gentoo-oldnet", maybe a name like |
29 |
"gentoo-network-init" makes sense, since I suspect that the vast |
30 |
majority of users are still using it. If newnet is split out, maybe call |
31 |
it "openrc-newnet-init" or something. |
32 |
-- |
33 |
Thanks, |
34 |
Zac |