conf/104884: Add support EtherChannel configuration to rc.conf

Florent Thoumie flz at FreeBSD.org
Fri Feb 9 00:00:36 UTC 2007


The following reply was made to PR conf/104884; it has been noted by GNATS.

From: Florent Thoumie <flz at FreeBSD.org>
To: Brooks Davis <brooks at FreeBSD.org>
Cc: Doug Barton <dougb at FreeBSD.org>, 
 Norikatsu Shigemura <nork at FreeBSD.org>,
  freebsd-bugs at FreeBSD.org,  FreeBSD-gnats-submit at FreeBSD.org, 
 freebsd-rc at FreeBSD.org
Subject: Re: conf/104884: Add support EtherChannel configuration to rc.conf
Date: Thu, 08 Feb 2007 23:48:04 +0000

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enig44FBBDEA77F2D581571B4587
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 Brooks Davis wrote:
 > On Thu, Feb 08, 2007 at 11:30:41PM +0000, Florent Thoumie wrote:
 >> Brooks Davis wrote:
 >>> On Thu, Feb 08, 2007 at 01:55:16PM -0800, Doug Barton wrote:
 >>>> Brooks Davis wrote:
 >>>>
 >>>>> The default should be an empty list which results in nothing happen=
 ing.
 >>>>> I'd suggest making empty list the value for the default gif_interfa=
 ces
 >>>>> in /etc/defaults/rc.conf in both branches, removing support for NO =
 in
 >>>>> CURRENT and emitting a warning in stable.
 >>>> How about issuing a warning for NO in both branches? Whether I agree=
 
 >>>> with you or not on the importance of keeping things clean and
 >>>> consistent, I definitely do not want to err on the side of pedantry
 >>>> over usability.
 >>> That would be fine.  I don't really care as long as it's deprecated.
 >>>
 >>> FWIW, only users who don't update /etc/defaults/rc.conf or who manual=
 ly
 >>> set gif_interfaces=3D"NO" would be effected so the size of the set of=
 
 >>> effected users is probalby close to epilon and even all that will hap=
 pen
 >>> is cloning an extra interface and then not configuring it so it shoul=
 d
 >>> be basicly harmless to just remove direct support for it.
 >> Fine with me as well. Should we make it a warning on RELENG_6 and an
 >> error on HEAD, or a warning on both. The former being be what I was
 >> planning to do, ie. remove support for "NO" in HEAD but issue a messag=
 e
 >> saying semantics have changed. The latter would mean identical code in=
 
 >> both HEAD and RELENG_6 (so "NO"-compatibility in both branches), but
 >> we'd need a reminder to remove this "NO"-support in HEAD once RELENG_7=
 
 >> is branched.
 >=20
 > I'd say a warning in both.
 
 Re-reading Doug's message, he's probably thinking the same thing, but
 this is for gif_interfaces only, right?
 
 --=20
 Florent Thoumie
 flz at FreeBSD.org
 FreeBSD Committer
 
 
 --------------enig44FBBDEA77F2D581571B4587
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.5 (FreeBSD)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iD8DBQFFy7a0MxEkbVFH3PQRCrFIAJ9oelmuwW66WzTncTrqPQspTLfpjQCeOq42
 FihB34D9SR37ISDNpVn2aeU=
 =PAkV
 -----END PGP SIGNATURE-----
 
 --------------enig44FBBDEA77F2D581571B4587--


More information about the freebsd-rc mailing list