From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brown Date: Tue, 16 Aug 2005 23:00:16 +0000 Subject: Re: udev-067 and 2.6.12? Message-Id: <9c21eeae050816160020f3fbc1@mail.gmail.com> List-Id: References: <200508162349.01610.s0348365@sms.ed.ac.uk> In-Reply-To: <200508162349.01610.s0348365@sms.ed.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Hmmmm, never tried renaming my ethernet or wireless devices with udev rules. Always just kept what they gave me... but you might try KERNEL="eth[0-9]*", SYSFS{address}="00:11:09:65:78:c7", NAME="wlan%n" Maybe... not to sure about that though... %n should be the number match so it will make eth0 become wlan0 etc. might not quite be what you are looking for :-\ - David Brown On 8/16/05, Alistair John Strachan wrote: > On Tuesday 16 August 2005 23:33, David Brown wrote: > > Check out the release notes for udev 059 > > I think your problem may be caused by the changes in that release > > and you should probably add the code below to your udev rules file > > > > RUN+="/sbin/udev_run_devd" > > > > > > I've noticed this problem as well loading firmware but everything was > > fixed when I made the two extra binaries in extras/run_directory and > > added the code above to my rules file > > > > - David Brown > > > > (Sorry linux-hotplug-devel, I thought I'd add to CC after Greg's suggestion > elsewhere in this thread). > > Obviously, this fixed it. Thanks a lot for the hint. > > I wouldn't mind knowing how to (from the README) "convert all the calls from > the directories to explicit udev rules and get completely rid of the > multiplexing". I'd like to not have to use backward compatibility stuff. > > The problem was caused by me renaming the network device on my system from > "eth1" to "wlan", and the lack of this legacy RUN meant hotplug wasn't doing > the right thing wrt loading the driver/firmware. > > What sort of udev rule am I looking at for both renaming AND fixing up the bad > hotplug stuff? I've currently got: > > KERNEL="eth?", SYSFS{address}="00:11:09:65:78:c7", NAME="lan" > KERNEL="eth?", SYSFS{address}="00:30:b4:00:00:00", NAME="wlan" > > Which looks sensible. I think. > > -- > Cheers, > Alistair. > > 'No sense being pessimistic, it probably wouldn't work anyway.' > Third year Computer Science undergraduate. > 1F2 55 South Clerk Street, Edinburgh, UK. > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel