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] rfc: *_iface variables in openrc network scripts
Date: Thu, 12 May 2011 21:18:57 -0500	[thread overview]
Message-ID: <20110513021857.GA1992@linux1> (raw)
In-Reply-To: <4DCC7202.5040201@gentoo.org>

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

Hi Jorge,

On Thu, May 12, 2011 at 11:49:22PM +0000, Jorge Manuel B. S. Vicetto wrote:
> On 12-05-2011 14:34, William Hubbs wrote:
> > I'm not sure I follow. would you rather keep the config_* variable?
> 
> I think we should try to keep them.
> 
> > If so, how do you feel about requiring the syntax of the variable to
> > match the tool you are using?
> 
> That's exactly what I meant.
> By choosing the module one would get tied to its syntax. That should
> make it simpler to parse the data.

Ok, cool, this was actually my first choice, but I wasn't sure how it
would go over.

> I would also suggest making the
> declaration of modules mandatory or for you to pick a default tool to be
> used when someone doesn't declare modules.

We already do this. iproute2 is preferred if you have it installed;
otherwise ifconfig is used.

I believe the order of preference is discussed in the net.example file.

The only time you really need the modules= or modules_iface= lines is if
you want to force a specific module to be preferred for an interface.

William


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

      reply	other threads:[~2011-05-13  2:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  1:45 [gentoo-dev] rfc: *_iface variables in openrc network scripts William Hubbs
2011-05-12  1:55 ` William Hubbs
2011-05-12  9:35   ` Petteri Räty
2011-05-12  2:01 ` Jorge Manuel B. S. Vicetto
2011-05-12 14:34   ` William Hubbs
2011-05-12 23:49     ` Jorge Manuel B. S. Vicetto
2011-05-13  2:18       ` William Hubbs [this message]

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=20110513021857.GA1992@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