SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Later would probably be better than sooner in this case. Sooner would run the risk of tangling with an update actually setting a rule for your device that doesn't match what you've been using and possibly breaking something.
...when dealing with overlapping rules in general, you want them to be defined in order of broadest scope to narrowest scope (everywhere/everything, ix86 or ppc machines, stuff that's here, this particular machine).
Last edited by evilDagmar; 11-19-2007 at 09:54 AM.
I have created a file to create symbolic links for my modem and dvd drives as /etc/udev/rules.d/10-udev.rules and seems to work fine for my purposes. I imagine that is would all depend on the types of rules that you are trying to create, or if they would conflict with and default udev rules.
In the first versions of udev, it read the list of rules and applied the first one that matched. This is a similar behaviour to iptables rules and other situations. In these first versions, the best strategy to create, for example, a symbolic link to a device was to find out the rule matching the device, copying it adding the symbolic links, and finally putting the rule in a file which was read before the rest of files.
However, udev later changed for practical reasons to a model in which every matching rule is applied in order, and some attributes admit the += operator to add more content. Some others only admit the = operator, and some of them may be assigned a fixed value that can't be modified later, with the := operator (see man udev). With this new model the order doesn't matter as much as before, and it can be right or wrong to put your rule before or after the system rules, depending on what you want to do. In general, I'd say it's safer to put your rules after the system rules, and add symbolic links with the += operator.