| 1 |
Hi, thanks a lot for the answers. The name of the rules file is |
| 2 |
00_whatever.rules, as far as i know there's also an option which |
| 3 |
prevents to modifye the setted rules. Well, if no one knows how to do |
| 4 |
i will try to find a different solution. |
| 5 |
|
| 6 |
2010/8/31 Dale <rdalek1967@×××××.com>: |
| 7 |
> Alex Schuster wrote: |
| 8 |
>> |
| 9 |
>> Pau Peris writes: |
| 10 |
>> |
| 11 |
>> |
| 12 |
>>> |
| 13 |
>>> Hi, after following your tips the code gets like the following one: |
| 14 |
>>> |
| 15 |
>>> SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda" |
| 16 |
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda" |
| 17 |
>>> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb" |
| 18 |
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc" |
| 19 |
>>> SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc" |
| 20 |
>>> |
| 21 |
>>> KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", |
| 22 |
>>> NAME="hda%n" KERNEL=="sd*", SUBSYSTEM=="block", |
| 23 |
>>> ATTR{serial}=="9QK0T4WM", NAME="sda%n" KERNEL=="sd*", |
| 24 |
>>> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb%n" |
| 25 |
>>> KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", |
| 26 |
>>> NAME="sdc%n" KERNEL=="sd*", SUBSYSTEM=="block", |
| 27 |
>>> ATTR{serial}=="9VP0SBVN", NAME="sdc%n" That's not working, when i plug |
| 28 |
>>> more devices they get named without taking care of the rules above. Do |
| 29 |
>>> someone know why? thanks. i would like to be able to name devies using |
| 30 |
>>> its serial number. Thanks in advanced |
| 31 |
>>> |
| 32 |
>> |
| 33 |
>> Could it be that the sd* notation is somewhere hardwired in UDEV? I'd try |
| 34 |
>> to give the devices different names, like NAME="myhda", and so on. |
| 35 |
>> |
| 36 |
>> Just guessing, |
| 37 |
>> |
| 38 |
>> Wonko |
| 39 |
>> |
| 40 |
>> |
| 41 |
> |
| 42 |
> This is a shot in the dark but just in case. What did you name the rules |
| 43 |
> file? Is it possible that it is reading your file then reading another file |
| 44 |
> udev generated and the last one it reads is the one that sets the names? I |
| 45 |
> would look to see if there is another file in the rules.d directory that |
| 46 |
> sets the naming and then see what udev reads last. |
| 47 |
> |
| 48 |
> Again, shot in the dark and this may not apply. |
| 49 |
> |
| 50 |
> Dale |
| 51 |
> |
| 52 |
> :-) :-) |
| 53 |
> |
| 54 |
> |
Archives