Andy Goldschmidt <[email protected]> writes: > Do we need to know how to write our own udev rules ? > or is it a simple case of just knowing how to "read" them ?
They need to know how to "troubleshoot" them. So "read" is mandatory. Write them...not so much. > udev and hotplug go together - but the topic doesn't cover hotplug - is > that correct ? What do you mean by "hotplug"? The old hotplug system? No it has been dropped. Also, this objective has only a weight of 1. Don't go overboard :) > Do we need to know about the command "udevinfo" ? You sure do. But not for the exam :) I thought about just including udevadm but didn't want to overwhelm the objective. We're really looking for people to either already know about udev and go, "oh, yeah. this part is easy on the exam" or go "what's udev?" and find out a little bit about it. It's really about understand/knowing that udev is there and the essentials of how it works. Udevmonitor was included in the list because it's fun to watch and give some visual impact on the fact that these events are going on. Regards, -- g. matthew rice <[email protected]> starnix care, toronto, ontario, ca phone: 647.722.5301 x242 gpg id: EF9AAD20 http://www.starnix.com professional linux services & products _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
