Hi, thanks a lot for the answers. The name of the rules file is
00_whatever.rules, as far as i know there's also an option which
prevents to modifye the setted rules. Well, if no one knows how to do
i will try to find a different solution.
2010/8/31 Dale <rdalek1...@gmail.com>:
> Alex Schuster wrote:
>>
>> Pau Peris writes:
>>
>>
>>>
>>> Hi, after following your tips the code gets like the following one:
>>>
>>> SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda"
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda"
>>> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb"
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc"
>>> SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc"
>>>
>>> KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH",
>>> NAME="hda%n" KERNEL=="sd*", SUBSYSTEM=="block",
>>> ATTR{serial}=="9QK0T4WM", NAME="sda%n" KERNEL=="sd*",
>>> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb%n"
>>> KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G",
>>> NAME="sdc%n" KERNEL=="sd*", SUBSYSTEM=="block",
>>> ATTR{serial}=="9VP0SBVN", NAME="sdc%n" That's not working, when i plug
>>> more devices they get named without taking care of the rules above. Do
>>> someone know why? thanks. i would like to be able to name devies using
>>> its serial number. Thanks in advanced
>>>
>>
>> Could it be that the sd* notation is somewhere hardwired in UDEV? I'd try
>> to give the devices different names, like NAME="myhda", and so on.
>>
>> Just guessing,
>>
>> Wonko
>>
>>
>
> This is a shot in the dark but just in case. What did you name the rules
> file? Is it possible that it is reading your file then reading another file
> udev generated and the last one it reads is the one that sets the names? I
> would look to see if there is another file in the rules.d directory that
> sets the naming and then see what udev reads last.
>
> Again, shot in the dark and this may not apply.
>
> Dale
>
> :-) :-)
>
>
