diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index f66bc80c48..461f2420ba 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -1,7 +1,7 @@ @@ -97,15 +97,15 @@ your configuration. If you already have another operating system installed, such as - Windows, or Linux, it is a good idea to use the facilities provided + Windows or Linux, it is a good idea to use the facilities provided by those operating systems to see how your hardware is already configured. If you are really not sure what settings an expansion - card is using you may find it printed on the card itself. Popular IRQ + card is using, you may find it printed on the card itself. Popular IRQ numbers are 3, 5, and 7, and IO port addresses are normally written as hexadecimal numbers, such as 0x330. We recommend you print or write down this information before - installing FreeBSD. It may help to use a table, like this; + installing FreeBSD. It may help to use a table, like this: Sample Device Inventory @@ -199,16 +199,16 @@ valuable data then ensure you have it backed up, and that you have tested the backups before installing FreeBSD. The FreeBSD installation routine will prompt you several times before writing any - data to your disk, but once that process has started it can not be + data to your disk, but once that process has started it cannot be undone. Decide Where to Install FreeBSD - If you want FreeBSD to use all your disk then there is nothing - more to concern yourself with at this point, and you can skip to the - next section.. + If you want FreeBSD to use all your disk, then there is nothing + more to concern yourself with at this point — you can skip to the + next section. However, if you need FreeBSD to co-exist with other operating systems then you need to have a rough understanding of how data is @@ -221,14 +221,14 @@ called partitions. By design, the PC only supports four partitions per disk. These partitions are called primary partitions. To work around this - limitation, and allow more than four partitions, a new partition type + limitation and allow more than four partitions, a new partition type was created, the extended partition. A disk may contain only one extended partition. Special partitions, called logical partitions, can be created inside this extended partition. Each partition has a partition ID, which is - a number, used to identify the type of data on the partition. FreeBSD + a number used to identify the type of data on the partition. FreeBSD partitions have the partition ID 165. In general, each operating system that you use will identify @@ -237,16 +237,16 @@ drive letter, starting with C:. - FreeBSD must be installed in to a primary partition. FreeBSD can + FreeBSD must be installed into a primary partition. FreeBSD can keep all its data, including any files that you create, on this one - partition. However, if you have multiple disks then you can create a - FreeBSD partition on all, or some, of them. When you install FreeBSD + partition. However, if you have multiple disks, then you can create a + FreeBSD partition on all, or some, of them. When you install FreeBSD, you must have one partition available. This might be a blank partition that you have prepared, or it might be an existing partition that contains data that you no longer care about. - If you are already using all the partitions on all your disks then - you will have to free one of them for FreeBSD to use, using the tools + If you are already using all the partitions on all your disks, then + you will have to free one of them for FreeBSD using the tools provided by the other operating systems you use (e.g., fdisk on DOS or Windows). @@ -259,7 +259,7 @@ leaving almost no space for your own files. A more realistic minimum is 250MB without a graphical environment, and 350MB or more if you want a graphical user interface. If you intend to install a lot of - third party software as well then you will need more space. + third party software as well, then you will need more space. You can use a commercial tool such as Partition Magic to resize your partitions to make space for @@ -278,7 +278,7 @@ Using an existing partition unchanged - Suppose that you have a computer with a single 4GB disk, that + Suppose that you have a computer with a single 4GB disk that already has a version of Windows installed, and you have split the disk in to two drive letters, C: and D:, each of which is 2GB in size. You have @@ -305,7 +305,7 @@ - Back up your Windows data, and then reinstall Windows, + Backup your Windows data, and then reinstall Windows, asking for a 2GB partition at install time. @@ -361,12 +361,13 @@ pqb0.0.1.4.0 PQB0 PCI EIDE refers to a SCSI with SCSI target ID 1 on the first SCSI bus (A), whereas DKC300 refers to a SCSI disk with SCSI ID 3 on the third SCSI bus (C). Devicename - PKxrefers to the SCSI host bus adapter. As + PKx refers to the SCSI host bus adapter. As seen in the SHOW DEVICE output SCSI CDROM drives are treated as any other SCSI hard disk drive. - IDE disks have names like DQx, - PQx is the associated IDE controller. + IDE disks have names similar to DQx, + while PQx is the associated IDE + controller. @@ -375,8 +376,9 @@ pqb0.0.1.4.0 PQB0 PCI EIDECollect Your Network Configuration DetailsIf you intend to connect to a network as part of your FreeBSD - installation (e.g., if you will be installing from an FTP site, or an - NFS server) then you need to know your network configuration. You + installation (for example, if you will be installing from an FTP + site, or an + NFS server), then you need to know your network configuration. You will be prompted for this information during the installation so that FreeBSD can connect to the network to complete the install. @@ -384,7 +386,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDEConnecting to an Ethernet Network, or Cable/DSL ModemIf you connect to an Ethernet network, or you have an Internet - connection via cable or DSL then you will need the following + connection via cable or DSL, then you will need the following information: @@ -405,7 +407,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE - If you do not know this information then ask your system + If you do not know this information, then ask your system administrator or service provider. They may say that this information is assigned automatically, using DHCP. If so, make a note of this. @@ -466,30 +468,34 @@ pqb0.0.1.4.0 PQB0 PCI EIDE If you have FreeBSD on CDROM or DVD, and your computer allows you to boot from the CDROM or DVD (typically a BIOS option called Boot Order or similar) then you can skip this - section. The FreeBSD CDROM and DVD images are bootable, and can be + section. The FreeBSD CDROM and DVD images are bootable and can be used to install FreeBSD without any other special preparation. The FreeBSD installation process is started by booting your - computer in to the FreeBSD installer—it is not a program you run - from within another operating system. To do this you must create some + computer into the FreeBSD installer—it is not a program you run + within another operating system. To do this, you must create some floppy disks that can be booted from, and then boot from them. If you are not installing directly from CDROM, DVD, or FTP then you are probably preparing your own installation media (e.g., an MS-DOS partition), which must be prepared - before you install FreeBSD. This is a slightly more advanced, and + before you install FreeBSD. This is a slightly more advanced, infrequent activity, and is documented in . This includes the scenario where you want to create your own FTP site on your own network so that other computers can use your site as a FreeBSD FTP installation site. + In general, to create boot floppy images, follow these + steps: + Acquire the Boot Floppy Images - The boot discs are available on your installation media, and + The boot discs are available on your installation media + in the floppies directory, and can also be downloaded from the floppies directory. @@ -509,7 +515,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE to download these disk images. Some web browsers have been known to use text (or ASCII) mode, which will be apparent if you - can not boot from the disks. + cannot boot from the disks. @@ -523,9 +529,9 @@ pqb0.0.1.4.0 PQB0 PCI EIDE If you try to install FreeBSD and the installation - program crashes, freezes, or otherwise misbehaves one of + program crashes, freezes, or otherwise misbehaves, one of the first things to suspect is the floppies. Try writing - the floppy image files to some other disks, and try + the floppy image files to some other disks and try again. @@ -536,38 +542,38 @@ pqb0.0.1.4.0 PQB0 PCI EIDEThe .flp files are not regular files you copy to the disk. Instead, they are images of the complete contents of the - disk. This means that you can not use + disk. This means that you cannot use commands like DOS' copy to write the files. Instead, you must use specific tools to write the images directly to the disk.DOSIf you are creating the floppies on a computer running - DOS/Windows then we provide a tool to do + DOS/Windows, then we provide a tool to do this called fdimage.If you are using the floppies from the CDROM, and your - CDROM is the E: drive then you would + CDROM is the E: drive, then you would run this:E:\> tools\fdimage floppies\kern.flp A:Repeat this command for each .flp - file, replacing the floppy disk each time, and being sure to label + file, replacing the floppy disk each time, being sure to label the disks with the name of the file that you copied to them. Adjust the command line as necessary, depending on where you have placed the .flp files. If you do not have - the CDROM then fdimage can be downloaded from + the CDROM, then fdimage can be downloaded from the tools directory on the FreeBSD FTP site.If you are writing the floppies on a Unix system (such as another FreeBSD system) you can use the &man.dd.1; command to - write the image files directly to disk. On FreeBSD you would + write the image files directly to disk. On FreeBSD, you would run:&prompt.root; dd if=kern.flp of=/dev/fd0 - On FreeBSD /dev/fd0 refers to the + On FreeBSD, /dev/fd0 refers to the first floppy disk (the A: drive). /dev/fd1 would be the B: drive, and so on. Other Unix @@ -633,13 +639,13 @@ We can take no responsibility for lost disk contents! Floppy, CDROM, First Hard Disk, and so on. - If you needed to prepare boot floppies then make sure that the + If you needed to prepare boot floppies, then make sure that the floppy disk is selected. If you are booting from the CDROM then - make sure that that is selected instead. In case of doubt you + make sure that that is selected instead. In case of doubt, you should consult the manual that came with your computer, and/or its motherboard. - Make the change, then save, and exit. The computer should now + Make the change, then save and exit. The computer should now restart. @@ -650,7 +656,7 @@ We can take no responsibility for lost disk contents! kern.flp. Put this disc in your floppy drive. - If you are booting from CDROM then you will need to turn on + If you are booting from CDROM, then you will need to turn on the computer, and insert the CDROM at the first opportunity. @@ -693,7 +699,7 @@ FreeBSD/i386 bootstrap loader, Revision 0.8 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _ - If you are booting from floppy disc you will see a display + If you are booting from floppy disc, you will see a display similar to this: Verifying DMI Pool Data ........ @@ -801,23 +807,23 @@ Booting [kernel] in 9 seconds... _ the FreeBSD kernel has a driver associated with it. Each driver has a two or three letter name, such as sa for the SCSI sequential access driver, or sio for the - Serial I/O driver (which manages com ports). + Serial I/O driver (which manages COM ports). - When the kernel starts each driver checks the system to see + When the kernel starts, each driver checks the system to see whether or not the hardware it supports exists on your system. If it - does then the driver configures the hardware, and makes it available + does, then the driver configures the hardware and makes it available to the rest of the kernel. This checking is commonly referred to as device probing. Unfortunately, it is not always possible to do this in a safe way. Some hardware drivers do not co-exist well together, and probing for one piece of hardware can sometimes leave - another piece of hardware in an inconsistent state. This is a basic + another in an inconsistent state. This is a basic limitation of the design of the PC. - Many older devices are what is called ISA devices—as opposed + Many older devices are called ISA devices—as opposed to PCI devices. The ISA specification requires each device to have - some information hard coded in to it, typically the Interrupt Request + some information hard coded into it, typically the Interrupt Request Line number (IRQ) and IO port address that the driver uses. This information is commonly set by using physical jumpers on the card, or by using a DOS based @@ -834,7 +840,7 @@ Booting [kernel] in 9 seconds... _ driver for that device will need to be configured with the IRQ and port address that you have set the card to. This is why carrying out an inventory of your hardware (see ) can be so useful. + linkend="install-inventory">) can be useful. Unfortunately, the default IRQs and memory ports used by some drivers clash. This is because some ISA devices are shipped with IRQs @@ -844,17 +850,17 @@ Booting [kernel] in 9 seconds... _ This is almost never an issue when running FreeBSD day-to-day. Your computer will not normally contain two pieces of hardware that - clash, because then one of them would not work (irrespective of the + clash, because tone of them would not work (irrespective of the operating system you are using). It becomes an issue when you are installing FreeBSD for the first time because the kernel used to carry out the install has to contain - as many drivers as possible, so that as many different hardware - configurations can be supported as possible. This means that some of + as many drivers as possible, so that many different hardware + configurations can be supported. This means that some of those drivers will have conflicting configurations. The devices are probed in a strict order, and if you own a device that is probed late - in the process, but that an earlier probe conflicted with, then your - hardware might not function, or be probed correctly when you install + in the process, but conflicted with an earlier probe, then your + hardware might not function or be probed correctly when you install FreeBSD. Because of this, the first thing you have the opportunity to do @@ -864,7 +870,7 @@ Booting [kernel] in 9 seconds... _ configuration if you do own the device but the defaults are wrong. - That probably sounds much more complicated than it actually + This probably sounds much more complicated than it actually is. shows the first kernel @@ -884,7 +890,7 @@ Booting [kernel] in 9 seconds... _ The kernel configuration screen () - is then divided in to four sections. + is then divided into four sections. @@ -1042,7 +1048,7 @@ Booting [kernel] in 9 seconds... _ Answer Y to save the parameters and the probing will start. After displaying the probe results in white - on black text Sysinstall will start, + on black text Sysinstall will start and display its main menu (). @@ -1063,7 +1069,7 @@ Booting [kernel] in 9 seconds... _ Reviewing the Device Probe Results The last few hundred lines that have been displayed on screen are - stored, and can be reviewed. + stored and can be reviewed. To review the buffer, press Scroll Lock. This turns on scrolling in the display. You can then use the arrow keys, or @@ -1127,8 +1133,8 @@ Mounting root from ufs:/dev/md0c Check the probe results carefully to make sure that FreeBSD found - all the devices you expected. If a device was not found then it will - be listed as missing. If the device's driver required configuring + all the devices you expected. If a device was not found, then it will + not be listed. If the device's driver required configuring with the IRQ and port address then you should check that you entered them correctly. @@ -1171,14 +1177,15 @@ Mounting root from ufs:/dev/md0c Introducing Sysinstall Sysinstall is the installation - application provided by the FreeBSD Project. It is text based, and is - divided in to a number of menus and screens that you can use to + application provided by the FreeBSD Project. It is console based and is + divided into a number of menus and screens that you can use to configure and control the installation process. The Sysinstall menu system is controlled by the arrow keys, Enter, Space. and other keys. A detailed description of these keys, and what they do, is - contained in sysinstall's usage information. + contained in Sysinstall's usage + information. To review this information, ensure that the Usage entry is highlighted and that the @@ -1341,130 +1348,13 @@ Mounting root from ufs:/dev/md0c - - Installation Destination + + Allocating Disk Space - - Disk Naming - - IDE - SCSI - RAID - flash memory - Physical drives come in two main flavors, - IDE, or SCSI; but there - are also drives backed by RAID controllers, flash memory, and so - forth. Since these behave quite differently, they have their - own drivers and devices. - -
- Physical Disk Naming Conventions - - - - - Drive type - Drive device name - - - - - IDE hard drives - ad in 4.0-RELEASE, - wd before 4.0-RELEASE. - - - IDE CDROM drives - acd from 4.0-RELEASE, - wcd before 4.0-RELEASE. - - - SCSI hard drives and USB Mass storage devices - da from 3.0-RELEASE, - sd before 3.0-RELEASE. - - - SCSI CDROM drives - cd - - - Assorted non-standard CDROM drives - mcd for Mitsumi CD-ROM, - scd for Sony CD-ROM, - matcd for Matsushita/Panasonic CD-ROM - - - - Floppy drives - fd - - - SCSI tape drives - sa from 3.0-RELEASE, - st before 3.0-RELEASE. - - - IDE tape drives - ast from 4.0-RELEASE, - wst before 4.0-RELEASE. - - - Flash drives - fla for DiskOnChip Flash device - from 3.3-RELEASE. - - - RAID drives - myxd for Mylex, and - amrd for AMI MegaRAID, - idad for Compaq Smart RAID. - from 4.0-RELEASE. id between - 3.2-RELEASE and 4.0-RELEASE. - - - -
- - All the drives attached through a specific driver are - numbered starting at 0. So the first IDE drive would be - ad0. You seldom need to use - these devices. - - - Slices and Partitions - slices - partitions - dangerously dedicated - Physical disks usually contain - slices, unless they are - dangerously dedicated. Slice numbers follow - the device name, prefixed with an s, - starting at 1. So da0s1 - is the first slice on the first SCSI drive. There can only be - four physical slices on a disk, but you can have logical - slices inside physical slices of the appropriate type. These - extended slices are numbered starting at 5, so - ad0s5 is the first - extended slice on a disk. These devices are used by file - systems that expect to occupy a slice. - - Slices, dangerously dedicated physical - drives, and other drives contain - partitions, which are represented as - letters from a to h. - This letter is appended to the device name, so - da0a is the a partition on - the first da drive, which is dangerously dedicated. - ad1s3e is the fifth partition - in the third slice of the second IDE disk drive. - - The boot code expects partition a to be - the root partition. Partition b is normally - reserved for swap partitions, and c is an - unused partition the size of the entire slice or drive. This - is explained in . - - + Your first task is to allocate disk space for FreeBSD, and label + that space so that Sysinstall can prepare + it. In order to do this you need to know how FreeBSD expects to find + information on the disk. BIOS Drive Numbering @@ -1573,15 +1463,6 @@ Mounting root from ufs:/dev/md0c apply equally to IDE drives. - - - - Allocating Disk Space - - Your first task is to allocate disk space for FreeBSD, and label - that space so that Sysinstall can prepare - it. In order to do this you need to know how FreeBSD expects to find - information on the disk. Disk Organization @@ -1856,6 +1737,31 @@ Mounting root from ufs:/dev/md0c FreeBSD's Unix background. Slices are numbered, starting at 1, through to 4. + slices + partitions + dangerously dedicated + + Slice numbers follow + the device name, prefixed with an s, + starting at 1. So da0s1 + is the first slice on the first SCSI drive. There can only be + four physical slices on a disk, but you can have logical + slices inside physical slices of the appropriate type. These + extended slices are numbered starting at 5, so + ad0s5 is the first + extended slice on a disk. These devices are used by file + systems that expect to occupy a slice. + + Slices, dangerously dedicated physical + drives, and other drives contain + partitions, which are represented as + letters from a to h. + This letter is appended to the device name, so + da0a is the a partition on + the first da drive, which is dangerously dedicated. + ad1s3e is the fifth partition + in the third slice of the second IDE disk drive. + Finally, each disk on the system is identified. A disk name starts with a code that indicates the type of disk, and then a number, indicating which disk it is. Unlike slices, disk numbering starts at @@ -2173,7 +2079,7 @@ Mounting root from ufs:/dev/md0c - You have more than one drive, and have installed FreeBSD on to + You have more than one drive, and have installed FreeBSD onto a drive other than the first one. @@ -2206,8 +2112,8 @@ Mounting root from ufs:/dev/md0c If there is more than one drive, it will return to the Select Drives screen after the boot manager selection. If you wish to - install FreeBSD on to more than one disk than you can select another - disk here, and repeat the slice process using + install FreeBSD on to more than one disk, then you can select another + disk here and repeat the slice process using FDisk,
@@ -2448,7 +2354,7 @@ Mounting root from ufs:/dev/md0c
Disklabel can automatically create - partitions for you, and assign them default sizes. Try this now, by + partitions for you and assign them default sizes. Try this now, by Pressing A. You will see a display similar to that shown in . Depending on the size of the disk you are using the defaults may or may not be appropriate. @@ -2492,7 +2398,7 @@ Mounting root from ufs:/dev/md0c The default size shown will create a partition that takes up the rest of the slice. If you are using the partition sizes described - earlier then delete the existing figure using + earlier, then delete the existing figure using Backspace, and then type in 64M, as shown in . Then press @@ -2684,7 +2590,7 @@ Mounting root from ufs:/dev/md0c Choosing Your Installation Media If Installing from a CDROM, use the arrow keys to highlight - Install from a FreeBSD CDROM. Ensure + Install from a FreeBSD CD/DVD. Ensure that [ OK ] is highlighted, then press Enter to proceed with the installation. @@ -2817,7 +2723,8 @@ Mounting root from ufs:/dev/md0c Enter to proceed. The installation time will vary according to the distribution - chosen and installation media used. There will be a series of + chosen, installation media used, and the speed of the computer. + There will be a series of messages displayed indicating the status. The installation is complete when the following message is @@ -2914,7 +2821,7 @@ installation menus to try and retry whichever operations have failed. If you want to try the new Internet protocol (IPv6), choose [ Yes ] and press Enter. - It will take several seconds for scanning RA servers. + It will take several seconds to scan for RA servers. User Confirmation Requested Do you want to try DHCP configuration of the interface? @@ -3540,7 +3447,7 @@ To change any of these settings later, edit /etc/rc.conf Mouse Settings - This option will allow you to cut and past text in the + This option will allow you to cut and paste text in the console and user programs with a 3-button mouse. If using a 2-button mouse, refer to manual page, &man.moused.8;, after installation for details on emulating the 3-button style. This example depicts a @@ -3701,7 +3608,7 @@ To change any of these settings later, edit /etc/rc.conf [ Press enter to continue ] - The indicates that the mouse daemon previously configured has been + This indicates that the mouse daemon previously configured has been detected. Press Enter to continue. Press [Enter] to switch to graphics mode. @@ -3830,8 +3737,8 @@ To change any of these settings later, edit /etc/rc.conf <guimenuitem>Other</guimenuitem> - There default settings are reasonable values so you - probably won't need to change anything here. + The default settings are reasonable values, so you + probably will not need to change anything here. The default setting which allows the server to be killed with the hotkey sequence @@ -3868,14 +3775,15 @@ when you've finished. After selecting Okay, some messages will briefly appear advising to wait and attempting to start - the x-server. This process takes a few moments, so be + the X-server. This process takes a few moments, so be patient. The screen will go blank for a short period of time and then a screen will appear with the message Congratulations, you've got a running server! - If nothing appears or is distorted, kill the x-server using + If nothing appears or the display is distorted, + kill the X-server using Ctrl Alt @@ -3894,11 +3802,11 @@ when you've finished. damage your equipment. Heed them. If in doubt, do not do it. Instead, use the monitor controls to adjust the display for x-windows. There may be some display differences when switching - back to text mode, but it is better than damaging equipment. The + back to text mode, but it is better than damaging equipment. xvidtune can be ran later using /stand/sysinstall. - Read the xvidtune before making + Read the &man.xvidtune.1; man page before making any adjustments. @@ -4219,7 +4127,7 @@ when you've finished. - Set Root Password + Set <username>root</username> Password Message Now you must set the system manager's password. @@ -4429,6 +4337,8 @@ Additional ABI support: linux. Local package initilization:. Additional TCP options:. +FreeBSD/i386 (k6-2.weeble.com) (ttyv0) + login: rpratt Password: