DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after reboot but very often I just get /dev/ad_teknik_reader not pointing at ttyUSB0.
When I delete /dev/ad_teknik_reader and reboot I can get it right but not always ... it is frustrating to reboot since it is also a server.
I have Debian 2.6.32-5-amd64 (server).
Strange that it should not behave the same way on every reboot. Is there a pattern to that, like it's OK every other reboot.
You could try changing SYMLINK+="ad_teknik_reader" to SYMLINK="ad_teknik_reader"
EDIT: can you avoid the need to reboot by using udevadm control --reload-rules and re-plugging the hardware or, for a more complete re-initialisation, run /etc/init.d/udev restart or whatever the equivalent is on your distro.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.