Author: matthew Date: 2005-04-16 10:09:09 -0600 (Sat, 16 Apr 2005) New Revision: 4979
Modified: branches/6.1/BOOK/chapter01/changelog.xml branches/6.1/BOOK/chapter07/udev.xml Log: * Reword handling of hotpluggable devices now that we install the hotplug package (merge r5978 from trunk) Modified: branches/6.1/BOOK/chapter01/changelog.xml =================================================================== --- branches/6.1/BOOK/chapter01/changelog.xml 2005-04-16 16:06:59 UTC (rev 4978) +++ branches/6.1/BOOK/chapter01/changelog.xml 2005-04-16 16:09:09 UTC (rev 4979) @@ -82,6 +82,9 @@ </itemizedlist> </listitem> +<listitem><para>April 16, 2005 [matt]: Reword handling of hotpluggable devices +now that we install the hotplug package (Andrew Benton)</para></listitem> + <listitem><para>April 16, 2005 [matt]: Minor wording/typo fixes (Allard Welter) </para></listitem> Modified: branches/6.1/BOOK/chapter07/udev.xml =================================================================== --- branches/6.1/BOOK/chapter07/udev.xml 2005-04-16 16:06:59 UTC (rev 4978) +++ branches/6.1/BOOK/chapter07/udev.xml 2005-04-16 16:09:09 UTC (rev 4979) @@ -154,22 +154,11 @@ <command>S05modules</command> bootscript), <command>udev</command> will be called upon to create the relevant device node(s) according to the <systemitem class="filesystem">sysfs</systemitem> data available in -<filename class="directory">/sys</filename>. If the driver for the -just plugged in device is available as a module but currently unloaded, -then attaching the device to the system will only cause the kernel's -bus driver to generate a hotplug event that notifies userspace of the -new device connection and it not being attached to a driver. In -effect, nothing happens and the device itself is not usable -yet.</para> +<filename class="directory">/sys</filename>.</para> -<para>If building a system that has a lot of drivers compiled as -modules rather than directly built into the kernel, using the -<command>S05modules</command> may not be practical. The Hotplug -package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can -be beneficial in these cases. When the Hotplug package is installed, -it will respond to the aforementioned kernel's bus driver hotplug -events. The Hotplug package will load the appropriate module and make -this device available by creating the device node(s) for it.</para> +<para>If the driver for the just plugged in device is available as a module but +currently unloaded, the Hotplug package will load the appropriate module +and make this device available by creating the device node(s) for it.</para> </sect2> <sect2> -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
