On 07/12/10 19:32, patrick keshishian wrote: > On Mon, Jul 12, 2010 at 2:58 PM, fred <[email protected]> wrote: >> Hello, >> >> A user needs to connect to external equipment using tip and a serial port. >> >> I created an /etc/remote file: >> snake:br=9600:dv=/dev/tty01:hf:nb:pa=none >> >> The group associated with /dev/tty01 was changed from dialer to one that >> includes the user: >> $ls -l /dev/tty01 >> crw-rw---- 1 uucp wheel 8, 1 Feb 7 09:38 /dev/tty01 > > so, the user is already in wheel group. Revert above change. Enable > sudo (if not already done so) for users in group wheel. > > $ sudo -u uucp tip snake > > --patrick
uh...if all else fails, do it as root? I think we'd prefer to avoid that, unless really a root-like activity. The "dialer" group is set up just for this purpose. The problem with changing the ownership (or group) of a device file is the next upgrade will overwrite your ownership change. Ask me how I know. Better idea, don't -- just use your imagination. I'm not sure why you didn't just add that user to group "dialer", but it is quite straight forward: /home/nick $ grep nick /etc/group wheel:*:0:root,nick wsrc:*:9:nick dialer:*:117:nick nick:*:1000: and...I (as "nick") have no trouble using my serial port without using sudo and without changing device file ownership. You will probably want to create a file /var/log/aculog which is writable by group "dialer", as well... Squishes an error message, and provides some useful logging, too. Nick.
