From owner-p4-projects@FreeBSD.ORG Mon Feb 20 20:54:08 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id A40FC1065678; Mon, 20 Feb 2012 20:54:08 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65C67106564A for ; Mon, 20 Feb 2012 20:54:08 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 4E8EE8FC0A for ; Mon, 20 Feb 2012 20:54:08 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id q1KKs8Ve024471 for ; Mon, 20 Feb 2012 20:54:08 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q1KKs7kt024468 for perforce@freebsd.org; Mon, 20 Feb 2012 20:54:07 GMT (envelope-from rene@FreeBSD.org) Date: Mon, 20 Feb 2012 20:54:07 GMT Message-Id: <201202202054.q1KKs7kt024468@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 206630 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2012 20:54:08 -0000 http://p4web.freebsd.org/@@206630?ac=10 Change 206630 by rene@rene_acer on 2012/02/20 20:53:48 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#28 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mac/chapter.sgml#12 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#43 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#131 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#78 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/audit/chapter.sgml#18 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/basics/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/config/chapter.sgml#38 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#52 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#58 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/disks/chapter.sgml#37 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.sgml#55 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#33 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/install/chapter.sgml#38 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/jails/chapter.sgml#28 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/l10n/chapter.sgml#24 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mac/chapter.sgml#21 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml#21 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#74 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.sgml#54 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ports/chapter.sgml#29 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#35 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/serialcomms/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/users/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#44 integrate .. //depot/projects/docproj_nl/share/pgpkeys/gibbs.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#70 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#67 integrate .. //depot/projects/docproj_nl/share/sgml/man-refs.ent#40 integrate .. //depot/projects/docproj_nl/www/en/internal/machines.sgml#9 integrate .. //depot/projects/docproj_nl/www/en/releases/8.3R/schedule.sgml#3 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#28 (text+ko) ==== @@ -1,14 +1,14 @@ - Jim + Jim Mock Restructured, reorganized, and parts rewritten by @@ -26,7 +26,7 @@ - Installing FreeBSD + Installing &os; 8.<replaceable>x</replaceable> and Earlier Synopsis @@ -34,11 +34,12 @@ installation FreeBSD is provided with a text-based, easy to use installation - program called sysinstall. This is the - default installation program for FreeBSD, although vendors are free to - provide their own installation suite if they wish. This chapter - describes how to use sysinstall to install - FreeBSD. + program. &os; 9.0-RELEASE and later use the installation program + known as bsdinstall, with releases prior + to 9.0-RELEASE using sysinstall for + installation. This chapter describes the use of sysinstall + to install &os;. The use of bsdinstall + is covered in . After reading this chapter, you will know: @@ -46,7 +47,7 @@ How to create the FreeBSD installation disks. - + How FreeBSD refers to, and subdivides, your hard disks. @@ -73,17 +74,101 @@ In general, these installation instructions are written - for &i386; (PC compatible) architecture - computers. Where applicable, instructions specific to other - platforms (for example, Alpha) will be listed. Although this + for &i386; (PC compatible) architecture + computers. Where applicable, instructions specific to other + platforms will be listed. Although this guide is kept as up to date as possible, you may find minor differences between the installer and what is shown here. It is - suggested that you use this chapter as a general guide rather + suggested that you use this chapter as a general guide rather than a literal installation manual. + + Hardware Requirements + + + Minimal Configuration + + 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 you choose to install &os;, you may + also need a floppy drive, a supported CDROM drive, and in some + case a network adapter. This will be covered by the . + + + &os;/&arch.i386; and &os;/&arch.pc98; + + Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 or + better processor and at least 24 MB of RAM. You will + need at least 150 MB of free hard drive space for the + most minimal installation. + + + In case of old configurations, most of time, getting + more RAM and more hard drive space is more important than + getting a faster processor. + + + + + &os;/&arch.amd64; + + 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, &amd.opteron; or better + processors. + + The second class of processors that can use + &os;/&arch.amd64; 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 you have a machine based on an nVidia nForce3 + Pro-150, you must use the BIOS setup to + disable the IO APIC. If you do not have an option to do + this, you will likely have to disable ACPI instead. There + are bugs in the Pro-150 chipset that we have not found a + workaround for yet. + + + + &os;/&arch.sparc64; + + To install &os;/&arch.sparc64;, you will need a supported + platform (see ). + + You will need a dedicated disk for &os;/&arch.sparc64;. It + is not possible to share a disk with another operating + system at this time. + + + + + Supported Hardware + + A list of supported hardware is provided with each &os; + 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 + sysinstall's documentation menu. + It lists, for a given architecture, what 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; Web site. + + + Pre-installation Tasks @@ -115,10 +200,10 @@ Sample Device Inventory - - - - + + + + Device Name @@ -198,11 +283,15 @@ + + Once the inventory of the components in your computer is + done, you have to check if they match the hardware + requirements of the &os; release you want to install. Backup Your Data - + If the computer you will be installing FreeBSD on contains valuable data, then ensure you have it backed up, and that you have tested the backups before installing FreeBSD. The FreeBSD @@ -223,10 +312,16 @@ laid out on the disk, and how this affects you. - Disk Layouts for the &i386; + Disk Layouts for &os;/&arch.i386; A PC disk can be divided into discrete chunks. These chunks are - called partitions. By design, the PC only + called partitions. Since + &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 + 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 primary partitions. To work around this limitation and allow more than four partitions, a new partition type @@ -240,7 +335,7 @@ partitions have the partition ID of 165. In general, each operating system that you use will identify - partitions in a particular way. For example, DOS, and its + partitions in a particular way. For example, &ms-dos;, and its descendants, like &windows;, assign each primary and logical partition a drive letter, starting with C:. @@ -256,34 +351,36 @@ If you are already using all the partitions on all your disks, then you will have to free one of them for FreeBSD using the tools provided by the other operating systems you use (e.g., - fdisk on DOS or &windows;). + fdisk on &ms-dos; or &windows;). If you have a spare partition then you can use that. However, you may need to shrink one or more of your existing partitions first. - A minimal installation of FreeBSD takes as little as 100 MB of disk + A minimal installation of FreeBSD 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 - is 250 MB without a graphical environment, and 350 MB or more if you + is 250 MB without a graphical environment, and 350 MB or + more if you want a graphical user interface. If you intend to install a lot of - third party software as well, then you will need more space. + third-party software as well, then you will need more space. - You can use a commercial tool such as &partitionmagic;, or a free tool such as GParted, + You can use a commercial tool such as &partitionmagic;, + or a free tool such as GParted, to resize your partitions and make space for - FreeBSD. The tools directory on the CDROM - contains two free software tools which can carry out this task, namely - FIPS and - PResizer. Documentation for both - of these is available in the same directory. - FIPS, - PResizer, and - &partitionmagic; can resize - FAT16 and FAT32 - partitions — used in &ms-dos; through &windows; ME. Both + &os;. Both &partitionmagic; and GParted are known to work on - NTFS. + NTFS. GParted + is available on a number of Live CD Linux distributions, such as + SystemRescueCD. + + Problems have been reported resizing µsoft; Vista + partitions. Having a Vista installation CDROM handy when + attempting such an operation is recommended. As with all + such disk maintenance tasks, a current set of backups is + also strongly advised. Incorrect use of these tools can delete the data on your disk. @@ -294,11 +391,13 @@ Using an Existing Partition Unchanged - Suppose that you have a computer with a single 4 GB disk that + Suppose that you have a computer with a single 4 GB disk + that already has a version of &windows; installed, and you have split the disk into two drive letters, C: and - D:, each of which is 2 GB in size. You have - 1 GB of data on C:, and 0.5 GB of data on + D:, each of which is 2 GB in size. + You have 1 GB of data on C:, and + 0.5 GB of data on D:. This means that your disk has two partitions on it, one per @@ -310,12 +409,12 @@ Shrinking an Existing Partition - Suppose that you have a computer with a single 4 GB disk that - already has a version of &windows; installed. When you installed + Suppose that you have a computer with a single 4 GB disk + 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 of - space. + currently using 1.5 GB of space, and want FreeBSD to have 2 GB + of space. In order to install FreeBSD you will need to either: @@ -334,58 +433,6 @@ - - - Disk Layouts for the Alpha - - Alpha - - You will need a dedicated disk for FreeBSD on the - Alpha. It is not possible to share a disk with another - operating system at this time. Depending on the specific - Alpha machine you have, this disk can either be a SCSI disk - or an IDE disk, as long as your machine is capable of - booting from it. - - Following the conventions of the Digital / Compaq - manuals all SRM input is shown in uppercase. SRM is case - insensitive. - - To find the names and types of disks in your machine, use - the SHOW DEVICE command from the SRM - console prompt: - - >>>SHOW DEVICE -dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476 -dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658 -dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015 -dva0.0.0.0.1 DVA0 -ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01 -pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27 -pqa0.0.0.4.0 PQA0 PCI EIDE -pqb0.0.1.4.0 PQB0 PCI EIDE - - This example is from a Digital Personal Workstation - 433au and shows three disks attached to the machine. The - first is a CDROM drive called DKA0 and - the other two are disks and are called - DKC0 and - DKC100 respectively. - - Disks with names of the form DKx - are SCSI disks. For example DKA100 - refers to a SCSI disk with SCSI target ID 1 on the first SCSI bus (A), - whereas DKC300 refers to a SCSI disk - with SCSI ID 3 on the third SCSI bus (C). Devicename - PKx refers to the SCSI host bus adapter. As - seen in the SHOW DEVICE output SCSI - CDROM drives are treated as any other SCSI hard disk drive. - - IDE disks have names similar to DQx, - while PQx is the associated IDE - controller. - - @@ -402,8 +449,8 @@ Connecting to an Ethernet Network or Cable/DSL Modem If you connect to an Ethernet network, or you have an Internet - connection using an Ethernet adapter via cable or DSL, then you will need the following - information: + connection using an Ethernet adapter via cable or DSL, then you will + need the following information: @@ -459,20 +506,21 @@ Check for FreeBSD Errata - + Although the FreeBSD project strives to ensure that each release of FreeBSD 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 FreeBSD Errata, + which is found on the FreeBSD 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. Information about all the releases, including the errata for each - release, can be found on the + release, can be found on the release - information section of the + information section of the FreeBSD web site. @@ -485,13 +533,17 @@ Local Media - + A CDROM or DVD - A DOS partition on the same computer + A USB Memory Stick + + + + A &ms-dos; partition on the same computer @@ -521,26 +573,26 @@ If you have purchased FreeBSD on CD or DVD then you already have - everything you need, and should proceed to the next section - (). + everything you need, and should proceed to the next section + (). If you have not obtained the FreeBSD installation files you should skip ahead to which explains how to prepare to install FreeBSD from any of the above. After reading - that section, you should come back here, and read on to - . + that section, you should come back here, and read on to + . - + Prepare the Boot Media - + The FreeBSD installation process is started by booting your computer into the FreeBSD installer—it is not a program you run within another operating system. Your computer normally boots using the operating system installed on your hard disk, but it can also be configured to use a bootable floppy disk. Most modern computers can also - boot from a CDROM in the CDROM drive. + boot from a CDROM in the CDROM drive or from a USB disk. If you have FreeBSD on CDROM or DVD (either one you purchased @@ -550,41 +602,159 @@ FreeBSD CDROM and DVD images are bootable and can be used to install FreeBSD without any other special preparation. - + + To create a bootable memory stick, follow these + steps: + + + + Acquire the Memory Stick Image + + Memory stick images for + &os; 8.X and earlier can be downloaded 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 which you want to + install, respectively. For example, the memory stick + images for &os;/&arch.i386; &rel2.current;-RELEASE are + available from . + + + A different directory path is used for + &os; 9.0-RELEASE and later versions. Details of + download and installation of &os; 9.0-RELEASE and + later is covered in . + + + The memory stick image has a .img + extension. The ISO-IMAGES/ directory + contains a number of different images, and the one you + will need to use will depend on the version of &os; you + are installing, and in some cases, the hardware you are + installing to. + + + Before proceeding, back up the + data you currently have on your USB stick, as this + procedure will erase it. + + + + + Write The Image File to the Memory Stick + + + Using FreeBSD 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. + + + + Writing the Image with &man.dd.1; + + The .img file + is not a regular file you copy to the + memory stick. It is an image of the complete contents of the + disk. This means that you cannot simply + copy files from one disk to another. Instead, you must use + &man.dd.1; 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 some + well-intentioned utility program. Then try + again. + + + + + Using &windows; To Write the Image + + + Make sure you use the correct drive letter as the output + target, or you may overwrite and destroy existing data. + + + + 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 + + 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. + + + + + To create boot floppy images, follow these steps: Acquire the Boot Floppy Images - + + + Please note, as of &os; 8.X, floppy disk images are + no longer available. Please see above for instructions + on how to install &os; using a USB memory stick or just + use a CDROM or a DVD. + + The boot disks are available on your installation media in the floppies/ directory, and - can also be downloaded from the floppies directory, ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<arch>/<version>-RELEASE/floppies/. - Replace <arch> and - <version> + can also be downloaded from the floppies directory, + ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/version-RELEASE/floppies/. + Replace arch and + version with the architecture and the version number which you want to install, respectively. For example, the boot floppy images for - &os; &rel.current;-RELEASE for &i386; are available - from . + &os;/&arch.i386; &rel2.current;-RELEASE are available + from . The floppy images have a .flp extension. The floppies/ directory contains a number of different images, and the ones you will need to use depends on the version of FreeBSD you are installing, and in some cases, the hardware you are installing to. - In most cases you will need three + In most cases you will need four floppies, boot.flp, - kern1.flp, and - kern2.flp. Check + kern1.flp, + kern2.flp, and + kern3.flp. Check README.TXT in the same directory for the most up to date information about these floppy images. - Additional device drivers may - be necessary for 5.X systems older than &os; 5.3. - These drivers are provided on the - drivers.flp image. - Your FTP program must use binary mode to download these disk images. Some web browsers have been @@ -596,7 +766,7 @@ Prepare the Floppy Disks - + You must prepare one floppy disk per image file you had to download. It is imperative that these disks are free from defects. The easiest way to test this is to format the disks @@ -628,14 +798,14 @@ DOS If you are creating the floppies on a computer running - &ms-dos;/&windows;, then we provide a tool to do - this called fdimage. + &ms-dos; / &windows;, then we provide a tool to do + this called fdimage. If you are using the floppies from the CDROM, and your - CDROM is the E: drive, then you would + CDROM is the E: drive, then you would run this: - E:\> tools\fdimage floppies\kern.flp A: + E:\> tools\fdimage floppies\boot.flp A: Repeat this command for each .flp file, replacing the floppy disk each time, being sure to label @@ -646,13 +816,13 @@ the tools directory on the FreeBSD FTP site. - + If you are writing the floppies on a &unix; system (such as another FreeBSD system) you can use the &man.dd.1; command to write the image files directly to disk. On FreeBSD, you would run: - - &prompt.root; dd if=kern.flp of=/dev/fd0 + + &prompt.root; dd if=boot.flp of=/dev/fd0 On FreeBSD, /dev/fd0 refers to the first floppy disk (the A: drive). @@ -693,7 +863,7 @@ Booting - Booting for the &i386; + Booting for the &i386; @@ -717,13 +887,14 @@ 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 + and commonly shown as a list of devices, such as Floppy, CDROM, First Hard Disk, and so on. - If you needed to prepare boot floppies, then make sure that the - floppy disk is selected. If you are booting from the CDROM then - make sure that that is selected instead. In case of doubt, you + If you are booting from the CDROM then make sure that + the CDROM is selected. If you are booting from a USB disk or + a floppy disk then + make sure that is selected instead. In case of doubt, you should consult the manual that came with your computer, and/or its motherboard. @@ -732,16 +903,23 @@ - If you needed to prepare boot floppies, as described in - , then one of them will be the - first boot disc, probably the one containing - kern.flp. Put this disc in your floppy - drive. + If you prepared a bootable USB stick, as described in + , then plug in your USB + stick before turning on the computer. If you are booting from CDROM, then you will need to turn on the computer, and insert the CDROM at the first opportunity. + + For &os; 7.X, installation + boot floppies are available and can be prepared as + described in . One of + them will be the first boot disc: + boot.flp. Put this disc in your + floppy drive and boot the computer. + + If your computer starts up as normal and loads your existing operating system, then either: @@ -763,129 +941,133 @@ - + FreeBSD will start to boot. If you are booting from CDROM you - will see a display similar to this (version information omitted): - - Verifying DMI Pool Data ........ -Boot from ATAPI CD-ROM : - 1. FD 2.88MB System Type-(00) -Uncompressing ... done + will see a display similar to this (version information + omitted): + + Booting from CD-Rom... +645MB medium detected +CD Loader 1.2 + +Building the boot loader arguments +Looking up /BOOT/LOADER... Found +Relocating the loader and the BTX +Starting the BTX loader -BTX loader 1.00 BTX version is 1.01 -Console: internal video/keyboard -BIOS drive A: is disk0 -BIOS drive B: is disk1 -BIOS drive C: is disk2 -BIOS drive D: is disk3 -BIOS 639kB/261120kB available memory +BTX loader 1.00 BTX version is 1.02 +Consoles: internal video/keyboard +BIOS CD is cd0 +BIOS drive C: is disk0 +BIOS drive D: is disk1 +BIOS 636kB/261056kB available memory -FreeBSD/i386 bootstrap loader, Revision 0.8 +FreeBSD/i386 bootstrap loader, Revision 1.1 -/kernel text=0x277391 data=0x3268c+0x332a8 | +Loading /boot/defaults/loader.conf +/boot/kernel/kernel text=0x64daa0 data=0xa4e80+0xa9e40 syms=[0x4+0x6cac0+0x4+0x88e9d] +\ -| -Hit [Enter] to boot immediately, or any other key for command prompt. -Booting [kernel] in 9 seconds... _ - If you are booting from floppy disc, you will see a display similar to this (version information omitted): - - Verifying DMI Pool Data ........ + + Booting from Floppy... +Uncompressing ... done -BTX loader 1.00 BTX version is 1.01 -Console: internal video/keyboard -BIOS drive A: is disk0 -BIOS drive C: is disk1 -BIOS 639kB/261120kB available memory +BTX loader 1.00 BTX version is 1.01 +Console: internal video/keyboard +BIOS drive A: is disk0 +BIOS drive C: is disk1 +BIOS 639kB/261120kB available memory -FreeBSD/i386 bootstrap loader, Revision 0.8 +FreeBSD/i386 bootstrap loader, Revision 1.1 +Loading /boot/defaults/loader.conf /kernel text=0x277391 data=0x3268c+0x332a8 | -Please insert MFS root floppy and press enter: +Insert disk labelled "Kernel floppy 1" and press any key... Follow these instructions by removing the - kern.flp disc, insert the - mfsroot.flp disc, and press - Enter. &os; 5.3 - and above provide other floppy disks set, as described - in previous - section. Boot from first floppy; + boot.flp disc, insert the + kern1.flp disc, and press + Enter. Boot from first floppy; when prompted, insert the other disks as required. - Whether you booted from floppy or CDROM, the - boot process will then get to this point: + Whether you booted from CDROM, USB stick or floppy, the + boot process will then get to the &os; boot loader + menu: + +
+ &os; Boot Loader Menu - Hit [Enter] to boot immediately, or any other key for command prompt. -Booting [kernel] in 9 seconds... _ + + + + + +
- Either wait ten seconds, or press Enter + Either wait ten seconds, or press Enter. + - Booting for the Alpha + Booting for &sparc64; - Alpha + Most &sparc64; systems are set up to boot automatically + from disk. To install &os;, you need to boot over the + network or from a CDROM, which requires you to break into + the PROM (OpenFirmware). - - - Start with your computer turned off. - + To do this, reboot the system, and wait until the boot + message appears. It depends on the model, but should look + about like: - - Turn on the computer and wait for a boot monitor - prompt. - + 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 you needed to prepare boot floppies, as described in - then one of them will be the - first boot disc, probably the one containing - kern.flp. Put this disc in your floppy - drive and type the following command to boot the disk - (substituting the name of your floppy drive if - necessary): + If your system proceeds to boot from disk at this point, + you need to press + L1A + or + StopA + on the keyboard, or send a BREAK over the + serial console (using for example ~# in + &man.tip.1; or &man.cu.1;) to get to the PROM prompt. It + looks like this: - >>>BOOT DVA0 -FLAGS '' -FILE '' + + + + + - If you are booting from CDROM, insert the CDROM into - the drive and type the following command to start the - installation (substituting the name of the appropriate - CDROM drive if necessary): + ok +ok {0} - >>>BOOT DKA0 -FLAGS '' -FILE '' - - - - FreeBSD will start to boot. If you are booting from a - floppy disc, at some point you will see the message: + + + This is the prompt used on systems with just one + CPU. + - Please insert MFS root floppy and press enter: + + This is the prompt used on SMP systems, the digit + indicates the number of the active CPU. + + + - Follow these instructions by removing the - kern.flp disc, insert the - mfsroot.flp disc, and press - Enter. - - - - Whether you booted from floppy or CDROM, the - boot process will then get to this point: + At this point, place the CDROM into your drive, and from + the PROM prompt, type boot cdrom. - Hit [Enter] to boot immediately, or any other key for command prompt. -Booting [kernel] in 9 seconds... _ - - Either wait ten seconds, or press Enter. This - will then launch the kernel configuration menu. - - - >>> TRUNCATED FOR MAIL (1000 lines) <<<