diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.xml b/en_US.ISO8859-1/books/handbook/install/chapter.xml index f9d9317ded..227c4c9dd0 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.xml @@ -5,34 +5,33 @@ $FreeBSD$ --> - Installing &os; 8.<replaceable>X</replaceable> + + Installing &os; 8.<replaceable>X</replaceable> + - JimMockRestructured, reorganized, and parts - rewritten by + JimMockRestructured, + reorganized, and parts rewritten by - RandyPrattThe sysinstall walkthrough, screenshots, and general - copy by + RandyPrattThe + sysinstall walkthrough, screenshots, and general copy by + - - - Synopsis installation &os; provides a text-based, easy to use installation - program. &os; 9.0-RELEASE and later use the installation program - known as &man.bsdinstall.8; - while &os; 8.X uses - &man.sysinstall.8;. This chapter describes - how to use &man.sysinstall.8;. - The use of &man.bsdinstall.8; - is covered in . + program. &os; 9.0-RELEASE and later use the installation + program known as &man.bsdinstall.8; while + &os; 8.X uses + &man.sysinstall.8;. This chapter describes how to use + &man.sysinstall.8;. The use of &man.bsdinstall.8; is covered in + . After reading this chapter, you will know: @@ -50,8 +49,8 @@ - The questions &man.sysinstall.8; asks, - what they mean, and how to answer them. + The questions &man.sysinstall.8; asks, what they mean, + and how to answer them. @@ -59,20 +58,20 @@ - Read the supported hardware list that shipped with the version - of &os; to install, and verify that the system's hardware is - supported. + Read the supported hardware list that shipped with the + version of &os; to install, and verify that the system's + hardware is supported. In general, these installation instructions are written - for the &i386; and &os;/&arch.amd64; architectures. - Where applicable, instructions specific to other - platforms will be listed. There may be minor - differences between the installer and what is shown here. - This chapter should be used as a general guide rather - than a literal installation manual. + for the &i386; and &os;/&arch.amd64; architectures. Where + applicable, instructions specific to other platforms will be + listed. There may be minor differences between the installer + and what is shown here. This chapter should be used as a + general guide rather than a literal installation + manual. @@ -86,25 +85,24 @@ The minimal configuration to install &os; varies with the &os; version and the hardware architecture. - A summary of this information is given in the following sections. - Depending on the method chosen to install &os;, - a floppy drive, CDROM drive, or - network adapter may be needed. Instructions on how to - prepare the installation media can be found in - . + A summary of this information is given in the following + sections. Depending on the method chosen to install &os;, + a floppy drive, CDROM drive, or network adapter may be needed. + Instructions on how to prepare the installation media can be + found in . &os;/&arch.i386; and &os;/&arch.pc98; - Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 or - better processor, at least 24 MB of RAM, and at - least 150 MB of free hard drive space for the - most minimal installation. + Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 + or better processor, at least 24 MB of RAM, and at + least 150 MB of free hard drive space for the most + minimal installation. In the case of older hardware, installing more RAM and - more hard drive space is often more important than - a faster processor. + more hard drive space is often more important than a + faster processor. @@ -113,32 +111,29 @@ There are two classes of processors capable of running &os;/&arch.amd64;. The first are AMD64 processors, - including the &amd.athlon;64, - &amd.athlon;64-FX, and &amd.opteron; or better - processors. + including the &amd.athlon;64, &amd.athlon;64-FX, and + &amd.opteron; or better processors. - The second class of processors - includes those using the &intel; EM64T - architecture. Examples of these processors include the - &intel; &core; 2 Duo, Quad, Extreme processor - families, and the &intel; &xeon; 3000, 5000, and 7000 - sequences of processors. + The second class of processors includes those using the + &intel; EM64T architecture. Examples of these processors + include the &intel; &core; 2 Duo, Quad, Extreme + processor families, and the &intel; &xeon; 3000, 5000, + and 7000 sequences of processors. - If the machine is based on an nVidia nForce3 - Pro-150, the BIOS setup must be used to - disable the IO APIC. If this option does not exist, - disable ACPI instead as there - are bugs in the Pro-150 chipset. + If the machine is based on an nVidia nForce3 Pro-150, + the BIOS setup must be used to disable + the IO APIC. If this option does not exist, disable ACPI + instead as there are bugs in the Pro-150 chipset. &os;/&arch.sparc64; - To install &os;/&arch.sparc64;, use a supported - platform (see ). + To install &os;/&arch.sparc64;, use a supported platform + (see ). - A dedicated disk is needed for &os;/&arch.sparc64; as - it is not possible to share a disk with another operating + A dedicated disk is needed for &os;/&arch.sparc64; as it + is not possible to share a disk with another operating system at this time. @@ -150,12 +145,13 @@ release in the &os; Hardware Notes. This document can usually be found in a file named HARDWARE.TXT, in the top-level directory of a CDROM or FTP distribution, or in - &man.sysinstall.8;'s documentation menu. - It lists, for a given architecture, which hardware devices are - known to be supported by each release of &os;. Copies of the - supported hardware list for various releases and architectures - can also be found on the Release - Information page of the &os; website. + &man.sysinstall.8;'s documentation menu. It lists, for a + given architecture, which hardware devices are known to be + supported by each release of &os;. Copies of the supported + hardware list for various releases and architectures can also + be found on the Release + Information page of the &os; website. @@ -167,31 +163,25 @@ Before installing &os; it is recommended to inventory the components in the computer. The &os; installation routines - will show components such as hard disks, network cards, - and CDROM drives with their model number and manufacturer. - &os; will also - attempt to determine the correct configuration for these devices, - including information about IRQ and I/O port usage. Due - to the - vagaries of computer hardware, this process is not always - completely - successful, and &os; may need some manual - configuration. + will show components such as hard disks, network cards, and + CDROM drives with their model number and manufacturer. &os; + will also attempt to determine the correct configuration for + these devices, including information about IRQ and I/O port + usage. Due to the vagaries of computer hardware, this process + is not always completely successful, and &os; may need some + manual configuration. - If another operating system is already installed, - use the facilities provided - by that operating systems to view the hardware configuration. - If the settings of an expansion - card are not obvious, check if they are printed on the - card itself. Popular IRQ - numbers are 3, 5, and 7, and I/O port addresses are normally - written as - hexadecimal numbers, such as 0x330. + If another operating system is already installed, use the + facilities provided by that operating systems to view the + hardware configuration. If the settings of an expansion card + are not obvious, check if they are printed on the card itself. + Popular IRQ numbers are 3, 5, and 7, and I/O port addresses + are normally written as hexadecimal numbers, such as + 0x330. It is recommended to print or write down this information - before - installing &os;. It may help to use a table, as seen in this - example: + before installing &os;. It may help to use a table, as seen + in this example: Sample Device Inventory @@ -221,7 +211,8 @@ N/A - 40 GB, made by Seagate, first IDE master + 40 GB, made by Seagate, first IDE + master @@ -241,7 +232,8 @@ N/A - 20 GB, made by IBM, second IDE master + 20 GB, made by IBM, second IDE + master @@ -282,174 +274,157 @@
Once the inventory of the components in the computer is - complete, check if it matches the hardware - requirements of the &os; release to install. + complete, check if it matches the hardware requirements of the + &os; release to install. Make a Backup - If the computer contains - valuable data, ensure it is backed up, and that the backup - has been - tested before installing &os;. The &os; - installer will prompt before writing any - data to disk, but once that process has started, it cannot be - undone. + If the computer contains valuable data, ensure it is + backed up, and that the backup has been tested before + installing &os;. The &os; installer will prompt before + writing any data to disk, but once that process has started, + it cannot be undone. Decide Where to Install &os; - If &os; is to be installed on the entire hard disk, - skip this - section. + If &os; is to be installed on the entire hard disk, skip + this section. However, if &os; will co-exist with other operating - systems, a rough understanding of how data is - laid out on the disk is useful. + systems, a rough understanding of how data is laid out on the + disk is useful. Disk Layouts for &os;/&arch.i386; - A PC disk can be divided into discrete chunks known as - partitions. Since - &os; also has partitions, naming - can quickly become confusing. Therefore, these - disk chunks are referred to as slices - in &os;. For example, the &os; version of - &man.fdisk.8; - refers to slices instead of 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 - 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. + A PC disk can be divided into discrete chunks known as + partitions. Since &os; also has + partitions, naming can quickly become confusing. Therefore, + these disk chunks are referred to as slices in &os;. For + example, the &os; version of &man.fdisk.8; refers to slices + instead of 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 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. &os; - partitions have the partition ID of 165. + Each partition has a partition + ID, which is a number used to identify the + type of data on the partition. &os; partitions have the + partition ID of 165. - In general, each operating system will identify - partitions in a particular way. For example, - &windows;, assigns each primary and logical partition a - drive letter, starting with - C:. + In general, each operating system will identify + partitions in a particular way. For example, &windows;, + assigns each primary and logical partition a + drive letter, starting with + C:. - &os; must be installed into a primary partition. If - there are multiple disks, a &os; - partition can be created - on all, or some, of them. When &os; is installed, at least - one partition must be available. This might be a blank - partition or it might be an existing partition whose - data can be overwritten. + &os; must be installed into a primary partition. If + there are multiple disks, a &os; partition can be created on + all, or some, of them. When &os; is installed, at least one + partition must be available. This might be a blank + partition or it might be an existing partition whose data + can be overwritten. - If all the partitions on all the disks are in use, - free one of them for &os; using the tools - provided by an existing operating system, such as &windows; - fdisk. + If all the partitions on all the disks are in use, free + one of them for &os; using the tools provided by an existing + operating system, such as &windows; + fdisk. - If there is a spare partition, use that. If it is too - small, - shrink one or more existing partitions to create more - available space. + If there is a spare partition, use that. If it is too + small, shrink one or more existing partitions to create more + available space. - A minimal installation of &os; takes as little as 100 MB - of disk - space. However, that is a very minimal install, - leaving almost no space for files. A more realistic minimum - is 250 MB without a graphical environment, and 350 MB or - more for - a graphical user interface. If other - third-party software will be installed, - even more space is needed. + A minimal installation of &os; takes as little as + 100 MB of disk space. However, that is a + very minimal install, leaving almost no + space for files. A more realistic minimum is 250 MB + without a graphical environment, and 350 MB or more for + a graphical user interface. If other third-party software + will be installed, even more space is needed. - You can use a tool such as GParted - to resize your partitions and make space for - &os;. GParted is known to work on - NTFS and - is available on a number of Live CD Linux distributions, such as - SystemRescueCD. + You can use a tool such as + GParted to resize your partitions + and make space for &os;. GParted + is known to work on NTFS and is available + on a number of Live CD Linux distributions, such as SystemRescueCD. - - Incorrect use of a shrinking tool can delete the data - on the disk. - Always have a recent, working backup before using this - type of tool. - + + Incorrect use of a shrinking tool can delete the data + on the disk. Always have a recent, working backup before + using this type of tool. + - - Using an Existing Partition Unchanged + + Using an Existing Partition Unchanged - Consider a computer with a single 4 GB disk - that - already has a version of &windows; installed, where the - disk has been split into two drive letters, - C: and - D:, each of which is 2 GB in size. - There is 1 GB of data on C:, - and - 0.5 GB of data on - D:. + Consider a computer with a single 4 GB disk that + already has a version of &windows; installed, where the + disk has been split into two drive letters, + C: and D:, each + of which is 2 GB in size. There is 1 GB of data + on C:, and 0.5 GB of data on + D:. - This disk has two partitions, one per - drive letter. Copy all existing data from - D: to C:, which - will free up the second partition, ready for &os;. - + This disk has two partitions, one per drive letter. + Copy all existing data from D: to + C:, which will free up the second + partition, ready for &os;. + - - Shrinking an Existing Partition + + Shrinking an Existing Partition - Consider a computer with a single 4 GB disk - that already has a version of &windows; installed. When - &windows; was installed, it created one large partition, - a - C: drive that is 4 GB in size. - Currently, 1.5 GB of space is used, and &os; should - have 2 GB - of space. + Consider a computer with a single 4 GB disk that + already has a version of &windows; installed. When + &windows; was installed, it created one large partition, + a C: drive that is 4 GB in size. + Currently, 1.5 GB of space is used, and &os; should + have 2 GB of space. - In order to install &os;, either: + In order to install &os;, either: - - - Backup the &windows; data and then reinstall - &windows;, - asking for a 2 GB partition at install time. - - - - Use one of the tools described above to shrink your &windows; - partition. - - - + + + Backup the &windows; data and then reinstall + &windows;, asking for a 2 GB partition at install + time. + + + Use one of the tools described above to shrink + your &windows; partition. + + + Collect the Network Configuration Details - Before - installing from an FTP - site or an + Before installing from an FTP site or an NFS server, make note of the network - configuration. The - installer - will prompt for this information so that - it can connect to the network to complete the + configuration. The installer will prompt for this information + so that it can connect to the network to complete the installation. - Connecting to an Ethernet Network or Cable/DSL Modem + Connecting to an Ethernet Network or Cable/DSL + Modem - If using an Ethernet network or an Internet - connection using an Ethernet adapter via cable or DSL, the - following information is needed: + If using an Ethernet network or an Internet connection + using an Ethernet adapter via cable or DSL, the following + information is needed: @@ -482,10 +457,9 @@ Connecting Using a Modem - If using a dialup modem, - &os; can still be installed over the Internet, it will just - take a very - long time. + If using a dialup modem, &os; can still be installed + over the Internet, it will just take a very long + time. You will need to know: @@ -510,28 +484,28 @@ Check for &os; Errata Although the &os; Project strives to ensure that each - release - of &os; is as stable as possible, bugs do occasionally creep into - the process. On rare occasions those bugs affect the - installation process. As these problems are discovered and fixed, they - are noted in the &os; Errata, - which is found on the &os; website. - Check the errata before installing to make sure that there are - no late-breaking problems to be aware of. + release of &os; is as stable as possible, bugs do occasionally + creep into the process. On rare occasions those bugs affect + the installation process. As these problems are discovered + and fixed, they are noted in the &os; + Errata, which is found on the &os; website. Check + the errata before installing to make sure that there are no + late-breaking problems to be aware of. Information about all releases, including the errata for - each - release, can be found on the - release - information section of the - &os; website. + each release, can be found on the release + information section of the &os; + website. Obtain the &os; Installation Files - The &os; installer can install &os; from files - located in any of the following places: + The &os; installer can install &os; from files located in + any of the following places: Local Media @@ -570,15 +544,14 @@ - If installing from a purchased &os; CD/DVD, - skip ahead to + If installing from a purchased &os; CD/DVD, skip ahead to . - To obtain the &os; installation files, - skip ahead to which explains how - to prepare the installation media. After reading - that section, come back here and read on to - . + To obtain the &os; installation files, skip ahead to which explains how to prepare + the installation media. After reading that section, come back + here and read on to . @@ -586,18 +559,15 @@ The &os; installation process is started by booting the computer into the &os; installer. It is not a program that - can be run - within another operating system. The computer normally boots - using the operating system installed on the hard disk, but it - can also be configured to boot from a CDROM or from a USB - disk. + can be run within another operating system. The computer + normally boots using the operating system installed on the + hard disk, but it can also be configured to boot from a CDROM + or from a USB disk. - If installing from a CD/DVD to a - computer whose BIOS supports booting from - the CD/DVD, skip this section. The - &os; CD/DVD images are bootable and can be used to - install + If installing from a CD/DVD to a computer whose BIOS + supports booting from the CD/DVD, skip this section. The + &os; CD/DVD images are bootable and can be used to install &os; without any other special preparation. @@ -610,16 +580,16 @@ Memory stick images for &os; 8.X can be downloaded - from - the ISO-IMAGES/ - directory at + from the ISO-IMAGES/ directory at ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/ISO-IMAGES/version/&os;-version-RELEASE-arch-memstick.img. Replace arch and - version with the - architecture and the version number to - install. For example, the memory stick - images for &os;/&arch.i386; &rel2.current;-RELEASE are - available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img. + version with the architecture + and the version number to install. For example, the + memory stick images for + &os;/&arch.i386; &rel2.current;-RELEASE are + available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img. A different directory path is used for @@ -632,14 +602,13 @@ The memory stick image has a .img extension. The ISO-IMAGES/ directory contains a number of different images and the one to - use depends on the version of &os; and the - type of media supported by the hardware being installed - to. + use depends on the version of &os; and the type of media + supported by the hardware being installed to. Before proceeding, back up the - data on the USB stick, as this - procedure will erase it. + data on the USB stick, as this procedure will + erase it. @@ -650,31 +619,29 @@ Using &os; to Write the Image - The example below - lists /dev/da0 as the - target device where the image will be written. Be very careful - that you have the correct device as the output target, or you - may destroy your existing data. + The example below lists + /dev/da0 as the target device + where the image will be written. Be very careful that + you have the correct device as the output target, or + you may destroy your existing data. Writing the Image with &man.dd.1; - The .img file - is not a regular file that can - just be copied to the - memory stick. It is an image of the complete contents of the - disk. This means that + The .img file is + not a regular file that can just + be copied to the memory stick. It is an image of the + complete contents of the disk. This means that &man.dd.1; must be used to write the image directly to the disk: &prompt.root; dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k - If an - Operation not permitted - error is displayed, make certain that the target device - is not in use, mounted, or being automounted by - another program. Then try + If an Operation not + permitted error is displayed, make + certain that the target device is not in use, mounted, + or being automounted by another program. Then try again. @@ -684,35 +651,38 @@ Make sure to use the correct drive letter as the - output - target, as this command will overwrite and destroy - any existing data on the specified device. + output target, as this command will overwrite and + destroy any existing data on the specified + device. - Obtaining <application>Image Writer for Windows</application> + Obtaining <application>Image Writer for + Windows</application> - Image Writer for Windows is a - free application that can correctly write an image file to a - memory stick. Download it from - https://launchpad.net/win32-image-writer/ + Image Writer for + Windows is a free application that can + correctly write an image file to a memory stick. + Download it from https://launchpad.net/win32-image-writer/ and extract it into a folder. Writing the Image with Image Writer - Double-click - the Win32DiskImager icon to start - the program. Verify that the drive letter shown - under Device is the drive - with the memory stick. Click the folder icon and select the - image to be written to the memory stick. - Click Save to accept the image file - name. Verify that everything is correct, and that no folders - on the memory stick are open in other windows. Finally, - click Write to write the image file to - the drive. + Double-click the + Win32DiskImager icon to + start the program. Verify that the drive letter shown + under Device is the + drive with the memory stick. Click the folder icon + and select the image to be written to the memory + stick. Click Save to accept + the image file name. Verify that everything is + correct, and that no folders on the memory stick are + open in other windows. Finally, click + Write to write the image file + to the drive. @@ -725,14 +695,15 @@ Acquire the Boot Floppy Images - The &os;/&arch.pc98; boot disks - can be downloaded from the floppies directory, + The &os;/&arch.pc98; boot disks can be downloaded from + the floppies directory, ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/version-RELEASE/floppies/. Replace version with the version number to install. The floppy images have a .flp - extension. floppies/ contains a number + extension. floppies/ contains a number of different images. Download boot.flp as well as the number of files associated with the type of installation, such as @@ -741,34 +712,29 @@ The FTP program must use binary - mode - to download these disk images. Some web browsers - use text or + mode to download these disk images. Some + web browsers use text or ASCII mode, which will be apparent - if - the disks are not bootable. + if the disks are not bootable. Prepare the Floppy Disks - Prepare one floppy disk per downloaded image file. - It is imperative that these disks are free from - defects. The easiest way to test this is to reformat the - disks. - Do not trust pre-formatted floppies. The format - utility in &windows; will not tell about the presence of - bad blocks, it simply marks them as bad - and ignores them. It is advised to use brand new - floppies. + Prepare one floppy disk per downloaded image file. It + is imperative that these disks are free from defects. The + easiest way to test this is to reformat the disks. Do not + trust pre-formatted floppies. The format utility in + &windows; will not tell about the presence of bad blocks, + it simply marks them as bad and ignores + them. It is advised to use brand new floppies. - If the installer - crashes, freezes, or otherwise misbehaves, one of - the first things to suspect is the floppies. Write - the floppy image files to new disks and try - again. + If the installer crashes, freezes, or otherwise + misbehaves, one of the first things to suspect is the + floppies. Write the floppy image files to new disks and + try again. @@ -777,44 +743,37 @@ The .flp files are not regular files that can be copied - to the disk. - They are images of the complete contents of the - disk. - Specific tools must be used to write the + to the disk. They are images of the complete contents of + the disk. Specific tools must be used to write the images directly to the disk. DOS - &os; provides a tool called - rawrite for creating the floppies on a - computer running - &windows;. This tool can be downloaded from + &os; provides a tool called rawrite + for creating the floppies on a computer running &windows;. + This tool can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/ - version-RELEASE/tools/ - on the &os; FTP site. Download this tool, insert a - floppy, then specify the filename to write to the floppy - drive: + version-RELEASE/tools/ on the + &os; FTP site. Download this tool, insert a floppy, then + specify the filename to write to the floppy drive: C:\> rawrite boot.flp A: Repeat this command for each .flp - file, replacing the floppy disk each time, being sure to label - the disks with the name of the file. - Adjust the command line as necessary, depending on where - the .flp files are located. + file, replacing the floppy disk each time, being sure to + label the disks with the name of the file. Adjust the + command line as necessary, depending on where the + .flp files are located. When writing the floppies on a &unix;-like system, - such as - another &os; system, use &man.dd.1; to - write the image files directly to disk. On &os;, - run: + such as another &os; system, use &man.dd.1; to write the + image files directly to disk. On &os;, run: &prompt.root; dd if=boot.flp of=/dev/fd0 On &os;, /dev/fd0 refers to the - first floppy disk. Other &unix; - variants might have different names for the floppy disk - device, so check the documentation for the - system as necessary. + first floppy disk. Other &unix; variants might have + different names for the floppy disk device, so check the + documentation for the system as necessary. @@ -827,8 +786,7 @@ By default, the installer will not make any changes to - the - disk(s) until after the following message: + the disk(s) until after the following message: Last Chance: Are you SURE you want continue the installation? @@ -839,10 +797,8 @@ We can take no responsibility for lost disk contents! The install can be exited at any time prior to this final warning without changing the contents of the hard drive. If - there is a - concern that something is configured incorrectly, - turn the computer off before this point, and no damage - will be + there is a concern that something is configured incorrectly, + turn the computer off before this point, and no damage will be done. @@ -852,86 +808,85 @@ We can take no responsibility for lost disk contents! Booting for the &i386; - - - Turn on the computer. As it starts it should display an - option to enter the system set up menu, or BIOS, commonly reached - by keys like F2, F10, - Del, or - - Alt - S - . Use whichever keystroke is indicated on screen. In - some cases the computer may display a graphic while it - starts. - Typically, pressing Esc will dismiss the graphic - and display the boot messages. - + + + Turn on the computer. As it starts it should + display an option to enter the system set up menu, or + BIOS, commonly reached by keys like F2, + F10, Del, or + + Alt + S + . Use whichever keystroke is indicated on + screen. In some cases the computer may display a + graphic while it starts. Typically, pressing + Esc will dismiss the graphic and + display the boot messages. + - - Find the setting that controls which devices the system boots - from. This is usually labeled as the Boot Order - and commonly shown as a list of devices, such as - Floppy, CDROM, - First Hard Disk, and so on. + + Find the setting that controls which devices the + system boots from. This is usually labeled as the + Boot Order and commonly shown as a list + of devices, such as Floppy, + CDROM, First Hard + Disk, and so on. - If booting from the CD/DVD, make sure that - the CDROM drive is selected. If booting from a USB disk, - make sure that it is selected instead. When in doubt, - consult the manual that came with the computer or its - motherboard. + If booting from the CD/DVD, make sure that the + CDROM drive is selected. If booting from a USB disk, + make sure that it is selected instead. When in doubt, + consult the manual that came with the computer or its + motherboard. - Make the change, then save and exit. The computer should now - restart. - + Make the change, then save and exit. The computer + should now restart. + - - If using a prepared a bootable USB - stick, as described in - , plug in the USB - stick before turning on the computer. + + If using a prepared a bootable USB + stick, as described in , plug in the USB stick + before turning on the computer. - If booting from CD/DVD, turn on - the computer, and insert the CD/DVD at the first - opportunity. + If booting from CD/DVD, turn on the computer, and + insert the CD/DVD at the first opportunity. - - For &os;/&arch.pc98;, installation boot floppies are - available and can be prepared as described in . The first floppy - disc will contain boot.flp. Put - this floppy in the floppy drive to boot into the - installer. - + + For &os;/&arch.pc98;, installation boot floppies + are available and can be prepared as described in + . The first + floppy disc will contain + boot.flp. Put this floppy in the + floppy drive to boot into the installer. + - If the computer starts up as normal and loads the - existing - operating system, then either: + If the computer starts up as normal and loads the + existing operating system, then either: - - - The disks were not inserted early enough in the boot - process. Leave them in, and try restarting the - computer. - + + + The disks were not inserted early enough in the + boot process. Leave them in, and try restarting the + computer. + - - The BIOS changes did not work correctly. - Redo that step until the right option is - selected. - + + The BIOS changes did not work correctly. Redo + that step until the right option is selected. + - - That particular BIOS does not support booting from - the desired media. - - - + + That particular BIOS does not support booting + from the desired media. + + + - - &os; will start to boot. If booting from CD/DVD, - messages will be displayed, similar to these: + + &os; will start to boot. If booting from CD/DVD, + messages will be displayed, similar to these: - Booting from CD-Rom... + Booting from CD-Rom... 645MB medium detected CD Loader 1.2 @@ -953,10 +908,10 @@ Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x64daa0 data=0xa4e80+0xa9e40 syms=[0x4+0x6cac0+0x4+0x88e9d] \ - If booting from floppy disc, a display - similar to this will be shown: + If booting from floppy disc, a display similar to + this will be shown: - Booting from Floppy... + Booting from Floppy... Uncompressing ... done BTX loader 1.00 BTX version is 1.01 @@ -972,100 +927,92 @@ Loading /boot/defaults/loader.conf Insert disk labelled "Kernel floppy 1" and press any key... - Remove the - boot.flp floppy, insert the - next floppy, and press - Enter. - When prompted, insert the other disks as required. - + Remove the boot.flp floppy, + insert the next floppy, and press + Enter. When prompted, insert the other + disks as required. + - - The - boot process will then display the &os; boot loader - menu: + + The boot process will then display the &os; boot + loader menu: -
- &os; Boot Loader Menu +
+ &os; Boot Loader Menu - - - - - -
- - Either wait ten seconds, or press Enter. - - + + + + + +
+ Either wait ten seconds, or press + Enter. + + Booting for &sparc64; Most &sparc64; systems are set to boot automatically - from disk. To install &os;, boot over the - network or from a CD/DVD and wait until the boot - message appears. The message depends on the model, but - should look similar to: + from disk. To install &os;, boot over the network or from a + CD/DVD and wait until the boot message appears. The message + depends on the model, but should look similar to: - Sun Blade 100 (UltraSPARC-IIe), Keyboard Present + Sun Blade 100 (UltraSPARC-IIe), Keyboard Present Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.2, 128 MB memory installed, Serial #51090132. Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - If the system proceeds to boot from disk, - press - L1A - or - StopA + If the system proceeds to boot from disk, press + L1A + or StopA on the keyboard, or send a BREAK over the - serial console using ~# in - &man.tip.1; or &man.cu.1; to get to the PROM prompt. It - looks like this: + serial console using ~# in &man.tip.1; or + &man.cu.1; to get to the PROM prompt. It looks like + this: - ok + ok ok {0} - - - This is the prompt used on systems with just one - CPU. - + + + This is the prompt used on systems with just one + CPU. + - - This is the prompt used on SMP systems and the - digit - indicates the number of the active CPU. - - + + This is the prompt used on SMP systems and the + digit indicates the number of the active CPU. + + At this point, place the CD/DVD into the drive and from the PROM prompt, type boot cdrom. - - Reviewing the Device Probe Results - The last few hundred lines that have been displayed on screen are - stored and can be reviewed. + The last few hundred lines that have been displayed on + screen are stored and can be reviewed. To review this buffer, press Scroll Lock - to - turn on scrolling in the display. Use the arrow keys or - PageUp and PageDown to view the - results. Press Scroll Lock again to stop + to turn on scrolling in the display. Use the arrow keys or + PageUp and PageDown to view + the results. Press Scroll Lock again to stop scrolling. - Do this now, to review the text that scrolled off the screen when - the kernel was carrying out the device probes. Text - similar to will be - displayed, although - it will differ depending on the devices in the - computer. + Do this now, to review the text that scrolled off the + screen when the kernel was carrying out the device probes. + Text similar to will be + displayed, although it will differ depending on the devices in + the computer.
Typical Device Probe Results @@ -1133,15 +1080,15 @@ Mounting root from ufs:/dev/md0c /stand/sysinstall running as init on vty0
- Check the probe results carefully to make sure that &os; found - all the devices. If a device was not found, it will - not be listed. A custom kernel - can be used to add in support for devices which are not in the + Check the probe results carefully to make sure that &os; + found all the devices. If a device was not found, it will + not be listed. A custom kernel can be used to + add in support for devices which are not in the GENERIC kernel. - After the device - probe, the menu shown in - will be displayed. Use the + After the device probe, the menu shown in will be displayed. Use the arrow key to choose a country, region, or group. Then press Enter to set the country. @@ -1157,10 +1104,9 @@ Mounting root from ufs:/dev/md0c If United States is selected as the country, the standard American keyboard map will be - used. - If a different country is chosen, the following menu will be - displayed. Use the arrow keys to choose the correct keyboard - map and press Enter. + used. If a different country is chosen, the following menu + will be displayed. Use the arrow keys to choose the correct + keyboard map and press Enter.
Selecting Keyboard Menu @@ -1181,22 +1127,23 @@ Mounting root from ufs:/dev/md0c Introducing &man.sysinstall.8; The &os; 8.X installer, - &man.sysinstall.8;, is console based and - is - divided into a number of menus and screens that can be used to - configure and control the installation process. + &man.sysinstall.8;, is console based and is divided into a + number of menus and screens that can be used to configure and + control the installation process. - This menu system is controlled - by the arrow keys, Enter, Tab, - Space, and - other keys. To view a detailed description of these keys and - what they do, ensure that the - Usage entry is highlighted and that the - [Select] button is selected, as shown in , then press Enter. + This menu system is controlled by the arrow keys, + Enter, Tab, + Space, and other keys. To view a detailed + description of these keys and what they do, ensure that the + Usage entry is highlighted and that + the [Select] button is selected, as shown + in , then press + Enter. - The instructions for using the menu system will be displayed. After - reviewing them, press Enter to return to the Main - Menu. + The instructions for using the menu system will be + displayed. After reviewing them, press Enter + to return to the Main Menu.
Selecting Usage from Sysinstall Main Menu @@ -1211,9 +1158,8 @@ Mounting root from ufs:/dev/md0c Selecting the Documentation Menu - From the Main Menu, select Doc with - the arrow keys and - press Enter. + From the Main Menu, select Doc + with the arrow keys and press Enter.
Selecting Documentation Menu @@ -1238,22 +1184,22 @@ Mounting root from ufs:/dev/md0c
It is important to read the documents provided. To view a - document, select it with the arrow keys and - press Enter. When finished reading a document, + document, select it with the arrow keys and press + Enter. When finished reading a document, press Enter to return to the Documentation Menu. To return to the Main Installation Menu, select - Exit with the - arrow keys and press Enter. + Exit with the arrow keys and press + Enter. Selecting the Keymap Menu - To change the keyboard mapping, use the arrow keys to select - Keymap from the menu and press - Enter. This is only required when + To change the keyboard mapping, use the arrow keys to + select Keymap from the menu and + press Enter. This is only required when using a non-standard or non-US keyboard.
@@ -1266,16 +1212,16 @@ Mounting root from ufs:/dev/md0c
- A different keyboard mapping may be chosen by selecting the - menu item using the up and down arrow keys and pressing - Space. - Pressing Space again will unselect the item. - When finished, choose the &gui.ok; using the arrow keys and press - Enter. + A different keyboard mapping may be chosen by selecting + the menu item using the up and down arrow keys and pressing + Space. Pressing Space again + will unselect the item. When finished, choose the &gui.ok; + using the arrow keys and press Enter. - Only a partial list is shown in this screen representation. - Selecting &gui.cancel; by pressing Tab will use the - default keymap and return to the Main Install Menu. + Only a partial list is shown in this screen + representation. Selecting &gui.cancel; by pressing + Tab will use the default keymap and return to + the Main Install Menu.
Sysinstall Keymap Menu @@ -1286,24 +1232,23 @@ Mounting root from ufs:/dev/md0c
- Installation Options Screen - Select Options and press + Select Options and press Enter. -
- Sysinstall Main Menu +
+ Sysinstall Main Menu - - - - - -
+ + + + + +
Sysinstall Options @@ -1320,12 +1265,12 @@ Mounting root from ufs:/dev/md0c to the version being installed. The description of the selected item will appear at the - bottom of the screen highlighted in blue. Notice that one of the - options is Use Defaults to reset all - values to startup defaults. + bottom of the screen highlighted in blue. Notice that one of + the options is Use Defaults to + reset all values to startup defaults. - Press F1 to read the help screen about the - various options. + Press F1 to read the help screen about + the various options. Press Q to return to the Main Install menu. @@ -1334,10 +1279,11 @@ Mounting root from ufs:/dev/md0c Begin a Standard Installation - The Standard installation is the - option recommended for those new to &unix; or &os;. Use the arrow - keys to select Standard and - then press Enter to start the installation. + The Standard installation is + the option recommended for those new to &unix; or &os;. Use + the arrow keys to select Standard + and then press Enter to start the + installation.
Begin Standard Installation @@ -1355,8 +1301,8 @@ Mounting root from ufs:/dev/md0c Allocating Disk Space The first task is to allocate disk space for &os;, and label - that space so that &man.sysinstall.8; can prepare - it. In order to do this you need to know how &os; expects to find + that space so that &man.sysinstall.8; can prepare it. In order + to do this you need to know how &os; expects to find information on the disk. @@ -1368,105 +1314,92 @@ Mounting root from ufs:/dev/md0c MS-DOS Microsoft Windows In a PC running a BIOS-dependent operating system such as - µsoft.windows;, the BIOS is able to abstract the - normal disk drive order and - the operating system goes along with the change. This allows the user - to boot from a disk drive other than the "primary - master". This is especially convenient for users - buy an identical second hard drive, and perform routine copies of the - first drive to the second drive. - If the - first drive fails, is attacked by a virus, or is scribbled upon by an - operating system defect, they can easily recover by instructing the BIOS - to logically swap the drives. It is like switching the cables on the - drives, without having to open the case. + µsoft.windows;, the BIOS is able to abstract the normal + disk drive order and the operating system goes along with the + change. This allows the user to boot from a disk drive other + than the "primary master". This is especially convenient for + users buy an identical second hard drive, and perform routine + copies of the first drive to the second drive. If the first + drive fails, is attacked by a virus, or is scribbled upon by + an operating system defect, they can easily recover by + instructing the BIOS to logically swap the drives. It is like + switching the cables on the drives, without having to open the + case. SCSI BIOS Systems with SCSI controllers often include BIOS - extensions which allow the SCSI drives to be re-ordered in a similar - fashion for up to seven drives. + extensions which allow the SCSI drives to be re-ordered in a + similar fashion for up to seven drives. - A user who is accustomed to taking advantage of these features may - become surprised when the results with &os; are not as expected. - &os; does not use the BIOS, and does not know the logical BIOS - drive mapping. This can lead to perplexing - situations, - especially when drives are physically identical in geometry - and have - been made as data clones of one another. + A user who is accustomed to taking advantage of these + features may become surprised when the results with &os; are + not as expected. &os; does not use the BIOS, and does not + know the logical BIOS drive mapping. This can + lead to perplexing situations, especially when drives are + physically identical in geometry and have been made as data + clones of one another. When using &os;, always restore the BIOS to natural drive numbering before installing &os;, and then leave it that way. - If drives - need to be switched around, take the time to - open the case and move the jumpers and cables. + If drives need to be switched around, take the time to open + the case and move the jumpers and cables. - An Illustration from the Files of Bill and Fred's Exceptional - Adventures: + An Illustration from the Files of Bill and Fred's + Exceptional Adventures: - Bill breaks-down an older Wintel box to make another &os; box - for Fred. Bill installs a single SCSI drive as SCSI unit zero and - installs &os; on it. + Bill breaks-down an older Wintel box to make another + &os; box for Fred. Bill installs a single SCSI drive as + SCSI unit zero and installs &os; on it. - Fred begins using the system, but after several days notices that - the older SCSI drive is reporting numerous + Fred begins using the system, but after several days + notices that the older SCSI drive is reporting numerous errors. - To address the - situation, Bill grabs an identical SCSI drive and installs - this drive as SCSI - unit four and makes an image copy from drive zero to drive four. Now - that the new drive is installed and functioning, Bill - decides - to start using it, so he uses features in the - SCSI BIOS to re-order the disk drives so that the system boots from - SCSI unit four. &os; boots and runs just fine. + To address the situation, Bill grabs an identical SCSI + drive and installs this drive as SCSI unit four and makes an + image copy from drive zero to drive four. Now that the new + drive is installed and functioning, Bill decides to start + using it, so he uses features in the SCSI BIOS to re-order + the disk drives so that the system boots from SCSI unit + four. &os; boots and runs just fine. - Fred continues his work and soon - decides that it is time to upgrade - to a - newer version of &os;. Bill removes SCSI unit zero because it was - a bit flaky and replaces it with another identical disk - drive. Bill then installs the new version of - &os; onto the new SCSI unit zero and the installation goes - well. + Fred continues his work and soon decides that it is time + to upgrade to a newer version of &os;. Bill removes SCSI + unit zero because it was a bit flaky and replaces it with + another identical disk drive. Bill then installs the new + version of &os; onto the new SCSI unit zero and the + installation goes well. - Fred uses the new version of &os; for a few days, and certifies - that it is good enough for use in the engineering department. It is - time to copy all of his work from the old version, so Fred - mounts - SCSI unit four which should contain the latest copy of the - older - &os; version. Fred - is dismayed to find that none of his work is present on SCSI - unit four. + Fred uses the new version of &os; for a few days, and + certifies that it is good enough for use in the engineering + department. It is time to copy all of his work from the old + version, so Fred mounts SCSI unit four which should contain + the latest copy of the older &os; version. Fred is dismayed + to find that none of his work is present on SCSI unit + four. It turns out that when Bill made an image copy of the - original SCSI unit zero onto - SCSI unit four, unit four became the new clone. - When Bill re-ordered the SCSI BIOS so that he could boot from - SCSI unit four, - &os; was still running on SCSI unit zero. - Making this kind of BIOS change causes some or all of the - boot and - loader code to be fetched from the selected BIOS drive. But - when the - &os; kernel drivers take over, the BIOS drive numbering is - ignored, and &os; transitions back to normal drive - numbering. - In this example, the system continued to operate on the - original SCSI unit zero, and all of Fred's data was there, not on SCSI - unit four. The fact that the system appeared to be running on SCSI - unit four was simply an artifact of human expectations. + original SCSI unit zero onto SCSI unit four, unit four + became the new clone. When Bill re-ordered + the SCSI BIOS so that he could boot from SCSI unit four, + &os; was still running on SCSI unit zero. Making this kind + of BIOS change causes some or all of the boot and loader + code to be fetched from the selected BIOS drive. But when + the &os; kernel drivers take over, the BIOS drive numbering + is ignored, and &os; transitions back to normal drive + numbering. In this example, the system continued to operate + on the original SCSI unit zero, and all of Fred's data was + there, not on SCSI unit four. The fact that the system + appeared to be running on SCSI unit four was simply an + artifact of human expectations. - Fortunately, the older SCSI - unit zero was retrieved and all of Fred's work was - restored. + Fortunately, the older SCSI unit zero was retrieved and + all of Fred's work was restored. - Although SCSI drives were used in this illustration, the concepts - apply equally to IDE drives. + Although SCSI drives were used in this illustration, the + concepts apply equally to IDE drives. @@ -1474,8 +1407,7 @@ Mounting root from ufs:/dev/md0c Creating Slices Using FDisk After choosing to begin a standard installation in - &man.sysinstall.8;, this - message will appear: + &man.sysinstall.8;, this message will appear: Message In the next menu, you will need to set up a DOS-style ("fdisk") @@ -1489,12 +1421,12 @@ Mounting root from ufs:/dev/md0c [ Press enter or space ] - Press Enter and - a list of all the hard drives that the kernel found when it - carried out the device probes will be displayed. - shows an example from a - system with two IDE disks called - ad0 and ad2. + Press Enter and a list of all the hard + drives that the kernel found when it carried out the device + probes will be displayed. shows an example from a + system with two IDE disks called ad0 and + ad2.
Select Drive for FDisk @@ -1506,63 +1438,60 @@ Mounting root from ufs:/dev/md0c
- Note that ad1 is not - listed here. + Note that ad1 is not listed + here. - Consider two IDE hard disks where one - is the master on the first IDE controller and one is the - master on - the second IDE controller. If &os; numbered these as - ad0 and - ad1, everything would work. + Consider two IDE hard disks where one is the master on the + first IDE controller and one is the master on the second IDE + controller. If &os; numbered these as + ad0 and ad1, + everything would work. But if a third disk is later added as the slave device on - the - first IDE controller, it would now be ad1, - and the previous ad1 would become - ad2. Because device names - are used to find filesystems, - some filesystems may no longer - appear correctly, requiring a change to the &os; + the first IDE controller, it would now be + ad1, and the previous + ad1 would become + ad2. Because device names are used to + find filesystems, some filesystems may no longer appear + correctly, requiring a change to the &os; configuration. - To work around this, the kernel can be configured to name IDE - disks based on where they are and not the order in which they - were - found. With this scheme, the master disk on the second IDE - controller will always be + To work around this, the kernel can be configured to name + IDE disks based on where they are and not the order in which + they were found. With this scheme, the master disk on the + second IDE controller will always be ad2, even if there are no ad0 or ad1 devices. - This configuration is the default for the &os; kernel, which - is why the display in this example shows - ad0 and - ad2. The machine on which this screenshot - was taken had IDE disks on both master channels of the IDE - controllers and no disks on the slave channels. + This configuration is the default for the &os; kernel, + which is why the display in this example shows + ad0 and ad2. The + machine on which this screenshot was taken had IDE disks on + both master channels of the IDE controllers and no disks on + the slave channels. - Select the disk on which to install &os;, - and then press &gui.ok;. - FDisk will start, with a display similar to - that shown in . + Select the disk on which to install &os;, and then press + &gui.ok;. FDisk will start, with a + display similar to that shown in . - The FDisk display is broken into three - sections. + The FDisk display is broken + into three sections. - The first section, covering the first two lines of the display, - shows details about the currently selected disk, including its &os; - name, the disk geometry, and the total size of the disk. + The first section, covering the first two lines of the + display, shows details about the currently selected disk, + including its &os; name, the disk geometry, and the total size + of the disk. - The second section shows the slices that are currently on the - disk, where they start and end, how large they are, the name &os; - gives them, and their description and sub-type. This example shows two - small unused slices which are artifacts of disk layout schemes - on the - PC. It also shows one large FAT slice, which - appears as C: in - &windows;, and an extended slice, which may contain other - drive letters in &windows;. + The second section shows the slices that are currently on + the disk, where they start and end, how large they are, the + name &os; gives them, and their description and sub-type. + This example shows two small unused slices which are artifacts + of disk layout schemes on the PC. It also shows one large + FAT slice, which appears as + C: in &windows;, and an extended slice, + which may contain other drive letters in &windows;. The third section shows the commands that are available in FDisk. @@ -1581,36 +1510,32 @@ Mounting root from ufs:/dev/md0c This step varies, depending on how the disk is to be sliced. - To install &os; to the entire disk, which will delete - all the other data on this disk, press A, - which - corresponds to the Use Entire Disk option. - The existing slices will be removed and replaced with a small - area - flagged as unused - and one large slice for &os;. Then, - select the newly created &os; slice using the arrow - keys and press S to mark the slice as being - bootable. The screen will then look similar to - . Note the - A in the Flags column, which - indicates that this slice is active, and will be - booted from. + To install &os; to the entire disk, which will delete all + the other data on this disk, press A, which + corresponds to the Use Entire Disk + option. The existing slices will be removed and replaced with + a small area flagged as unused and one + large slice for &os;. Then, select the newly created &os; + slice using the arrow keys and press S to + mark the slice as being bootable. The screen will then look + similar to . Note the + A in the Flags column, + which indicates that this slice is + active, and will be booted from. If an existing slice needs to be deleted to make space for - &os;, select the slice using the arrow keys and - press D. Then, press C to - be prompted for the size of the slice to create. Enter the + &os;, select the slice using the arrow keys and press + D. Then, press C to be + prompted for the size of the slice to create. Enter the appropriate value and press Enter. The - default - value in this box represents the largest possible slice to - make, which could be the largest contiguous block of unallocated - space or the size of the entire hard disk. + default value in this box represents the largest possible + slice to make, which could be the largest contiguous block of + unallocated space or the size of the entire hard disk. - If you have already made space for &os; - then you can - press C to create a new slice. Again, you will be - prompted for the size of slice you would like to create. + If you have already made space for &os; then you can press + C to create a new slice. Again, you will be + prompted for the size of slice you would like to + create.
Fdisk Partition Using Entire Disk @@ -1623,39 +1548,35 @@ Mounting root from ufs:/dev/md0c
When finished, press Q. Any changes will - be - saved in &man.sysinstall.8;, but will not yet be - written to disk. + be saved in &man.sysinstall.8;, but will not yet be written to + disk. Install a Boot Manager The next menu provides the option to install a boot - manager. In general, - install the &os; boot manager if: + manager. In general, install the &os; boot manager if: There is more than one drive and &os; will be - installed onto - a drive other than the first one. + installed onto a drive other than the first one. &os; will be installed alongside another operating - system - on the same disk, and you want to choose whether to start &os; - or the other operating system when the computer + system on the same disk, and you want to choose whether to + start &os; or the other operating system when the computer starts. - If &os; is going to be the only operating system on - this machine, installed on the first hard disk, then the + If &os; is going to be the only operating system on this + machine, installed on the first hard disk, then the Standard boot manager will suffice. - Choose None if using a - third-party boot manager capable of booting &os;. + Choose None if using a third-party + boot manager capable of booting &os;. Make a selection and press Enter. @@ -1670,8 +1591,8 @@ Mounting root from ufs:/dev/md0c
The help screen, reached by pressing F1, - discusses the problems that can be encountered when trying to share - the hard disk between operating systems. + discusses the problems that can be encountered when trying to + share the hard disk between operating systems. @@ -1679,14 +1600,14 @@ 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. To - install &os; on to more than one disk, select another - disk and repeat the slice process using + install &os; on to more than one disk, select another disk and + repeat the slice process using FDisk. - If installing &os; on a drive other than the - first drive, the &os; boot manager needs to be installed on - both drives. + If installing &os; on a drive other than the first + drive, the &os; boot manager needs to be installed on both + drives.
@@ -1700,13 +1621,11 @@ Mounting root from ufs:/dev/md0c
Use Tab to toggle between the last drive - selected, &gui.ok;, and - &gui.cancel;. + selected, &gui.ok;, and &gui.cancel;. - Press Tab once to toggle to - &gui.ok;, then - press Enter - to continue with the installation. + Press Tab once to toggle to &gui.ok;, + then press Enter to continue with the + installation. @@ -1717,24 +1636,20 @@ Mounting root from ufs:/dev/md0c Remember that each partition is lettered, from a through to h, and that partitions b, c, and - d have conventional meanings that should - be adhered - to. + d have conventional meanings that should be + adhered to. Certain applications can benefit from particular partition schemes, especially when laying out partitions across more - than - one disk. However, for a first &os; installation, do - not give too much thought to how to partition the disk. It - is more important to install &os; and start learning how to - use it. You can always re-install &os; to change the - partition + than one disk. However, for a first &os; installation, do not + give too much thought to how to partition the disk. It is + more important to install &os; and start learning how to use + it. You can always re-install &os; to change the partition scheme after becoming more familiar with the operating system. - The following scheme features four partitions: one - for swap space and - three for filesystems. + The following scheme features four partitions: one for + swap space and three for filesystems. Partition Layout for First Disk @@ -1765,12 +1680,12 @@ Mounting root from ufs:/dev/md0c 1 GB - This is the root filesystem. Every other filesystem - will be mounted somewhere under this one. 1 GB is a - reasonable size for this filesystem as user files - should not be stored here and - a regular &os; install will put - about 128 MB of data here. + This is the root filesystem. Every other + filesystem will be mounted somewhere under this one. + 1 GB is a reasonable size for this filesystem as + user files should not be stored here and a regular + &os; install will put about 128 MB of data + here. @@ -1780,23 +1695,20 @@ Mounting root from ufs:/dev/md0c 2-3 x RAM - The system's swap space is kept on the b partition. - Choosing the right amount of swap space can be a bit of an - art. A good rule of thumb is that swap - space should be two or three times as much as the - available physical memory (RAM). - There should be at least 64 MB of swap, so if - there is - less than 32 MB of RAM in the computer, set - the swap amount to 64 MB. - If there is more than one disk, swap - space can be put on each disk. &os; will then use - each disk for - swap, which effectively speeds up the act of swapping. In - this case, calculate the total amount of swap needed - and divide this by the number of - disks to give the amount of swap - to put on each disk. + The system's swap space is kept on the + b partition. Choosing the right + amount of swap space can be a bit of an art. A good + rule of thumb is that swap space should be two or + three times as much as the available physical memory + (RAM). There should be at least 64 MB of swap, + so if there is less than 32 MB of RAM in the + computer, set the swap amount to 64 MB. If there + is more than one disk, swap space can be put on each + disk. &os; will then use each disk for swap, which + effectively speeds up the act of swapping. In this + case, calculate the total amount of swap needed and + divide this by the number of disks to give the amount + of swap to put on each disk. @@ -1806,16 +1718,15 @@ Mounting root from ufs:/dev/md0c 512 MB to 4096 MB - /var - contains - files that are constantly varying, such as - log files and other administrative files. Many - of these files are read from or written to extensively - during - &os;'s day-to-day running. Putting these files on another + /var contains files that are + constantly varying, such as log files and other + administrative files. Many of these files are read + from or written to extensively during &os;'s + day-to-day running. Putting these files on another filesystem allows &os; to optimize the access of these - files without affecting other files in other directories that - do not have the same access pattern. + files without affecting other files in other + directories that do not have the same access + pattern. @@ -1837,13 +1748,13 @@ Mounting root from ufs:/dev/md0c The values above are given as example and should be used by experienced users only. Users are encouraged to use the automatic partition layout called Auto - Defaults by the &os; partition editor. + Defaults by the &os; partition editor. - If installing &os; on to more than one disk, - create partitions in the other configured slices. - The easiest way to do this is to create two partitions on - each disk, one for the swap space, and one for a filesystem. + If installing &os; on to more than one disk, create + partitions in the other configured slices. The easiest way to + do this is to create two partitions on each disk, one for the + swap space, and one for a filesystem.
Partition Layout for Subsequent Disks @@ -1874,9 +1785,9 @@ Mounting root from ufs:/dev/md0c See description - Swap space can be split across - each disk. Even though the a partition is - free, convention dictates that swap space stays on the + Swap space can be split across each disk. Even + though the a partition is free, + convention dictates that swap space stays on the b partition. @@ -1887,22 +1798,20 @@ Mounting root from ufs:/dev/md0c Rest of disk - The rest of the disk is taken up with one big partition. - This could easily be put on the a - partition, instead of the e partition. - However, convention says that the a - partition on a slice is reserved for the filesystem that will - be the root (/) - filesystem. Following + The rest of the disk is taken up with one big + partition. This could easily be put on the + a partition, instead of the + e partition. However, convention + says that the a partition on a + slice is reserved for the filesystem that will be the + root (/) filesystem. Following this convention is not necessary, but - &man.sysinstall.8; uses it, so following it - makes the installation slightly cleaner. - This filesystem can be mounted anywhere; this example - mounts it as - /diskn, - where - n is a number that changes for each - disk. + &man.sysinstall.8; uses it, so following it makes the + installation slightly cleaner. This filesystem can be + mounted anywhere; this example mounts it as /diskn, + where n is a number that + changes for each disk. @@ -1932,20 +1841,19 @@ Mounting root from ufs:/dev/md0c The first few lines show the name of the disk being worked on and the slice that contains the partitions to create. At this point, Disklabel - calls - this the Partition name rather than slice - name. - This display also shows the amount of free space within the slice; - that is, space that was set aside in the slice, but that has not yet - been assigned to a partition. + calls this the Partition name rather than + slice name. This display also shows the amount of free space + within the slice; that is, space that was set aside in the + slice, but that has not yet been assigned to a + partition. - The middle of the display shows the partitions that have been - created, the name of the filesystem that each partition contains, - their size, and some options pertaining to the creation of the - filesystem. + The middle of the display shows the partitions that have + been created, the name of the filesystem that each partition + contains, their size, and some options pertaining to the + creation of the filesystem. - The bottom third of the screen shows the keystrokes that are valid - in Disklabel. + The bottom third of the screen shows the keystrokes that + are valid in Disklabel.
Sysinstall Disklabel Editor @@ -1957,22 +1865,21 @@ Mounting root from ufs:/dev/md0c
- Disklabel can automatically create - partitions and assign them default sizes. The default sizes - are calculated with the help of an internal partition sizing algorithm - based on the disk size. - Press A to see a display similar to that - shown in . Depending on the size of + Disklabel can automatically + create partitions and assign them default sizes. The default + sizes are calculated with the help of an internal partition + sizing algorithm based on the disk size. Press + A to see a display similar to that shown in + . Depending on the size of the disk, the defaults may or may not be appropriate. - - The default partitioning assigns - /tmp its own - partition instead - of being part of the / partition. This - helps avoid filling the / partition with - temporary files. - + + The default partitioning assigns + /tmp its own partition instead of + being part of the / partition. This + helps avoid filling the / partition + with temporary files. +
Sysinstall Disklabel Editor with Auto Defaults @@ -1984,26 +1891,21 @@ Mounting root from ufs:/dev/md0c
- To - replace the default partitions, - use the arrow keys to select the first partition and press - D to delete it. Repeat this to delete all the - suggested partitions. + To replace the default partitions, use the arrow keys to + select the first partition and press D to + delete it. Repeat this to delete all the suggested + partitions. To create the first partition, a, - mounted as - /, make sure the - proper disk slice - at the top of - the screen is selected and press C. A dialog box - will appear, prompting for the size of the new partition, - as shown - in . The size can - be entered as - the number of disk blocks to use or as a - number followed by either M for megabytes, - G for gigabytes, or C for - cylinders. + mounted as /, make sure the proper disk + slice at the top of the screen is selected and press + C. A dialog box will appear, prompting for + the size of the new partition, as shown in . The size can be entered + as the number of disk blocks to use or as a number followed by + either M for megabytes, + G for gigabytes, or C + for cylinders.
Free Space for Root Partition @@ -2015,12 +1917,12 @@ Mounting root from ufs:/dev/md0c
- The default size shown will create a partition that takes up the - rest of the slice. If using the partition sizes described - in the earlier example, delete the existing figure using - Backspace, and then type in - 512M, as shown in - . Then press + The default size shown will create a partition that takes + up the rest of the slice. If using the partition sizes + described in the earlier example, delete the existing figure + using Backspace, and then type in + 512M, as shown in . Then press &gui.ok;.
@@ -2034,10 +1936,10 @@ Mounting root from ufs:/dev/md0c
After choosing the partition's size, the installer will - ask whether - this partition will contain a filesystem or swap space. The dialog - box is shown in . This first - partition will contain a filesystem, so check that + ask whether this partition will contain a filesystem or swap + space. The dialog box is shown in . This first partition + will contain a filesystem, so check that FS is selected and press Enter. @@ -2051,13 +1953,11 @@ Mounting root from ufs:/dev/md0c - Finally, tell - Disklabel where the filesystem will - be - mounted. The dialog box is shown in + Finally, tell Disklabel where + the filesystem will be mounted. The dialog box is shown in . Type - /, and - then press Enter. + /, and then press + Enter.
Choose the Root Mount Point @@ -2070,19 +1970,16 @@ Mounting root from ufs:/dev/md0c
The display will then update to show the newly created - partition. Repeat this procedure for the other - partitions. When creating the swap partition, it will not - prompt for the filesystem mount point. When creating the - final partition, - /usr, leave the - suggested size as is to + partition. Repeat this procedure for the other partitions. + When creating the swap partition, it will not prompt for the + filesystem mount point. When creating the final partition, + /usr, leave the suggested size as is to use the rest of the slice. The final &os; DiskLabel Editor screen will appear similar - to - , although the values - chosen may - be different. Press Q to finish. + to , although the values + chosen may be different. Press Q to + finish.
Sysinstall Disklabel Editor @@ -2102,42 +1999,40 @@ Mounting root from ufs:/dev/md0c Select the Distribution Set - Deciding which distribution set to install will depend largely - on the intended use of the system and the amount of disk space - available. The predefined options range from installing the - smallest possible configuration to everything. Those who are - new to &unix; or &os; should select one - of these canned options. Customizing a distribution set is - typically for the more experienced user. + Deciding which distribution set to install will depend + largely on the intended use of the system and the amount of + disk space available. The predefined options range from + installing the smallest possible configuration to everything. + Those who are new to &unix; or &os; should select one of these + canned options. Customizing a distribution set is typically + for the more experienced user. Press F1 for more information on the distribution set options and what they contain. When finished - reviewing the help, press Enter to return - to the Select Distributions Menu. + reviewing the help, press Enter to return to + the Select Distributions Menu. If a graphical user interface is desired, the configuration of &xorg; and - selection of a default - desktop must be done after the installation of &os;. More - information regarding the installation and configuration of a - &xorg; can be found in . + selection of a default desktop must be done after the + installation of &os;. More information regarding the + installation and configuration of a + &xorg; can be found in . - If compiling a custom kernel is anticipated, select an option - which includes the source code. For more information on why a - custom kernel should be built or how to build a custom kernel, see - . + If compiling a custom kernel is anticipated, select an + option which includes the source code. For more information + on why a custom kernel should be built or how to build a + custom kernel, see . - The most versatile system is one that includes - everything. If there is adequate disk space, select - All, as shown in - , by using the arrow keys - and + The most versatile system is one that includes everything. + If there is adequate disk space, select + All, as shown in , by using the arrow keys and pressing Enter. If there is a concern about - disk - space, consider using an option that is more suitable for the - situation. - Do not fret over the perfect choice, as other distributions can be - added after installation. + disk space, consider using an option that is more suitable for + the situation. Do not fret over the perfect choice, as other + distributions can be added after installation.
Choose Distributions @@ -2153,14 +2048,13 @@ Mounting root from ufs:/dev/md0c Installing the Ports Collection - After selecting the desired distribution, an opportunity to - install the &os; Ports Collection is presented. The Ports + After selecting the desired distribution, an opportunity + to install the &os; Ports Collection is presented. The Ports Collection is an easy and convenient way to install software - as it provides a collection of files that - automate the downloading, compiling, and installation - of third-party software packages. - discusses how to use the Ports - Collection. + as it provides a collection of files that automate the + downloading, compiling, and installation of third-party + software packages. discusses how to + use the Ports Collection. The installation program does not check to see if you have adequate space. Select this option only if you have @@ -2169,7 +2063,7 @@ Mounting root from ufs:/dev/md0c You can safely assume a larger value for more recent versions of &os;. - User Confirmation Requested + User Confirmation Requested Would you like to install the FreeBSD ports collection? This will give you ready access to over &os.numports; ported software packages, @@ -2188,10 +2082,10 @@ Mounting root from ufs:/dev/md0c [ Yes ] No - Select &gui.yes; with the arrow keys to - install the Ports Collection or &gui.no; to - skip this option. Press Enter to continue. - The Choose Distributions menu will redisplay. + Select &gui.yes; with the arrow keys to install the Ports + Collection or &gui.no; to skip this option. Press + Enter to continue. The Choose Distributions + menu will redisplay.
Confirm Distributions @@ -2204,10 +2098,9 @@ Mounting root from ufs:/dev/md0c
Once satisfied with the options, select - Exit with the arrow keys, ensure that - &gui.ok; is highlighted, and press + Exit with the arrow keys, ensure + that &gui.ok; is highlighted, and press Enter to continue. - @@ -2216,8 +2109,8 @@ Mounting root from ufs:/dev/md0c If installing from a CD/DVD, use the arrow keys to highlight Install from a &os; CD/DVD. Ensure - that &gui.ok; is highlighted, then press - Enter to proceed with the installation. + that &gui.ok; is highlighted, then press Enter + to proceed with the installation. For other methods of installation, select the appropriate option and follow the instructions. @@ -2254,18 +2147,18 @@ Mounting root from ufs:/dev/md0c server - This option makes all FTP transfers - use Active - mode. This will not work through firewalls, but will - often work with older FTP servers that do not support - passive mode. If the connection hangs with passive - mode (the default), try using active mode. + This option makes all FTP transfers use + Active mode. This will not work through + firewalls, but will often work with older FTP servers + that do not support passive mode. If the connection + hangs with passive mode (the default), try using active + mode. - FTP Passive: Install from an FTP server through a - firewall + FTP Passive: Install from an FTP server + through a firewall This option instructs &man.sysinstall.8; to use @@ -2274,8 +2167,7 @@ Mounting root from ufs:/dev/md0c passive mode for all FTP operations. This allows the user to pass through firewalls that do not allow - incoming connections on random TCP ports. - + incoming connections on random TCP ports. @@ -2287,7 +2179,7 @@ Mounting root from ufs:/dev/md0c This option instructs &man.sysinstall.8; to use the HTTP protocol to connect to a proxy for all FTP operations. The proxy will translate the requests and - send them to the FTP server. This allows the user to + send them to the FTP server. This allows the user to pass through firewalls that do not allow FTP, but offer a HTTP proxy FTP @@ -2301,22 +2193,22 @@ Mounting root from ufs:/dev/md0c For a proxy FTP server, give the name of the server as part of the username, after an @ sign. The proxy server then fakes the real server. For - example, to install from - ftp.FreeBSD.org, using the proxy - FTP server foo.example.com, - listening on port 1234, go to the options menu, set the FTP - username to ftp@ftp.FreeBSD.org and the - password to an email address. As the installation media, - specify FTP (or passive FTP, if the proxy supports it), and - the URL + example, to install from ftp.FreeBSD.org, using the + proxy FTP server foo.example.com, listening + on port 1234, go to the options menu, set the FTP username to + ftp@ftp.FreeBSD.org and the password to an + email address. As the installation media, specify FTP (or + passive FTP, if the proxy supports it), and the URL ftp://foo.example.com:1234/pub/FreeBSD. - Since /pub/FreeBSD - from - ftp.FreeBSD.org is proxied under - foo.example.com, the proxy - will fetch the files - from ftp.FreeBSD.org as the + Since /pub/FreeBSD from ftp.FreeBSD.org is proxied + under foo.example.com, the proxy + will fetch the files from ftp.FreeBSD.org as the installer requests them. @@ -2338,13 +2230,13 @@ Mounting root from ufs:/dev/md0c [ Yes ] No - Select &gui.yes; and press - Enter to proceed. + Select &gui.yes; and press Enter to + proceed. - The installation time will vary according to the distribution - chosen, installation media, and the speed of the computer. - There will be a series of - messages displayed, indicating the status. + The installation time will vary according to the + distribution chosen, installation media, 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 displayed: @@ -2363,13 +2255,12 @@ do so by typing: /usr/sbin/sysinstall. [ Press enter or space ] - Press Enter to proceed with post-installation - configurations. + Press Enter to proceed with + post-installation configurations. - Selecting &gui.no; and pressing - Enter will abort - the installation so no changes will be made to the system. The - following message will appear: + Selecting &gui.no; and pressing Enter will + abort the installation so no changes will be made to the system. + The following message will appear: Message Installation complete with some errors. You may wish to scroll @@ -2380,8 +2271,8 @@ installation menus to retry whichever operations have failed. [ OK ] This message is generated because nothing was installed. - Pressing Enter will return to the - Main Installation Menu to exit the installation. + Pressing Enter will return to the Main + Installation Menu to exit the installation. @@ -2389,24 +2280,20 @@ installation menus to retry whichever operations have failed. Configuration of various options can be performed after a successful installation. An option can be configured by - re-entering the - configuration menus before booting the new &os; - system or after boot using - &man.sysinstall.8; - and then selecting the - Configure menu. + re-entering the configuration menus before booting the new &os; + system or after boot using &man.sysinstall.8; and then selecting + the Configure menu. Network Device Configuration If PPP was previously configured for an FTP install, this - screen - will not display and can be configured after boot as described - above. + screen will not display and can be configured after boot as + described above. For detailed information on Local Area Networks and - configuring &os; as a gateway/router refer to the - Advanced Networking + configuring &os; as a gateway/router refer to the Advanced Networking chapter. User Confirmation Requested @@ -2414,9 +2301,9 @@ installation menus to retry whichever operations have failed. [ Yes ] No - To configure a network device, select - &gui.yes; and press Enter. - Otherwise, select &gui.no; to continue. + To configure a network device, select &gui.yes; and press + Enter. Otherwise, select &gui.no; to + continue.
Selecting an Ethernet Device @@ -2428,8 +2315,8 @@ installation menus to retry whichever operations have failed.
- Select the interface to be configured with the arrow keys and press - Enter. + Select the interface to be configured with the arrow keys + and press Enter. User Confirmation Requested Do you want to try IPv6 configuration of the interface? @@ -2437,15 +2324,14 @@ installation menus to retry whichever operations have failed. Yes [ No ] In this private local area network, the current Internet - type protocol (IPv4) was sufficient and &gui.no; - was selected with the arrow keys and Enter - pressed. + type protocol (IPv4) was sufficient and + &gui.no; was selected with the arrow keys and + Enter pressed. If connected to an existing IPv6 - network - with an RA server, choose - &gui.yes; and press Enter. - It will take several seconds to scan for RA servers. + network with an RA server, choose + &gui.yes; and press Enter. It will take + several seconds to scan for RA servers. User Confirmation Requested Do you want to try DHCP configuration of the interface? @@ -2453,21 +2339,21 @@ installation menus to retry whichever operations have failed. Yes [ No ] If Dynamic Host Configuration Protocol - DHCP) is not required, - select &gui.no; with the arrow keys and press - Enter. + DHCP) is not required, select &gui.no; with + the arrow keys and press Enter. - Selecting &gui.yes; will execute - &man.dhclient.8; and, if successful, will fill - in the network configuration information automatically. Refer to - for more information. + Selecting &gui.yes; will execute &man.dhclient.8; and, if + successful, will fill in the network configuration information + automatically. Refer to for + more information. The following Network Configuration screen shows the - configuration of the Ethernet device for a system that will act - as the gateway for a Local Area Network. + configuration of the Ethernet device for a system that will + act as the gateway for a Local Area Network.
- Set Network Configuration for <replaceable>ed0</replaceable> + Set Network Configuration for + <replaceable>ed0</replaceable> @@ -2476,16 +2362,16 @@ installation menus to retry whichever operations have failed.
- Use Tab to select the information fields and - fill in appropriate information: + Use Tab to select the information fields + and fill in appropriate information: Host - The fully-qualified hostname, such as - k6-2.example.com in + The fully-qualified hostname, such as k6-2.example.com in this case. @@ -2494,9 +2380,10 @@ installation menus to retry whichever operations have failed. Domain - The name of the domain that the machine is - in, such as example.com - for this case. + The name of the domain that the machine is in, such + as example.com for this + case. @@ -2506,11 +2393,10 @@ installation menus to retry whichever operations have failed. IP address of host forwarding packets to non-local destinations. This must be filled in if the machine is - a node - on the network. Leave this field blank - if the machine is the gateway to the Internet for the - network. The IPv4 Gateway is also known as the default - gateway or default route. + a node on the network. Leave this field + blank if the machine is the gateway to the + Internet for the network. The IPv4 Gateway is also + known as the default gateway or default route. @@ -2519,10 +2405,11 @@ installation menus to retry whichever operations have failed. IP address of the local DNS server. There is no - local - DNS server on this private local area network so the IP - address of the provider's DNS server - (208.163.10.2) was used. + local DNS server on this private local area network so + the IP address of the provider's DNS server + (208.163.10.2) was + used. @@ -2531,7 +2418,8 @@ installation menus to retry whichever operations have failed. The IP address to be used for this interface was - 192.168.0.1 + 192.168.0.1 @@ -2540,11 +2428,11 @@ installation menus to retry whichever operations have failed. The address block being used for this local area - network is - 192.168.0.0 - + network is 192.168.0.0 - 192.168.0.255 - with a netmask of - 255.255.255.0. + with a netmask of 255.255.255.0. @@ -2559,21 +2447,19 @@ installation menus to retry whichever operations have failed. - Use Tab to select &gui.ok; - when finished and press Enter. - + Use Tab to select &gui.ok; when finished + and press Enter. User Confirmation Requested Would you like to bring the ed0 interface up right now? [ Yes ] No - Choosing &gui.yes; and pressing - Enter will bring - the machine up on the network so it is ready for use. - However, - this does not accomplish much during installation, since - the machine still needs to be rebooted. + Choosing &gui.yes; and pressing Enter + will bring the machine up on the network so it is ready for + use. However, this does not accomplish much during + installation, since the machine still needs to be + rebooted. @@ -2584,11 +2470,10 @@ installation menus to retry whichever operations have failed. [ Yes ] No - If the machine will be acting as the gateway for a local area - network and forwarding packets between other machines, select - &gui.yes; and press Enter. - If the machine is a node on a network, - select &gui.no; and press + If the machine will be acting as the gateway for a local + area network and forwarding packets between other machines, + select &gui.yes; and press Enter. If the + machine is a node on a network, select &gui.no; and press Enter to continue. @@ -2600,15 +2485,15 @@ Do you want to configure inetd and the network services that it provides? Yes [ No ] - If &gui.no; is selected, various services - will not be enabled. These services can be enabled after - installation by editing - /etc/inetd.conf with a text editor. - See for more information. + If &gui.no; is selected, various services will not be + enabled. These services can be enabled after installation by + editing /etc/inetd.conf with a text + editor. See for more + information. - Otherwise, select &gui.yes; to - configure these services during install. An additional - confirmation will display: + Otherwise, select &gui.yes; to configure these services + during install. An additional confirmation will + display: User Confirmation Requested The Internet Super Server (inetd) allows a number of simple Internet @@ -2635,9 +2520,9 @@ use the current settings. [ Yes ] No - Selecting &gui.yes; allows services to be enabled - by deleting the # at the beginning - of the lines representing those services. + Selecting &gui.yes; allows services to be enabled by + deleting the # at the beginning of the + lines representing those services.
Editing <filename>inetd.conf</filename> @@ -2649,10 +2534,9 @@ use the current settings.
- Once the edits are complete, press Esc - to display a menu which will exit the editor and save - the changes. - + Once the edits are complete, press Esc to + display a menu which will exit the editor and save the + changes. @@ -2668,10 +2552,10 @@ use the current settings. Yes [ No ] Selecting &gui.yes; will enable &man.sshd.8;, the daemon - for OpenSSH. This - allows secure remote access to the machine. For more - information about OpenSSH, see - . + for OpenSSH. This allows secure + remote access to the machine. For more information about + OpenSSH, see . @@ -2691,22 +2575,23 @@ use the current settings. Deny Anonymous FTP Selecting the default &gui.no; and pressing - Enter will still allow users who have accounts - with passwords to use FTP to access the machine. + Enter will still allow users who have + accounts with passwords to use FTP to access the + machine. Allow Anonymous FTP - Anyone can access the machine if - anonymous FTP connections are allowed. The security - implications should be - considered before enabling this option. For more information - about security, see . + Anyone can access the machine if anonymous FTP + connections are allowed. The security implications should + be considered before enabling this option. For more + information about security, see . To allow anonymous FTP, use the arrow keys to select - &gui.yes; and press Enter. - An additional confirmation will display: + &gui.yes; and press Enter. An additional + confirmation will display: User Confirmation Requested Anonymous FTP permits un-authenticated users to connect to the system @@ -2729,9 +2614,8 @@ use the current settings. This message indicates that the FTP service will also have to be enabled in /etc/inetd.conf to allow anonymous FTP connections. Select &gui.yes; and - press - Enter to continue. The following screen - will display: + press Enter to continue. The following + screen will display:
Default Anonymous FTP Configuration @@ -2751,9 +2635,8 @@ use the current settings. UID - The user ID to assign to the anonymous - FTP user. All files uploaded will be owned by this - ID. + The user ID to assign to the anonymous FTP user. + All files uploaded will be owned by this ID. @@ -2794,11 +2677,11 @@ use the current settings. - The FTP root directory will be put in /var - by default. If there is not enough room there for the - anticipated FTP needs, use /usr instead - by setting the FTP root directory to - /usr/ftp. + The FTP root directory will be put in + /var by default. If there is not + enough room there for the anticipated FTP needs, use + /usr instead by setting the FTP root + directory to /usr/ftp. Once satisfied with the values, press Enter to continue. @@ -2808,9 +2691,8 @@ use the current settings. [ Yes ] No - If &gui.yes; is selected, press - Enter and the &man.ee.1; editor - will automatically start. + If &gui.yes; is selected, press Enter + and the &man.ee.1; editor will automatically start.
Edit the FTP Welcome Message @@ -2822,14 +2704,13 @@ use the current settings.
- Use the - instructions to change the message. Note the file name - location - at the bottom of the editor screen. + Use the instructions to change the message. Note the + file name location at the bottom of the editor + screen. - Press Esc and a pop-up menu will default - to a) leave editor. Press - Enter to exit and continue. Press + Press Esc and a pop-up menu will + default to a) leave editor. + Press Enter to exit and continue. Press Enter again to save any changes. @@ -2838,10 +2719,9 @@ use the current settings. Configure the Network File System The Network File System (NFS) allows - sharing of files across a - network. A machine can be configured as a server, a client, or - both. Refer to for more - information. + sharing of files across a network. A machine can be + configured as a server, a client, or both. Refer to for more information. NFS Server @@ -2852,12 +2732,10 @@ use the current settings. Yes [ No ] If there is no need for a NFS server, - select &gui.no; and press - Enter. + select &gui.no; and press Enter. - If &gui.yes; is chosen, a message will - pop-up indicating that /etc/exports - must be + If &gui.yes; is chosen, a message will pop-up indicating + that /etc/exports must be created. Message @@ -2867,8 +2745,8 @@ access to your local filesystems. Press [Enter] now to invoke an editor on /etc/exports [ OK ] - Press Enter to continue. A text editor will - start, allowing /etc/exports to be + Press Enter to continue. A text editor + will start, allowing /etc/exports to be edited.
@@ -2882,13 +2760,12 @@ Press [Enter] now to invoke an editor on /etc/exports
Use the instructions to add the exported filesystems. - Note the - file name location at the bottom of the editor + Note the file name location at the bottom of the editor screen. - Press Esc and a pop-up menu will default to - a) leave editor. Press - Enter to exit and continue. + Press Esc and a pop-up menu will + default to a) leave editor. + Press Enter to exit and continue. @@ -2902,26 +2779,24 @@ Press [Enter] now to invoke an editor on /etc/exports Yes [ No ] - With the arrow keys, select &gui.yes; - or &gui.no; as appropriate and - press Enter. + With the arrow keys, select &gui.yes; or &gui.no; as + appropriate and press Enter. System Console Settings - There are several options available to customize the system - console. + There are several options available to customize the + system console. User Confirmation Requested Would you like to customize your system console settings? [ Yes ] No - To view and configure the options, select - &gui.yes; and press - Enter. + To view and configure the options, select &gui.yes; and + press Enter.
System Console Configuration Options @@ -2933,8 +2808,8 @@ Press [Enter] now to invoke an editor on /etc/exports
- A commonly used option is the screen saver. Use the arrow keys - to select Saver and then press + A commonly used option is the screen saver. Use the arrow + keys to select Saver and then press Enter.
@@ -2947,15 +2822,16 @@ Press [Enter] now to invoke an editor on /etc/exports
- Select the desired screen saver using the arrow keys - and then press Enter. The System Console + Select the desired screen saver using the arrow keys and + then press Enter. The System Console Configuration menu will redisplay. - The default time interval is 300 seconds. To change the time - interval, select Saver again. At the - Screen Saver Options menu, select Timeout - using the arrow keys and press Enter. A pop-up - menu will appear: + The default time interval is 300 seconds. To change the + time interval, select Saver again. + At the Screen Saver Options menu, select + Timeout using the arrow keys and + press Enter. A pop-up menu will + appear:
Screen Saver Timeout @@ -2967,8 +2843,8 @@ Press [Enter] now to invoke an editor on /etc/exports
- The value can be changed, then select &gui.ok; - and press Enter to return to the System Console + The value can be changed, then select &gui.ok; and press + Enter to return to the System Console Configuration menu.
@@ -2989,22 +2865,21 @@ Press [Enter] now to invoke an editor on /etc/exports Setting the Time Zone - Setting the time zone allows the system to - automatically correct for any regional time changes and perform - other time zone related functions properly. + Setting the time zone allows the system to automatically + correct for any regional time changes and perform other time + zone related functions properly. The example shown is for a machine located in the Eastern time zone of the United States. The selections will vary - according - to the geographic location. + according to the geographic location. User Confirmation Requested Would you like to set this machine's time zone now? [ Yes ] No - Select &gui.yes; and press - Enter to set the time zone. + Select &gui.yes; and press Enter to set + the time zone. User Confirmation Requested Is this machine's CMOS clock set to UTC? If it is set to local time @@ -3012,9 +2887,9 @@ Press [Enter] now to invoke an editor on /etc/exports Yes [ No ] - Select &gui.yes; - or &gui.no; according to how the machine's - clock is configured, then press Enter. + Select &gui.yes; or &gui.no; according to how the + machine's clock is configured, then press + Enter.
Select the Region @@ -3039,8 +2914,8 @@ Press [Enter] now to invoke an editor on /etc/exports
- Select the appropriate country using the arrow keys - and press Enter. + Select the appropriate country using the arrow keys and + press Enter.
Select the Time Zone @@ -3061,20 +2936,18 @@ Press [Enter] now to invoke an editor on /etc/exports [ Yes ] No Confirm that the abbreviation for the time zone is - correct. - If it looks okay, press Enter to continue with - the post-installation configuration. + correct. If it looks okay, press Enter to + continue with the post-installation configuration. Mouse Settings - This option allows cut and paste in the - console and user programs using a 3-button mouse. If using a - 2-button - mouse, refer to &man.moused.8; for - details on emulating the 3-button style. This example depicts a - non-USB mouse configuration: + This option allows cut and paste in the console and user + programs using a 3-button mouse. If using a 2-button mouse, + refer to &man.moused.8; for details on emulating the 3-button + style. This example depicts a non-USB mouse + configuration: User Confirmation Requested Does this system have a PS/2, serial, or bus mouse? @@ -3095,8 +2968,9 @@ Press [Enter] now to invoke an editor on /etc/exports
- Use the arrow keys to select Type and - press Enter. + Use the arrow keys to select + Type and press + Enter.
Set Mouse Protocol @@ -3108,11 +2982,11 @@ Press [Enter] now to invoke an editor on /etc/exports
- The mouse used in this example is a PS/2 type, so the default - Auto is appropriate. To change the - mouse protocol, - use the arrow keys to select another option. Ensure that &gui.ok; is - highlighted and press Enter to exit this menu. + The mouse used in this example is a PS/2 type, so the + default Auto is appropriate. To + change the mouse protocol, use the arrow keys to select + another option. Ensure that &gui.ok; is highlighted and press + Enter to exit this menu.
Configure Mouse Port @@ -3124,8 +2998,9 @@ Press [Enter] now to invoke an editor on /etc/exports
- Use the arrow keys to select Port and - press Enter. + Use the arrow keys to select + Port and press + Enter.
Setting the Mouse Port @@ -3139,8 +3014,8 @@ Press [Enter] now to invoke an editor on /etc/exports This system had a PS/2 mouse, so the default PS/2 is appropriate. To change the - port, - use the arrow keys and then press Enter. + port, use the arrow keys and then press + Enter.
Enable the Mouse Daemon @@ -3169,11 +3044,10 @@ Press [Enter] now to invoke an editor on /etc/exports
Move the mouse around the screen to verify that the cursor - responds properly. If it does, select - &gui.yes; and press Enter. If - not, the mouse has not been configured correctly. Select - &gui.no; and try using different configuration - options. + responds properly. If it does, select &gui.yes; and press + Enter. If not, the mouse has not been + configured correctly. Select &gui.no; and try using different + configuration options. Select Exit with the arrow keys and press Enter to continue with the @@ -3181,16 +3055,15 @@ Press [Enter] now to invoke an editor on /etc/exports - Install Packages + Install Packages Packages are pre-compiled binaries and are a convenient way to install software. Installation of one package is shown for purposes of illustration. Additional packages can also be added at this - time if desired. After installation, - &man.sysinstall.8; can be used to add additional - packages. + time if desired. After installation, &man.sysinstall.8; can + be used to add additional packages. User Confirmation Requested The FreeBSD package collection is a collection of hundreds of @@ -3199,9 +3072,8 @@ Press [Enter] now to invoke an editor on /etc/exports [ Yes ] No - Select &gui.yes; and press - Enter to be presented with - the Package Selection screens: + Select &gui.yes; and press Enter to be + presented with the Package Selection screens:
Select Package Category @@ -3218,8 +3090,7 @@ Press [Enter] now to invoke an editor on /etc/exports All packages available will be displayed if All is selected. Otherwise, select - a - particular category. Highlight the selection with the arrow + a particular category. Highlight the selection with the arrow keys and press Enter. A menu will display showing all the packages available for @@ -3236,26 +3107,24 @@ Press [Enter] now to invoke an editor on /etc/exports
The bash shell is shown as - selected. - Select as many packages as desired by highlighting the package - and pressing - Space. A short description of each package - will - appear in the lower left corner of the screen. + selected. Select as many packages as desired by highlighting + the package and pressing Space. A short + description of each package will appear in the lower left + corner of the screen. Press Tab to toggle between the last selected package, &gui.ok;, and &gui.cancel;. - Once finished marking the packages for installation, - press Tab once to toggle to &gui.ok; and - press - Enter to return to the Package Selection menu. - - The left and right arrow keys will also toggle between &gui.ok; - and &gui.cancel;. This method can also be used to select &gui.ok; and - press Enter to return to the Package Selection + Once finished marking the packages for installation, press + Tab once to toggle to &gui.ok; and press + Enter to return to the Package Selection menu. + The left and right arrow keys will also toggle between + &gui.ok; and &gui.cancel;. This method can also be used to + select &gui.ok; and press Enter to return to + the Package Selection menu. +
Install Packages @@ -3266,9 +3135,10 @@ Press [Enter] now to invoke an editor on /etc/exports
- Use the Tab and arrow keys to select [ Install ] - and press Enter to see the installation - confirmation message: + Use the Tab and arrow keys to select + [ Install ] and press + Enter to see the installation confirmation + message:
Confirm Package Installation @@ -3282,8 +3152,8 @@ Press [Enter] now to invoke an editor on /etc/exports Select &gui.ok; and press Enter to start the package installation. Installation messages will appear - until all of the installations have - completed. Make note if there are any error messages. + until all of the installations have completed. Make note if + there are any error messages. The final configuration continues after packages are installed. If no packages are selected, select @@ -3294,11 +3164,12 @@ Press [Enter] now to invoke an editor on /etc/exports Add Users/Groups - Add at least one user during the installation so - that the system can be used without logging in as - root. The root partition is generally small - and running applications as root can quickly - fill it. A bigger danger is noted below: + Add at least one user during the installation so that the + system can be used without logging in as root. The root partition is + generally small and running applications as root can quickly fill it. A + bigger danger is noted below: User Confirmation Requested Would you like to add any initial user accounts to the system? Adding @@ -3308,8 +3179,8 @@ Press [Enter] now to invoke an editor on /etc/exports [ Yes ] No - Select &gui.yes; and press - Enter to continue with adding a user. + Select &gui.yes; and press Enter to + continue with adding a user.
Select User @@ -3334,9 +3205,10 @@ Press [Enter] now to invoke an editor on /etc/exports
- The following descriptions will appear in the lower part of - the screen as the items are selected with Tab - to assist with entering the required information: + The following descriptions will appear in the lower part + of the screen as the items are selected with + Tab to assist with entering the required + information: @@ -3411,19 +3283,19 @@ Press [Enter] now to invoke an editor on /etc/exports In this example, the login shell was changed from /bin/sh to /usr/local/bin/bash to use the - bash shell that was previously installed as - a package. Do not use a shell that does not exist or the user - will - not be able to login. The most common shell used in &os; - is the C shell, + bash shell that was previously + installed as a package. Do not use a shell that does not + exist or the user will not be able to login. The most common + shell used in &os; is the C shell, /bin/tcsh. - The user was also added to the wheel group - to be able to become a superuser with root - privileges. + The user was also added to the wheel group to be able to + become a superuser with root privileges. - Once satisfied, press &gui.ok; and - the User and Group Management menu will redisplay: + Once satisfied, press &gui.ok; and the User and Group + Management menu will redisplay:
Exit User and Group Management @@ -3436,9 +3308,8 @@ Press [Enter] now to invoke an editor on /etc/exports
Groups can also be added at this time. Otherwise, this - menu may be accessed using - &man.sysinstall.8; - at a later time. + menu may be accessed using &man.sysinstall.8; at a later + time. When finished adding users, select Exit with the arrow keys and press @@ -3446,7 +3317,8 @@ Press [Enter] now to invoke an editor on /etc/exports - Set the <systemitem class="username">root</systemitem> Password + Set the <systemitem class="username">root</systemitem> + Password Message Now you must set the system manager's password. @@ -3456,13 +3328,12 @@ Press [Enter] now to invoke an editor on /etc/exports [ Press enter or space ] - Press Enter to set the root - password. + Press Enter to set the root password. The password will need to be typed in twice correctly. - Do not forget this password. - Notice that the typed password is not echoed, nor - are asterisks displayed. + Do not forget this password. Notice that the typed password + is not echoed, nor are asterisks displayed. New password: Retype new password : @@ -3474,8 +3345,7 @@ Retype new password : Exiting Install - A message will ask if - configuration is complete: + A message will ask if configuration is complete: User Confirmation Requested Visit the general configuration menu for a chance to set any last @@ -3483,9 +3353,9 @@ Retype new password : Yes [ No ] - Select &gui.no; with the arrow keys - and press Enter to return to the Main - Installation Menu. + Select &gui.no; with the arrow keys and press + Enter to return to the Main Installation + Menu.
Exit Install @@ -3497,19 +3367,17 @@ Retype new password :
- Select [X Exit Install] with the arrow - keys and press Enter. The installer will - prompt to - confirm exiting the installation: + Select [X Exit Install] with the + arrow keys and press Enter. The installer + will prompt to confirm exiting the installation: User Confirmation Requested Are you sure you wish to exit? The system will reboot. [ Yes ] No - Select &gui.yes;. If booting from the CDROM drive, - the following message will remind you to remove the - disk: + Select &gui.yes;. If booting from the CDROM drive, the + following message will remind you to remove the disk: Message Be sure to remove the media from the drive. @@ -3517,43 +3385,41 @@ Retype new password : [ OK ] [ Press enter or space ] - The CDROM drive is locked until the machine - starts to reboot, then the disk can quickly - be removed from the drive. Press &gui.ok; to reboot. + The CDROM drive is locked until the machine starts to + reboot, then the disk can quickly be removed from the drive. + Press &gui.ok; to reboot. - The system will reboot so watch for any error messages that - may appear, see for more + The system will reboot so watch for any error messages + that may appear, see for more details. - Configure Additional Network Services + + Configure Additional Network Services + - TomRhodesContributed by + TomRhodesContributed + by - - Configuring network services can be a daunting - task for users that lack previous - knowledge in this area. Since networking and the Internet - are critical to all modern operating systems, - it is useful to have some understanding of + Configuring network services can be a daunting task for + users that lack previous knowledge in this area. Since + networking and the Internet are critical to all modern + operating systems, it is useful to have some understanding of &os;'s extensive networking capabilities. Network services are programs that accept input from - anywhere on the network. Since - there have been cases where bugs in network services have been - exploited by attackers, it is important to - only enable needed network services. If - in doubt, do not enable a network service until - it is needed. Services can be enabled - with &man.sysinstall.8; or by - editing + anywhere on the network. Since there have been cases where + bugs in network services have been exploited by attackers, it + is important to only enable needed network services. If in + doubt, do not enable a network service until it is needed. + Services can be enabled with &man.sysinstall.8; or by editing /etc/rc.conf. - Selecting the Networking option will display - a menu similar to the one below: + Selecting the Networking option will + display a menu similar to the one below:
Network Configuration Upper-level @@ -3569,30 +3435,27 @@ Retype new password : is covered in . Selecting the AMD option adds - support for &man.amd.8;. - This is usually used in conjunction with - NFS - for automatically mounting remote filesystems. + support for &man.amd.8;. This is usually used in conjunction + with NFS for automatically mounting remote + filesystems. - Next is the AMD Flags - option. When selected, a menu will pop up where - specific AMD flags can be entered. - The menu already contains a set of default options: + Next is the AMD Flags option. + When selected, a menu will pop up where specific + AMD flags can be entered. The menu already + contains a set of default options: -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map - sets the default mount - location which is specified here as - /.amd_mnt. - specifies the default log; - however, when &man.syslogd.8; is used, all log - activity will be sent to the system log daemon. - /host is used - to mount an exported file system from a remote - host, while /net + sets the default mount location which + is specified here as /.amd_mnt. + specifies the default + log; however, when &man.syslogd.8; is + used, all log activity will be sent to the system log daemon. + /host is used to mount an exported file + system from a remote host, while /net is used to mount an exported filesystem from an - IP address. The default - options for AMD exports are defined in + IP address. The default options for + AMD exports are defined in /etc/amd.map. @@ -3600,25 +3463,25 @@ Retype new password : anonymous - The Anon FTP option permits anonymous - FTP connections. Select this option to - make this machine an anonymous FTP server. - Be aware of the security risks involved with this option. - Another menu will be displayed to explain the security risks - and configuration in depth. + The Anon FTP option permits + anonymous FTP connections. Select this + option to make this machine an anonymous + FTP server. Be aware of the security risks + involved with this option. Another menu will be displayed to + explain the security risks and configuration in depth. The Gateway menu will configure - the machine to be a gateway. This menu - can also be used to unset the - Gateway option if - it was accidentally selected during installation. + the machine to be a gateway. This menu can also be used to + unset the Gateway option if it was + accidentally selected during installation. - The Inetd option can be used to configure - or completely disable &man.inetd.8;. + The Inetd option can be used to + configure or completely disable &man.inetd.8;. - The Mail option is used to configure the - system's default Mail Transfer Agent (MTA). - Selecting this option will bring up the following menu: + The Mail option is used to + configure the system's default Mail Transfer Agent + (MTA). Selecting this option will bring up + the following menu:
Select a Default MTA @@ -3631,45 +3494,41 @@ Retype new password :
This menu offers a choice as to which - MTA to install - and set as the default. An MTA is - a mail server which delivers email to users on the - system or the Internet. + MTA to install and set as the default. An + MTA is a mail server which delivers email + to users on the system or the Internet. Select Sendmail to install Sendmail as the default - MTA. Select - Sendmail local - to set Sendmail as the - default + MTA. Select Sendmail + local to set + Sendmail as the default MTA, but disable its ability to receive incoming email from the Internet. The other options, Postfix and - Exim, provide - alternatives to + Exim, provide alternatives to Sendmail. The next menu after the MTA menu is NFS client. This menu is used to configure the system to communicate with a NFS server which in turn is used to - make filesystems available to other machines on the - network over the NFS protocol. - See - for more - information about client and server configuration. + make filesystems available to other machines on the network + over the NFS protocol. See for more information about client + and server configuration. - Below that option is the NFS server - option, for setting the system up as an + Below that option is the NFS + server option, for setting the system up as an NFS server. This adds the required - information to start up the Remote Procedure - Call RPC - services. RPC is used to - coordinate connections between hosts and programs. + information to start up the Remote Procedure Call + RPC services. RPC is + used to coordinate connections between hosts and + programs. - Next in line is the Ntpdate option, - which deals with time synchronization. When selected, a menu - like the one below shows up: + Next in line is the Ntpdate + option, which deals with time synchronization. When selected, + a menu like the one below shows up:
Ntpdate Configuration @@ -3682,21 +3541,19 @@ Retype new password :
From this menu, select the server which is geographically - closest. - This will make the time - synchronization more accurate as a farther server - may have more connection latency. + closest. This will make the time synchronization more + accurate as a farther server may have more connection + latency. - The next option is the PCNFSD selection. - This option will install the - net/pcnfsd package from - the Ports Collection. This is a useful utility which provides - NFS authentication services for systems which - are unable to provide their own, such as Microsoft's + The next option is the PCNFSD + selection. This option will install the + net/pcnfsd package from the Ports + Collection. This is a useful utility which provides + NFS authentication services for systems + which are unable to provide their own, such as Microsoft's &ms-dos; operating system. - Now, scroll down a bit to see the other - options: + Now, scroll down a bit to see the other options:
Network Configuration Lower-level @@ -3708,72 +3565,60 @@ Retype new password :
- RPC. - communication - between NFS servers and clients is managed - by &man.rpcbind.8; which is - required for NFS servers to operate - correctly. Status monitoring is provided by - &man.rpc.statd.8; and the reported status is usually held - in /var/db/statd.status. The - next option is for &man.rpc.lockd.8; - which provides file locking - services. This is usually used with - &man.rpc.statd.8; to monitor which hosts are - requesting locks and how frequently they request them. - While these last two options are useful for debugging, they - are not required for NFS servers and clients - to operate correctly. + RPC. communication between + NFS servers and clients is managed by + &man.rpcbind.8; which is required for NFS + servers to operate correctly. Status monitoring is provided + by &man.rpc.statd.8; and the reported status is usually held + in /var/db/statd.status. The next option + is for &man.rpc.lockd.8; which provides file locking + services. This is usually used with &man.rpc.statd.8; to + monitor which hosts are requesting locks and how frequently + they request them. While these last two options are useful + for debugging, they are not required for + NFS servers and clients to operate + correctly. - The next menu, - Routed, configures the routing - daemon. - &man.routed.8;, manages network routing tables, - discovers multicast routers, and supplies a copy of the routing - tables to any physically connected host on the network upon - request. This is mainly used for machines which act as a - gateway for the local network. If selected, a menu will - request the default location of the utility. - To accept the default location, - press Enter. Yet - another menu will ask for the - flags to pass to &man.routed.8;. The - default of should appear - on the screen. + The next menu, Routed, + configures the routing daemon. &man.routed.8;, manages + network routing tables, discovers multicast routers, and + supplies a copy of the routing tables to any physically + connected host on the network upon request. This is mainly + used for machines which act as a gateway for the local + network. If selected, a menu will request the default + location of the utility. To accept the default location, + press Enter. Yet another menu will ask for + the flags to pass to &man.routed.8;. The default of + should appear on the screen. - The next menu, Rwhod, - starts &man.rwhod.8; - during system initialization. This - utility broadcasts system messages across the network - periodically, or collects them when in consumer - mode. More information can be found in &man.ruptime.1; and + The next menu, Rwhod, starts + &man.rwhod.8; during system initialization. This utility + broadcasts system messages across the network periodically, or + collects them when in consumer mode. More + information can be found in &man.ruptime.1; and &man.rwho.1;. - The next to last option in the list is for - &man.sshd.8;, the secure shell server for + The next to last option in the list is for &man.sshd.8;, + the secure shell server for OpenSSH. It is highly recommended - over the standard &man.telnetd.8; and - &man.ftpd.8; servers as it - is used to create a secure, encrypted connection from one host - to - another. + over the standard &man.telnetd.8; and &man.ftpd.8; servers as + it is used to create a secure, encrypted connection from one + host to another. The final option is TCP - Extensions which are - defined in RFC 1323 and - RFC 1644. While on many hosts this can - speed up connections, it can also cause some connections to be - dropped. It is not recommended for servers, but may be + Extensions which are defined in + RFC 1323 and + RFC 1644. While on many hosts this + can speed up connections, it can also cause some connections + to be dropped. It is not recommended for servers, but may be beneficial for stand alone machines. - Once the network services are configured, - scroll up to the very top item which is - X Exit - and continue on to the next configuration item or simply exit - &man.sysinstall.8; by selecting - X Exit twice then [X - Exit Install]. - + Once the network services are configured, scroll up to the + very top item which is X Exit and + continue on to the next configuration item or simply exit + &man.sysinstall.8; by selecting X + Exit twice then [X + Exit Install]. @@ -3782,26 +3627,26 @@ Retype new password : &os;/&arch.i386; Bootup - If everything went well, messages will scroll along - the screen and a login prompt will appear. To view - these messages, press - Scroll-Lock - then use PgUp and PgDn. - Press Scroll-Lock again to return - to the prompt. + If everything went well, messages will scroll along the + screen and a login prompt will appear. To view these + messages, press Scroll-Lock then use + PgUp and PgDn. Press + Scroll-Lock again to return to the + prompt. - All of the messages may not display due to buffer - limitations, but - they can be read after logging using - &man.dmesg.8;. + All of the messages may not display due to buffer + limitations, but they can be read after logging using + &man.dmesg.8;. - Login using the username and password which were set - during installation. Avoid logging in as - root except when necessary. + Login using the username and password which were set + during installation. Avoid logging in as root except when + necessary. - Typical boot messages (version information omitted): + Typical boot messages (version information + omitted): -Copyright (c) 1992-2002 The FreeBSD Project. + Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. @@ -3928,49 +3773,44 @@ FreeBSD/i386 (k6-2.example.com) (ttyv0) login: rpratt Password: - Generating the RSA and DSA keys may take some time on slower - machines. This happens only on the initial boot-up of a new - installation. Subsequent boots will be faster. - - If &xorg; has been configured - and a default desktop - chosen, it can be started by typing startx at - the command line. + Generating the RSA and DSA keys may take some time on + slower machines. This happens only on the initial boot-up + of a new installation. Subsequent boots will be + faster. + If &xorg; has been configured + and a default desktop chosen, it can be started by typing + startx at the command line. &os; Shutdown - It is important to properly shutdown the operating - system. Do not just turn off the power. First, become the - superuser using - &man.su.1; and entering the - root password. This will work only if the user - is a member of wheel. - Otherwise, login as root. To shutdown - the system, type - shutdown -h now. + It is important to properly shutdown the operating system. + Do not just turn off the power. First, become the superuser + using &man.su.1; and entering the root password. This will work + only if the user is a member of wheel. Otherwise, login as + root. To shutdown + the system, type shutdown -h now. The operating system has halted. Please press any key to reboot. - It is safe to turn off the power after the shutdown command - has been issued and the message - Please press any key to reboot - appears. If any key is pressed instead of turning off the power - switch, the system will reboot. + It is safe to turn off the power after the shutdown + command has been issued and the message Please press + any key to reboot appears. If any key is pressed + instead of turning off the power switch, the system will + reboot. - The - + The Ctrl Alt Del - - key combination can also be used to reboot the system; - however, this is not recommended. - + key combination can also be used to reboot the + system; however, this is not recommended. @@ -3982,106 +3822,102 @@ Please press any key to reboot. troubleshooting This section covers basic installation troubleshooting of - common problems. There are also a few - questions and answers for people wishing to dual-boot &os; with - &windows;. + common problems. There are also a few questions and answers for + people wishing to dual-boot &os; with &windows;. If Something Goes Wrong Due to various limitations of the PC architecture, it is impossible for device probing to be 100% reliable. However, - there are a - few things to try if it fails. + there are a few things to try if it fails. - Check the Hardware Notes - document for the version of &os; to make sure the - hardware is supported. + Check the Hardware + Notes document for the version of &os; to make sure + the hardware is supported. If the hardware is supported but still experiences - lock-ups or other problems, build a custom kernel - to add in support for devices which are not present in the + lock-ups or other problems, build a custom kernel to add in + support for devices which are not present in the GENERIC kernel. The default kernel - assumes that most hardware devices are in their - factory default configuration in terms of IRQs, I/O addresses, - and - DMA channels. If the hardware has been reconfigured, - create a custom kernel configuration file and recompile to - tell - &os; where to find things. + assumes that most hardware devices are in their factory + default configuration in terms of IRQs, I/O addresses, and + DMA channels. If the hardware has been reconfigured, create a + custom kernel configuration file and recompile to tell &os; + where to find things. It is also possible that a probe for a device not present - will - cause a later probe for another device that is present to fail. In - that case, the probes for the conflicting driver(s) should be - disabled. + will cause a later probe for another device that is present to + fail. In that case, the probes for the conflicting driver(s) + should be disabled. Some installation problems can be avoided or alleviated - by updating the firmware on various hardware components, most notably - the motherboard - BIOS. Most motherboard and computer - manufacturers have a website where upgrade - information may be located. + by updating the firmware on various hardware components, + most notably the motherboard BIOS. Most + motherboard and computer manufacturers have a website where + upgrade information may be located. Most manufacturers strongly advise against upgrading the - motherboard BIOS unless there is a good reason - for doing so, such as - a critical update. The upgrade process - can go wrong, causing permanent damage to the - BIOS chip. - + motherboard BIOS unless there is a good + reason for doing so, such as a critical update. The upgrade + process can go wrong, causing permanent + damage to the BIOS chip. + Using &windows; Filesystems - At this time, &os; does not support file systems compressed with - the Double Space™ application. - Therefore the file system will need to be uncompressed before &os; can - access the data. This - can be done by running the Compression Agent - located in the - Start> Programs > + At this time, &os; does not support file systems + compressed with the + Double Space™ application. + Therefore the file system will need to be uncompressed before + &os; can access the data. This can be done by running the + Compression Agent located in the + Start> + Programs > System Tools menu. &os; can support &ms-dos; file systems (sometimes called - FAT file systems). The &man.mount.msdosfs.8; command grafts such file - systems onto the existing directory hierarchy, allowing the file - system's contents to be accessed. The &man.mount.msdosfs.8; program - is not usually - invoked directly; instead, it is called by the system through a line - in /etc/fstab or by using - &man.mount.8; - with the appropriate parameters. + FAT file systems). The &man.mount.msdosfs.8; command grafts + such file systems onto the existing directory hierarchy, + allowing the file system's contents to be accessed. The + &man.mount.msdosfs.8; program is not usually invoked directly; + instead, it is called by the system through a line in + /etc/fstab or by using &man.mount.8; with + the appropriate parameters. - A typical line in /etc/fstab is: + A typical line in /etc/fstab + is: /dev/ad0sN /dos msdosfs rw 0 0 - /dos must - already - exist for this to work. For details about the format of - /etc/fstab, see &man.fstab.5;. + + /dos must already exist for this to + work. For details about the format of + /etc/fstab, see &man.fstab.5;. + - A typical call to &man.mount.8; for a FAT filesystem - looks like: + A typical call to &man.mount.8; for a FAT filesystem looks + like: &prompt.root; mount -t msdosfs /dev/ad0s1 /mnt In this example, the FAT filesystem is located on the - first - partition of the primary hard disk. The - output from &man.dmesg.8; and - &man.mount.8; should produce enough + first partition of the primary hard disk. The output from + &man.dmesg.8; and &man.mount.8; should produce enough information to give an idea of the partition layout. - &os; may number FAT partitions - differently than other operating systems. In particular, extended - partitions are usually given higher slice numbers than - primary partitions. Use &man.fdisk.8; to help - determine which slices belong to &os; and which belong to other - operating systems. + + &os; may number FAT partitions differently than other + operating systems. In particular, extended partitions are + usually given higher slice numbers than primary partitions. + Use &man.fdisk.8; to help determine which slices belong to + &os; and which belong to other operating systems. + @@ -4094,24 +3930,24 @@ Please press any key to reboot. or it behaves strangely during install. - &os; makes extensive use of the system - ACPI service on the i386, amd64, and ia64 platforms to - aid in system configuration if it is detected during - boot. Unfortunately, some bugs still exist in the - ACPI driver and various system motherboards. - The use of ACPI can be disabled by setting - hint.acpi.0.disabled in the - third stage boot loader: + &os; makes extensive use of the system ACPI service + on the i386, amd64, and ia64 platforms to aid in system + configuration if it is detected during boot. + Unfortunately, some bugs still exist in the ACPI driver + and various system motherboards. The use of ACPI can be + disabled by setting + hint.acpi.0.disabled in the third + stage boot loader: set hint.acpi.0.disabled="1" This is reset each time the system is booted, so it - is necessary to - add hint.acpi.0.disabled="1" to + is necessary to add + hint.acpi.0.disabled="1" to /boot/loader.conf to make this - change permanent. More - information about the boot loader can be found - in . + change permanent. More information about the boot + loader can be found in . @@ -4125,24 +3961,20 @@ Please press any key to reboot. What is wrong? - This can occur when - the boot disk is not the first disk in the system. The - BIOS uses a different numbering scheme to &os;, and - working out which numbers correspond to which is - difficult to get right. + This can occur when the boot disk is not the first + disk in the system. The BIOS uses a different numbering + scheme to &os;, and working out which numbers correspond + to which is difficult to get right. - If this occurs, - tell &os; where the root - filesystem is by specifying the BIOS disk - number, the disk type, and the &os; disk number for that - type. + If this occurs, tell &os; where the root filesystem + is by specifying the BIOS disk number, the disk type, + and the &os; disk number for that type. - Consider two IDE disks, - each configured as the master on their respective IDE - bus, where &os; should be booted from the second disk. - The - BIOS sees these as disk 0 and disk 1, while &os; sees - them as ad0 and + Consider two IDE disks, each configured as the + master on their respective IDE bus, where &os; should be + booted from the second disk. The BIOS sees these as + disk 0 and disk 1, while &os; sees them as + ad0 and ad2. If &os; is on BIOS disk 1, of type @@ -4158,32 +3990,30 @@ Please press any key to reboot. The second situation involves booting from a SCSI disk when there are one or more IDE disks in the system. In this case, the &os; disk number is lower than the - BIOS disk number. For two IDE disks and a - SCSI disk, where the SCSI disk is BIOS disk 2, - type da, and &os; disk number 0, the + BIOS disk number. For two IDE disks and a SCSI disk, + where the SCSI disk is BIOS disk 2, type + da, and &os; disk number 0, the correct value is: 2:da(0,a)kernel - This tells &os; to boot from BIOS disk 2, - which is the first SCSI disk in the system. If there - is only IDE disk, use 1: - instead. + This tells &os; to boot from BIOS disk 2, which is + the first SCSI disk in the system. If there is only IDE + disk, use 1: instead. - Once the correct value to use is determined, - put the command - in /boot.config using a - text editor. Unless instructed otherwise, &os; - will use the contents of this file as the default - response to the boot: prompt. + Once the correct value to use is determined, put the + command in /boot.config using a + text editor. Unless instructed otherwise, &os; will use + the contents of this file as the default response to the + boot: prompt. When booting from the hard disk for the first time after installing &os;, the Boot Manager prompt just - prints F? at the boot menu and - the boot will not go any further. + prints F? at the boot menu and the + boot will not go any further. The hard disk geometry was set incorrectly in the @@ -4192,11 +4022,11 @@ Please press any key to reboot. the hard disk. &os; must be reinstalled again from the beginning with the correct geometry. - For a dedicated &os; system that does not need - future compatibility with another operating system, - use the entire disk by selecting - A in the installer's - partition editor. + For a dedicated &os; system that does not need + future compatibility with another operating system, use + the entire disk by selecting + A in the installer's + partition editor. @@ -4208,46 +4038,42 @@ Please press any key to reboot. The card is probably on a different IRQ from what is specified in /boot/device.hints. The - &man.ed.4; driver does not use software - configuration by default, - but it will if - -1 is specified in the hints for the - interface. + &man.ed.4; driver does not use software configuration by + default, but it will if -1 is + specified in the hints for the interface. Either move the jumper on the card to the configuration setting or specify the IRQ as - -1 - by setting the hint hint.ed.0.irq="-1". - This tells the kernel to use the software - configuration. + -1 by setting the hint + hint.ed.0.irq="-1". This tells the + kernel to use the software configuration. Another possibility is that the card is at IRQ 9, which is shared by IRQ 2 and frequently a cause of - problems, especially if a VGA card is using IRQ - 2. Do not use IRQ 2 or 9 if at all - possible. + problems, especially if a VGA card is using IRQ 2. Do + not use IRQ 2 or 9 if at all possible. - When &man.sysinstall.8; is used - in an &xorg; terminal, the - yellow font is difficult to read - against the light gray background. Is there a way to - provide higher contrastcolor - contrast for - this application? + When &man.sysinstall.8; is usedin an + &xorg; terminal, the yellow + font is difficult to read against the light gray + background. Is there a way to provide higher + contrastcolor + contrast for this + application? - If the default - colors chosen by &man.sysinstall.8; - make text illegible while using x11/xterm or x11/rxvt, - add the following to ~/.Xdefaults - to - get a darker background gray: XTerm*color7: - #c0c0c0 + If the default colors chosen by &man.sysinstall.8; + make text illegible while using + x11/xterm or + x11/rxvt, add the following to + ~/.Xdefaults to get a darker + background gray: XTerm*color7: + #c0c0c0 @@ -4255,20 +4081,21 @@ Please press any key to reboot. - Advanced Installation Guide + + Advanced Installation Guide + - ValentinoVaschettoContributed by + ValentinoVaschettoContributed + by - MarcFonvieilleUpdated by + MarcFonvieilleUpdated + by - - - This section describes how to install &os; in exceptional cases. @@ -4282,139 +4109,129 @@ Please press any key to reboot. serial console This type of installation is called a headless - install because the machine to be installed - does not have either an attached monitor or a - VGA output. This type of installation is possible using a - serial console, another - machine which acts as the main display and keyboard. - To do this, follow the steps to create - an installation USB stick, explained in , or download the correct - installation ISO image as described in . + install because the machine to be installed does not + have either an attached monitor or a VGA output. This type of + installation is possible using a serial console, another + machine which acts as the main display and keyboard. To do + this, follow the steps to create an installation USB stick, + explained in , or download + the correct installation ISO image as described in . To modify the installation media to boot into a serial - console, follow - these steps. If using a CD/DVD media, skip the first - step): + console, follow these steps. If using a CD/DVD media, skip + the first step): Enabling the Installation USB Stick to Boot into a Serial Console - - &man.mount.8; - - By default, booting into the USB stick - boots into the installer. - To instead boot into a serial console, mount the - USB disk onto a &os; - system using &man.mount.8;: + + &man.mount.8; + + By default, booting into the USB stick boots into the + installer. To instead boot into a serial console, mount + the USB disk onto a &os; system using + &man.mount.8;: - &prompt.root; mount /dev/da0a /mnt + &prompt.root; mount /dev/da0a /mnt - - Adapt the device node and the mount point to the - situation. - + + Adapt the device node and the mount point to the + situation. + - Once the USB stick is mounted, set - it to boot into a serial console. - Add this line to /boot/loader.conf - on the USB stick: + Once the USB stick is mounted, set it to boot into a + serial console. Add this line to + /boot/loader.conf on the USB + stick: - &prompt.root; echo 'console="comconsole"' >> /mnt/boot/loader.conf + &prompt.root; echo 'console="comconsole"' >> /mnt/boot/loader.conf - Now that the USB is stick configured correctly, - unmount the disk using &man.umount.8;: + Now that the USB is stick configured correctly, + unmount the disk using &man.umount.8;: - &prompt.root; umount /mnt + &prompt.root; umount /mnt - Now, unplug the USB stick and jump directly - to the third step of this procedure. - + Now, unplug the USB stick and jump directly to the + third step of this procedure. + Enabling the Installation CD/DVD to Boot into a Serial Console - - &man.mount.8; - - By default, when booting into the installation - CD/DVD, &os; boots into its - normal install mode. To instead boot into a serial - console, - extract, modify, and regenerate the ISO image before - burning it to the CD/DVD media. + + &man.mount.8; + + By default, when booting into the installation CD/DVD, + &os; boots into its normal install mode. To instead boot + into a serial console, extract, modify, and regenerate the + ISO image before burning it to the CD/DVD media. - From the &os; system with the saved installation - ISO image, - use &man.tar.1; to extract all the files: + From the &os; system with the saved installation ISO + image, use &man.tar.1; to extract all the files: - &prompt.root; mkdir /path/to/headless-iso + &prompt.root; mkdir /path/to/headless-iso &prompt.root; tar -C /path/to/headless-iso -pxvf &os;-&rel.current;-RELEASE-i386-disc1.iso - Next, set the installation media to boot into a - serial console. Add this line to the - /boot/loader.conf of the extracted - ISO image: + Next, set the installation media to boot into a + serial console. Add this line to the + /boot/loader.conf of the extracted + ISO image: - &prompt.root; echo 'console="comconsole"' >> /path/to/headless-iso/boot/loader.conf + &prompt.root; echo 'console="comconsole"' >> /path/to/headless-iso/boot/loader.conf - Then, create a new ISO image from the modified - tree. This example uses &man.mkisofs.8; from the - sysutils/cdrtools - package or port: + Then, create a new ISO image from the modified tree. + This example uses &man.mkisofs.8; from the + sysutils/cdrtools package or + port: - &prompt.root; mkisofs -v -b boot/cdboot -no-emul-boot -r -J -V "Headless_install" \ + &prompt.root; mkisofs -v -b boot/cdboot -no-emul-boot -r -J -V "Headless_install" \ -o Headless-&os;-&rel2.current;-RELEASE-i386-disc1.iso/path/to/headless-iso - Now that the ISO image is configured correctly, - burn it to a CD/DVD media using a burning - application. - + Now that the ISO image is configured correctly, burn + it to a CD/DVD media using a burning application. + - - Connecting the Null-modem Cable + + Connecting the Null-modem Cable - null-modem cable - Connect a - null-modem cable - to the serial - ports of the two machines. A normal serial - cable will not work. A null-modem - cable is required. - + null-modem cable + Connect a null-modem cable to + the serial ports of the two machines. A + normal serial cable will not work. A + null-modem cable is required. + - - Booting Up for the Install + + Booting Up for the Install - It is now time to go ahead and start the install. Plug in - the USB stick or insert the CD/DVD media in - the headless install machine - and power it on. - + It is now time to go ahead and start the install. + Plug in the USB stick or insert the CD/DVD media in the + headless install machine and power it on. + - - Connecting to the Headless Machine + + Connecting to the Headless Machine - - &man.cu.1; - + + &man.cu.1; + - Next, connect to that machine with - &man.cu.1;: + Next, connect to that machine with &man.cu.1;: - &prompt.root; cu -l /dev/cuau0 + &prompt.root; cu -l /dev/cuau0 - + - The headless machine can now be controlled - using &man.cu.1;. It will load the kernel - and then dispaly - a selection of which type of terminal to use. Select the - &os; color console and proceed with the installation. + The headless machine can now be controlled using + &man.cu.1;. It will load the kernel and then dispaly a + selection of which type of terminal to use. Select the &os; + color console and proceed with the installation. @@ -4422,38 +4239,33 @@ Please press any key to reboot. Preparing Custom Installation Media - Some situations may require a customized - &os; installation media and/or source. This might be physical - media - or a source that &man.sysinstall.8; - can use to retrieve the installation files. Some example - situations include: + Some situations may require a customized &os; installation + media and/or source. This might be physical media or a source + that &man.sysinstall.8; can use to retrieve the installation + files. Some example situations include: - A local network with many machines has a private - FTP server hosting the - &os; installation files which the machines should - use for installation. + A local network with many machines has a private FTP + server hosting the &os; installation files which the + machines should use for installation. - &os; does not recognize the - CD/DVD drive but &windows; does. In this case, copy the - &os; installation files to a &windows; partition on the same - computer, and then install &os; using those files. + &os; does not recognize the CD/DVD drive but &windows; + does. In this case, copy the &os; installation files to a + &windows; partition on the same computer, and then install + &os; using those files. - The computer to install does not have a CD/DVD - drive or a network card, but can be connected using a - null-printer cable to a computer - that does. + The computer to install does not have a CD/DVD drive or + a network card, but can be connected using a null-printer + cable to a computer that does. - A tape will be be used to install - &os;. + A tape will be be used to install &os;. @@ -4461,18 +4273,19 @@ Please press any key to reboot. Creating an Installation ISO As part of each release, the &os; Project provides ISO - images for each supported - architecture. These images can be written - (burned) to CD or DVD media using a burning - application, and then used - to install &os;. If a CD/DVD writer is available, - this is the easiest way to install &os;. + images for each supported architecture. These images can be + written (burned) to CD or DVD media using a + burning application, and then used to install &os;. If a + CD/DVD writer is available, this is the easiest way to install + &os;. Download the Correct ISO Images - The ISO images for each release can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch/version or the closest mirror. + The ISO images for each release can be downloaded from + ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch/version + or the closest mirror. or the closest mirror. Substitute arch and version as appropriate. @@ -4497,19 +4310,19 @@ Please press any key to reboot. &os;-version-RELEASE-arch-bootonly.iso - This CD image starts the installation - process by booting from a CD-ROM drive but it does not - contain the support for installing &os; from the CD - itself. Perform a network based install, such as - from an FTP server, after booting from this + This CD image starts the installation process + by booting from a CD-ROM drive but it does not + contain the support for installing &os; from the + CD itself. Perform a network based install, such + as from an FTP server, after booting from this CD. &os;-version-RELEASE-arch-dvd1.iso.gz - This DVD image contains everything necessary to - install the base &os; operating system, a + This DVD image contains everything necessary + to install the base &os; operating system, a collection of pre-built packages, and the documentation. It also supports booting into a livefs based rescue mode. @@ -4518,11 +4331,11 @@ Please press any key to reboot. &os;-version-RELEASE-arch-memstick.img - This image can be written to a USB memory stick - in order to install machines capable of booting - from USB drives. It also supports booting into a - livefs based rescue mode. The only - included package is the documentation + This image can be written to a USB memory + stick in order to install machines capable of + booting from USB drives. It also supports booting + into a livefs based rescue mode. + The only included package is the documentation package. @@ -4541,9 +4354,9 @@ Please press any key to reboot. &os;-version-RELEASE-arch-disc1.iso - This CD image contains the base &os; operating - system and the documentation package but no other - packages. + This CD image contains the base &os; + operating system and the documentation package but + no other packages. @@ -4551,7 +4364,8 @@ Please press any key to reboot. A CD image with as many third-party packages as would fit on the disc. This image is not - available for &os; 9.X. + available for + &os; 9.X. @@ -4559,58 +4373,54 @@ Please press any key to reboot. Another CD image with as many third-party packages as would fit on the disc. This image is - not available for &os; 9.X. + not available for + &os; 9.X. &os;-version-RELEASE-arch-livefs.iso - This CD image contains support for booting into - a livefs based rescue mode but does not - support doing an install from the CD itself. + This CD image contains support for booting + into a livefs based rescue mode but + does not support doing an install from the CD + itself.
When performing a CD installation, download either - the bootonly ISO image - or disc1. Do not download - both, since disc1 - contains everything that the bootonly - ISO image contains. + the bootonly ISO image or + disc1. Do not download both, since + disc1 contains everything that the + bootonly ISO image contains. Use the bootonly ISO to perform a network install over the Internet. Additional software - can be installed as needed using - the Ports Collection as described in - . + can be installed as needed using the Ports Collection as + described in . - Use dvd1 to - install &os; - and a selection of third-party packages - from the disc. + Use dvd1 to install &os; and a + selection of third-party packages from the disc. Burn the Media Next, write the downloaded image(s) to disc. If using - another &os; system, refer to - and + another &os; system, refer to and for instructions. - If using another platform, - use any burning utility that exists for - that platform. The images are in the standard ISO format - which most CD writing applications support. + If using another platform, use any burning utility + that exists for that platform. The images are in the + standard ISO format which most CD writing applications + support. - To build a customized - release of &os;, refer to the Release Engineering - Article. - + To build a customized release of &os;, refer to the + Release Engineering + Article. @@ -4622,22 +4432,21 @@ Please press any key to reboot. FTP - &os; discs are laid out in the same way as the FTP site. This - makes it easy to create a local FTP site that can be used + &os; discs are laid out in the same way as the FTP site. + This makes it easy to create a local FTP site that can be used by other machines on a network to install &os;. - On the &os; computer that will host the FTP site, ensure - that the CD/DVD is in the drive and mounted: + On the &os; computer that will host the FTP site, + ensure that the CD/DVD is in the drive and mounted: &prompt.root; mount /cdrom Create an account for anonymous FTP. Use &man.vipw.8; - to insert - this line: + to insert this line: ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent @@ -4650,187 +4459,167 @@ Please press any key to reboot. Anyone with network connectivity to the machine can now chose a media type of FTP and type in - ftp://your machine - after picking Other in the FTP sites menu during - the install. + ftp://your + machine after picking + Other in the FTP sites menu during the + install. - If the boot media for the FTP - clients is not precisely the same version as that provided - by the local FTP site, &man.sysinstall.8; - will not - complete the installation. - To override this, go into the - Options menu and change the distribution - name to + If the boot media for the FTP clients is not precisely + the same version as that provided by the local FTP site, + &man.sysinstall.8; will not complete the installation. To + override this, go into the Options menu + and change the distribution name to any. This approach is acceptable for a machine on the local - network which - is protected by a firewall. Offering anonymous FTP services - to - other machines over the Internet - exposes the computer to increased security risks. - It is strongly recommended to follow good security - practices when providing services over the Internet. + network which is protected by a firewall. Offering + anonymous FTP services to other machines over the Internet + exposes the computer to increased security risks. It is + strongly recommended to follow good security practices when + providing services over the Internet. - - Installing from an &windows; Partition + + Installing from an &windows; Partition - - installation - from &windows; - - To prepare for an installation from a &windows; - partition, - copy the files from the distribution into a directory - in the root directory of the - partition, such as c:\freebsd. Since the - directory structure must be - reproduced, it is recommended to use - robocopy when copying from a CD/DVD. - For example, to prepare for a minimal installation of - &os;: + + installation + from &windows; + + To prepare for an installation from a &windows; partition, + copy the files from the distribution into a directory in the + root directory of the partition, such as + c:\freebsd. Since the directory + structure must be reproduced, it is recommended to use + robocopy when copying from a CD/DVD. For + example, to prepare for a minimal installation of &os;: - C:\> md c:\freebsd + C:\> md c:\freebsd C:\> robocopy e:\bin c:\freebsd\bin\ /s C:\> robocopy e:\manpages c:\freebsd\manpages\ /s - This example assumes that C: - has enough - free space and E: is where the - CD/DVD - is mounted. + This example assumes that C: has + enough free space and E: is where the + CD/DVD is mounted. - Alternatively, download the - distribution from ftp.FreeBSD.org. - Each distribution is in its own directory; for example, the - base distribution can be found in the &rel2.current;/base/ - directory. + Alternatively, download the distribution from ftp.FreeBSD.org. + Each distribution is in its own directory; for example, the + base distribution can be found in the + &rel2.current;/base/ + directory. - Copy the distributions to install from a &windows; - partition to c:\freebsd. Both the - base and kernel - distributions are needed for - the most minimal installation. - + Copy the distributions to install from a &windows; + partition to c:\freebsd. Both the + base and kernel + distributions are needed for the most minimal + installation. + - - Before Installing over a Network + + Before Installing over a Network + + + installation + network + serial (PPP) + + + installation + network + parallel (PLIP) + + + installation + network + Ethernet + + There are three types of network installations + available: Ethernet, PPP, and PLIP. + + For the fastest possible network installation, use an + Ethernet adapter. &os; supports most common Ethernet cards. + A list of supported cards is provided in the Hardware Notes + for each release of &os;. If using a supported PCMCIA + Ethernet card, be sure that it is plugged in + before the system is powered on as &os; + does not support hot insertion of PCMCIA cards during + installation. + + Make note of the system's IP address, subnet mask, + hostname, default gateway address, and DNS server addresses if + these values are statically assigned. If installing by FTP + through a HTTP proxy, make note of the proxy's address. If + you do not know these values, ask the system administrator or + ISP before trying this type of + installation. + + If using a dialup modem, have the service provider's PPP + information handy as it is needed early in the installation + process. + + If PAP or CHAP are used to connect to the + ISP without using a script, type + dial at the &os; + ppp prompt. Otherwise, know how to + dial the ISP using the AT + commands specific to the modem, as the PPP dialer + provides only a simple terminal emulator. Refer to and &url.books.faq;/ppp.html + for further information. Logging can be directed to the + screen using set log local .... + + If a hard-wired connection to another &os; machine is + available, the installation can occur over a null-modem + parallel port cable. The data rate over the parallel port is + higher than what is typically possible over a serial + line. + + + Before Installing via <acronym>NFS</acronym> installation network - serial (PPP) + NFS - - installation - network - parallel (PLIP) - - - installation - network - Ethernet - - There are three types of network installations - available: - Ethernet, PPP, and - PLIP. + To perform an NFS installation, copy + the needed &os; distribution files to an + NFS server and then point the installer's + NFS media selection to it. - For the fastest possible network installation, use an - Ethernet adapter. &os; supports most - common Ethernet cards. A list of supported cards - is provided in the Hardware Notes for each - release of &os;. If using a supported PCMCIA - Ethernet card, be sure that it is plugged in - before the system is powered on as - &os; does - not support hot insertion of PCMCIA cards - during installation. + If the server supports only a privileged + port, set the option NFS Secure + in the Options menu so that the + installation can proceed. - Make note of the system's IP address, - subnet mask, hostname, default gateway address, and DNS - server addresses if these values are statically assigned. - If installing by FTP through a - HTTP proxy, make note of the proxy's address. - If you do not know these values, ask the system - administrator - or ISP before trying this type of - installation. + If using a poor quality Ethernet card which suffers + from slow transfer rates, toggle the + NFS Slow flag to on. - If using a dialup modem, have the service - provider's PPP information handy as it is needed - early in the installation process. + In order for an NFS installation to + work, the server must support subdir mounts. For example, + if the &os; &rel.current; distribution lives on: + ziggy:/usr/archive/stuff/FreeBSD, + ziggy will have to allow the direct + mounting of /usr/archive/stuff/FreeBSD, + not just /usr or + /usr/archive/stuff. - If PAP or CHAP are used to connect to the - ISP without using a script, - type dial at the &os; - ppp prompt. Otherwise, - know how to dial the ISP using the - AT commands - specific to the modem, as the PPP dialer provides only a - simple terminal emulator. Refer to and &url.books.faq;/ppp.html - for further information. - Logging can be directed to the screen using - set log local .... - - If a hard-wired connection to another &os; - machine is available, the installation can occur - over a null-modem parallel port cable. The data rate - over the parallel port is higher than what is typically - possible over a serial line. - - - Before Installing via <acronym>NFS</acronym> - - - installation - network - NFS - - To perform an NFS installation, - copy the needed &os; distribution files to an - NFS server - and then point the installer's NFS - media selection to it. - - If the server supports only a privileged - port, - set the option NFS Secure in the - Options menu so that the installation - can - proceed. - - If using a poor quality Ethernet card which suffers - from slow transfer rates, toggle the - NFS Slow flag to on. - - In order for an NFS installation to - work, the server must - support subdir mounts. For example, if the - &os; &rel.current; distribution lives on: - ziggy:/usr/archive/stuff/FreeBSD, - ziggy will have to allow the direct mounting - of /usr/archive/stuff/FreeBSD, - not just - /usr or - /usr/archive/stuff. - - In &os;, this - is controlled by using in - /etc/exports. Other - NFS - servers may have different conventions. If the server is - displaying - permission denied messages, - it is likely that this is not enabled - properly. - - + In &os;, this is controlled by using + in + /etc/exports. Other + NFS servers may have different + conventions. If the server is displaying + permission denied messages, it is + likely that this is not enabled properly. + +