From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Date: Tue, 13 Oct 2009 18:06:22 +0000 Subject: Re: PATCH: Network Device Naming mechanism and policy Message-Id: <1255457182.2196.21.camel@localhost.localdomain> List-Id: References: <20091009140000.GA18765@mock.linuxdev.us.dell.com> <20091009145137.GD19218@mock.linuxdev.us.dell.com> <1255344075.2143.1.camel@warcraft> <20091012173705.GA22736@nostromo.devel.redhat.com> In-Reply-To: <20091012173705.GA22736@nostromo.devel.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Bill Nottingham Cc: Scott James Remnant , Matt Domsch , Narendra K , netdev@vger.kernel.org, linux-hotplug@vger.kernel.org, jordan_hargrave@dell.com On Mon, 2009-10-12 at 13:37 -0400, Bill Nottingham wrote: > Scott James Remnant (scott@ubuntu.com) said: > > On the other hand, they *tend* to be unique for a wide range of systems. > > This makes them pretty comparable to LABELs on disks, and we have > > a /dev/disk/by-label > > > > Remember that udev already supports symlink stacking, and priorities and > > such. > > > > I don't think there's any danger of supporting a /dev/netdev/by-mac by > > default, it'll be a benefit to most and those who don't have unique MACs > > will just ignore it. > > At the moment, we do not appear to get the proper change uevents from things > like 'ip link set dev address ', so we can't currently maintain > these symlinks. And if we really want seamless support for MAC spoofing, we want ETHTOOL_GPERMADDR for all drivers too, so that if your configuration says "rename device XX:XX:XX:XX:XX:XX to YY:YY:YY:YY:YY:YY" we can actually figure stuff out after the spoof. Dan