How is the group-id for the USB-devices in /dev during boot determined?
How do the group-ids for the devices in /dev get determined during boot up? The system must get the defaults for the devices some time during the boot process. Where are the defaults listed?
Actual reason for my question is that I need a permanent change of "dialout" to "uucp" or, even better to "dialout,uucp" in this line: Code:
|
You could always set the GID using udev.
Please read the entire page before doing anything drastic. http://reactivated.net/writing_udev_...html#ownership (and please mention the OS concerned in posts) |
Yes I could, thanks. I could also place a simple shell script in KDE's autostart directory with a chgrp statement. That doesn't answer the basic question, though: "How do the group-ids for the devices in /dev get determined during boot up?" Do you have any information on that?
Oh, this is for SuSE 11.2. |
Quote:
EDIT: This assumes /dev/ttyUSB0 is an unpluggable device as the "USB" part of its name suggests. The conventional way to modify udev rules is by using/creating /etc/udev/rules.d/90-local.rules. An earlier numbering may result in the rule's effects being overridden by a later rule. A later numbering supplants rules intended to be run at the end of processing. |
Quote:
/lib/udev/rules.d then. Quote:
|
Quote:
|
Quote:
Quote:
|
Quote:
EDIT: no right answers, only choices! |
Bull's eye. And 90-... it is.
Now this is from /lib/udev/rules.d/50-udev-default.rules: Code:
… Code:
P: /devices/pci0000:00/0000:00:07.2/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0 Code:
KERNEL=="ttyUSB[0-9], DRIVER=="kobil", GROUP="uucp" |
Quote:
Code:
KERNEL=="ttyUSB[0-9], GROUP="uucp" |
But I do have those, and one of them is my wireless stick for the internet :(. Darn, the card reader has a specific driver, how do I find out its name or get an otherwise unambiguous attribute for it :scratch:
The problem is further confounded by the fact that udevinfo seems defunct or to be integrated into udevadm, which seems to give less information in particular about the ATTR(S) specifics... |
Okay, this is what I did. udevadm has obviously integrated the functionality of udevinfo, thus the necessary command in my case is now
Code:
udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) Code:
Udevadm info starts with the device specified by the devpath and then Code:
Bus 002 Device 002: ID 0d46:2012 Kobil Systems GmbH KAAN Standard Plus (Smartcard reader) Code:
KERNEL=="ttyUSB[0-9], ATTRS{idVendor}=="0d46", ATTRS{idProduct}=="2012", GROUP="uucp" Code:
crw-rw---- 1 root dialout 188, 0 May 4 17:52 /dev/ttyUSB0 |
I would have thought that the reader device would be the device identified by
ATTRS{product}=="HUAWEI Mobile" As the next device down is the EHCI controller. Also a search for Kobil and HUAWEI eventually leads here http://hardware4linux.info/component/24136/ where it appears Huawei are vendors of usb mass storage devices and related technology. |
Umm, just as a clarification of my setup: The Kobil gadget is the card reader, usually residing at /dev/ttyUSB0. The Huawei is a wireless stick (Huawei E176) for a connection to the internet, it has also a small (50 MB) memory for the vendor to put its drivers on it. The position varies but usually it takes /dev/ttyUSB2.
This is the entire output of lsusb -vv Code:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub |
Quote:
Code:
KERNEL=="ttyUSB[0-9]", GROUP="uucp" Just saw "But I do have those, and one of them is my wireless stick for the internet . Darn, the card reader has a specific driver, how do I find out its name or get an otherwise unambiguous attribute for it The problem is further confounded by the fact that udevinfo seems defunct or to be integrated into udevadm, which seems to give less information in particular about the ATTR(S) specifics..." Will follow up in another post. |
All times are GMT -5. The time now is 03:03 AM. |