Hello Dieter I placed the file in the location you suggested, but i wasn't sure how to "set the attributes accordingly: root.root / 0755 (whatever the other rules files do have, to stay in tune with the ubuntu-rules)"
I rebooted, but Xsane did not recognise the scanner. If it is of any significance, typing the following command produced the following reply with '55-scanner.rules' text is shown in green! david at david-desktop:~$ ls -l /etc/udev/rules.d total 16 -rwxrwxrwx 1 root root 1362 2009-06-07 13:06 55-scanner.rules -rw-r--r-- 1 root root 459 2009-05-28 21:51 70-persistent-cd.rules -rw-r--r-- 1 root root 392 2009-05-28 20:19 70-persistent-net.rules -rw-r--r-- 1 root root 1398 2009-04-09 01:19 README david at david-desktop:~$ I think we need to fiddle a little more :-) Regards Dave On Sat, 2009-06-06 at 20:49 +0200, Dr. Ing. Dieter Jurzitza wrote: > Dear David, > attached please find a udev-rule file that should do what you (we ..) want. > Please test as follows: > > - put 55-scanner.rules into /etc/udev/rues.d > - set the attributes accordingly: root.root / 0755 (whatever the other rules > files do have, to stay in tune with the ubuntu-rules) > - reboot > > now your scanner ought to have the device properties root.users 0660 > (/dev/sg2 > in your case). If that does not work, we'll have to fiddle a little more (it > is always possible that I made some mistakes here :-) please try) > > > Am Samstag 06 Juni 2009 19:14:48 schrieben Sie: > > I have heard of undev rules to somehow alter things at boot, so it > > begins to make some sense to me! > Good! But be aware, the future will come with a different tool chain that > makes things even worse. But don't be scared, I've gone through this mess > readily :-))) > > > > > My understanding of the user account situation is as follows: > > > > I have enabled all user priveliges for me, username 'david', which > > included administering the system (perhaps initially set for first > > user). There are 3 other users, but without administrative rights. Only > > david is has the password for sudo type operations. This is how i like > > it to be. > > > > Interestingly, i am not specifically associated with any group as such, > > and neither are the other users. There is a facility to specifically > > associate users with groups, which includes 'root, users, saned, > > admin, ...'. > This information was not neccessary for me. What I had had wanted to know - > but guessed now - was the fact that "you" are david and you belong to the > group "users". Because I dislike to make devices world readable / writable, I > prefer restricting this to the group. > Say, your current boot comes with /dev/sg2 owned by root and having the group > root, I modify this to be owned by root (still) and belong to the group > users. > So every member of the "users" group may read and write (0660) - but nobody > else. This is a weak restriction, but better than nothing (IMHO). If my guess > with "users" would be wrong, please adapt the GROUP="users" entry accordingly. > > > > > david at david-desktop:~$ ls -l /etc/udev/rules.d > > total 12 > > -rw-r--r-- 1 root root 459 2009-05-28 21:51 70-persistent-cd.rules > > -rw-r--r-- 1 root root 392 2009-05-28 20:19 70-persistent-net.rules > > -rw-r--r-- 1 root root 1398 2009-04-09 01:19 README > > david at david-desktop:~$ > I hoped it would look that way! > > > > > Please let me know if you need anything else > I am waiting for your results :-))))) > Good luck, > > > > Dieter > > >
