At a Slack 11, as root, I´m trying to change the permissions of devices ttyS0, ttyS1, ttyS2 and ttyS3 to able comom users to change the device configuration at minicom. I tried to to change the permissions at two workstation but it didn´t work at the both computers. I put in the terminal:

# chmod 776 ttyS*
# chgrp eng ttyS*

The terminal just jump to the next confiming the execution of the command but when I list the devices:

# ls -l ttyS*

The permissions are still the same.
I used to do this process at workstations with Slack 10.2 and worked fine but at Slack 11 I fighting to get it working...
Is there any other process to make this happen?

I'm not sure if it will work, but you could try <if you are using udev> to modify

/etc/udev/rules.d/udev.rules

find this section and modify accordingly:

# tty devices
KERNEL=="console", NAME="%k", GROUP="tty", MODE="0600"
KERNEL=="tty", NAME="%k", GROUP="tty", MODE="0666"
KERNEL=="tty[0-9]*", NAME="vc/%n", SYMLINK+="%k", GROUP="tty"
KERNEL=="ttyS[0-9]*", NAME="tts/%n", SYMLINK+="%k", GROUP="tty"
KERNEL=="ttyUSB[0-9]*", NAME="tts/USB%n", GROUP="tty", MODE="0666"
KERNEL=="ippp0", NAME="%k", GROUP="tty"
KERNEL=="isdn*", NAME="%k", GROUP="tty"
KERNEL=="dcbri*", NAME="%k", GROUP="tty"
KERNEL=="ircomm*", NAME="%k", GROUP="tty"

I imagine you could add MODE="0666" to the KERNEL=="ttyS[0-9]*" line
# udevtrigger as root should make the change immediately
tobyl

It didn´t work... but I will check out the configuration address of the serial board, even I had put the same configuration I put in the old machine I´m gonna check because even when I´m as root at minicom and I print something through the serial it doesn´t show anything at the screen that´s why I suspect of the board config.

Ok, looks like you have more than just a permissions problem.

http://tldp.org/HOWTO/Serial-HOWTO.html

is a superb guide if you haven't found it already, but I don't think it has quite caught up with udev yet.
If you have more than 4 serial ports you may need to recompile your kernel to allow for this.
If you are still stuck, make sure you state which kernel you are using in your reply.

good luck,

tobyl

The correct way to allow normal users to use ttySx is to add group tty to said user.