Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Feb 2007 23:40:31 GMT
From:      Florent Thoumie <flz@FreeBSD.org>
To:        freebsd-rc@FreeBSD.org
Subject:   Re: conf/104884: Add support EtherChannel configuration to rc.conf
Message-ID:  <200702082340.l18NeVbN022723@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/104884; it has been noted by GNATS.

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

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enig5E80D3757FBED01672C33A4F
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 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 happenin=
 g.
 >>> I'd suggest making empty list the value for the default gif_interface=
 s
 >>> 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.
 >=20
 > That would be fine.  I don't really care as long as it's deprecated.
 >=20
 > FWIW, only users who don't update /etc/defaults/rc.conf or who manually=
 
 > 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 happe=
 n
 > is cloning an extra interface and then not configuring it so it should
 > 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 message
 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
 Florent Thoumie
 flz@FreeBSD.org
 FreeBSD Committer
 
 
 --------------enig5E80D3757FBED01672C33A4F
 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
 
 iD8DBQFFy7KmMxEkbVFH3PQRCmK4AJ9Kll/nStdtq4bJj7/DOWXrPERuVwCePPRv
 995tN2tSqMK/JfKTcq+27W8=
 =tBI1
 -----END PGP SIGNATURE-----
 
 --------------enig5E80D3757FBED01672C33A4F--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702082340.l18NeVbN022723>