compress text to fit into 80char wide terminals

1 files changed, 115 insertions, 69 deletions

diff --git a/doc/official_installation_guide_en b/doc/official_installation_guide_en
index 44a3a5f..2217860 100644
--- a/doc/official_installation_guide_en
+++ b/doc/official_installation_guide_en
@@ -7,11 +7,13 @@ General installation documentation for the Arch Linux distribution.
 This guide is only valid for release 2009.08 or newer.
 
 This guide is maintained in [aif git](http://projects.archlinux.org/?p=aif.git)  
-Patches/comments are welcome on the [arch-releng mailing list](http://www.archlinux.org/mailman/listinfo/arch-releng) or mail to dieter@archlinux.org
+Patches/comments are welcome on the arch
+[releng mailing list](http://www.archlinux.org/mailman/listinfo/arch-releng)
+or mail to dieter@archlinux.org
 
 **Related articles**
 
-[Beginners Guide](http://wiki.archlinux.org/index.php/Beginners_Guide "Beginners Guide") (If you are new to Arch)
+[Beginners Guide](http://wiki.archlinux.org/index.php/Beginners_Guide) (If you are new to Arch)
 
 ## Contents
 
@@ -93,11 +95,14 @@ Arch Linux, you should decide which installation method you would like to use.
 Arch Linux provides bootable images for:
 
 * CD-rom drives ( ISO format): works on almost any machine with a CD-ROM drive
-* USB disk images (raw format): works on any system capable of booting from a usb drive.
+* USB disk images (raw format): works on any system capable of booting
+  from a usb drive.
 
-The GRUB bootloader is used, but for those having problems with GRUB not loading
-with certain CD-rom drives, ISO images with the ISOLINUX bootloader are offered as well.
-There are two variants of each installation medium which only differ in terms of supplied packages.
+The GRUB bootloader is used, but for those having problems with GRUB
+not loading with certain CD-rom drives, ISO images with the ISOLINUX
+bootloader are offered as well.  
+There are two variants of each installation medium which only differ
+in terms of supplied packages.
 
   * The "core" images contain a snapshot of the core packages. These images
 are best suited for people who have an internet connection which is slow or
@@ -109,10 +114,11 @@ to-date system and they are best suited for people with fast internet
 connections.
 
 You can instruct the installer to obtain the packages via the internet (or
-any network) using either of these images, and all images can also be used as fully functioning recovery
-environments. The images run like any regular installed Arch Linux system. In
-fact, they're exactly the same, just installed to a CD or USB image instead of
-a hard disk. They include the entire "base" package set, as well as various
+any network) using either of these images, and all images can also be used as
+fully functioning recovery environments.  
+The images run like any regular installed Arch Linux system.  
+In fact, they're exactly the same, just installed to a CD or USB image instead
+of a hard disk. They include the entire "base" package set, as well as various
 networking utilities and drivers and have the aif package installed.
 If there's something else you happen to need
 at runtime, just get your Internet connection up and install it using pacman.
@@ -120,27 +126,39 @@ A short pacman command reference is available at the end of this document.
 
 ### AIF, the installation tool
 
-Arch Linux uses AIF aka 'Arch Linux Installation Framework' to perform installations.
-This tool - written in bash - consists of some libraries to perform various functions (installing packages, setting up disks etc)
-and some so called procedures which use these libraries to provide an easy means
-to do an installation or to smaller related tasks ('partial procedures').
+Arch Linux uses AIF aka 'Arch Linux Installation Framework' to perform
+installations.
+This tool - written in bash - consists of some libraries to perform various
+functions (installing packages, setting up disks etc) and some so called
+procedures which use these libraries to provide an easy means to do
+an installation or to smaller related tasks ('partial procedures').
 These procedures are shipped by default:
 
-* interactive: An interactive installation procedure, which asks you some questions, guides you through an installation
-               and helps you configuring the target system by automatically changing some settings for you depending on what you did earlier (eg network settings)
-               The installed system will initially have only a customisable set of "base" packages installed with whatever utilities
-               and drivers you need to get online. Then once you've successfully booted the installed system,
-               you'll run a full system upgrade and install any other packages you want.
+* interactive: An interactive installation procedure, which asks you some
+               questions, guides you through an installation and helps you
+               configuring the target system by automatically changing some
+               settings for you depending on what you did earlier
+               (eg network settings)
+               The installed system will initially have only a customisable
+               set of "base" packages installed with whatever utilities
+               and drivers you need to get online.  Then once you've
+               successfully booted the installed system, you'll run a full
+               system upgrade and install any other packages you want.
                (aliased as `/arch/setup`)
-* automatic:   An automated, deploy-tool-alike procedure.  designed for low-to zero interactivity.
-               uses profiles for configuration of the installation/target system.
+* automatic:   An automated, deploy-tool-alike procedure  designed for
+               low-to zero interactivity.
+               uses profiles for configuration of the target system.
                See /usr/share/aif/examples/ for example profile files.
                The examples implement quite generic scenarios but you're
                free to change them how you like to install extra packages,
                do configuration tweaks, etc.
-* base:        basic, little-interactivity installation with some common defaults.
-               This procedure is used by the others to inherit from, it is NOT meant to be used directly by end users
-* partial-configure-network: exposes the network configuration step from the interactive procedure, to help you setup the network in the live environment
+* base:        basic, little-interactivity installation with some
+               common defaults.
+               This procedure is used by the others to inherit from,
+               it is NOT meant to be used directly by end users
+* partial-configure-network: exposes the network configuration step from
+                             the interactive procedure, to help you setup
+                             the network in the live environment
 * partial-disks: Process disk subsystem or do a rollback
 * partial-keymap: change your keymap/console font settings. (aliased as `km`)
 
@@ -151,9 +169,10 @@ if you want to apply your settings to the config files of the target system.
 
 If you want to go further, you can also:
 
-* write your own procedures from scratch or by overriding certain parts of other procedures
-* write your own libraries, to provide reusable logic that does not come by default
-* for certain procedures that use config files (eg automatic), create your own configs
+* write your own procedures from scratch or by overriding certain parts of
+  other procedures
+* write your own libraries, to provide new, reusable functionality
+* create your own configs for the procedures that support them (eg automatic)
 
 For more information, consult the readme of AIF.
 
@@ -220,33 +239,44 @@ files on it before doing this.
 
 Make sure your BIOS is set in a way to allow booting from your CD-ROM or USB
 device. Reboot your computer with the Arch Linux Installation CD in the drive
-or the USB stick plugged in the port. Once the installation medium has
-started booting you will see the Arch Linux logo and a grub menu waiting for your selection.
+or the USB stick plugged in the port. Once the installation medium has started
+booting you will see the Arch Linux logo and a grub menu waiting for your
+selection.  
 Most likely you can just hit enter at this point.
-If Grub hangs, you're one of the unlucky few whose CD-rom drive doesn't work with grub and you should try the isolinux image.
+If Grub hangs, you're one of the unlucky few whose CD-rom drive doesn't work
+with grub and you should try the isolinux image.
 
 #### Post-boot
-At the end of the boot procedure, you should be at a login prompt with some simple instructions at
-the top of the screen. You should login as root. At this point you can
+At the end of the boot procedure, you should be at a login prompt with some
+simple instructions at the top of the screen.
+You should login as root. At this point you can
 optionally perform manual preparations and commence the actual installation
 
-* If you prefer a non-US keymap or specific consolefont, type `km` to change any of these.
-* If for some reason you need network access before starting the installer (the interactive procedure will let you configure the network if you want to do a NET installation)
+* If you prefer a non-US keymap or specific consolefont, type `km` to change
+  any of these.
+* If for some reason you need network access before starting the installer
+  (the interactive procedure lets you configure the network for NET
+  installations)
   you can type `aif -p partial-configure-network`
 
-For both items, changed settings will be remembered to be optionally applied to the target system when using the interactive procedure.
+For both items, changed settings will be remembered to be optionally applied
+to the target system when using the interactive procedure.
 
-There is also an `arch` login which can be usefull if you want to do things as non-privileged user.  Most people don't need this.
+There is also an `arch` login which can be usefull if you want to do things
+as non-privileged user.  Most people don't need this.
 
-You will find that everything you need to perform this installation (a copy of this guide, aif README, shortcuts to common aif procedures) can be found in /arch
+You will find that everything you need to perform this installation
+(a copy of this guide, aif README, shortcuts to common aif procedures)
+can be found in /arch
 
 ### Performing the installation
 You can either use the interactive procedure or the automatic one.  See
-section [2.3 AIF, the installation tool](#Aif_the_installation_tool) or the AIF readme for more info.
+section [2.3 AIF, the installation tool](#Aif_the_installation_tool) or
+the AIF readme for more info.
 
 #### Interactive Installation Procedure
 
-Type `/arch/setup` (or `aif -p interactive`, which is the same) to get you started.
+Type `/arch/setup` (or `aif -p interactive`, which is the same) to start.
 
 After the welcome message and disclaimer you will be presented with the main
 installation menu. You can use UP and DOWN arrow to navigate menus. Use TAB to
@@ -315,8 +345,9 @@ Menu.
 
 Set Clock will allow you to set up your system clock and date. 
 First you have to say if your hardwareclock is (or should be) in UTC or
-localtime.  UTC is preferred, but if you have an OS installed which cannot handle UTC BIOS times
-correctly, like Windows, you'll have to choose localtime.
+localtime.
+UTC is preferred, but if you have an OS installed which cannot handle UTC
+BIOS times correctly -like Windows- you'll have to choose localtime.
 Next the setup will want you to select your continent/country (timezone),
 and allow you to set the date and time (for which you can also use
 [NTP](http://www.ntp.org/) if your network is up)
@@ -327,9 +358,10 @@ Prepare Hard Drive will lead you into a submenu offering two alternatives of
 preparing your target drive(s) for installation, and a means to undo changes if
 you want to retry.
 
-* Auto-prepare will automatically partition (and fully overwrite) one disk of your choice.
+* Auto-prepare will automatically partition (and fully overwrite) one disk
+  of your choice.
   It creates a simple layout with a /boot, swap, / and /home partition where
-  you have some control over the used filesystems and sizes thereof where relevant.
+  you have some control over the used filesystems and sizes thereof.
 * If you wish/need more control you can manually partition one or more hard
   disks and then manually specify a complete setup using the partitions on your
   disks.  You can also use things such as lvm and dm_crypt here.
@@ -342,9 +374,9 @@ you want to retry.
 ######  Auto-Prepare
 
 Auto-Prepare will automatically partition a hard drive of your choice
-into a /boot, swap, a root partition, and a /home and then create filesystems on all four. These partitions will also be
-automatically mounted in the proper place. To be exact, this option will
-create:
+into a /boot, swap, a root partition, and a /home and then create filesystems
+on all four. These partitions will also be automatically mounted
+in the proper place. To be exact, this option will create:
 
   * 32 MB ext2 /boot partition
   * 256 MB swap partition
@@ -370,11 +402,15 @@ In this menu all recognized partitions are listed.  On top of these you can
 create new filesystems.
 You should be aware of three things:
 
-* All of this is just a model, and everything will only be set up after you confirmed it.
-* Not all blockdevices support all filesystems (Eg you cannot put an LVM volumegroup on something other then a LVM physical volume).
-  The installer will automatically filter the list of possible filesystems and even select the one automatically for you if there's only one option.
-* Some filesystems will cause new blockdevices to be created.  This is the case for dm_crypt and lvm volumes.
-  You will see them appear in the model and you can use them to put another filesystem on top of it.
+* All of this is just a model, everything will only be set up after you confirm.
+* Not all blockdevices support all filesystems (Eg you cannot put an LVM
+  volumegroup on something other then a LVM physical volume).
+  The installer will automatically filter the list of possible filesystems
+  and even select the one automatically for you if there's only one option.
+* Some filesystems will cause new blockdevices to be created.
+  This is the case for dm_crypt and lvm volumes.
+  You will see them appear in the model and you can use them to put another
+  filesystem on top of it.
 
 Once you've setup some filesystems, you can select 'Done'.  At this point a
 check will be run which will tell you any critical errors (such as no root
@@ -425,17 +461,20 @@ selected with resolved dependencies onto your harddisk.
 
 Configure System does multiple things:
 
-* automatically preseed some configuration files (eg grub's menu.lst, mkinitcpio.conf's HOOKS, keymap settings in rc.conf, pacman mirror etc)
-* preseed some configuration files after your confirmation (eg network settings)
-* allow you to manually change important configuration files for your target system.
-  You will be asked which editor you want to use.  You have the choice between nano, joe and vi
+* automatically preseed some configuration files (eg grub's menu.lst,
+  mkinitcpio.conf's HOOKS, keymap settings in rc.conf, pacman mirror etc)
+* preseed some configuration files after you agreed. (eg network settings)
+* allow you to manually change important config files for your target system.
+  You'll be asked which text editor you want to use.
+  You have the choice between nano, joe and vi
 * allow you to set the root password for the target.
 
 **Configuration Files**
 
 These are the core configuration files for Arch Linux.
-If you need help configuring a specific service, please read the appropriate manpage or refer to any online
-documentation you need. In many cases, the Arch Linux [Wiki][46] and
+If you need help configuring a specific service, please read the appropriate
+manpage or refer to any online documentation you need.
+In many cases, the Arch Linux [Wiki][46] and
 [forums][47] are a rich source for help as well.
 
    [46]: http://wiki.archlinux.org/ (http://wiki.archlinux.org/)
@@ -579,10 +618,11 @@ on by udev, during the init process.
 
 By default, mkinitcpio.conf is configured to autodetect all needed modules for
 IDE, SCSI, or SATA systems through so-called HOOKS. The installed should
-also have inserted hooks like crypt, lvm, keymap and usbinput if relevant. This means the default
-initrd should work for almost everybody. You can edit mkinitcpio.conf and
-remove the subsystem HOOKS (ie, IDE, SCSI, RAID, USB, etc) that you don't
-need. You can customize even further by specifying the exact modules you need
+also have inserted hooks like crypt, lvm, keymap and usbinput if relevant.
+This means the default initrd should work for almost everybody.
+You can edit mkinitcpio.conf and remove the subsystem HOOKS
+(ie, IDE, SCSI, RAID, USB, etc) that you don't need.
+You can customize even further by specifying the exact modules you need
 in the MODULES array and remove even more of the hooks, but proceed with
 caution.
 
@@ -736,19 +776,24 @@ reboot at the command line and cross your fingers!
 #### Automatic Installation Procedure
 
 With the automatic installation procedure, you can do scripted/automatic
-installations.  See [2.3 AIF, the installation tool](#Aif_the_installation_tool)
+installations.
+See [2.3 AIF, the installation tool](#Aif_the_installation_tool)
 In /usr/share/aif/examples you will find example profiles which will need
 no or minimal editing in order to install a system:
 
 * generic-install-on-sda
-  this file demonstrates some things you can do (adding custom packages, setting timezone, update config files etc)
-  it sets up a simple installation (with a structure like what you get with Auto-prepare) on /dev/sda
+  this file demonstrates some things you can do (adding custom packages,
+  setting timezone, update config files etc)
+  it sets up a simple installation (with a structure similar to what you get
+   with Auto-prepare) on /dev/sda
 * fancy-install-on-sda
-  very similar to generic-install-on-sda, but sets up a "filesystems on lvm on dm_crypt" system on /dev/sda
+  very similar to generic-install-on-sda,
+  but sets up a "filesystems on lvm on dm_crypt" system on /dev/sda
 
 
 Invoke as `aif -p automatic -c /path/to/configfile`
-Obviously, don't forget to change the hard disk names unless you want to use /dev/sda.
+Obviously, don't forget to change the hard disk names unless you want
+to use /dev/sda.
 
 
 #### Customizing Installations
@@ -762,11 +807,12 @@ This is a moving target, so consult the AIF readme for more information.
 
 
 ## Your new system
-If all went well, you can reboot your system (make sure you don't boot again from the same USB disk or CD-ROM drive)
-and your new system will boot.
+If all went well, you can reboot your system (make sure you don't boot again
+from the same USB disk or CD-ROM drive) and your new system will boot.
 
 You'll notice that in the early userspace (the part that comes after the
-bootloader) the hooks (as defined in mkinitcpio.conf) needed to get your root filesystem are run.
+bootloader) the hooks (as defined in mkinitcpio.conf) needed to get your root
+filesystem are run.  
 If you have lvm, it will run the lvm hook.  If you use encryption, it will
 the keymap and encrypt hooks so you can enter your password to decrypt the
 volume.