1 |
On Tue, Feb 07, 2012 at 04:46:58PM +0000, Duncan wrote: |
2 |
> 1) Separate net.lo service for stuff that doesn't have to have an |
3 |
> external connection at all. |
4 |
|
5 |
This can be easily done. I'll just make net.lo* not provide net. |
6 |
|
7 |
> 2) A default net (or net*) service that is is composed of all non-net.lo |
8 |
> services, with a default any-one-of-them policy. |
9 |
> Two reasons for this: |
10 |
> |
11 |
> 2a) It'll "just work" in the simple case. |
12 |
> |
13 |
> 2b) It's the easiest to automatically preconfigure without getting into |
14 |
> lots of "detect all the networks and magically figure out whether they're |
15 |
> lan-only or inet" hairballs. |
16 |
|
17 |
As soon as you add a second interface, this default "net" service |
18 |
breaks. That is why I think we should add an "internet" service that |
19 |
consists of interfaces the user says provide a connection to the |
20 |
internet. Then we could make our services that need real |
21 |
internet connections need that service instead of net. |
22 |
|
23 |
> 3) Allow the user/admin to configure net1, net2... just like the default |
24 |
> net/net*, specifying individual interfaces for each as well as whether |
25 |
> one or all of the configured interfaces must be up for the service to be |
26 |
> provided. |
27 |
|
28 |
This one or all functionality you are talking about is already available |
29 |
through rc_depend_strict. |
30 |
|
31 |
Also, you can set up virtual services already (see the rc.conf section |
32 |
on dependencies). |
33 |
|
34 |
William |