Hi All,
I've written a custom udev rule to change the permissions of /dev/ttyS* but
it doesn't seem to be working at boot up. If I run
/sbin/udevcontrol reload_rules; udevtrigger
The rules are parsed, applied and the permissions are then correct but why is it
not doing so at boot? The file in questions I've called
/etc/udev/rules.d/49-udev-override.rules and it contains
KERNEL=="tty[A-Z]*", NAME="%k",
GROUP="rcl", MODE="0660", OPTIONS="last_rule"
the default 50-udev.rules file has been left untouched. SELinux is in
permissive mode and so I can't find a reason why it is happening. Anyone
have any ideas?
--
James A. Peltier
IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone : 778-782-6573
Fax : 778-782-3045
E-Mail : jpeltier at sfu.ca
Website : http://www.sfu.ca/itservices
http://blogs.sfu.ca/people/jpeltier
James A. Peltier wrote:> Hi All, > > I've written a custom udev rule to change the permissions of /dev/ttyS* but it doesn't seem to be working at boot up. If I run > > /sbin/udevcontrol reload_rules; udevtrigger > > The rules are parsed, applied and the permissions are then correct but why is it not doing so at boot? The file in questions I've called /etc/udev/rules.d/49-udev-override.rules and it contains > > KERNEL=="tty[A-Z]*", NAME="%k", GROUP="rcl", MODE="0660", OPTIONS="last_rule" > > the default 50-udev.rules file has been left untouched. SELinux is in permissive mode and so I can't find a reason why it is happening. Anyone have any ideas? >The thread starting at: <http://lists.centos.org/pipermail/centos/2009-July/079133.html> may gives some clues James Pearson
On 6/14/11, James A. Peltier <jpeltier at sfu.ca> wrote:> The rules are parsed, applied and the permissions are then correct but why > is it not doing so at boot? The file in questions I've called > /etc/udev/rules.d/49-udev-override.rules and it contains > > KERNEL=="tty[A-Z]*", NAME="%k", GROUP="rcl", MODE="0660", > OPTIONS="last_rule" > > the default 50-udev.rules file has been left untouched. SELinux is in > permissive mode and so I can't find a reason why it is happening. Anyone > have any ideas?I had similar problems with udev rules when adding a 2nd NIC and needed to override the assignments which switched the original eth0 to eth1. For some reason, despite all the info that says the over-ride filename should be alphanumerically "smaller", it only works if the file is alphanumerically "larger". Which kind of make sense to me since a later rule should override an earlier one. So instead of 49-, try 51- instead :D