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