I think I used that longer workaround, because "udevadm trigger" causes add events to be called for all devices. My workaround only sets settings for hard drives.
I didn't want to call "udevadm trigger" because I didn't want to spend time investigating if it would affect anything else in the system (this is kind of a production box). -- Settings in /etc/hdparm.conf are not applied during boot https://bugs.launchpad.net/bugs/595138 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
