Date: Thu, 21 Feb 2008 09:24:08 -0600 From: Brooks Davis <brooks@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Cc: Dag-Erling Sm??rgrav <des@des.no>, John-Mark Gurney <jmg@funkthat.com>, arch@freebsd.org Subject: Re: dev.* analogue for interfaces Message-ID: <20080221152408.GA12023@lor.one-eyed-alien.net> In-Reply-To: <20080221100156.V52922@fledge.watson.org> References: <86odacc04t.fsf@ds4.des.no> <20080219233217.GS27248@funkthat.com> <20080220111157.H44565@fledge.watson.org> <86ablvuzgx.fsf@ds4.des.no> <20080221100156.V52922@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 21, 2008 at 10:07:08AM +0000, Robert Watson wrote: > On Wed, 20 Feb 2008, Dag-Erling Sm?rgrav wrote: >=20 >> Robert Watson <rwatson@FreeBSD.org> writes: >>=20 >>> We also support interface renaming... Does newbus mind if you rename t= he=20 >>> devices in its tree? >>=20 >> I'm not sure whether you're replying to my proposal or to Julian's=20 >> interpretation / extrapolation of it... but I have no intention of=20 >> hooking interfaces into newbus. I just want a sysctl tree for struct=20 >> ifnet like we have a sysctl tree for device_t, to access interface=20 >> parameters which are not easily accessible through ifconfig. >=20 > Hmm. When I look at net/if.c, I don't see renaming support, so perhaps= =20 > this was just a proposal I was thinking of and not actual code. In eithe= r=20 > case, I think the question stands: in a world where interface renaming is= =20 > supported, is your plan to also rename the if.X sysctl tree created for t= he=20 > interface? Does sysctl have a facility to do this? I think that one way or another it should be possible to reach the sysctl by if_index since that is the only stable way to access an interface though out its life. I might actually suggest making that the only way and have if.1.name be available. -- Brooks --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHvZeYXY6L6fI4GtQRAq+SAKDWoU2VUwWkotuw0L46r8MGqzarVQCeJb+6 eOUZsjvip/UzKDo0m+7EEQI= =T+v0 -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080221152408.GA12023>