| |||||||||||||
|
| |||||||||||||
Udev rules and the management of the plumbing layerUdev rules and the management of the plumbing layerPosted Aug 13, 2008 8:56 UTC (Wed) by gnb (subscriber, #5132)In reply to: Udev rules and the management of the plumbing layer by mattdm Parent article: Udev rules and the management of the plumbing layer
> It has nothing to do with desktop or server software. But it has to do with desktop/server deployments. Embedded systems with a fixed set of hardware can often still be built with all the drivers built-in, a fixed /dev containing the correct nodes, and no need for early userspace or udev or probably most of the daemons you had in mind. There is plenty that can be done with a bare kernel and a minimal userpsace to push config. into it, just not in the desktop space.
(Log in to post comments)
Udev rules and the management of the plumbing layer Posted Aug 14, 2008 22:24 UTC (Thu) by deleteme (guest, #49633) [Link] Well at somepoint it's going to be cheaper to just run udev than mapping everything on your own, even in embedded.
Udev rules and the management of the plumbing layer Posted Aug 15, 2008 0:17 UTC (Fri) by madscientist (subscriber, #16861) [Link] On my embedded systems, which are busybox-based, I use mdev instead. Same basic idea though.
Udev rules and the management of the plumbing layer Posted Aug 15, 2008 0:01 UTC (Fri) by quotemstr (subscriber, #45331) [Link] Isn't it fair to assume the desktop space by default and make it explicit if you're talking about embedded Linux?
|
|
||||||||||||