All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <dmlb2000@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-067 and 2.6.12?
Date: Tue, 16 Aug 2005 23:00:16 +0000	[thread overview]
Message-ID: <9c21eeae050816160020f3fbc1@mail.gmail.com> (raw)
In-Reply-To: <200508162349.01610.s0348365@sms.ed.ac.uk>

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 <s0348365@sms.ed.ac.uk> 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
> > <snip>
> > RUN+="/sbin/udev_run_devd"
> > </snip>
> >
> > 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

  reply	other threads:[~2005-08-16 23:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 22:49 udev-067 and 2.6.12? Alistair John Strachan
2005-08-16 23:00 ` David Brown [this message]
2005-08-16 23:26 ` Alistair John Strachan
2005-08-16 23:31 ` David Brown
2005-08-16 23:55 ` Kay Sievers
2005-08-17  8:09 ` Arioch
2005-08-17  8:26 ` Alistair John Strachan
2005-08-17 12:35 ` Kay Sievers
2005-08-17 14:52 ` Alistair John Strachan
2005-08-17 15:10 ` Kay Sievers
2005-08-17 23:48 ` Greg KH
2005-08-18 15:27 ` David Brown
2005-08-18 15:38 ` Greg KH
2005-08-18 15:53 ` David Brown
2005-08-18 16:32 ` Alistair John Strachan
2005-08-18 16:56 ` Greg KH
2005-08-18 17:19 ` Alistair John Strachan
  -- strict thread matches above, loose matches on Subject: below --
2005-08-16 22:02 Alistair John Strachan
2005-08-16 22:05 ` Greg KH
2005-08-16 22:12   ` Alistair John Strachan
2005-08-16 22:14     ` Greg KH
2005-08-16 23:09       ` Kay Sievers
2005-08-16 23:33         ` Alistair John Strachan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9c21eeae050816160020f3fbc1@mail.gmail.com \
    --to=dmlb2000@gmail.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.