public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: rfc: only the loopback interface should provide net
Date: Tue, 7 Feb 2012 11:33:42 -0600	[thread overview]
Message-ID: <20120207173342.GB4579@linux1> (raw)
In-Reply-To: <pan.2012.02.07.16.46.58@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]

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


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-02-07 17:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 21:04 [gentoo-dev] rfc: only the loopback interface should provide net William Hubbs
2012-02-06 21:36 ` Zac Medico
2012-02-06 23:15 ` Alexandre Rostovtsev
2012-02-07  1:41   ` William Hubbs
2012-02-07  2:33     ` Alexandre Rostovtsev
2012-02-07  3:21       ` [gentoo-dev] " Duncan
2012-02-07  6:43   ` [gentoo-dev] " William Hubbs
2012-02-07  8:28     ` Alexandre Rostovtsev
2012-02-07 14:39       ` Ian Stakenvicius
2012-02-07 16:44         ` William Hubbs
2012-02-07 16:58           ` Alec Warner
2012-02-07 16:46         ` [gentoo-dev] " Duncan
2012-02-07 17:12           ` Ian Stakenvicius
2012-02-07 17:33           ` William Hubbs [this message]
2012-02-07 18:31             ` Alexandre Rostovtsev
2012-02-22 21:19   ` [gentoo-dev] " William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120207173342.GB4579@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox