From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: only the loopback interface should provide net
Date: Mon, 06 Feb 2012 21:33:39 -0500 [thread overview]
Message-ID: <1328582019.8348.58.camel@rook> (raw)
In-Reply-To: <20120207014115.GA2683@linux1>
On Mon, 2012-02-06 at 19:41 -0600, William Hubbs wrote:
> > My counterproposal is to
> > (a) fix init scripts for Category 2 so that instead of "use net" or
> > "need net", they only "use net.lo" or "need net.lo"; and
>
> I think it would be better if I provided another service these scripts
> could use|need, because the loopback goes by at least one name other than
> "lo" that I know of, and that is "lo0", so if I don't provide a service,
> all of these scripts would have to conditionally use or need at least lo
> or lo0 depending on which platform they are running on.
Maybe a virtual service called "lo", provided by net.lo and net.lo0?
> For the normal use case, I submit that category one should not care
> about the loopback interface, since we don't make remote connections
> that way. That would mean that loopback would not provide net by
> default.
Yes, that certainly seems reasonable.
-Alexandre
next prev parent reply other threads:[~2012-02-07 2: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 [this message]
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
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=1328582019.8348.58.camel@rook \
--to=tetromino@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