| PLEX86 | ||
|
How to write udev rules for ttyUSBn devicesDisk Drive LED via Software linnix An ide-mib (Management Information Base) patch for disk read-write counters and some useful-useless information is available here: We use them for...
This bit of misinformation is what seems to have caused all of my problems. Accordign to the page mentioned: change hard drive to IDE 3 using Promise 20276 controller On Thursday 27 April 2006 23:24, Kooner stood up and spoke the following words to the mbuttes inalt.os.linux.mandrake...: More precisely, if every IDE channel has... Using multiple SYMLINK style rules Another recent feature is the ability to write rules that do not specify a NAME, but instead they simply specify SYMLINK keys. This allows you to avoid the issue where your own rules effectively mask the udev defaults. Take the rule: KERNEL=="hdc", SYMLINK="dvd" When udev finds this rule, it will take a mental note of it. Upon finding another rule matching the same device which also includes a NAME parameter, udev will create the node as specified by the NAME parameter, plus symbolic links as specified by the SYMLINK parameters of both rules. To put it into practical terms, when udev is naming nodes for my hdc device, it will use the default rules for block devices as usual, with the addition of my personal symlink "dvd". Similarly to normal rules, rules of this type will only take effect if udev is able to find them before it finds a rule specifying a NAME parameter. At least under Gentoo, the exact opposite is the case: when udev finds the rule with a NAME=, it resets the symlink list (discarding the symlinks that have already been set). So, when I put rules like that before the defaults rules (e.g. in 10-local.rules), they have no effect. If I place them after the default rules which contain the NAME= buttignments (e.g. in 99-local.rules), then they work fine. -- Grant Edwards grante Yow! .. I'll make you at an ASHTRAY!! visi.com
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||