Red Hat Bugzilla – Bug 145889
udev config tool to create alternate /dev entries
Last modified: 2014-03-16 22:52:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
Devices, particularly USB devices, can be mounted on a first come,
first served basis. However, things like printer configuration need to
map to specific devices.
I have two printers and need to create /dev/printer0 and /dev/printer1
which always map to the physical printer, regardless of the
/dev/usb/lp? that gets assigned during hot/coldplugging.
Yes, you can go in and edit /etc/hotplug policies and agents, but
there must be an easier way of doing it, through system-config-hotplug
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. It's not a bug
With printers I'm fairly sure CUPS has a magic syntax that includes the printer
name in the device string (this is using CUPS' own web tool thing)... I have no
idea if this works or whether the system-config-printer supports it though.
Can't you use udev entries for this?
It depends where you see the boundary of responsibility for managing this
New devices are detected by hotplug, therefore hotplug should be responsible for
managing all tasks associated with that activity. You are correct that udev does
the work, but that should not prevent another task issuing instructions as to
what to do when something is added.
In truth the boundary of responsibility between the two is not clear, even in
kernel.org's eyes. Both are hosted in the same directory.
Maybe this should be a wider discussion between the Redhat maintainers of
hotplug and udev.
Perhaps I'm not clear.
If you *want* to make alternately named devices on creation of a device node,
the correct place is in the udev configuration.
Changing summary to make it more accurate.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing this; FC3 is EOL, and this would need to be solved outside of the
hotplug package, which no longer exists.