Date: Mon, 7 Apr 2008 15:25:27 -0500 From: Brooks Davis <brooks@freebsd.org> To: Ermal Lu?i <ermal.luci@gmail.com> Cc: freebsd-arch@freebsd.org Subject: Re: Question about network interface naming and devfs(5)! Message-ID: <20080407202527.GG28511@lor.one-eyed-alien.net> In-Reply-To: <9a542da30804071201o520812f8w4fc413131c4140b0@mail.gmail.com> References: <9a542da30804071201o520812f8w4fc413131c4140b0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Apr 07, 2008 at 09:01:18PM +0200, Ermal Lu?i wrote: > Hello, > > it seems that devfs(5) is not consistent with network interface naming feature. > > Network interface naming is offered by ifconfig $interface name $name. > This feature is really helpful to distinguish interfaces properly in a > machine and helps in scripting things. > The problem is that the ioctl that renames the device advertises it as > an interface arrival event which devfs does not handle and such you > have inconsistence between ifconfig output and the information in > devfs. > > Are there any plans to fix this or is there any issue for not making > devfs(5) aware of network interfaces events?! I haven't dealt with it because a) there's no way to rename entries which currently means you've have to destroy the current entry and add a completely new one which would break applications using the devfs entries across renames and b) I think the devfs entries are a mistake and should die. -- Brooks [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFH+oM3XY6L6fI4GtQRApIRAKDLVECgTdMb6Ba/331rYq3lhtBl3wCgyFHV XwHgDF/q3lOwPFuMcr5imcI= =EwHx -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080407202527.GG28511>