From owner-svn-doc-head@FreeBSD.ORG Mon Mar 11 21:08:55 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 031ED1BE; Mon, 11 Mar 2013 21:08:55 +0000 (UTC) (envelope-from keramida@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id E66461B1; Mon, 11 Mar 2013 21:08:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r2BL8snv092991; Mon, 11 Mar 2013 21:08:54 GMT (envelope-from keramida@svn.freebsd.org) Received: (from keramida@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r2BL8s8Q092990; Mon, 11 Mar 2013 21:08:54 GMT (envelope-from keramida@svn.freebsd.org) Message-Id: <201303112108.r2BL8s8Q092990@svn.freebsd.org> From: Giorgos Keramidas Date: Mon, 11 Mar 2013 21:08:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41166 - head/en_US.ISO8859-1/books/handbook/install X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 21:08:55 -0000 Author: keramida Date: Mon Mar 11 21:08:54 2013 New Revision: 41166 URL: http://svnweb.freebsd.org/changeset/doc/41166 Log: Replace 'FreeBSD' with &os; in the install chapter of the Handbook. Approved by: remko (mentor) Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon Mar 11 20:55:24 2013 (r41165) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon Mar 11 21:08:54 2013 (r41166) @@ -176,14 +176,14 @@ Inventory Your Computer - Before installing FreeBSD you should attempt to inventory the - components in your computer. The FreeBSD installation routines will + Before installing &os; you should attempt to inventory the + components in your computer. The &os; installation routines will show you the components (hard disks, network cards, CDROM drives, and - so forth) with their model number and manufacturer. FreeBSD will also + so forth) with their model number and manufacturer. &os; will also attempt to determine the correct configuration for these devices, which includes information about IRQ and IO port usage. Due to the vagaries of PC hardware this process is not always completely - successful, and you may need to correct FreeBSD's determination of + successful, and you may need to correct &os;'s determination of your configuration. If you already have another operating system installed, such as @@ -195,7 +195,7 @@ hexadecimal numbers, such as 0x330. We recommend you print or write down this information before - installing FreeBSD. It may help to use a table, like this: + installing &os;. It may help to use a table, like this: Sample Device Inventory @@ -293,22 +293,22 @@ Backup Your Data - If the computer you will be installing FreeBSD on contains + If the computer you will be installing &os; on contains valuable data, then ensure you have it backed up, and that you have - tested the backups before installing FreeBSD. The FreeBSD + tested the backups before installing &os;. The &os; installation routine will prompt you before writing any data to your disk, but once that process has started it cannot be undone. - Decide Where to Install FreeBSD + Decide Where to Install &os; - If you want FreeBSD to use your entire hard disk, then there is nothing + If you want &os; to use your entire hard disk, then there is nothing more to concern yourself with at this point — you can skip this section. - However, if you need FreeBSD to co-exist with other operating + However, if you need &os; to co-exist with other operating systems then you need to have a rough understanding of how data is laid out on the disk, and how this affects you. @@ -320,7 +320,7 @@ &os; internally also has partitions, the naming can become confusing very quickly, therefore these disk chunks are referred to as disk slices or simply slices - in &os; itself. For example, the FreeBSD utility + in &os; itself. For example, the &os; utility fdisk which operates on the PC disk partitions, refers to slices instead of partitions. By design, the PC only supports four partitions per disk. These partitions are called @@ -332,7 +332,7 @@ extended partition. Each partition has a partition ID, which is - a number used to identify the type of data on the partition. FreeBSD + a number used to identify the type of data on the partition. &os; partitions have the partition ID of 165. In general, each operating system that you use will identify @@ -341,16 +341,16 @@ drive letter, starting with C:. - FreeBSD must be installed into a primary partition. FreeBSD can + &os; must be installed into a primary partition. &os; can keep all its data, including any files that you create, on this one partition. However, if you have multiple disks, then you can create a - FreeBSD partition on all, or some, of them. When you install FreeBSD, + &os; partition on all, or some, of them. When you install &os;, you must have one partition available. This might be a blank partition that you have prepared, or it might be an existing partition that contains data that you no longer care about. If you are already using all the partitions on all your disks, then - you will have to free one of them for FreeBSD using the tools + you will have to free one of them for &os; using the tools provided by the other operating systems you use (e.g., fdisk on &ms-dos; or &windows;). @@ -358,7 +358,7 @@ may need to shrink one or more of your existing partitions first. - A minimal installation of FreeBSD takes as little as 100 MB + 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 your own files. A more realistic minimum @@ -404,7 +404,7 @@ This means that your disk has two partitions on it, one per drive letter. You can copy all your existing data from D: to C:, which - will free up the second partition, ready for FreeBSD. + will free up the second partition, ready for &os;. @@ -414,10 +414,10 @@ that already has a version of &windows; installed. When you installed &windows; you created one large partition, giving you a C: drive that is 4 GB in size. You are - currently using 1.5 GB of space, and want FreeBSD to have 2 GB + currently using 1.5 GB of space, and want &os; to have 2 GB of space. - In order to install FreeBSD you will need to either: + In order to install &os; you will need to either: @@ -439,12 +439,12 @@ Collect Your Network Configuration Details - If you intend to connect to a network as part of your FreeBSD + If you intend to connect to a network as part of your &os; installation (for example, if you will be installing from an FTP site or an NFS server), then you need to know your network configuration. You will be prompted for this information during the installation so that - FreeBSD can connect to the network to complete the install. + &os; can connect to the network to complete the install. Connecting to an Ethernet Network or Cable/DSL Modem @@ -485,7 +485,7 @@ Connecting Using a Modem If you dial up to an ISP using a regular modem then you can - still install FreeBSD over the Internet, it will just take a very + still install &os; over the Internet, it will just take a very long time. You will need to know: @@ -506,14 +506,14 @@ - Check for FreeBSD Errata + Check for &os; Errata - Although the FreeBSD project strives to ensure that each release - of FreeBSD is as stable as possible, bugs do occasionally creep into + 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 very rare occasions those bugs affect the installation process. As these problems are discovered and fixed, they - are noted in the FreeBSD Errata, - which is found on the FreeBSD web site. You + are noted in the &os; Errata, + which is found on the &os; web site. You should check the errata before installing to make sure that there are no late-breaking problems which you should be aware of. @@ -523,13 +523,13 @@ url="&url.base;/releases/index.html">release information section of the FreeBSD web site. + url="&url.base;/index.html">&os; web site. - Obtain the FreeBSD Installation Files + Obtain the &os; Installation Files - The FreeBSD installation process can install FreeBSD from files + The &os; installation process can install &os; from files located in any of the following places: @@ -573,13 +573,13 @@ - If you have purchased FreeBSD on CD or DVD then you already have + If you have purchased &os; on CD or DVD then you already have everything you need, and should proceed to the next section (). - If you have not obtained the FreeBSD installation files you should + If you have not obtained the &os; installation files you should skip ahead to which explains how - to prepare to install FreeBSD from any of the above. After reading + to prepare to install &os; from any of the above. After reading that section, you should come back here, and read on to . @@ -587,20 +587,20 @@ Prepare the Boot Media - The FreeBSD installation process is started by booting the - computer into the FreeBSD installer—it is not a program you run + The &os; installation process is started by booting the + computer into the &os; installer—it is not a program you 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 you have FreeBSD on CDROM or DVD (either one you purchased + If you have &os; on CDROM or DVD (either one you purchased or you prepared yourself), and your computer allows you to boot from the CDROM or DVD (typically a BIOS option called Boot Order or similar), then you can skip this section. The - FreeBSD CDROM and DVD images are bootable and can be used to install - FreeBSD without any other special preparation. + &os; CDROM and DVD images are bootable and can be used to install + &os; without any other special preparation. To create a bootable memory stick, follow these @@ -649,7 +649,7 @@ Write The Image File to the Memory Stick - Using FreeBSD To Write the Image + Using &os; To Write the Image The example below @@ -761,7 +761,7 @@ floppies if choosing this installation route. - If you try to install FreeBSD and the installation + If you try to install &os; and the installation program 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 @@ -799,16 +799,16 @@ the CDROM, then fdimage can be downloaded from the tools - directory on the FreeBSD FTP site. + directory on the &os; FTP site. If you are writing the floppies on a &unix; system (such as - another FreeBSD system) you can use the &man.dd.1; command to - write the image files directly to disk. On FreeBSD, you would + another &os; system) you can use the &man.dd.1; command to + write the image files directly to disk. On &os;, you would run: &prompt.root; dd if=boot.flp of=/dev/fd0 - On FreeBSD, /dev/fd0 refers to the + On &os;, /dev/fd0 refers to the first floppy disk (the A: drive). /dev/fd1 would be the B: drive, and so on. Other &unix; @@ -818,7 +818,7 @@ - You are now ready to start installing FreeBSD. + You are now ready to start installing &os;. @@ -927,7 +927,7 @@ We can take no responsibility for lost d - FreeBSD will start to boot. If you are booting from CDROM you + &os; will start to boot. If you are booting from CDROM you will see a display similar to this (version information omitted): @@ -1140,7 +1140,7 @@ Mounting root from ufs:/dev/md0c /stand/sysinstall running as init on vty0 - Check the probe results carefully to make sure that FreeBSD found + Check the probe results carefully to make sure that &os; found all the devices you expected. If a device was not found, then it will not be listed. A custom kernel allows you to add in support for devices which are not in the @@ -1187,7 +1187,7 @@ Mounting root from ufs:/dev/md0c Introducing Sysinstall The sysinstall utility is the installation - application provided by the FreeBSD Project. It is console based and is + application provided by the &os; Project. It is console based and is divided into a number of menus and screens that you can use to configure and control the installation process. @@ -1344,7 +1344,7 @@ Mounting root from ufs:/dev/md0c Begin a Standard Installation The Standard installation is the - option recommended for those new to &unix; or FreeBSD. Use the arrow + option recommended for those new to &unix; or &os;. Use the arrow keys to select Standard and then press Enter to start the installation. @@ -1363,15 +1363,15 @@ Mounting root from ufs:/dev/md0c Allocating Disk Space - Your first task is to allocate disk space for FreeBSD, and label + Your first task is to allocate disk space for &os;, and label that space so that sysinstall can prepare - it. In order to do this you need to know how FreeBSD expects to find + it. In order to do this you need to know how &os; expects to find information on the disk. BIOS Drive Numbering - Before you install and configure FreeBSD on your system, there is an + Before you install and configure &os; on your system, there is an important subject that you should be aware of, especially if you have multiple hard drives. @@ -1400,14 +1400,14 @@ Mounting root from ufs:/dev/md0c fashion for up to seven drives. A user who is accustomed to taking advantage of these features may - become surprised when the results with FreeBSD are not as expected. - FreeBSD does not use the BIOS, and does not know the logical BIOS + 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 very perplexing situations, especially when drives are physically identical in geometry, and have also been made as data clones of one another. - When using FreeBSD, always restore the BIOS to natural drive - numbering before installing FreeBSD, and then leave it that way. If you + When using &os;, always restore the BIOS to natural drive + numbering before installing &os;, and then leave it that way. If you need to switch drives around, then do so, but do it the hard way, and open the case and move the jumpers and cables. @@ -1415,9 +1415,9 @@ Mounting root from ufs:/dev/md0c An Illustration from the Files of Bill and Fred's Exceptional Adventures: - Bill breaks-down an older Wintel box to make another FreeBSD box + 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 FreeBSD on it. + installs &os; on it. Fred begins using the system, but after several days notices that the older SCSI drive is reporting numerous soft errors and reports @@ -1432,21 +1432,21 @@ Mounting root from ufs:/dev/md0c that the new drive is installed and functioning nicely, Bill decides that it is a good idea 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. FreeBSD boots and runs just fine. + SCSI unit four. &os; boots and runs just fine. Fred continues his work for several days, and soon Bill and Fred decide that it is time for a new adventure — time to upgrade to a - newer version of FreeBSD. Bill removes SCSI unit zero because it was + newer version of &os;. Bill removes SCSI unit zero because it was a bit flaky and replaces it with another identical disk drive from the archive. Bill then installs the new version of - FreeBSD onto the new SCSI unit zero using Fred's magic Internet FTP + &os; onto the new SCSI unit zero using Fred's magic Internet FTP floppies. The installation goes well. - Fred uses the new version of FreeBSD for a few days, and certifies + 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 (the latest copy of the older FreeBSD version). Fred + SCSI unit four (the latest copy of the older &os; version). Fred is dismayed to find that none of his precious work is present on SCSI unit four. @@ -1456,11 +1456,11 @@ Mounting root from ufs:/dev/md0c 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, he was only fooling himself. - FreeBSD was still running on SCSI unit zero. + &os; was still running on SCSI unit zero. Making this kind of BIOS change will cause some or all of the Boot and Loader code to be fetched from the selected BIOS drive, but when the - FreeBSD kernel drivers take-over, the BIOS drive numbering will be - ignored, and FreeBSD will transition back to normal drive numbering. + &os; kernel drivers take-over, the BIOS drive numbering will be + ignored, and &os; will transition back to normal drive numbering. In the illustration at hand, 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 @@ -1528,7 +1528,7 @@ Mounting root from ufs:/dev/md0c Consider what would happen if you had two IDE hard disks, one as the master on the first IDE controller, and one as the master on - the second IDE controller. If FreeBSD numbered these as it found + the second IDE controller. If &os; numbered these as it found them, as ad0 and ad1 then everything would work. @@ -1538,7 +1538,7 @@ Mounting root from ufs:/dev/md0c ad2. Because device names (such as ad1s1a) are used to find filesystems, you may suddenly discover that some of your filesystems no longer - appear correctly, and you would need to change your FreeBSD + appear correctly, and you would need to change your &os; configuration. To work around this, the kernel can be configured to name IDE @@ -1549,13 +1549,13 @@ Mounting root from ufs:/dev/md0c ad0 or ad1 devices. - This configuration is the default for the FreeBSD kernel, which + This configuration is the default for the &os; kernel, which is why this display 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. - You should select the disk on which you want to install FreeBSD, + You should select the disk on which you want to install &os;, and then press &gui.ok;. FDisk will start, with a display similar to that shown in . @@ -1564,11 +1564,11 @@ Mounting root from ufs:/dev/md0c sections. The first section, covering the first two lines of the display, - shows details about the currently selected disk, including its FreeBSD + 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 FreeBSD + 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 @@ -1592,15 +1592,15 @@ Mounting root from ufs:/dev/md0c What you do now will depend on how you want to slice up your disk. - If you want to use FreeBSD for the entire disk (which will delete + If you want to use &os; for the entire disk (which will delete all the other data on this disk when you confirm that you want sysinstall to continue later in the installation process) then you can 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 (again, an artifact of PC disk - layout), and then one large slice for FreeBSD. If you do this, then - you should select the newly created FreeBSD slice using the arrow + layout), and then one large slice for &os;. If you do this, then + you should 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 very similar to . Note the @@ -1609,7 +1609,7 @@ Mounting root from ufs:/dev/md0c booted from. If you will be deleting an existing slice to make space for - FreeBSD then you should select the slice using the arrow keys, and + &os; then you should select the slice using the arrow keys, and then press D. You can then press C, and be prompted for size of slice you want to create. Enter the appropriate figure and press Enter. The default @@ -1617,7 +1617,7 @@ Mounting root from ufs:/dev/md0c 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 FreeBSD (perhaps by using a + If you have already made space for &os; (perhaps by using a tool such as &partitionmagic;) 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. @@ -1641,26 +1641,26 @@ Mounting root from ufs:/dev/md0c Install a Boot Manager You now have the option to install a boot manager. In general, - you should choose to install the FreeBSD boot manager if: + you should choose to install the &os; boot manager if: - You have more than one drive, and have installed FreeBSD onto + You have more than one drive, and have installed &os; onto a drive other than the first one. - You have installed FreeBSD alongside another operating system - on the same disk, and you want to choose whether to start FreeBSD + You have installed &os; alongside another operating system + on the same disk, and you want to choose whether to start &os; or the other operating system when you start the computer. - If FreeBSD is going to be the only operating system on + 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 you are using a - third-party boot manager capable of booting FreeBSD. + third-party boot manager capable of booting &os;. Make your choice and press Enter. @@ -1684,13 +1684,13 @@ Mounting root from ufs:/dev/md0c If there is more than one drive, it will return to the Select Drives screen after the boot manager selection. If you wish to - install FreeBSD on to more than one disk, then you can select another + install &os; on to more than one disk, then you can select another disk here and repeat the slice process using FDisk. - If you are installing FreeBSD on a drive other than your - first, then the FreeBSD boot manager needs to be installed on + If you are installing &os; on a drive other than your + first, then the &os; boot manager needs to be installed on both drives. @@ -1727,10 +1727,10 @@ Mounting root from ufs:/dev/md0c Certain applications can benefit from particular partition schemes, especially if you are laying out partitions across more than - one disk. However, for this, your first FreeBSD installation, you do + one disk. However, for this, your first &os; installation, you do not need to give too much thought to how you partition the disk. It - is more important that you install FreeBSD and start learning how to - use it. You can always re-install FreeBSD to change your partition + is more important that you install &os; and start learning how to + use it. You can always re-install &os; to change your partition scheme when you are more familiar with the operating system. This scheme features four partitions—one for swap space, and @@ -1768,11 +1768,11 @@ Mounting root from ufs:/dev/md0c This is the root filesystem. Every other filesystem will be mounted somewhere under this one. 1 GB is a reasonable size for this filesystem. You will not be storing - too much data on it, as a regular FreeBSD install will put + too much data on it, as a regular &os; install will put about 128 MB of data here. The remaining space is for temporary data, and also leaves expansion space if future versions of - FreeBSD need more space in /. + &os; need more space in /. @@ -1792,7 +1792,7 @@ Mounting root from ufs:/dev/md0c the swap amount to 64 MB. If you have more than one disk then you can put swap - space on each disk. FreeBSD will then use each disk for + space 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 you need (e.g., 128 MB), and then divide this by the number of @@ -1812,8 +1812,8 @@ Mounting root from ufs:/dev/md0c files that are constantly varying; log files, and other administrative files. Many of these files are read-from or written-to extensively during - FreeBSD's day-to-day running. Putting these files on another - filesystem allows FreeBSD to optimize the access of these + &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. @@ -1839,7 +1839,7 @@ Mounting root from ufs:/dev/md0c Defaults by the &os; partition editor. - If you will be installing FreeBSD on to more than one disk then + If you will be installing &os; on to more than one disk then you must also create partitions in the other slices that you configured. The easiest way to do this is to create two partitions on each disk, one for the swap space, and one for a filesystem. @@ -2068,7 +2068,7 @@ Mounting root from ufs:/dev/md0c /usr, you can leave the suggested size as is, to use the rest of the slice. - Your final FreeBSD DiskLabel Editor screen will appear similar to + Your final &os; DiskLabel Editor screen will appear similar to , although your values chosen may be different. Press Q to finish. @@ -2094,7 +2094,7 @@ Mounting root from ufs:/dev/md0c 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; and/or FreeBSD should almost certainly select one + new to &unix; and/or &os; should almost certainly select one of these canned options. Customizing a distribution set is typically for the more experienced user. @@ -2139,7 +2139,7 @@ Mounting root from ufs:/dev/md0c Installing the Ports Collection After selecting the desired distribution, an opportunity to - install the FreeBSD Ports Collection is presented. The ports + install the &os; Ports Collection is presented. The ports collection is an easy and convenient way to install software. The Ports Collection does not contain the source code necessary to compile the software. Instead, it is a collection of files which @@ -2150,10 +2150,10 @@ Mounting root from ufs:/dev/md0c The installation program does not check to see if you have adequate space. Select this option only if you have - adequate hard disk space. As of FreeBSD &rel.current;, the FreeBSD + adequate hard disk space. As of &os; &rel.current;, the &os; Ports Collection takes up about &ports.size; of disk space. You can safely assume a larger value for more recent versions - of FreeBSD. + of &os;. User Confirmation Requested Would you like to install the FreeBSD ports collection? @@ -2382,7 +2382,7 @@ installation menus to retry whichever op Configuration of various options follows the successful installation. An option can be configured by re-entering the - configuration options before booting the new FreeBSD + configuration options before booting the new &os; system or after installation using sysinstall and selecting @@ -2396,7 +2396,7 @@ installation menus to retry whichever op above. For detailed information on Local Area Networks and - configuring FreeBSD as a gateway/router refer to the + configuring &os; as a gateway/router refer to the Advanced Networking chapter. @@ -3926,7 +3926,7 @@ Password: - FreeBSD Shutdown + &os; Shutdown It is important to properly shutdown the operating system. Do not just turn off power. First, become a superuser by @@ -3966,7 +3966,7 @@ Please press any key to reboot. The following section covers basic installation troubleshooting, such as common problems people have reported. There are also a few - questions and answers for people wishing to dual-boot FreeBSD with + questions and answers for people wishing to dual-boot &os; with &ms-dos; or &windows;. @@ -4283,11 +4283,11 @@ Please press any key to reboot. Advanced Installation Guide - This section describes how to install FreeBSD in exceptional + This section describes how to install &os; in exceptional cases. - Installing FreeBSD on a System without a Monitor or + <title>Installing &os; on a System without a Monitor or Keyboard @@ -4297,7 +4297,7 @@ Please press any key to reboot. serial console This type of installation is called a headless install, because the machine that you are trying to install - FreeBSD on either does not have a monitor attached to it, or does not + &os; on either does not have a monitor attached to it, or does not even have a VGA output. How is this possible you ask? Using a serial console. A serial console is basically using another machine to act as the main display and keyboard for a @@ -4320,8 +4320,8 @@ Please press any key to reboot. mount If you were to boot into the USB stick that you just - made, FreeBSD would boot into its normal install mode. We - want FreeBSD to boot into a serial console for our + made, &os; would boot into its normal install mode. We + want &os; to boot into a serial console for our install. To do this, you have to mount the USB disk onto your &os; system using the &man.mount.8; command. @@ -4438,7 +4438,7 @@ Please press any key to reboot. through your cu session. It will load the kernel and then it will come up with a selection of what kind of terminal to use. Select the - FreeBSD color console and proceed with your install! + &os; color console and proceed with your install! @@ -4447,13 +4447,13 @@ Please press any key to reboot. Preparing Your Own Installation Media - To prevent repetition, FreeBSD disc in this context - means a FreeBSD CDROM or DVD that you have purchased or produced + To prevent repetition, &os; disc in this context + means a &os; CDROM or DVD that you have purchased or produced yourself. There may be some situations in which you need to create your own - FreeBSD installation media and/or source. This might be physical media, + &os; installation media and/or source. This might be physical media, such as a tape, or a source that sysinstall can use to retrieve the files, such as a local FTP site, or an &ms-dos; partition. @@ -4463,16 +4463,16 @@ Please press any key to reboot. You have many machines connected to your local network, and one - FreeBSD disc. You want to create a local FTP site using the - contents of the FreeBSD disc, and then have your machines use this + &os; disc. You want to create a local FTP site using the + contents of the &os; disc, and then have your machines use this local FTP site instead of needing to connect to the Internet. - You have a FreeBSD disc, and FreeBSD does not recognize your + You have a &os; disc, and &os; does not recognize your CD/DVD drive, but &ms-dos; / &windows; does. You want to copy the - FreeBSD installation files to a &ms-dos; partition on the same - computer, and then install FreeBSD using those files. + &os; installation files to a &ms-dos; partition on the same + computer, and then install &os; using those files. @@ -4484,19 +4484,19 @@ Please press any key to reboot. You want to create a tape that can be used to install - FreeBSD. + &os;. Creating an Installation CDROM - As part of each release, the FreeBSD project makes available at + As part of each release, the &os; project makes available at least two CDROM images (ISO images) per supported architecture. These images can be written (burned) to CDs if you have a CD writer, and then used - to install FreeBSD. If you have a CD writer, and bandwidth is cheap, - then this is the easiest way to install FreeBSD. + to install &os;. If you have a CD writer, and bandwidth is cheap, + then this is the easiest way to install &os;. @@ -4536,7 +4536,7 @@ Please press any key to reboot. &os;-version-RELEASE-arch-dvd1.iso.gz This DVD image contains everything necessary to - install the base FreeBSD operating system, a + 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. @@ -4622,7 +4622,7 @@ Please press any key to reboot. Write the CDs You must then write the CD images to disc. If you will be - doing this on another FreeBSD system then see + doing this on another &os; system then see for more information (in particular, and ). @@ -4635,14 +4635,14 @@ Please press any key to reboot. If you are interested in building a customized - release of FreeBSD, please see the Release Engineering Article. - Creating a Local FTP Site with a FreeBSD Disc + Creating a Local FTP Site with a &os; Disc installation @@ -4650,13 +4650,13 @@ Please press any key to reboot. FTP - FreeBSD discs are laid out in the same way as the FTP site. This + &os; discs are laid out in the same way as the FTP site. This makes it very easy for you to create a local FTP site that can be used - by other machines on your network when installing FreeBSD. + by other machines on your network when installing &os;. - On the FreeBSD computer that will host the FTP site, ensure + On the &os; computer that will host the FTP site, ensure that the CDROM is in the drive, and mounted on /cdrom. @@ -4734,7 +4734,7 @@ Please press any key to reboot. the use of improperly formatted media, which is why we are making a point of it now. - If you are creating the floppies on another FreeBSD machine, + If you are creating the floppies on another &os; machine, a format is still not a bad idea, though you do not need to put a &ms-dos; filesystem on each floppy. You can use the bsdlabel and newfs @@ -4787,7 +4787,7 @@ Please press any key to reboot. reproduced within this directory, so we suggest using the &ms-dos; xcopy command if you are copying it from a CD. For example, to prepare for a minimal installation of - FreeBSD: + &os;: C:\> md c:\freebsd C:\> xcopy e:\bin c:\freebsd\bin\ /s @@ -4866,12 +4866,12 @@ Please press any key to reboot. Parallel port (PLIP (laplink cable)). For the fastest possible network installation, an - Ethernet adapter is always a good choice! FreeBSD supports most + Ethernet adapter is always a good choice! &os; supports most common PC Ethernet cards; a table of supported cards (and their required settings) is provided in the Hardware Notes for each - release of FreeBSD. If you are using one of the supported PCMCIA + release of &os;. If you are using one of the supported PCMCIA Ethernet cards, also be sure that it is plugged in - before the laptop is powered on! FreeBSD does + before the laptop is powered on! &os; does not, unfortunately, currently support hot insertion of PCMCIA cards during installation. @@ -4909,7 +4909,7 @@ Please press any key to reboot. If you have problems, logging can be directed to the screen using the command set log local .... - If a hard-wired connection to another FreeBSD + If a hard-wired connection to another &os; machine is available, you might also consider installing over a laplink parallel port cable. The data rate over the parallel port is much higher than what is typically @@ -4925,7 +4925,7 @@ Please press any key to reboot. NFS The NFS installation is fairly straight-forward. Simply - copy the FreeBSD distribution files you want onto an NFS server + copy the &os; distribution files you want onto an NFS server and then point the NFS media selection at it. If this server supports only privileged port @@ -4940,14 +4940,14 @@ Please press any key to reboot. In order for NFS installation to work, the server must support subdir mounts, for example, if your - FreeBSD &rel.current; distribution directory lives on: + &os; &rel.current; distribution directory lives on: ziggy:/usr/archive/stuff/FreeBSD, then ziggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. - In FreeBSD's /etc/exports file, this + In &os;'s /etc/exports file, this is controlled by the options. Other NFS servers may have different conventions. If you are getting permission denied messages from the