Bug 133790

Summary:	udev breaks console.perms for pilot
Product:	[Fedora] Fedora	Reporter:	Thomas Zehetbauer <thomasz>
Component:	udev	Assignee:	Harald Hoyer <harald>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 13:23:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	123268

Description Thomas Zehetbauer 2004-09-27 14:23:39 UTC

udev causes /dev/ttyUSB* to be recreated every time one presses the
hotsync button and the Palm appears on the USB.

This means not only that /etc/security/console.perms cannot be applied
to the /dev/pilot symlink on login because /dev/ttyUSB* has been
removed on shutdown but also causes ownership and permissions to be
reset every time someone presses the hotsync button.

Comment 1 Bill Nottingham 2004-09-29 03:19:17 UTC

udev needs to be handling the console.perms stuff on device creation,
not just login.

Comment 2 Harald Hoyer 2004-09-29 08:45:27 UTC

That's not the problem, Bill...

The problem is, that the device seems to reconnect to the USB bus,
causing one REMOVE and one ADD hotplug event.

Which module is this?

Comment 3 Thomas Zehetbauer 2004-09-29 09:49:13 UTC

The device is a Palm Zire 71, the driver is CONFIG_USB_SERIAL_VISOR.

Comment 4 Harald Hoyer 2004-09-29 10:06:00 UTC

do you really have the problem with the permissions, btw?
if yes, which version of udev?

Comment 5 Thomas Zehetbauer 2004-09-29 23:02:52 UTC

It breaks the way this used to work: have a symlink from /dev/pilot to
/dev/ttyUSB1 and /dev/pilot listed in /etc/security/console.perms

It works now that I have created a /etc/udev/rules.d/10-local.rules
with KERNEL="ttyUSB1",SYMLINK="pilot"

The alternative would be to change /etc/console.perms to list
/dev/ttyUSB1 instead of /dev/pilot

Comment 6 Greg Kroah-Hartman 2004-09-29 23:15:28 UTC

Yes, the hardware causes that device to disconnect and reconnect every
time, you can't do anything about that, unfortunatly :(

And, as I just pointed out on linux-hotplug-devel, /dev/pilot
shouldn't always point to /dev/ttyUSB1, it all depends on the type of
device
you currently have (some Sony Clie devices use /dev/ttyUSB0 to sync
off of...)

Comment 7 Thomas Zehetbauer 2004-09-29 23:24:27 UTC

This is why it is (was) recommended practice to use a symlink.

Comment 8 Harald Hoyer 2004-09-30 10:41:14 UTC

Quick solution:
# ln -s ttyUSB1 /etc/udev/devices/pilot
as of >= udev-032-5 this should get copied to the real dev on every reboot