| 1 |
swift 05/08/10 13:09:27 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en usb-guide.xml |
| 4 |
Log: |
| 5 |
Small spelling issues, no content. Thanks to cynric on the Gentoo forums for noticing |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.6 +11 -11 xml/htdocs/doc/en/usb-guide.xml |
| 9 |
|
| 10 |
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 |
| 11 |
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 |
| 12 |
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 |
| 13 |
|
| 14 |
Index: usb-guide.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v |
| 17 |
retrieving revision 1.5 |
| 18 |
retrieving revision 1.6 |
| 19 |
diff -u -r1.5 -r1.6 |
| 20 |
--- usb-guide.xml 17 Jun 2005 10:51:16 -0000 1.5 |
| 21 |
+++ usb-guide.xml 10 Aug 2005 13:09:27 -0000 1.6 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.5 2005/06/17 10:51:16 fox2mike Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.6 2005/08/10 13:09:27 swift Exp $ --> |
| 26 |
|
| 27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 28 |
|
| 29 |
@@ -156,7 +156,7 @@ |
| 30 |
|
| 31 |
<p> |
| 32 |
First emerge the kernel sources of your choice. Here we'll use the |
| 33 |
-<c>gentoo-sources</c> For more information on the various kernel sources |
| 34 |
+<c>gentoo-sources</c>. For more information on the various kernel sources |
| 35 |
available on Portage, please look up the <uri |
| 36 |
link="/doc/en/gentoo-kernel.xml">Gentoo Linux Kernel Guide</uri>. |
| 37 |
</p> |
| 38 |
@@ -395,7 +395,7 @@ |
| 39 |
|
| 40 |
<p> |
| 41 |
Once the device is connected and mounted, you can access it like a normal hard |
| 42 |
-disk. Usual operations like <c>cp</c>, <c>mv</c>, <c>rm</c> etc work fine. You |
| 43 |
+disk. Usual operations like <c>cp</c>, <c>mv</c>, <c>rm</c>, etc work fine. You |
| 44 |
could also create a filesystem on the USB stick/format it. |
| 45 |
</p> |
| 46 |
|
| 47 |
@@ -530,8 +530,8 @@ |
| 48 |
to ensure that they work properly and often firmware may contain code that is |
| 49 |
critical to ensure that the hardware performs as expected. Firmware is present |
| 50 |
in a wide variety of computer devices ranging from ROM chips to state of the |
| 51 |
-art USB and PCMCIA cards. When a device is plugged in, the firmware (which may |
| 52 |
-in some cases be the driver as well) is read and loaded onto memory after |
| 53 |
+art USB and PCMCIA cards. When a device is plugged in, the firmware (which may, |
| 54 |
+in some cases, be the driver as well) is read and loaded onto memory after |
| 55 |
which the device can be used by the system. |
| 56 |
</p> |
| 57 |
|
| 58 |
@@ -540,7 +540,7 @@ |
| 59 |
the firmware side of things in <e>hot-pluggable</e> devices. |
| 60 |
<c>sys-apps/hotplug</c> will use the required firmware to make that device |
| 61 |
usable. The firmware should be put in the <path>/lib/firmware</path> directory |
| 62 |
-and is picked up from there. Getting it is simple, the usual emerge will do. |
| 63 |
+and is picked up from there. Getting it is simple: the usual emerge will do. |
| 64 |
</p> |
| 65 |
|
| 66 |
<pre caption="Installing hotplug"> |
| 67 |
@@ -551,8 +551,8 @@ |
| 68 |
Now the obvious question would be, what is coldplug and why is it needed? |
| 69 |
<c>sys-apps/coldplug</c> does what hotplug does, but it does it for |
| 70 |
<e>hot-pluggable</e> devices that are already connected at boot time. A good |
| 71 |
-example of this would be a USB Network card. Earlier hotplug was the package |
| 72 |
-responsible for handling both but then it was split into hotplug and coldplug, |
| 73 |
+example of this would be a USB Network card. Earlier the hotplug package was |
| 74 |
+responsible for handling both, but then it was split into hotplug and coldplug, |
| 75 |
each with their distinct purposes. Emerge it if you have <e>hot-pluggable</e> |
| 76 |
devices that you need activated on boot up. |
| 77 |
</p> |
| 78 |
@@ -582,9 +582,9 @@ |
| 79 |
<body> |
| 80 |
|
| 81 |
<p> |
| 82 |
-A good number of documents online helped me during writing this, and there are |
| 83 |
-some that are that are highly technical but truly interesting. I thought they |
| 84 |
-all deserve some credit. So here we go! |
| 85 |
+A good number of online documents helped me during the development of this |
| 86 |
+document and there are some that are highly technical but truly interesting. |
| 87 |
+I thought they all deserve some credit, so here we go! |
| 88 |
</p> |
| 89 |
|
| 90 |
<ul> |
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
-- |
| 95 |
gentoo-doc-cvs@g.o mailing list |
Archives