On Wed, Apr 24, 2013 at 07:32:44PM -0400, Rick "Zero_Chaos" Farina wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/24/2013 07:17 PM, William Hubbs wrote: > > On Wed, Apr 24, 2013 at 06:34:46PM -0400, Walter Dnes wrote: > >> On Wed, Apr 24, 2013 at 02:16:51PM -0400, Rich Freeman wrote > >> > >>> Considering our default configuration ships sshd (an argument we don't > >>> need to rehash here), it seems a bit silly to not ship networking > >>> support by default. I'd rather not do it as part of the system set, > >>> though that would be consistent with what we're doing with ssh, and it > >>> is still override-able. > >> To handle the various possible cases, maybe we need a "virtual/net" as > >> part of the system set, which can be satisfied by either oldnet or > >> newnet or whatever. The install ISO will have a basic working network > >> stack (IPV4+IPV6). After the initial install, the admin can do > >> whatever. Maybe even invoke package.provided. > > > > 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. William
signature.asc
Description: Digital signature
