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
Cc: heroxbd@gentoo.org
Subject: Re: [gentoo-dev] rfc: OpenRC network provides revisited
Date: Fri, 24 Aug 2012 18:48:20 -0500	[thread overview]
Message-ID: <20120824234820.GA1944@linux1> (raw)
In-Reply-To: <86y5l3vrpw.fsf@gentoo.org>

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

On Sat, Aug 25, 2012 at 07:40:43AM +0900, heroxbd@gentoo.org wrote:
> Besides, IMHO, we should avoid changing OpenRC's default dependency too
> often. The solution for one user can be received as a regression to
> others.
> 
> People file bugs saying "it worked for OpenRC-0.9 but not 0.10". For
> devs, we know we just changed default value of something perfectly
> configurable. But for that user, it is quite discouraging to feel
> "something in OpenRC is still unstable".

Another thing to consider is, do the services we say "need net" really
_NEED_ net?

If a service is a listener like sshd that isn't bound to a specific
address by default and can deal with interfaces going up and down, I
would guess that it doesn't. I am thinking that we can set up the
depends for sshd as follows:

use net
after net

That would make sure a net provider runs before sshd if one is
in the runlevel, but allow sshd to start if one is not as well.

This would have to be tested on a case-by-case basis.

About changing default values, I think that if we have a good reason to
change them, we should inform users and change them.

I think the advantage here is that it makes openrc run out of the box in
more situations.

William


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

  reply	other threads:[~2012-08-24 23:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 17:10 [gentoo-dev] rfc: OpenRC network provides revisited William Hubbs
2012-08-24 17:50 ` Alexandre Rostovtsev
2012-08-24 19:58   ` William Hubbs
2012-08-24 21:01     ` Diego Elio Pettenò
2012-08-24 22:19     ` heroxbd
2012-08-25  1:17     ` Ian Stakenvicius
2012-08-25  5:14       ` [gentoo-dev] " Duncan
2012-08-24 22:40 ` [gentoo-dev] " heroxbd
2012-08-24 23:48   ` William Hubbs [this message]
2012-08-25  1:22     ` Ian Stakenvicius
2012-08-25  3:57       ` William Hubbs
2012-08-25  4:14         ` Diego Elio Pettenò
2012-08-25  6:19         ` heroxbd
2012-08-25 15:53           ` William Hubbs
2012-08-25 18:49             ` Ian Stakenvicius
2012-08-25 20:16               ` William Hubbs
2012-08-27 12:42                 ` Ian Stakenvicius

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=20120824234820.GA1944@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=heroxbd@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