[virtualization-guide] iscsi section update
by Chris Curran
commit 2e1b88100d0a8554bde0ce234f1220d4fb6c4a97
Author: Chris Curran <ccurran(a)redhat.com>
Date: Fri Jul 2 14:36:24 2010 +1000
iscsi section update
en-US/Colophon.xml | 2 +-
en-US/KVM_Clock.xml | 6 +-
en-US/KVM_Win_PV.xml | 2 +-
en-US/Misc_Administration.xml | 13 ++--
en-US/PCI.xml | 6 +-
en-US/Reference_virsh.xml | 8 +-
en-US/Reference_virt-manager.xml | 4 +-
en-US/Storage_Pools_iSCSI.xml | 152 +++++++++++++++++++++++++++++++++++---
en-US/Troubleshooting.xml | 6 +-
9 files changed, 167 insertions(+), 32 deletions(-)
---
diff --git a/en-US/Colophon.xml b/en-US/Colophon.xml
index 843ea79..6e0f369 100644
--- a/en-US/Colophon.xml
+++ b/en-US/Colophon.xml
@@ -8,7 +8,7 @@
This manual was written in the DocBook XML v4.3 format.
</para>
<para>
- This book is based on the work of Jan Mark Holzer and Chris Curran.
+ This book is based on the original work of Jan Mark Holzer, Justin Clift and Chris Curran.
</para>
<para>
Other writing credits go to:
diff --git a/en-US/KVM_Clock.xml b/en-US/KVM_Clock.xml
index a6addc0..dec299e 100644
--- a/en-US/KVM_Clock.xml
+++ b/en-US/KVM_Clock.xml
@@ -77,10 +77,10 @@ http://cleo.tlv.redhat.com/qumrawiki/KVM/TimeKeeping#head-a03434101d51798...
<para>
If the CPU lacks the <computeroutput>constant_tsc</computeroutput> bit, disable all power management features (<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=513138">BZ#513138</ulink>). Each system has several timers it uses to keep time. The TSC is not stable on the host, which is sometimes caused by <command>cpufreq</command> changes, deep C state, or migration to a host with a faster TSC. Deep C sleep states can stop the TSC. To prevent the kernel using deep C states append <command>processor.max_cstate=1</command> to the kernel boot options in the <filename>grub.conf</filename> file on the host:
</para>
-<!--FIXME-->
- <screen>term Fedora (2.6.18-159.el5)
+
+ <screen>term Red Hat Enterprise Linux (2.6.32-36.x86-64)
root (hd0,0)
- kernel /vmlinuz-2.6.18-159.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <emphasis>processor.max_cstate=1</emphasis>
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <emphasis>processor.max_cstate=1</emphasis>
</screen>
<para>
Disable <command>cpufreq</command> (only necessary on hosts without the <command>constant_tsc</command>) by editing the <filename>/etc/sysconfig/cpuspeed</filename> configuration file and change the <command>MIN_SPEED</command> and <command>MAX_SPEED</command> variables to the highest frequency available. Valid limits can be found in the <filename>/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies</filename> files.
diff --git a/en-US/KVM_Win_PV.xml b/en-US/KVM_Win_PV.xml
index f804e3c..47c3ad5 100644
--- a/en-US/KVM_Win_PV.xml
+++ b/en-US/KVM_Win_PV.xml
@@ -11,7 +11,7 @@
</para>
<para>
The KVM para-virtualized drivers are automatically loaded and installed on the following:</para>
- <itemizedlist><listitem><para>Any 2.6.27 or newer kernel. </para></listitem>
+ <itemizedlist><listitem><para>Any kernel version 2.6.27 or newer. </para></listitem>
<listitem><para>Newer Ubuntu, Fedora, CentOS, Red Hat Enterprise Linux.</para></listitem></itemizedlist>
<para>
Those versions of Linux detect and install the drivers so additional installation steps are not required.
diff --git a/en-US/Misc_Administration.xml b/en-US/Misc_Administration.xml
index 5157211..6dd94a7 100644
--- a/en-US/Misc_Administration.xml
+++ b/en-US/Misc_Administration.xml
@@ -506,17 +506,18 @@ exec gnome-session
</section>
<section>
<title>Gracefully shutting down guests</title>
- <para>Virtualized Red Hat Enterprise Linux 6 guests installed with the <option>Minimal installation</option> does not install the <package>acpid</package> package.</para>
- <para>Without the <package>acpid</package> package the Red Hat Enterprise Linux 6 will not shut down when the <command>virsh shutdown</command> command is used to gracefully shut down the virtualized guest.</para>
- <para>Using <command>virsh shutdown</command> is easier for system administration. Without graceful shut down with the <command>virsh shutdown</command> command a system administrator must log into a virtualized guest manually or send a <keycap>Ctrl</keycap>-<keycap>Alt</keycap>-<keycap>Del</keycap> key combination to each guest.</para>
+ <para>Installing virtualized Red Hat Enterprise Linux 6 guests with the <option>Minimal installation</option> installation option will not install the <package>acpid</package> package.</para>
+ <para>Without the <package>acpid</package> package, the Red Hat Enterprise Linux 6 guest does not shut down when the <command>virsh shutdown</command> command is executed. The <command>virsh shutdown</command> command is designed to gracefully shut down virtualized guests.</para>
+ <para>Using <command>virsh shutdown</command> is easier amd safer for system administration. Without graceful shut down with the <command>virsh shutdown</command> command a system administrator must log into a virtualized guest manually or send the <keycap>Ctrl</keycap>-<keycap>Alt</keycap>-<keycap>Del</keycap> key combination to each guest.</para>
<note>
<title>Other virtualized operating systems</title>
- <para>Other virtualized guests may also be affected by this issue. The <command>virsh shutdown</command> command requires that the guest operating system is configured to handle ACPI shut down requests. Configure the guest to accept ACPI shut down requests for <command>virsh shutdown</command> to work effectively and properly.</para>
+ <para>Other virtualized operating systems may be affected by this issue. The <command>virsh shutdown</command> command requires that the guest operating system is configured to handle ACPI shut down requests. Many operating systems require additional configuration on the guest operating system to accept ACPI shut down requests.</para>
</note>
<procedure><title>Workaround for Red Hat Enteprise Linux 6</title>
<step>
<title>Install the acpid package</title>
- <para>To work around this issue, install the <package>acpid</package> package on the guest:</para>
+ <para>The <command>acpid</command> service listen and processes ACPI requests.</para>
+ <para>Log into the guest and install the <package>acpid</package> package on the guest:</para>
<screen># yum install acpid</screen>
</step>
<step>
@@ -526,7 +527,7 @@ exec gnome-session
# service acpid start</screen>
</step>
</procedure>
- <para>The guest is now configured to shut down when the host uses the <command>virsh shutdown</command> command.</para>
+ <para>The guest is now configured to shut down when the <command>virsh shutdown</command> command is used.</para>
</section>
<!--<section id="sect-Virtualization-Tips_and_tricks-Cloning_guest_configuration_files">
diff --git a/en-US/PCI.xml b/en-US/PCI.xml
index cfef288..bb8d8c9 100644
--- a/en-US/PCI.xml
+++ b/en-US/PCI.xml
@@ -31,10 +31,10 @@
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
-title Fedora Server (2.6.18-190.el5)
+title Red Hat Enterprise Linux Server (2.6.32-36.x86-64)
root (hd0,0)
- kernel /vmlinuz-2.6.18-190.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <emphasis>intel_iommu=on</emphasis>
- initrd /initrd-2.6.18-190.el5.img</screen>
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <emphasis>intel_iommu=on</emphasis>
+ initrd /initrd-2.6.32-36.x86-64.img</screen>
</step>
<step>
diff --git a/en-US/Reference_virsh.xml b/en-US/Reference_virsh.xml
index 7c724e5..e9b3c51 100644
--- a/en-US/Reference_virsh.xml
+++ b/en-US/Reference_virsh.xml
@@ -2,10 +2,12 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter id="chap-Virtualization-Managing_guests_with_virsh">
- <title>Managing guests with virsh</title>
-
+ <title>virsh reference guide</title>
+ <para>
+ This chapter provides a comprehensive reference for the <command>virsh</command> command provided by the <package>libvirt</package> package. This chapter covers various functions, parameters and provides examples of common tasks using the <command>virsh</command> command.<!--FIXME RHEL-->
+ </para>
<para>
- <command>virsh</command> is a command line interface tool for managing guests and the hypervisor.
+ <command>virsh</command> is a command line interface tool for managing virtualized guests and the hypervisor.
</para>
<para>
The <command>virsh</command> tool is built on the <command>libvirt</command> management API and operates as an alternative to the <command>xm</command> command and the graphical guest Manager (<command>virt-manager</command>). <command>virsh</command> can be used in read-only mode by unprivileged users. You can use <command>virsh</command> to execute scripts for the guest machines.
diff --git a/en-US/Reference_virt-manager.xml b/en-US/Reference_virt-manager.xml
index 993163a..7ed946a 100644
--- a/en-US/Reference_virt-manager.xml
+++ b/en-US/Reference_virt-manager.xml
@@ -2,9 +2,9 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter id="chap-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">
- <title>Managing guests with the Virtual Machine Manager (virt-manager)</title>
+ <title>virt-manager reference guide</title>
<para>
- This section describes the Virtual Machine Manager (<command>virt-manager</command>) windows, dialog boxes, and various GUI controls.
+ This chapter provides a comprehensive reference for the Virtual Machine Manager (<command>virt-manager</command>) package. This chapter covers dialog boxes, windows, and various graphical controls for libvirt on Fedora.<!--FIXME RHEL-->
</para>
<para>
<command>virt-manager</command> provides a graphical view of hypervisors and guest on your system and on remote machines. You can use <command>virt-manager</command> to define virtualized guests. <command>virt-manager</command> can perform virtualization management tasks, including:
diff --git a/en-US/Storage_Pools_iSCSI.xml b/en-US/Storage_Pools_iSCSI.xml
index 2b5e765..5191a21 100644
--- a/en-US/Storage_Pools_iSCSI.xml
+++ b/en-US/Storage_Pools_iSCSI.xml
@@ -12,7 +12,7 @@
<para>Fedora provides a tool for creating software backed iSCSI targets, the <package>scsi-target-utils</package> package.</para>
<procedure>
<title>Creating an iSCSI target</title>
-
+
<step>
<title>Install the required packages</title>
@@ -43,7 +43,9 @@
<step>
<title>Create a LVM logical volume</title>
<para>Create a logical volume group named <replaceable>virtimage1</replaceable> on the <replaceable>virtstore</replaceable> volume group with a size of 20GB using the <command>lvcreate</command> command.</para>
- <screen># lvcreate --size 20G -n <replaceable>virtimage1</replaceable> <replaceable>virtstore</replaceable></screen>
+ <screen># lvcreate --size 20G -n <replaceable>virtimage1</replaceable>
+ <replaceable>virtstore</replaceable>
+ </screen>
<para>The new logical volume, <replaceable>virtimage1</replaceable>, is ready to use for iSCSI.</para>
</step>
</substeps>
@@ -178,7 +180,7 @@ scsiadm: Max file limits 1024 1024
Logging in to [iface: default, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.0.1,3260]
Login to [iface: default, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.0.1,3260] successful.</screen>
-<para>Detach the device.</para>
+ <para>Detach the device.</para>
<screen># iscsiadm -d2 -m node --logout
scsiadm: Max file limits 1024 1024
@@ -192,9 +194,10 @@ Logout of [sid: 2, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.
<section>
<title>Adding an iSCSI target to virt-manager</title>
<para>This procedure covers creating a storage pool with an iSCSI target in <command>virt-manager</command>.</para>
- <!--reusable--><procedure>
+ <!--reusable-->
+ <procedure>
<title>Adding an iSCSI device to virt-manager</title>
- <step>
+ <step>
<title>Open the host storage tab</title>
<para>Open the <guilabel>Storage</guilabel> tab in the <guilabel>Host Details</guilabel> window.</para>
<substeps>
@@ -222,7 +225,7 @@ Logout of [sid: 2, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.
</step>
</substeps>
</step>
-
+
<step>
<title>Add a new pool (part 1)</title>
<para>
@@ -237,7 +240,7 @@ Logout of [sid: 2, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.
Choose a name for the storage pool, change the Type to iscsi, and press <guibutton>Forward</guibutton> to continue.
</para>
</step>
-
+
<step>
<title>Add a new pool (part 2)</title>
<para>
@@ -260,10 +263,139 @@ Logout of [sid: 2, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.
</step>
</procedure>
</section>
-
+
<section>
- <title>Adding an iSCSI target with virsh</title>
- <para>Placeholder</para>
+ <title>Creating an iSCSI-based storage pool with virsh</title>
+ <procedure>
+ <step>
+ <title>
+ Create the storage pool definition
+ </title>
+ <para>The example below is an XML definition file for a iSCSI-based storage pool.</para>
+ <variablelist>
+ <varlistentry>
+ <term><name>trial1</name></term>
+ <listitem>
+ <para>The <command>name</command> element sets the name for the storage pool. The name is required and must be unique.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><uuid>afcc5367-6770-e151-bcb3-847bc36c5e28</uuid>T</term>
+ <listitem>
+ <para>The optional <command>uuid</command> element provides a unique global identifier for the storage pool. The <command>uuid</command> element can contain any valid UUID or an existing UUID for the storage device. If a UUID is not provided, <command>virsh</command> will generate a UUID for the storage pool.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+
+ <term><host name='server1.example.com'/></term>
+ <listitem>
+ <para>The <command>host</command> element with the <parameter>name</parameter> attribute specifies the hostname of the iSCSI server. The <command>host</command> element attribute can contain a <parameter>port</parameter> attribute for a non-standard iSCSI protocol port number. </para>
+ </listitem>
+ </varlistentry>
+
+
+
+ <varlistentry>
+ <term><device path='<replaceable>iqn.2010-05.com.example.server1:trial1</replaceable>'/></term>
+ <listitem>
+ <para>
+ The <command>device</command> element <parameter>path</parameter> attribute must contain the IQN for the iSCSI server.</para>
+ </listitem>
+ </varlistentry>
+
+
+ </variablelist>
+ <para>With a text editor, create an XML file for the iSCSI storage pool. This example uses a XML definition named <filename>trial1.xml</filename>.</para>
+ <screen><pool type='iscsi'>
+ <name>trial1</name>
+ <uuid>afcc5367-6770-e151-bcb3-847bc36c5e28</uuid>
+ <source>
+ <host name='server1.example.com'/>
+ <device path='iqn.2010-05.com.example.server1:trial1'/>
+ </source>
+ <target>
+ <path>/dev/disk/by-path</path>
+ </target>
+</pool></screen>
+
+ <para>Use the <command>pool-define</command> command to define the storage pool but not start it.</para>
+<screen># virsh pool-define trial1.xml
+Pool trial1 defined
+</screen>
+ </step>
+ <step>
+ <title><emphasis role="bold">Alternative step:</emphasis> Use pool-define-as from command line</title>
+ <para>
+ Use the <command>virsh pool-define-as</command> command to define a new storage pool. There are two options required for creating directory-based storage pools:
+ </para>
+ <screen> # virsh pool-define-as <replaceable>trial1</replaceable> iscsi - - - - "<replaceable>/dev/disk/by-path</replaceable>"
+Pool trial1 defined</screen>
+ </step>
+ <step>
+ <title>Verify the storage pool is listed</title>
+ <para>
+ Verify the storage pool object is created correctly and the state reports as <computeroutput>inactive</computeroutput>.
+ </para>
+ <screen># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<replaceable>trial1</replaceable> inactive no </screen>
+
+
+ </step>
+
+ <step>
+ <title>Start the storage pool</title>
+ <para>
+ Use the virsh command <command>pool-start</command> for this. <command>pool-start</command> enables a directory storage pool, allowing it to be used for volumes and guests.
+ </para>
+ <screen># virsh pool-start <replaceable>guest_images_disk</replaceable>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<replaceable>trial1</replaceable> active no
+</screen>
+ </step>
+
+ <step>
+ <title>Turn on autostart</title>
+ <para>
+ Turn on <parameter>autostart</parameter> for the storage pool. Autostart configures the <systemitem class="daemon">libvirtd</systemitem> service to start the storage pool when the service starts.
+ </para>
+
+
+ <screen># virsh pool-autostart <replaceable>trial1</replaceable>
+Pool trial1 marked as autostarted</screen>
+ <para>Verify that the <replaceable>trial1</replaceable> pool has autostart set:</para>
+ <screen># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<replaceable>trial1</replaceable> active yes
+</screen>
+ </step>
+
+ <step>
+ <title>Verify the storage pool configuration</title>
+ <para>
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <computeroutput>running</computeroutput>.
+ </para>
+ <screen># virsh pool-info <replaceable>trial1</replaceable>
+Name: <replaceable>trial1</replaceable>
+UUID: afcc5367-6770-e151-bcb3-847bc36c5e28
+State: running
+Persistent: unknown
+Autostart: yes
+Capacity: 100.31 GB
+Allocation: 0.00
+Available: 100.31 GB
+</screen>
+ </step>
+ </procedure>
+ <para>An iSCSI-based storage pool is now available.</para>
</section>
</section>
diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml
index b85f553..58c75e3 100644
--- a/en-US/Troubleshooting.xml
+++ b/en-US/Troubleshooting.xml
@@ -214,11 +214,11 @@ topology-change-timer 0.00 gc-timer 0.02
To output kernel information from a fully virtualized Linux guest into the domain modify the <filename>/boot/grub/grub.conf</filename> file by inserting the line <parameter>console=tty0 console=ttys0,115200</parameter>.
</para>
- <screen>title Fedora Server (2.6.18-92.el5)
+ <screen>title Red Hat Enterprise Linux Server (2.6.32-36.x86-64)
root (hd0,0)
- kernel /vmlinuz-2.6.18-92.el5 ro root=/dev/volgroup00/logvol00
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/volgroup00/logvol00
<parameter>console=tty0 console=ttys0,115200</parameter>
- initrd /initrd-2.6.18-92.el5.img
+ initrd /initrd-2.6.32-36.x86-64.img
</screen>
<para>
Reboot the guest.
13 years, 9 months
r150 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-02 02:02:35 +0000 (Fri, 02 Jul 2010)
New Revision: 150
Modified:
community/trunk/en-US/Standards.xml
Log:
re-word
Modified: community/trunk/en-US/Standards.xml
===================================================================
--- community/trunk/en-US/Standards.xml 2010-07-01 23:16:43 UTC (rev 149)
+++ community/trunk/en-US/Standards.xml 2010-07-02 02:02:35 UTC (rev 150)
@@ -13,6 +13,14 @@
<itemizedlist>
<listitem>
<para>
+ <emphasis>FCC</emphasis> - Federal Communications Commission.
+ </para>
+ <para>
+ Regulates spectrum usage in the US. Also defines rules such as those for limitations of power output and maximum antenna height. More information can be found at the FCC homepage: <ulink url="http://www.fcc.gov/"></ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<emphasis>ITU-R</emphasis> - The Radio communications sector of the International Telecommunications Union.
</para>
<para>
@@ -21,6 +29,13 @@
</listitem>
<listitem>
<para>
+ <emphasis>ETSI</emphasis> - European Telecommunications Standards Institute.</para>
+ <para>
+ Produces communications standards including those for radio communications in Europe. More information can be found at the ETSI homepage: <ulink url="http://www.etsi.org/WebSite/AboutETSI/AboutEtsi.aspx"></ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<emphasis>Wi-Fi Alliance</emphasis> - A non-profit, worldwide association consisting of more than 300 member companies from more than 20 countries.
</para>
<para>
@@ -70,4 +85,4 @@
</itemizedlist>
</para>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
13 years, 9 months
r149 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 23:16:43 +0000 (Thu, 01 Jul 2010)
New Revision: 149
Modified:
community/trunk/en-US/Communication.xml
Log:
minor re-wording
Modified: community/trunk/en-US/Communication.xml
===================================================================
--- community/trunk/en-US/Communication.xml 2010-07-01 22:38:37 UTC (rev 148)
+++ community/trunk/en-US/Communication.xml 2010-07-01 23:16:43 UTC (rev 149)
@@ -25,7 +25,7 @@
<section id="sect-Wireless_Guide-Hardware-Received_Signal_Strength_Indicator">
<title>Received Signal Strength Indicator</title>
<para>
-This series of speeds used in Dynamic Rate Switching, and the current connected rate is usually intepreted in some sort of graphical form in your operating system as a graph or bar or other explanatory text. This is known as the <command>Received Signal Strength Indicator</command> (RSSI).
+The series of speeds used in Dynamic Rate Switching, and the current connected rate, are usually displayed in your operating system, perhaps as a graph or series of bars, or other explanatory text giving you an idea of your signal strength. This is known as the <command>Received Signal Strength Indicator</command> (RSSI). The RSSI can be very useful in determining signal strength, however there is no specification in the IEEE standards of how the RSSI should present its information, or even interpret the wireless information. Because of this, the RSSI tools can differ greatly between different operating systems. Any information presented to you by the RSSI should be evaluated with this point in mind.
</para>
</section>
<section id="sect-Wireless_Guide-Hardware-Connection_Modes">
13 years, 9 months
r148 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 22:38:37 +0000 (Thu, 01 Jul 2010)
New Revision: 148
Modified:
community/trunk/en-US/Fedora_Wireless.xml
community/trunk/en-US/Introduction.xml
community/trunk/en-US/Wireless_Guide.ent
Log:
PRODUCT is now Fedora Documentation
add new OS ent, search/replace &PRODUCT; with &OS;...
Modified: community/trunk/en-US/Fedora_Wireless.xml
===================================================================
--- community/trunk/en-US/Fedora_Wireless.xml 2010-07-01 05:51:34 UTC (rev 147)
+++ community/trunk/en-US/Fedora_Wireless.xml 2010-07-01 22:38:37 UTC (rev 148)
@@ -5,15 +5,15 @@
<chapter id="chap-Wireless_Guide-Fedora_And_Wireless">
<title>Fedora And Wireless</title>
<para>
- This chapter covers details specific to &PRODUCT; and the support for wireless hardware in the Linux kernel. Also included are instructions showing how to use the graphical and command-line interface (CLI) utilities when configuring a simple wireless connection.
+ This chapter covers details specific to &OS; and the support for wireless hardware in the Linux kernel. Also included are instructions showing how to use the graphical and command-line interface (CLI) utilities when configuring a simple wireless connection.
</para>
<section id="sect-Wireless_Guide-Fedora_And_Wireless-Hardware">
<title>Hardware</title>
<para>
- Before purchasing wireless hardware for &PRODUCT; it is a good idea to do some research first to make sure support for the hardware exists. The make and model of a particular client adapter may not be the most important factor when deciding on hardware; what is important in terms of Linux is which underlying <emphasis>chipset</emphasis> is used, as wireless hardware is rarely advertised based on its chipset.
+ Before purchasing wireless hardware for &OS; it is a good idea to do some research first to make sure support for the hardware exists. The make and model of a particular client adapter may not be the most important factor when deciding on hardware; what is important in terms of Linux is which underlying <emphasis>chipset</emphasis> is used, as wireless hardware is rarely advertised based on its chipset.
</para>
<para>
- The chipset is what the Linux driver usually recognises, and although the overall features are important (for instance 802.11g or 802.11n support, power output levels), the brand name is not always important to the &PRODUCT; infrastructure. For instance, a wireless card branded as a Netgear product might actually use an Atheros chipset for its internal mechanisms.
+ The chipset is what the Linux driver usually recognises, and although the overall features are important (for instance 802.11g or 802.11n support, power output levels), the brand name is not always important to the &OS; infrastructure. For instance, a wireless card branded as a Netgear product might actually use an Atheros chipset for its internal mechanisms.
</para>
</section>
<section id="sect-Wireless_Guide-Fedora_And_Wireless-Current_Status-Drivers_and_Chipsets">
@@ -25,7 +25,7 @@
<section id="sect-Wireless_Guide-Fedora_And_Wireless-Network_Manager">
<title>Using NetworkManager</title>
<para>
- This section demonstrates setting up a wireless connection in &PRODUCT; using NetworkManager. You can configure a wired or wireless connection with NetworkManager, and roaming between different connections is possible, as the service can choose the best available connection. NetworkManager will only work once the appropriate drivers for the underlying hardware are installed and configured properly. This section provides screenshots for configuring a simple wireless connection via the graphical interface provided by &PRODUCT;. This is an example only and demonstrates how simple wireless connections are configured in &PRODUCT; using NetworkManager.
+ This section demonstrates setting up a wireless connection in &OS; using NetworkManager. You can configure a wired or wireless connection with NetworkManager, and roaming between different connections is possible, as the service can choose the best available connection. NetworkManager will only work once the appropriate drivers for the underlying hardware are installed and configured properly. This section provides screenshots for configuring a simple wireless connection via the graphical interface provided by &OS;. This is an example only and demonstrates how simple wireless connections are configured in &OS; using NetworkManager.
</para>
<orderedlist>
<listitem>
@@ -97,12 +97,12 @@
</imageobject>
</mediaobject>
<para>
- Note the different type of <computeroutput>Wireless security</computeroutput> options in the images. This represents the different types of encryption that the network uses. &PRODUCT; will detect which type is in use and present the correct option for you to enter your network key.
+ Note the different type of <computeroutput>Wireless security</computeroutput> options in the images. This represents the different types of encryption that the network uses. &OS; will detect which type is in use and present the correct option for you to enter your network key.
</para>
</listitem>
<listitem>
<para>
- Enter your network key/password (WEP or WPA) into the available field and click <computeroutput>Connect</computeroutput>. If the access point is using DHCP and configured properly, &PRODUCT; will connect and network access should be functional.
+ Enter your network key/password (WEP or WPA) into the available field and click <computeroutput>Connect</computeroutput>. If the access point is using DHCP and configured properly, &OS; will connect and network access should be functional.
</para>
</listitem>
</orderedlist>
@@ -110,7 +110,7 @@
<section id="sect-Wireless_Guide-Fedora_And_Wireless-iwconfig">
<title>Using the command line interface</title>
<para>
- The following steps demonstrate how to configure a wireless connection in &PRODUCT; using the command-line interface (CLI) using the <command>iwconfig</command> command. This is an example only and demonstrates how simple wireless connections are configured in &PRODUCT; using the <command>iwconfig</command> command. Using NetworkManager is the recommended method to configure a wireless network, and knowing how to use <command>iwconfig</command> is usually not required.
+ The following steps demonstrate how to configure a wireless connection in &OS; using the command-line interface (CLI) using the <command>iwconfig</command> command. This is an example only and demonstrates how simple wireless connections are configured in &OS; using the <command>iwconfig</command> command. Using NetworkManager is the recommended method to configure a wireless network, and knowing how to use <command>iwconfig</command> is usually not required.
</para>
<orderedlist>
<listitem>
@@ -174,4 +174,4 @@
Tx excessive retries:0 Invalid misc:7 Missed beacon:12
</screen>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: community/trunk/en-US/Introduction.xml
===================================================================
--- community/trunk/en-US/Introduction.xml 2010-07-01 05:51:34 UTC (rev 147)
+++ community/trunk/en-US/Introduction.xml 2010-07-01 22:38:37 UTC (rev 148)
@@ -10,13 +10,13 @@
Not only has wireless data access achieved a great deal of market penetration in recent years, but the price of the related hardware has continued to drop, making it even more accessible. Wi-Fi seems to be everywhere; in laptops, desktops, PDAs, cell phones and routers, and there is such a large amount of wireless networks in many urban areas that complete overcrowding of the public wireless radio spectrum in use can occur.
</para>
<para>
- This guide provides a high-level overview of the past, present, and future of IEEE 802.11 wireless networking standards, communication concepts, hardware components, security concerns, and their relation to &PRODUCT; Linux. Although the specific wireless technology based on IEEE 802.11 is the primary focus of this guide, other mobile technologies and their relation to &PRODUCT; and Linux are also mentioned. Parts of this guide contain detailed information specific to &PRODUCT; and other Linux operating systems, however, many of the topics and concepts relate to all operating systems, vendors, and environments.
+ This guide provides a high-level overview of the past, present, and future of IEEE 802.11 wireless networking standards, communication concepts, hardware components, security concerns, and their relation to &OS; Linux. Although the specific wireless technology based on IEEE 802.11 is the primary focus of this guide, other mobile technologies and their relation to &OS; and Linux are also mentioned. Parts of this guide contain detailed information specific to &OS; and other Linux operating systems, however, many of the topics and concepts relate to all operating systems, vendors, and environments.
</para>
<section id="sect-Wireless_Guide-Introduction-Who_Should_Read_This_Guide">
<title>Who should read this guide?</title>
<para>
- You should read this guide if you are looking for an overview of wireless technologies and how they are implemented in &PRODUCT; or other Linux operating systems. Other readers will gain general information on how wireless works, the hardware involved, and other topics such as standards and security.
+ You should read this guide if you are looking for an overview of wireless technologies and how they are implemented in &OS; or other Linux operating systems. Other readers will gain general information on how wireless works, the hardware involved, and other topics such as standards and security.
</para>
</section>
<section id="sect-Wireless_Guide-Introduction-What_Is_A_Wireless_LAN">
@@ -55,7 +55,7 @@
<section id="sect-Wireless_Guide-Introduction-Linux_Support">
<title>Linux Wireless Support</title>
<para>
- Linux supports many wireless devices. Client adapters are typically available in PCI, PCI Express, Mini-PCI, USB, ExpressCard, Cardbus and PCMCIA form. Many of these adapters are supported by default in the Linux kernel via open source drivers available in &PRODUCT;. Your device is most likely supported; however, to find an overview of devices and drivers currently supported in Linux and &PRODUCT;, refer to the following URL at Linuxwireless.org: <ulink url="http://linuxwireless.org/en/users/Devices"></ulink>. Specific information on configuring and activating a WLAN in &PRODUCT; is discussed later.
+ Linux supports many wireless devices. Client adapters are typically available in PCI, PCI Express, Mini-PCI, USB, ExpressCard, Cardbus and PCMCIA form. Many of these adapters are supported by default in the Linux kernel via open source drivers available in &OS;. Your device is most likely supported; however, to find an overview of devices and drivers currently supported in Linux and &OS;, refer to the following URL at Linuxwireless.org: <ulink url="http://linuxwireless.org/en/users/Devices"></ulink>. Specific information on configuring and activating a WLAN in &OS; is discussed later.
</para>
</section>
<section id="sect-Wireless_Guide-Introduction-Disclaimer">
Modified: community/trunk/en-US/Wireless_Guide.ent
===================================================================
--- community/trunk/en-US/Wireless_Guide.ent 2010-07-01 05:51:34 UTC (rev 147)
+++ community/trunk/en-US/Wireless_Guide.ent 2010-07-01 22:38:37 UTC (rev 148)
@@ -1,4 +1,5 @@
-<!ENTITY PRODUCT "Fedora">
+<!ENTITY PRODUCT "Fedora Documentation">
+<!ENTITY OS "Fedora">
<!ENTITY PRODVER "13">
<!ENTITY BOOKID "wireless-guide">
<!ENTITY YEAR "2010">
13 years, 9 months
r244 - community/trunk/Managing_Confined_Services/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 05:56:16 +0000 (Thu, 01 Jul 2010)
New Revision: 244
Modified:
community/trunk/Managing_Confined_Services/en-US/Managing_Confined_Services.ent
Log:
fix ent
Modified: community/trunk/Managing_Confined_Services/en-US/Managing_Confined_Services.ent
===================================================================
--- community/trunk/Managing_Confined_Services/en-US/Managing_Confined_Services.ent 2010-06-16 16:14:36 UTC (rev 243)
+++ community/trunk/Managing_Confined_Services/en-US/Managing_Confined_Services.ent 2010-07-01 05:56:16 UTC (rev 244)
@@ -1,4 +1,4 @@
-<!ENTITY PRODUCT "Fedora Documentation">
+<!ENTITY PRODUCT "Fedora">
<!ENTITY BOOKID "selinux-managing-confined-services-guide">
<!ENTITY HOLDER "Red Hat, Inc">
<!ENTITY YEAR "2010">
13 years, 9 months
r147 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 05:51:34 +0000 (Thu, 01 Jul 2010)
New Revision: 147
Modified:
community/trunk/en-US/Wireless_Guide.ent
Log:
fix ent
Modified: community/trunk/en-US/Wireless_Guide.ent
===================================================================
--- community/trunk/en-US/Wireless_Guide.ent 2010-07-01 04:13:41 UTC (rev 146)
+++ community/trunk/en-US/Wireless_Guide.ent 2010-07-01 05:51:34 UTC (rev 147)
@@ -1,4 +1,4 @@
-<!ENTITY PRODUCT "Fedora Documentation">
+<!ENTITY PRODUCT "Fedora">
<!ENTITY PRODVER "13">
<!ENTITY BOOKID "wireless-guide">
<!ENTITY YEAR "2010">
13 years, 9 months
r146 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 04:13:41 +0000 (Thu, 01 Jul 2010)
New Revision: 146
Modified:
community/trunk/en-US/Communication.xml
Log:
Modified: community/trunk/en-US/Communication.xml
===================================================================
--- community/trunk/en-US/Communication.xml 2010-07-01 01:38:18 UTC (rev 145)
+++ community/trunk/en-US/Communication.xml 2010-07-01 04:13:41 UTC (rev 146)
@@ -4,23 +4,30 @@
<chapter id="chap-Wireless_Guide-Communication">
<title>Wireless Communication</title>
- <para>
- stuff
- </para>
<section id="sect-Wireless_Guide-Hardware-Data_Rates_and_Throughput">
<title>Data Rates and Throughput</title>
<para>
- Several metrics and measurements are used to define elements of wireless LANs. Some of these include terms to define data rate, throughput, signal to noise ratio, antenna gain, signal loss and encryption strength. One commonly misunderstood set of measurements is <emphasis>data rate</emphasis> and <emphasis>throughput</emphasis>. To use the IEEE 802.11g standard as an example, it is often referred to and marketed as having a 54Mbps (megabits/s) connection speed. This is however only a theoretical maximum speed under perfect conditions defined in the standard. Unfortunately, the real world is not a perfect environment, and in some cases can be outright hostile to facilitating wireless communication.
+ Several metrics and measurements are used to define elements of a WLAN, such as data rate, throughput, signal to noise ratio (SNR), antenna gain, signal loss and encryption strength. One commonly misunderstood concept is the relationship between <emphasis>data rate</emphasis> and <emphasis>throughput</emphasis>.
</para>
<para>
- Continuing to use the IEEE 802.11g standard to define these terms, the standard is actually capable of negotiating its connection with other devices at several different <emphasis>data rates</emphasis>. This ability to change data rates is known as <command>Dynamic Rate Switching</command>, and a properly functioning card will negotiate the best possible speed depending on the distance from the Access Point, the amount and type of other devices that are connecting, and overall environmental conditions.
+ To use the IEEE 802.11g standard as an example, which is often referred to and marketed as having a 54Mbps (megabits/s) connection speed, this is only a theoretical maximum speed under perfect conditions defined in the standard. Unfortunately, the real world is not a perfect environment, and in some cases can be outright hostile to facilitating wireless communication.
</para>
- <para>The IEEE 802.11g standard can operate under the following data rates: 6, 9, 12, 18, 24, 36, 48 and 54 Mbps, and can use 802.11b speeds if in a mixed-mode environment. This series of speeds, and the current connected rate is usually intepreted in a graphical form in your operating system as a graph or bar or other text, representing signal strength (this is known as the <command>Received Signal Strength Indicator</command>). So, while the standard defines 54Mbps as the maximum speed, the data rate is actually negotiating one of the above speeds based on environmental conditions. This data rate is related to, but different from the <emphasis>actual amount</emphasis> of network data coming through the connection at any given time. This actual data transfer speed is known as <emphasis>throughput</emphasis>.
+ <para>
+ The full 54Mbps throughput as defined in the standard never be achieved in the real world. Your actual throughput of network data is typically 15% to 40% of this marketed level. <emphasis>Data rate</emphasis> is the negotiated, variable, maximum possible link to other devices, and <emphasis>throughput</emphasis> is the real-world, measured amount of actual data flow.
</para>
+</section>
+<section id="sect-Wireless_Guide-Hardware-Dynamic_Rate_Switching">
+<title>Dynamic Rate Switching</title>
<para>
- As mentioned, the full 54Mbps throughput as defined in the standard can never be achieved in the real world. Your actual throughput of network data is typically 15-40% of this maximum level. <emphasis>Data rate</emphasis> is the negotiated, variable, maximum possible link to other devices, and <emphasis>throughput</emphasis> is the real-world speed of actual data flow.
+ Continuing to use the IEEE 802.11g standard to define these terms, a wireless client is capable of negotiating its connection with other devices at several different <emphasis>data rates</emphasis>. This ability to change data rates is known as <command>Dynamic Rate Switching</command>, and a properly functioning client will be able to negotiate the best possible, theoretical speed depending on the distance from the Access Point, the amount and type of other devices that are connecting, and overall environmental conditions. The IEEE 802.11g standard can operate under the following data rates: 6, 9, 12, 18, 24, 36, 48 and 54 Mbps, and can use 802.11b data rates if in a mixed-mode environment.
</para>
</section>
+<section id="sect-Wireless_Guide-Hardware-Received_Signal_Strength_Indicator">
+<title>Received Signal Strength Indicator</title>
+ <para>
+This series of speeds used in Dynamic Rate Switching, and the current connected rate is usually intepreted in some sort of graphical form in your operating system as a graph or bar or other explanatory text. This is known as the <command>Received Signal Strength Indicator</command> (RSSI).
+ </para>
+</section>
<section id="sect-Wireless_Guide-Hardware-Connection_Modes">
<title>Connection Modes</title>
<para>
13 years, 9 months
r145 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 01:38:18 +0000 (Thu, 01 Jul 2010)
New Revision: 145
Modified:
community/trunk/en-US/Introduction.xml
Log:
Modified: community/trunk/en-US/Introduction.xml
===================================================================
--- community/trunk/en-US/Introduction.xml 2010-07-01 00:17:40 UTC (rev 144)
+++ community/trunk/en-US/Introduction.xml 2010-07-01 01:38:18 UTC (rev 145)
@@ -7,10 +7,10 @@
<para>
Due to increased demand for convenient networking and more flexible access to both the Internet and company resources via more geographically widespread coverage areas, wireless networking use has increased dramatically in recent years. Mobile access to data services previously unavailable is now common. The sales and penetration of wireless access have resulted in a recent projection by <ulink url="http://www.abiresearch.com/">ABI Research</ulink> that one billion Wi-Fi chipsets <ulink url="http://www.abiresearch.com/press/1474-One+Billion+Wi-Fi+Chipsets+to+Ship+...">will ship in the year 2011</ulink>.</para>
<para>
- Not only has wireless data access achieved a great deal of market penetration in recent years, but the price of the related hardware has dropped dramatically, making it even more accessible. Wi-Fi seems to be everywhere; in laptops, desktops, PDAs, cell phones and routers, and there is such a large amount of wireless networks in many urban areas that complete overcrowding of the public wireless radio spectrum in use can occur.
+ Not only has wireless data access achieved a great deal of market penetration in recent years, but the price of the related hardware has continued to drop, making it even more accessible. Wi-Fi seems to be everywhere; in laptops, desktops, PDAs, cell phones and routers, and there is such a large amount of wireless networks in many urban areas that complete overcrowding of the public wireless radio spectrum in use can occur.
</para>
<para>
- This guide provides a high-level overview of the past, present, and future of IEEE 802.11 wireless networking standards, concepts, hardware components, security concerns, and their relation to &PRODUCT; Linux. Although the specific wireless technology based on IEEE 802.11 is the primary focus of this guide, other mobile technologies and their relation to &PRODUCT; and Linux are also mentioned. Parts of this guide contain detailed information specific to &PRODUCT; and other Linux operating systems, however, many of the topics and concepts relate to all operating systems, vendors, and environments.
+ This guide provides a high-level overview of the past, present, and future of IEEE 802.11 wireless networking standards, communication concepts, hardware components, security concerns, and their relation to &PRODUCT; Linux. Although the specific wireless technology based on IEEE 802.11 is the primary focus of this guide, other mobile technologies and their relation to &PRODUCT; and Linux are also mentioned. Parts of this guide contain detailed information specific to &PRODUCT; and other Linux operating systems, however, many of the topics and concepts relate to all operating systems, vendors, and environments.
</para>
<section id="sect-Wireless_Guide-Introduction-Who_Should_Read_This_Guide">
@@ -25,7 +25,7 @@
A wireless LAN (referred to as WLAN in this guide) is a wireless local area network that allows computers or other devices to communicate via radio frequency (RF) technology. It affords the user mobility to move around and stay connected to the network without using physical cables such as in a traditional Ethernet system.
</para>
<para>
- The IEEE (Institute of Electrical and Electronics Engineers) is a non-profit, global organization which implemented and continually develops a set of standards for wireless communication. This family of standards is known as IEEE 802.11 and consists of the actual standards and protocols defining how computers communicate via a WLAN. Standards are discussed in more detail later. Although wireless networks are commonly referred to as Wi-Fi, this is only a marketing term chosen by the Wireless Ethernet Compatibility Alliance (now known as the Wi-Fi Alliance). When referring to Wi-Fi, the underlying technology is typically a WLAN or device operating within the standards of the IEEE within the 802.11 family.
+ The IEEE (Institute of Electrical and Electronics Engineers) is a non-profit, global organization which implemented and continually develops a set of standards for wireless communication. This family of standards is known as IEEE 802.11 and consists of the actual standards and protocols defining how computers communicate via a WLAN. Standards are discussed in more detail later. Although wireless networks are commonly referred to as Wi-Fi, this is only a marketing term chosen by the Wi-Fi Alliance. When referring to Wi-Fi, the underlying technology is typically a WLAN or device operating within the standards of the IEEE 802.11 family.
</para>
</section>
<section id="sect-Wireless_Guide-Introduction-History_Of_Wireless_LANs">
13 years, 9 months
r144 - community/trunk/en-US
by sradvan
Author: sradvan
Date: 2010-07-01 00:17:40 +0000 (Thu, 01 Jul 2010)
New Revision: 144
Modified:
community/trunk/en-US/Book_Info.xml
community/trunk/en-US/Communication.xml
community/trunk/en-US/Hardware.xml
community/trunk/en-US/Introduction.xml
community/trunk/en-US/Revision_History.xml
Log:
bump, review
Modified: community/trunk/en-US/Book_Info.xml
===================================================================
--- community/trunk/en-US/Book_Info.xml 2010-06-30 23:27:45 UTC (rev 143)
+++ community/trunk/en-US/Book_Info.xml 2010-07-01 00:17:40 UTC (rev 144)
@@ -7,8 +7,8 @@
<subtitle>Wireless and mobile networking overview for Fedora Linux</subtitle>
<productname>Fedora</productname>
<productnumber>13</productnumber>
- <edition>1.3</edition>
- <pubsnumber>1</pubsnumber>
+ <edition>1.4</edition>
+ <pubsnumber>0</pubsnumber>
<abstract>
<para>An overview of IEEE 802.11-based and other mobile networking technologies and their implementation in Fedora Linux.</para>
</abstract>
Modified: community/trunk/en-US/Communication.xml
===================================================================
--- community/trunk/en-US/Communication.xml 2010-06-30 23:27:45 UTC (rev 143)
+++ community/trunk/en-US/Communication.xml 2010-07-01 00:17:40 UTC (rev 144)
@@ -7,6 +7,20 @@
<para>
stuff
</para>
+<section id="sect-Wireless_Guide-Hardware-Data_Rates_and_Throughput">
+<title>Data Rates and Throughput</title>
+ <para>
+ Several metrics and measurements are used to define elements of wireless LANs. Some of these include terms to define data rate, throughput, signal to noise ratio, antenna gain, signal loss and encryption strength. One commonly misunderstood set of measurements is <emphasis>data rate</emphasis> and <emphasis>throughput</emphasis>. To use the IEEE 802.11g standard as an example, it is often referred to and marketed as having a 54Mbps (megabits/s) connection speed. This is however only a theoretical maximum speed under perfect conditions defined in the standard. Unfortunately, the real world is not a perfect environment, and in some cases can be outright hostile to facilitating wireless communication.
+ </para>
+ <para>
+ Continuing to use the IEEE 802.11g standard to define these terms, the standard is actually capable of negotiating its connection with other devices at several different <emphasis>data rates</emphasis>. This ability to change data rates is known as <command>Dynamic Rate Switching</command>, and a properly functioning card will negotiate the best possible speed depending on the distance from the Access Point, the amount and type of other devices that are connecting, and overall environmental conditions.
+ </para>
+ <para>The IEEE 802.11g standard can operate under the following data rates: 6, 9, 12, 18, 24, 36, 48 and 54 Mbps, and can use 802.11b speeds if in a mixed-mode environment. This series of speeds, and the current connected rate is usually intepreted in a graphical form in your operating system as a graph or bar or other text, representing signal strength (this is known as the <command>Received Signal Strength Indicator</command>). So, while the standard defines 54Mbps as the maximum speed, the data rate is actually negotiating one of the above speeds based on environmental conditions. This data rate is related to, but different from the <emphasis>actual amount</emphasis> of network data coming through the connection at any given time. This actual data transfer speed is known as <emphasis>throughput</emphasis>.
+ </para>
+ <para>
+ As mentioned, the full 54Mbps throughput as defined in the standard can never be achieved in the real world. Your actual throughput of network data is typically 15-40% of this maximum level. <emphasis>Data rate</emphasis> is the negotiated, variable, maximum possible link to other devices, and <emphasis>throughput</emphasis> is the real-world speed of actual data flow.
+ </para>
+</section>
<section id="sect-Wireless_Guide-Hardware-Connection_Modes">
<title>Connection Modes</title>
<para>
Modified: community/trunk/en-US/Hardware.xml
===================================================================
--- community/trunk/en-US/Hardware.xml 2010-06-30 23:27:45 UTC (rev 143)
+++ community/trunk/en-US/Hardware.xml 2010-07-01 00:17:40 UTC (rev 144)
@@ -81,7 +81,7 @@
</listitem>
<listitem>
<para>
- Semidirectional - <emphasis>Semidirectional antennas</emphasis> are designed to provide specific, directed signal coverage over large areas. An example of a semidirectional antenna is a <emphasis>Yagi antenna</emphasis>.
+ Semidirectional - <emphasis>Semidirectional antennas</emphasis> are designed to provide specific, directed signal coverage over large areas. Examples of a semidirectional antenna are <emphasis>Yagi</emphasis> or <emphasis>patch</emphasis>.
</para>
</listitem>
<listitem>
Modified: community/trunk/en-US/Introduction.xml
===================================================================
--- community/trunk/en-US/Introduction.xml 2010-06-30 23:27:45 UTC (rev 143)
+++ community/trunk/en-US/Introduction.xml 2010-07-01 00:17:40 UTC (rev 144)
@@ -5,7 +5,7 @@
<chapter id="chap-Wireless_Guide-Introduction">
<title>Introduction</title>
<para>
- Due to increased demand for convenient networking and more flexible access to both the Internet and company resources via more geographically widespread coverage areas, wireless networking use has flourished in recent years. Mobile access to data services previously unavailable is now common. The sales and penetration of wireless access have resulted in a recent projection by <ulink url="http://www.abiresearch.com/">ABI Research</ulink> that one billion Wi-Fi chipsets <ulink url="http://www.infoworld.com/d/networking/one-billion-wi-fi-chipsets-in-2011-216">will ship in the year 2011</ulink>.</para>
+ Due to increased demand for convenient networking and more flexible access to both the Internet and company resources via more geographically widespread coverage areas, wireless networking use has increased dramatically in recent years. Mobile access to data services previously unavailable is now common. The sales and penetration of wireless access have resulted in a recent projection by <ulink url="http://www.abiresearch.com/">ABI Research</ulink> that one billion Wi-Fi chipsets <ulink url="http://www.abiresearch.com/press/1474-One+Billion+Wi-Fi+Chipsets+to+Ship+...">will ship in the year 2011</ulink>.</para>
<para>
Not only has wireless data access achieved a great deal of market penetration in recent years, but the price of the related hardware has dropped dramatically, making it even more accessible. Wi-Fi seems to be everywhere; in laptops, desktops, PDAs, cell phones and routers, and there is such a large amount of wireless networks in many urban areas that complete overcrowding of the public wireless radio spectrum in use can occur.
</para>
Modified: community/trunk/en-US/Revision_History.xml
===================================================================
--- community/trunk/en-US/Revision_History.xml 2010-06-30 23:27:45 UTC (rev 143)
+++ community/trunk/en-US/Revision_History.xml 2010-07-01 00:17:40 UTC (rev 144)
@@ -34,7 +34,7 @@
</simplelist>
</revdescription>
</revision>
-<revision>
+ <revision>
<revnumber>1.2</revnumber>
<date>6 Jan 2010</date>
<author>
@@ -48,7 +48,7 @@
</simplelist>
</revdescription>
</revision>
-<revision>
+ <revision>
<revnumber>1.3</revnumber>
<date>1 Mar 2010</date>
<author>
@@ -62,6 +62,20 @@
</simplelist>
</revdescription>
</revision>
+ <revision>
+ <revnumber>1.4</revnumber>
+ <date>1 Jul 2010</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Radvan</surname>
+ <email>sradvan(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Add rate switching, difference between data rate and throughput.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
</revhistory>
</simpara>
</appendix>
13 years, 9 months