Argh! It looks like FC5 changed how you administer your SELinux configuration, completely messing with the SELinux workflow I developed way back in FC4. Dag nabbit. Now I have to learn this new system before I can debug configuration issues in Apache and, no, Dave, I won’t turn it off.

It seems that every time I upgrade/install FC on a workstation or laptop, I have to fight this battle. Really, it’s only a small skirmish, but it’s annoying. Here’s the lastest “solution” for FC5. I created /etc/udev/rules.d/10-palm.rules with the following in it.

KERNEL==”ttyUSB[02468]“, SYSFS{product}==”Palm Handheld*”, NAME=”%k”, GROUP=”uucp”, MODE=”0660″, OPTIONS=”last_rule”

KERNEL==”ttyUSB[13579]“, SYSFS{product}==”Palm Handheld*”, NAME=”%k”, GROUP=”uucp”, MODE=”0660″, SYMLINK=”pilot”

These rules should ensure that /dev/pilot only points to the odd ttyUSB device created by the T3 when the hotsync button is pressed. Otherwise, /dev/pilot only seems to point to the odd device about 1/2 the time and the even device the other half.

udev, palm, linux, fedora core 5, fc5, linux palm