| |||||||||||||
Udev and firmwareUdev and firmwarePosted Oct 11, 2012 22:21 UTC (Thu) by rwmj (subscriber, #5474)Parent article: Udev and firmware
I'd support a fork (or rewrite) of udev:
- There's no reason for it to be included in systemd.
- Since it was included in systemd, the location of the daemon seems to move around, breaking our small Linux appliance (it uses udev, not systemd).
- The udev rules format is braindead. Whoever wrote it had never heard of parsers.
(Log in to post comments)
Udev and firmware Posted Oct 12, 2012 0:49 UTC (Fri) by liam (subscriber, #84133) [Link]
I more might be misunderstanding things but they seem as if they perform complementary actions. Both are event driven. Both can even perform similar actions (say, creating mount points).
Regarding syntax, perhaps it would be possible to rewrite the udev rules into the systemd format? I haven't actually tried doing that yet so I don't know if it would be possible, especially with the complicated matching schemes of udev.
Udev and firmware Posted Oct 12, 2012 14:29 UTC (Fri) by nix (subscriber, #2304) [Link] Since it was included in systemd, the location of the daemon seems to move aroundThis actually first happened in udev 174, which predates the systemd merge. No compatibility symlink was left behind and no rationale was given for the move, which contravenes long-standing Unix policy anyway (moving a daemon into /lib/udev? Total number of other daemons in /lib: zero.)
|
|||||||||||||