Hello folks!
Well, seems new udev is a pain not only for me, but here is my story. Being and embedded developer for a long period, I have my AVR programmer, based on FTDI FT232RL USB to USART bridge with me for years now. Besides, I have a number of devices and some other stuff I need to talk to my PC, based on same FT232RL bridge (and all of them emerge as ttyUSBn in system). So, not to make a mess, I wrote a simple udev rule, the after my programmed is plugged in, name it as /dev/avrusb500v2 and make a symlink to this name from the original kernel device name like ttyUSBn.

That used to work perfectly until the udev-197 came to life. Now udev ignores this and names programmer as a regular /dev/ttyUSBn, where n - number of such devices attached to the system at this moment. Sure, I have "product" variable programmed into FT232RL EEPROM, so it shows up in lsusb -v like this:

I played with rule, but without any luck. Besides, I tried to use this rule on machine, running udev-172, and it works just perfect, giving me /dev/avrusb500v2 device with a symlink to /dev/ttyUSB0. So, what should be done to get this little thing work again?

Seems it somehow connected with NAME parameter. If I cut it out and leave only SYMLINK+="avrusb500v2", it work flawlessly, making /dev/ttyUSBn as a primary device file and a symlink /dev/avrusb500v2 , pointing to it.