Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
08-09-2006, 07:34 AM
|
#1
|
Member
Registered: Mar 2003
Location: USA
Distribution: Slackware-current
Posts: 155
Rep:
|
slackware-current, udev 0.96, and custom udev rules not working
I just updated to the most recent -current. I have everything working fine except for one thing, my custom udev rules don't seem to be working. I have a file called 10-local.rules in my /etc/udev/rules.d directory with the contents of:
BUS="usb", SYSFS{manufacturer}="Cypress Semiconductor", SYSFS{product}="USB2.0 Storage Device", KERNEL="sd*", NAME="%k", SYMLINK="backup%n"
BUS="scsi", SYSFS{model}="USB Flash Memory", KERNEL="sd*", NAME="%k", SYMLINK="pendrive"
BUS="usb", SYSFS{product}="iAUDIO M5", KERNEL="sd*", NAME="%k", SYMLINK="iaudio"
Which has been working correctly. According to the udev man page all files in ruldes.d with the extention of .rules will be read in lexical order. My devices work fine, it's just that udev doesn't create the symlinks that I expect them to according to the above rules.
Has anyone else run into this?
Thanks,
Brian
|
|
|
08-09-2006, 08:00 AM
|
#2
|
Member
Registered: Oct 2004
Location: Norway
Distribution: Slackware, CentOS
Posts: 641
Rep:
|
Have you tried dropping the KERNEL and NAME parameters (if all you want to do is symlink, you shouldn't override the NAME parameter, as I believe that can cause trouble with the native udev rules.
A good practice seems to be to only use the SYSFS{} variables and then symlink/alias only, as this doesn't interfere with the base udev settings.
Thus the following might be worth a shot:
Code:
BUS="usb", SYSFS{manufacturer}="Cypress Semiconductor", SYSFS{product}="USB2.0 Storage Device", SYMLINK="backup%n"
-Y1
|
|
|
08-09-2006, 08:05 AM
|
#3
|
Senior Member
Registered: Sep 2004
Distribution: slackware
Posts: 4,734
|
Which kernel version are you running?
Note that udev-096 requires at least a 2.6.15 kernel to work properly.
Pat has noted this in today's Changelog, which, coincidentally, contains the 3rd update to udev in as many days!
Last edited by rkelsen; 08-09-2006 at 08:07 AM.
|
|
|
08-09-2006, 09:00 AM
|
#4
|
Member
Registered: Dec 2005
Location: Madrid
Distribution: Solaris 10, Solaris Express Community Edition
Posts: 547
Rep:
|
Syntax of rule files has changed!
Filters must have == instead of =, assignements has the = and SYMLINK now wants +=.
Your file should look like:
BUS=="usb", SYSFS{manufacturer}=="Cypress Semiconductor", SYSFS{product}=="USB2.0 Storage Device", KERNEL=="sd*", NAME="%k", SYMLINK+="backup%n"
Bye
Last edited by crisostomo_enrico; 08-09-2006 at 09:02 AM.
|
|
|
08-09-2006, 09:54 AM
|
#5
|
Member
Registered: Mar 2003
Location: USA
Distribution: Slackware-current
Posts: 155
Original Poster
Rep:
|
Quote:
Originally Posted by rkelsen
Which kernel version are you running?
Note that udev-096 requires at least a 2.6.15 kernel to work properly.
Pat has noted this in today's Changelog, which, coincidentally, contains the 3rd update to udev in as many days!
|
Yeah, I saw that this morning after my post! Interesting. I am running 2.6.16.18 so I should be good.
crisostomo_enrico:
That's interesting to know! I didn't even consider a syntax change as a possability. I'll try it out when I get home from work.
Thanks.
|
|
|
08-09-2006, 04:25 PM
|
#6
|
Member
Registered: Mar 2003
Location: USA
Distribution: Slackware-current
Posts: 155
Original Poster
Rep:
|
So, I gave it a shot and I ultimately had to edit the rules file as crisostomo_enrico. But I also had to reduce each rule to include just SYSFS and SYMLINK directives before my rules finally took effect.
Thanks for all the input guys. I seem to be good for now. Until the next big udev update comes along.
Regards,
Brian
|
|
|
08-10-2006, 04:43 AM
|
#7
|
Member
Registered: Dec 2005
Location: Madrid
Distribution: Solaris 10, Solaris Express Community Edition
Posts: 547
Rep:
|
So didn't I.  And when my custom udev rules stopped working, I had to dig it out!
|
|
|
All times are GMT -5. The time now is 12:14 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|