New answers tagged

2

I'm concerned about 2 points PID files which I'm not familiar with, but I would suggest using pgrep as workaround. ds4drv seems a daemon but udev supports only short running processes. RUN{type} ... This can only be used for very short-running foreground tasks. Running an event process for a long period of time may block all further events ...


1

I had the same issue. The debian maintainers added a patch to mdadm which causes the raid assembly to start before the devices are up. I have not yet completely found out why as it's supposed to fix broken RAIDs as root file system. But you can fix it for now by downgrading the mdadm package. Get the older version from here: ...


1

/dev/null is created by the kernel at boot time, because the kernel requires it. It's not udev specific.


3

All but the root bus (which is typically a platform bus, e.g. ACPI on PCs) are bridged off the root bus, and their order depends on enumeration. Now normally bus enumeration is mostly deterministic as the order in which devices on the bus are found is normally static, but there is no guarantee for that, and when two bus bridges are chained, enumeration is ...


1

I cannot comment so I guess an "Answer" will have to suffice. Have you upgraded your system at all? Now I am by no means an expert in this, but if you add additional PCI/PCI slots to an existing PCI bus, then there is the "possibility" that the numbers can change I believe. I would much rather have made this a comment in case I was wrong, but I am sure ...


1

Network interfaces usually do not appear in /dev at all. Their configuration is not done with accesses to device files but with accesses to the NETLINK socket. I don't think that you can give access to this socket to an ordinary user. You need a suitable sudo rule (and maybe a wrapper script) so that the user can call ip addr.


2

According to man page --action=change is the default value for udevadm. -c, --action=ACTION Type of event to be triggered. The default value is change. Therefore you better try --action=add instead. It should help: /sbin/udevadm trigger --type=devices --action=add


0

So it turns out by editing the line in automount() in /etc/udev/scripts/mount.sh did work, I just must have been editing it wrong. Originally the line (25) looks like this if ! $MOUNT -t auto -o async,relatime $DEVNAME "/media/$name" Previously I have been adding fmask & dmask options wrongly. if ! $MOUNT -t auto -o ...



Top 50 recent answers are included