From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] rfc: *_iface variables in openrc network scripts
Date: Wed, 11 May 2011 20:45:40 -0500 [thread overview]
Message-ID: <20110512014540.GA28033@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
All,
we received a regression for openrc which prompted me to post this to
the list to see what everyone thinks. The bug is
http://bugs.gentoo.org/366905.
Currently, we use one variable, config_$(INTERFACE), to configure
the interfaces,.
In the bsd world there are no issues, because there is only one configuration
tool, ifconfig.
However, in the linux world, there are two, ifconfig
and iproute2, which have completely different command line syntax.
Currently, we try to keep the syntax of config_* constant, which means
that the scripts attempt to convert ifconfig syntax to iproute2, and
the other way around.
In my opinion, the best way to fix this, and the best way forward, would
be to stop doing this. My plan is something like this:
For the next openrc release, put in a warning that config_* is
deprecated and advise the use of ifconfig_* or ipconfig_* depending on
which interface handler is being used. Then, at some point in the
future, remove support for config_*.
Does anyone have any thoughts?
Thanks,
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-05-12 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 1:45 William Hubbs [this message]
2011-05-12 1:55 ` [gentoo-dev] rfc: *_iface variables in openrc network scripts 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
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=20110512014540.GA28033@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