Tag Info

New answers tagged

1

The path you used for systemctl is wrong. systemctl is in /bin/, not /usr/bin/ (this is Debian/Ubuntu specific).


7

Modern Linux kernels support the devtmpfs file system (do not confuse with ancient devfs), which creates all device nodes dynamically as soon as the kernel discovers them. (In fact, latest udev releases require this; you'll find that udev doesn't create any device nodes anymore, only symlinks.) Similarly, firmware loading has been moved into the kernel as ...


10

There are various alternatives to udev out there. Seemingly Gentoo can use something called mdev. Another option would be to attempt to use udev's predecessor devfsd. Finally, you can always create all the device files you need with mknod. Note that with the latter there is no need to create everything at boot time since the nodes can be created on disk and ...


0

Run udevadm info -a -n /dev/sdb where /dev/sdb is the device you want to identify to see what rules would match it. Pick one or more whose combination match only the devices you want to act on. This is a general strategy for coming up with udev rules; see Triggering an action when a specific volume is connected. In this case: DRIVERS=="usb-storage"


1

You can use 'KERNEL=="sd*", SUBSYSTEMS=="scsi" ' with some ATTRS to filter USB storage devices. Notice all the USB storage devices thus also pendrives and memory cards are recognized as SCSI devices so they are assigned as /dev/sd*. Here you have a very good tutorial on how to create UDEV rules: http://www.reactivated.net/writing_udev_rules.html


0

Using Jander's rule, I was able to access my USB serial adapter... but only if running PuTTY as root. Modifying the rule to specify different permissions allowed me to access it by any user. I.E. SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", MODE="0666", SYMLINK+="serial"


0

While this is rather late, I fixed my issue by removing the KERNEL="eth*", part of the rule in /etc/udev/rules.d/70-persistent-net.rules file. This works because, once UDEV has renamed the device to "rename*", this part will stop the rule matching. So, removing it allows the correct name to be assigned to the correct device regardless of what UDEV has ...



Top 50 recent answers are included