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