swift 05/08/10 13:09:27 Modified: xml/htdocs/doc/en usb-guide.xml Log: Small spelling issues, no content. Thanks to cynric on the Gentoo forums for noticing
Revision Changes Path 1.6 +11 -11 xml/htdocs/doc/en/usb-guide.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/usb-guide.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/usb-guide.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/usb-guide.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo Index: usb-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- usb-guide.xml 17 Jun 2005 10:51:16 -0000 1.5 +++ usb-guide.xml 10 Aug 2005 13:09:27 -0000 1.6 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.5 2005/06/17 10:51:16 fox2mike Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.6 2005/08/10 13:09:27 swift Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -156,7 +156,7 @@ <p> First emerge the kernel sources of your choice. Here we'll use the -<c>gentoo-sources</c> For more information on the various kernel sources +<c>gentoo-sources</c>. For more information on the various kernel sources available on Portage, please look up the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Linux Kernel Guide</uri>. </p> @@ -395,7 +395,7 @@ <p> Once the device is connected and mounted, you can access it like a normal hard -disk. Usual operations like <c>cp</c>, <c>mv</c>, <c>rm</c> etc work fine. You +disk. Usual operations like <c>cp</c>, <c>mv</c>, <c>rm</c>, etc work fine. You could also create a filesystem on the USB stick/format it. </p> @@ -530,8 +530,8 @@ to ensure that they work properly and often firmware may contain code that is critical to ensure that the hardware performs as expected. Firmware is present in a wide variety of computer devices ranging from ROM chips to state of the -art USB and PCMCIA cards. When a device is plugged in, the firmware (which may -in some cases be the driver as well) is read and loaded onto memory after +art USB and PCMCIA cards. When a device is plugged in, the firmware (which may, +in some cases, be the driver as well) is read and loaded onto memory after which the device can be used by the system. </p> @@ -540,7 +540,7 @@ the firmware side of things in <e>hot-pluggable</e> devices. <c>sys-apps/hotplug</c> will use the required firmware to make that device usable. The firmware should be put in the <path>/lib/firmware</path> directory -and is picked up from there. Getting it is simple, the usual emerge will do. +and is picked up from there. Getting it is simple: the usual emerge will do. </p> <pre caption="Installing hotplug"> @@ -551,8 +551,8 @@ Now the obvious question would be, what is coldplug and why is it needed? <c>sys-apps/coldplug</c> does what hotplug does, but it does it for <e>hot-pluggable</e> devices that are already connected at boot time. A good -example of this would be a USB Network card. Earlier hotplug was the package -responsible for handling both but then it was split into hotplug and coldplug, +example of this would be a USB Network card. Earlier the hotplug package was +responsible for handling both, but then it was split into hotplug and coldplug, each with their distinct purposes. Emerge it if you have <e>hot-pluggable</e> devices that you need activated on boot up. </p> @@ -582,9 +582,9 @@ <body> <p> -A good number of documents online helped me during writing this, and there are -some that are that are highly technical but truly interesting. I thought they -all deserve some credit. So here we go! +A good number of online documents helped me during the development of this +document and there are some that are highly technical but truly interesting. +I thought they all deserve some credit, so here we go! </p> <ul> -- [email protected] mailing list
