1 |
On Wed, Apr 24, 2013 at 07:32:44PM -0400, Rick "Zero_Chaos" Farina wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> On 04/24/2013 07:17 PM, William Hubbs wrote: |
6 |
> > On Wed, Apr 24, 2013 at 06:34:46PM -0400, Walter Dnes wrote: |
7 |
> >> On Wed, Apr 24, 2013 at 02:16:51PM -0400, Rich Freeman wrote |
8 |
> >> |
9 |
> >>> Considering our default configuration ships sshd (an argument we don't |
10 |
> >>> need to rehash here), it seems a bit silly to not ship networking |
11 |
> >>> support by default. I'd rather not do it as part of the system set, |
12 |
> >>> though that would be consistent with what we're doing with ssh, and it |
13 |
> >>> is still override-able. |
14 |
> >> To handle the various possible cases, maybe we need a "virtual/net" as |
15 |
> >> part of the system set, which can be satisfied by either oldnet or |
16 |
> >> newnet or whatever. The install ISO will have a basic working network |
17 |
> >> stack (IPV4+IPV6). After the initial install, the admin can do |
18 |
> >> whatever. Maybe even invoke package.provided. |
19 |
> > |
20 |
> > This would actually be cleaner than a bogus dependency in OpenRC. |
21 |
> > I would probably call it virtual/network-manager though. |
22 |
> > |
23 |
> You can't call it virtual/network-manager, that calls to mind, you know, |
24 |
> net-misc/networkmanager. That's just too confusing imho. I wouldn't |
25 |
> object to virtual/net, or pretty much anything else that isn't |
26 |
> confusing. The net scripts are not a network manager, networkmanager, |
27 |
> wicd, even wpa_supplicant would be things I would consider to be network |
28 |
> managers. |
29 |
|
30 |
But the oldnet scripts do run wpa_supplicant, dhcp clients, etc, for |
31 |
each interface they manage. |
32 |
|
33 |
Newnet doesn't even try that, it just manages static interfaces and |
34 |
assumes that you will use a dhcp client or something like wpa_supplicant |
35 |
in standalone mode to control your interfaces. |
36 |
|
37 |
William |