From 71b6d856622586e091751e119aa6542cae455dd2 Mon Sep 17 00:00:00 2001 From: Glen Barber Date: Sun, 19 Feb 2012 20:24:34 +0000 Subject: [PATCH] Revert r1.141 which mistakenly removed 9.0-RELEASE additions. Spotted by: rene --- .../books/handbook/install/chapter.sgml | 3686 ++++++++--------- 1 file changed, 1657 insertions(+), 2029 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index eca3915aac..e6365cd9df 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -8,7 +8,7 @@ - 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 @@ We can take no responsibility for lost disk contents! Booting - Booting for the &i386; + Booting for the &i386; @@ -717,13 +887,14 @@ We can take no responsibility for lost disk contents! 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 @@ We can take no responsibility for lost disk contents! - 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,128 +941,132 @@ We can take no responsibility for lost disk contents! - + 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): -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 + Booting from CD-Rom... +645MB medium detected +CD Loader 1.2 -FreeBSD/i386 bootstrap loader, Revision 0.8 +Building the boot loader arguments +Looking up /BOOT/LOADER... Found +Relocating the loader and the BTX +Starting the BTX loader -/kernel text=0x277391 data=0x3268c+0x332a8 | +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 1.1 + +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 ........ -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 + Booting from Floppy... +Uncompressing ... done -FreeBSD/i386 bootstrap loader, Revision 0.8 +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 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: - Hit [Enter] to boot immediately, or any other key for command prompt. -Booting [kernel] in 9 seconds... _ +
+ &os; Boot Loader Menu - 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: - - 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. - - + At this point, place the CDROM into your drive, and from + the PROM prompt, type boot cdrom. @@ -911,15 +1093,15 @@ Booting [kernel] in 9 seconds... _
Typical Device Probe Results - avail memory = 253050880 (247120K bytes) + avail memory = 253050880 (247120K bytes) Preloaded elf kernel "kernel" at 0xc0817000. Preloaded mfs_root "/mfsroot" at 0xc0817084. md0: Preloaded image </mfsroot> 4423680 bytes at 0xc03ddcd4 md1: Malloc disk Using $PIR table, 4 entries at 0xc00fde60 -npx0: <math processor> on motherboard -npx0: INT 16 interface +npx0: <math processor> on motherboard +npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1:<VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 @@ -951,7 +1133,7 @@ isa0: unexpected small tag 14 orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0 fdc0: FIFO enabled, 8 bytes threshold -fd0: <1440-KB 3.5" drive> on fdc0 drive 0 +fd0: <1440-KB 3.5” drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> flags 0x1 irq1 on atkbdc0 kbd0 at atkbd0 @@ -976,42 +1158,44 @@ Mounting root from ufs:/dev/md0c Check the probe results carefully to make sure that FreeBSD found all the devices you expected. If a device was not found, then it will - not be listed. If the device's driver required configuring - with the IRQ and port address then you should check that you entered - them correctly. + not be listed. A custom kernel + allows you to add in support for devices which are not in the + GENERIC kernel, such as sound cards. - If you need to make changes to the UserConfig device probing, - it is easy to exit the sysinstall program - and start over again. It is also a good way to become more familiar - with the process. + After the procedure of device + probing, you will see . Use the + arrow key to choose a country, region, or group. Then press + Enter, it will set your country + easily. -
- Select Sysinstall Exit +
+ Selecting Country Menu - +
- Use the arrow keys to select - Exit Install from the Main - Install Screen menu. The following message will display: + If you selected United States + as 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. +
+ Selecting Keyboard Menu - User Confirmation Requested - Are you sure you wish to exit? The system will reboot - (be sure to remove any floppies from the drives). + + + + + +
- [ Yes ] No - - The install program will start again if the CDROM is left - in the drive and &gui.yes; is selected. - - If you are booting from floppies it will be necessary to remove - the mfsroot.flp floppy and replace it with - kern.flp before rebooting. + After the country selecting, the sysinstall + main menu will display. @@ -1024,9 +1208,10 @@ Mounting root from ufs:/dev/md0c configure and control the installation process. The sysinstall menu system is controlled - by the arrow keys, Enter, Space, and + by the arrow keys, Enter, Tab, + Space, and other keys. A detailed description of these keys and what they do is - contained in sysinstall's usage + contained in sysinstall's usage information. To review this information, ensure that the @@ -1085,7 +1270,7 @@ Mounting root from ufs:/dev/md0c Menu. To return to the Main Installation Menu, select - Exit with the + Exit with the arrow keys and press Enter. @@ -1114,8 +1299,8 @@ Mounting root from ufs:/dev/md0c 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. + Selecting &gui.cancel; by pressing Tab will use the + default keymap and return to the Main Install Menu.
Sysinstall Keymap Menu @@ -1139,7 +1324,7 @@ Mounting root from ufs:/dev/md0c Sysinstall Main Menu - + @@ -1206,17 +1391,17 @@ Mounting root from ufs:/dev/md0c important subject that you should be aware of, especially if you have multiple hard drives. - DOS + MS-DOS Microsoft Windows In a PC running a BIOS-dependent operating system such as &ms-dos; or µ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 so-called primary - master. This is especially convenient for some users who have + master. This is especially convenient for some users who have found that the simplest and cheapest way to keep a system backup is to buy an identical second hard drive, and perform routine copies of the - first drive to the second drive using + first drive to the second drive using Ghost or XCOPY . Then, if the first drive fails, or is attacked by a virus, or is scribbled upon by an @@ -1245,7 +1430,7 @@ 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 for Fred. Bill installs a single SCSI drive as SCSI unit zero and installs FreeBSD on it. @@ -1266,7 +1451,8 @@ Mounting root from ufs:/dev/md0c SCSI unit four. FreeBSD 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 + 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 a bit flaky and replaces it with another identical disk drive from the archive. Bill then installs the new version of @@ -1314,7 +1500,8 @@ Mounting root from ufs:/dev/md0c No changes you make at this point will be written to the disk. If you think you have made a mistake and want to start again you can use the menus to exit sysinstall and try - again or press U to use the Undo option. + again or press U to use the + Undo option. If you get confused and can not see how to exit you can always turn your computer off. @@ -1330,14 +1517,14 @@ Mounting root from ufs:/dev/md0c the disk(s) selected) then use the (A)ll command to select the default partitioning scheme followed by a (Q)uit. If you wish to allocate only free space to FreeBSD, move to a partition marked "unused" and use the - (C)reate command. - [ OK ] + (C)reate command. + [ OK ] [ Press enter or space ] Press Enter as instructed. You will then be shown a list of all the hard drives that the kernel found when it - carried out the device probes. + carried out the device probes. shows an example from a system with two IDE disks. They have been called ad0 and ad2. @@ -1369,7 +1556,7 @@ Mounting root from ufs:/dev/md0c may suddenly discover that some of your filesystems no longer appear correctly, and you would need to change your FreeBSD 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 @@ -1400,9 +1587,10 @@ Mounting root from ufs:/dev/md0c disk, where they start and end, how large they are, the name FreeBSD 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 almost certainly appears - as C: in &ms-dos; / &windows;, and an extended - slice, which may contain other drive letters for &ms-dos; / &windows;. + PC. It also shows one large FAT slice, which + almost certainly appears as C: in + &ms-dos; / &windows;, and an extended slice, which may contain other + drive letters for &ms-dos; / &windows;. The third section shows the commands that are available in FDisk. @@ -1430,7 +1618,7 @@ Mounting root from ufs:/dev/md0c layout), and then one large slice for FreeBSD. If you do this, then you should select the newly created FreeBSD slice using the arrow keys, and press S to mark the slice as being - bootable. The screen will then look very similar to + bootable. The screen will then look very similar to . Note the A in the Flags column, which indicates that this slice is active, and will be @@ -1441,10 +1629,10 @@ Mounting root from ufs:/dev/md0c 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 - value in this box represents the largest possible slice you can + value in this box represents the largest possible slice you can 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 tool such as &partitionmagic;) then you can press C to create a new slice. Again, you will be @@ -1533,7 +1721,7 @@ Mounting root from ufs:/dev/md0c
The Tab key toggles between the last drive - selected, &gui.ok;, and + selected, &gui.ok;, and &gui.cancel;. Press the Tab once to toggle to the @@ -1545,7 +1733,7 @@ Mounting root from ufs:/dev/md0c Creating Partitions Using <application>Disklabel</application> - + You must now create some partitions inside each slice that you have just created. Remember that each partition is lettered, from a through to h, and that @@ -1568,15 +1756,15 @@ Mounting root from ufs:/dev/md0c Partition Layout for First Disk - - - - + + + + Partition - + Filesystem Size @@ -1591,14 +1779,15 @@ Mounting root from ufs:/dev/md0c / - 100 MB + 1 GB This is the root filesystem. Every other filesystem - will be mounted somewhere under this one. 100 MB is a + 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 - about 40 MB of data here. The remaining space is for temporary - data, and also leaves expansion space if future versions of + 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 /. @@ -1609,23 +1798,23 @@ Mounting root from ufs:/dev/md0c 2-3 x RAM - The system's swap space is kept on this partition. + 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 your swap space should be two or three times as much as the available physical memory (RAM). - You should also have at least 64 MB of swap, so if you have - less than 32 MB of RAM in your computer then set the swap - amount to 64 MB. + You should also have at least 64 MB of swap, so if you + have less than 32 MB of RAM in your computer then set + 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. FreeBSD 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 disks - you have (e.g., two disks) to give the amount of swap you - should put on each disk, in this example, 64 MB of swap per - disk. + (e.g., 128 MB), and then divide this by the number of + disks you have (e.g., two disks) to give the amount of swap + you should put on each disk, in this example, 64 MB of + swap per disk. @@ -1633,7 +1822,7 @@ Mounting root from ufs:/dev/md0c /var - 50 MB + 512 MB to 4096 MB The /var directory contains files that are constantly varying; @@ -1650,7 +1839,7 @@ Mounting root from ufs:/dev/md0c /usr - Rest of disk + Rest of disk (at least 8 GB) All your other files will typically be stored in /usr and its subdirectories. @@ -1658,7 +1847,14 @@ 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. + + If you will be installing FreeBSD 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 @@ -1668,15 +1864,15 @@ Mounting root from ufs:/dev/md0c Partition Layout for Subsequent Disks - - - - + + + + Partition - + Filesystem Size @@ -1732,10 +1928,10 @@ Mounting root from ufs:/dev/md0c Message Now, you need to create BSD partitions inside of the fdisk partition(s) just created. If you have a reasonable amount of disk - space (200MB or more) and don't have any special requirements, simply + space (1GB or more) and don't have any special requirements, simply use the (A)uto command to allocate space automatically. If you have more specific needs or just don't care for the layout chosen by - (A)uto, press F1 for more information on manual layout. + (A)uto, press F1 for more information on manual layout. [ OK ] [ Press enter or space ] @@ -1774,7 +1970,9 @@ Mounting root from ufs:/dev/md0c
Disklabel can automatically create - partitions for you and assign them default sizes. Try this now, by + partitions for you and assign them default sizes. The default sizes + are calculated with the help of an internal partition sizing algorithm + based on the disk size. Try this now, by Pressing A. You will see a display similar to that shown in . Depending on the size of the disk you are using, the defaults may or may not be appropriate. @@ -1806,7 +2004,8 @@ Mounting root from ufs:/dev/md0c suggested partitions. To create the first partition (a, mounted as - / — root), make sure the proper disk slice at the top of + / — root), make sure the proper disk slice + at the top of the screen is selected and press C. A dialog box will appear prompting you for the size of the new partition (as shown in ). You can enter the size as @@ -1815,15 +2014,6 @@ Mounting root from ufs:/dev/md0c G for gigabytes, or C for cylinders. - Beginning with FreeBSD 5.X, users can: select - UFS2 (which is default on &os; 5.1 and - above) using the Custom Newfs - (Z) option, create labels with - Auto Defaults and modify them with the Custom Newfs option or - add during the regular creation period. - Do not forget to add for SoftUpdates if you use the Custom Newfs - option! -
Free Space for Root Partition @@ -1838,10 +2028,10 @@ Mounting root from ufs:/dev/md0c rest of the slice. If you are using the partition sizes described in the earlier example, then delete the existing figure using Backspace, and then type in - 64M, as shown in + 512M, as shown in . Then press &gui.ok;. - +
Edit Root Partition Size @@ -1861,17 +2051,17 @@ Mounting root from ufs:/dev/md0c
Choose the Root Partition Type - +
- + Finally, because you are creating a filesystem, you must tell Disklabel where the filesystem is to be - mounted. The dialog box is shown in + mounted. The dialog box is shown in . The root filesystem's mount point is /, so type /, and then press Enter. @@ -1900,7 +2090,7 @@ Mounting root from ufs:/dev/md0c
Sysinstall Disklabel Editor - + @@ -1924,22 +2114,16 @@ Mounting root from ufs:/dev/md0c of these canned options. Customizing a distribution set is typically for the more experienced user. - Press F1 for more information on the + Press F1 for more information on the distribution set options and what they contain. When finished reviewing the help, pressing Enter will return to the Select Distributions Menu. - If a graphical user interface is desired then a distribution - set that is preceded by an X should be - chosen. The configuration of the X server and selection of a default + If a graphical user interface is desired then the + configuration of the X server and selection of a default desktop must be done after the installation of &os;. More - information regarding the configuration of a X server can be - found in . - - The default version of X11 that is installed depends on the - version of FreeBSD that you are installing. For FreeBSD versions - prior to 5.3, &xfree86; 4.X is installed. For &os; 5.3 and later, - &xorg; is the default. + information regarding the installation and configuration of a + X server 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 @@ -1947,7 +2131,7 @@ Mounting root from ufs:/dev/md0c . Obviously, the most versatile system is one that includes - everything. If there is adequate disk space, select + everything. If there is adequate disk space, select All as shown in by using the arrow keys and press Enter. If there is a concern about disk @@ -1988,21 +2172,21 @@ Mounting root from ufs:/dev/md0c of FreeBSD. User Confirmation Requested - Would you like to install the FreeBSD ports collection? + Would you like to install the FreeBSD ports collection? This will give you ready access to over &os.numports; ported software packages, at a cost of around &ports.size; of disk space when "clean" and possibly much more than that if a lot of the distribution tarballs are loaded (unless you have the extra CDs from a FreeBSD CD/DVD distribution available and can mount it on /cdrom, in which case this is far less - of a problem). + of a problem). The Ports Collection is a very valuable resource and well worth having - on your /usr partition, so it is advisable to say Yes to this option. + on your /usr partition, so it is advisable to say Yes to this option. For more information on the Ports Collection & the latest ports, - visit: - http://www.FreeBSD.org/ports + visit: + http://www.FreeBSD.org/ports [ Yes ] No @@ -2032,11 +2216,11 @@ Mounting root from ufs:/dev/md0c Choosing Your Installation Media - If Installing from a CDROM or DVD, use the arrow keys to highlight + If Installing from a CDROM or DVD, use the arrow keys to highlight Install from a FreeBSD CD/DVD. Ensure 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. @@ -2062,7 +2246,7 @@ Mounting root from ufs:/dev/md0c network FTP - + There are three FTP installation modes you can choose from: active FTP, passive FTP, or via a HTTP proxy. @@ -2070,9 +2254,9 @@ Mounting root from ufs:/dev/md0c FTP Active: Install from an FTP server - + - This option will make all FTP transfers + This option will make all FTP transfers use Active mode. This will not work through firewalls, but will often work with older FTP servers that do not support @@ -2080,36 +2264,37 @@ Mounting root from ufs:/dev/md0c mode (the default), try active! - + FTP Passive: Install from an FTP server through a firewall - + FTP passive mode - This option instructs sysinstall to use - Passive mode for all FTP operations. + This option instructs sysinstall + to Passive mode for all FTP operations. This allows the user to pass through firewalls that do not allow incoming connections on random TCP ports. - + FTP via a HTTP proxy: Install from an FTP server through a http proxy - + FTP via a HTTP proxy - - This option instructs sysinstall to use the HTTP + + This option instructs sysinstall + to use the HTTP protocol (like a web browser) to connect to a proxy for all FTP operations. The proxy will translate the requests and send them to the FTP server. @@ -2121,26 +2306,26 @@ Mounting root from ufs:/dev/md0c - + For a proxy FTP server, you should usually give the name of the server you really want as a part of the username, after an @ sign. The proxy server then fakes the real server. For example, assuming you want to install from ftp.FreeBSD.org, using the proxy FTP server foo.example.com, listening on port - 1024. - + 1234. + In this case, you go to the options menu, set the FTP username to ftp@ftp.FreeBSD.org, and the password to your email address. As your installation media, you 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 + Since /pub/FreeBSD from + ftp.FreeBSD.org is proxied under foo.example.com, you are able to install from that machine (which will fetch the files - from ftp.FreeBSD.org as your + from ftp.FreeBSD.org as your installation requests them). @@ -2153,39 +2338,39 @@ Mounting root from ufs:/dev/md0c to the hard drive. User Confirmation Requested - Last Chance! Are you SURE you want to continue the installation? + Last Chance! Are you SURE you want to continue the installation? If you're running this on a disk with data you wish to save then WE - STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding! + STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding! - We can take no responsibility for lost disk contents! + We can take no responsibility for lost disk contents! [ Yes ] No - Select &gui.yes; and press + 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 is complete when the following message is displayed: - Message + Message -Congratulations! You now have FreeBSD installed on your system. +Congratulations! You now have FreeBSD installed on your system. -We will now move on to the final configuration questions. -For any option you do not wish to configure, simply select No. +We will now move on to the final configuration questions. +For any option you do not wish to configure, simply select No. If you wish to re-enter this utility after the system is up, you may -do so by typing: /stand/sysinstall . +do so by typing: /usr/sbin/sysinstall. - [ OK ] + [ OK ] - [ Press enter to continue ] + [ Press enter or space ] Press Enter to proceed with post-installation configurations. @@ -2197,9 +2382,9 @@ do so by typing: /stand/sysinstall . Message Installation complete with some errors. You may wish to scroll -through the debugging messages on VTY1 with the scroll-lock feature. +through the debugging messages on VTY1 with the scroll-lock feature. You can also choose "No" at the next prompt and go back into the -installation menus to retry whichever operations have failed. +installation menus to retry whichever operations have failed. [ OK ] @@ -2211,12 +2396,12 @@ installation menus to retry whichever operations have failed. Post-installation - Configuration of various options follows the successful + Configuration of various options follows the successful installation. An option can be configured by re-entering the configuration options before booting the new FreeBSD system or after installation using - sysinstall (/stand/sysinstall - in &os; versions older than 5.2) and selecting + sysinstall + and selecting Configure. @@ -2231,8 +2416,8 @@ installation menus to retry whichever operations have failed. Advanced Networking chapter. - User Confirmation Requested - Would you like to configure any Ethernet or SLIP/PPP network devices? + User Confirmation Requested + Would you like to configure any Ethernet or PPP network devices? [ Yes ] No @@ -2253,7 +2438,7 @@ installation menus to retry whichever operations have failed. Select the interface to be configured with the arrow keys and press Enter. - User Confirmation Requested + User Confirmation Requested Do you want to try IPv6 configuration of the interface? Yes [ No ] @@ -2268,7 +2453,7 @@ installation menus to retry whichever operations have failed. &gui.yes; and press Enter. It will take several seconds to scan for RA servers. - User Confirmation Requested + User Confirmation Requested Do you want to try DHCP configuration of the interface? Yes [ No ] @@ -2304,7 +2489,8 @@ installation menus to retry whichever operations have failed. 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. @@ -2314,7 +2500,8 @@ installation menus to retry whichever operations have failed. The name of the domain that your machine is - in, such as example.com for this case. + in, such as example.com + for this case. @@ -2379,8 +2566,8 @@ installation menus to retry whichever operations have failed. when finished and press Enter. - User Confirmation Requested - Would you like to Bring Up the ed0 interface right now? + User Confirmation Requested + Would you like to bring the ed0 interface up right now? [ Yes ] No @@ -2394,7 +2581,7 @@ installation menus to retry whichever operations have failed. Configure Gateway - User Confirmation Requested + User Confirmation Requested Do you want this machine to function as a network gateway? [ Yes ] No @@ -2402,7 +2589,7 @@ installation menus to retry whichever operations have failed. If the machine will be acting as the gateway for a local area network and forwarding packets between other machines then select &gui.yes; and press Enter. - If the machine is a node on a network then + If the machine is a node on a network then select &gui.no; and press Enter to continue. @@ -2419,7 +2606,7 @@ Do you want to configure inetd and the network services that it provides? such telnetd will not be enabled. This means that remote users will not be able to telnet into this machine. Local users - will be still be able to access remote machines with + will still be able to access remote machines with telnet. These services can be enabled after installation by editing @@ -2470,11 +2657,30 @@ use the current settings.
After adding the desired services, pressing Esc - will display a menu which will allow exiting and saving + will display a menu which will allow exiting and saving the changes. + + Enabling SSH login + + + SSH + sshd + + + User Confirmation Requested + Would you like to enable SSH login? + Yes [ No ] + + Selecting &gui.yes; will enable &man.sshd.8;, the daemon + program for OpenSSH. This will + allow secure remote access to your machine. For more + information about OpenSSH see . + + Anonymous FTP @@ -2484,13 +2690,13 @@ use the current settings. User Confirmation Requested - Do you want to have anonymous FTP access to this machine? + Do you want to have anonymous FTP access to this machine? Yes [ No ] 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. @@ -2506,7 +2712,32 @@ use the current settings. To allow anonymous FTP, use the arrow keys to select &gui.yes; and press Enter. - The following screen (or similar) will display: + An additional confirmation will display: + + User Confirmation Requested + Anonymous FTP permits un-authenticated users to connect to the system + FTP server, if FTP service is enabled. Anonymous users are + restricted to a specific subset of the file system, and the default + configuration provides a drop-box incoming directory to which uploads + are permitted. You must separately enable both inetd(8), and enable + ftpd(8) in inetd.conf(5) for FTP services to be available. If you + did not do so earlier, you will have the opportunity to enable inetd(8) + again later. + + If you want the server to be read-only you should leave the upload + directory option empty and add the -r command-line option to ftpd(8) + in inetd.conf(5) + + Do you wish to continue configuring anonymous FTP? + + [ Yes ] No + + This message informs you that the FTP service will also + have to be enabled in /etc/inetd.conf + if you want to allow anonymous FTP connections, see . Select &gui.yes; and press + Enter to continue; the following screen + will display:
Default Anonymous FTP Configuration @@ -2518,38 +2749,67 @@ use the current settings.
- Pressing F1 will display the help: + Use Tab to select the information + fields and fill in appropriate information: - This screen allows you to configure the anonymous FTP user. + + + UID -The following configuration values are editable: + + The user ID you wish to assign to the anonymous + FTP user. All files uploaded will be owned by this + ID. + + -UID: The user ID you wish to assign to the anonymous FTP user. - All files uploaded will be owned by this ID. + + Group -Group: Which group you wish the anonymous FTP user to be in. + + Which group you wish the anonymous FTP user to be + in. + + -Comment: String describing this user in /etc/passwd + + Comment + + String describing this user in + /etc/passwd. + + -FTP Root Directory: + + FTP Root Directory - Where files available for anonymous FTP will be kept. + + Where files available for anonymous FTP will be + kept. + + -Upload subdirectory: + + Upload Subdirectory - Where files uploaded by anonymous FTP users will go. + + Where files uploaded by anonymous FTP users will + go. + + + - The ftp root directory will be put in /var + The FTP root directory will be put in /var by default. If you do not have enough room there for the anticipated FTP needs, the /usr directory - could be used by setting the FTP Root Directory to + could be used by setting the FTP root directory to /usr/ftp. - When you are satisfied with the values, press + When you are satisfied with the values, press Enter to continue. - User Confirmation Requested + User Confirmation Requested Create a welcome message file for anonymous FTP users? [ Yes ] No @@ -2592,7 +2852,7 @@ Upload subdirectory: NFS Server User Confirmation Requested - Do you want to configure this machine as an NFS server? + Do you want to configure this machine as an NFS server? Yes [ No ] @@ -2640,7 +2900,7 @@ Press [Enter] now to invoke an editor on /etc/exports The NFS client allows your machine to access NFS servers. User Confirmation Requested - Do you want to configure this machine as an NFS client? + Do you want to configure this machine as an NFS client? Yes [ No ] @@ -2650,191 +2910,13 @@ Press [Enter] now to invoke an editor on /etc/exports - - Security Profile - - A security profile is a set of - configuration options that attempts to achieve the desired - ratio of security to convenience by enabling and disabling - certain programs and other settings. The more severe the - security profile, the fewer programs will be enabled by - default. This is one of the basic principles of security: do - not run anything except what you must. - - Please note that the security profile is just a default - setting. All programs can be enabled and disabled after you - have installed FreeBSD by editing or adding the appropriate - line(s) to /etc/rc.conf. For more - information, please see the &man.rc.conf.5; manual - page. - - The following table describes what each of the security - profiles does. The columns are the choices you have for a - security profile, and the rows are the program or feature that - the profile enables or disables. - - - Possible Security Profiles - - - - - - - Extreme - - Moderate - - - - - - - &man.sendmail.8; - - NO - - YES - - - - &man.sshd.8; - - NO - - YES - - - - &man.portmap.8; - - NO - - MAYBE - - The portmapper is enabled if the machine has - been configured as an NFS client or server earlier - in the installation. - - - - - - NFS server - - NO - - YES - - - - &man.securelevel.8; - - YES - - If you choose a security profile that sets the - securelevel to Extreme or - High, you must be aware of the - implications. Please read the &man.init.8; - manual page and pay particular attention to the - meanings of the security levels, or you may have - significant trouble later! - - - - NO - - - -
- - User Confirmation Requested - Do you want to select a default security profile for this host (select - No for "medium" security)? - - [ Yes ] No - - Selecting &gui.no; and pressing - Enter will set the security profile to medium. - - Selecting &gui.yes; and pressing - Enter will allow selecting a different security - profile. - -
- Security Profile Options - - - - - - -
- - Press F1 to display the help. Press - Enter to return to selection menu. - - Use the arrow keys to choose Medium - unless your are sure that another level is required for your needs. - With &gui.ok; highlighted, press - Enter. - - An appropriate confirmation message will display depending on - which security setting was chosen. - - Message - -Moderate security settings have been selected. - -Sendmail and SSHd have been enabled, securelevels are -disabled, and NFS server setting have been left intact. -PLEASE NOTE that this still does not save you from having -to properly secure your system in other ways or exercise -due diligence in your administration, this simply picks -a standard set of out-of-box defaults to start with. - -To change any of these settings later, edit /etc/rc.conf - - [OK] - - Message - -Extreme security settings have been selected. - -Sendmail, SSHd, and NFS services have been disabled, and -securelevels have been enabled. -PLEASE NOTE that this still does not save you from having -to properly secure your system in other ways or exercise -due diligence in your administration, this simply picks -a more secure set of out-of-box defaults to start with. - -To change any of these settings later, edit /etc/rc.conf - - [OK] - - Press Enter to continue with the - post-installation configuration. - - - The security profile is not a silver bullet! Even if - you use the extreme setting, you need to keep up with - security issues by reading an appropriate mailing - list (), - using good passwords and passphrases, and - generally adhering to good security practices. It simply - sets up the desired security to convenience ratio out of the - box. - - - - System Console Settings There are several options available to customize the system console. - User Confirmation Requested + User Confirmation Requested Would you like to customize your system console settings? [ Yes ] No @@ -2917,7 +2999,7 @@ To change any of these settings later, edit /etc/rc.conf time zone of the United States. Your selections will vary according to your geographical location. - User Confirmation Requested + User Confirmation Requested Would you like to set this machine's time zone now? [ Yes ] No @@ -2927,11 +3009,11 @@ To change any of these settings later, edit /etc/rc.conf User Confirmation Requested Is this machine's CMOS clock set to UTC? If it is set to local time - or you don't know, please choose NO here! + or you don't know, please choose NO here! Yes [ No ] - Select &gui.yes; + Select &gui.yes; or &gui.no; according to how the machine's clock is configured and press Enter. @@ -2974,7 +3056,7 @@ To change any of these settings later, edit /etc/rc.conf The appropriate time zone is selected using the arrow keys and pressing Enter. - Confirmation + Confirmation Does the abbreviation 'EDT' look reasonable? [ Yes ] No @@ -2987,7 +3069,13 @@ To change any of these settings later, edit /etc/rc.conf Linux Compatibility - User Confirmation Requested + + This part only applies to &os; 7.X + installation, if you install &os; 8.X + this screen will not be proposed. + + + User Confirmation Requested Would you like to enable Linux binary compatibility? [ Yes ] No @@ -3012,12 +3100,12 @@ To change any of these settings later, edit /etc/rc.conf details on emulating the 3-button style. This example depicts a non-USB mouse configuration (such as a PS/2 or COM port mouse): - User Confirmation Requested - Does this system have a non-USB mouse attached to it? + User Confirmation Requested + Does this system have a PS/2, serial, or bus mouse? [ Yes ] No - Select &gui.yes; for a non-USB mouse or + Select &gui.yes; for a PS/2, serial or bus mouse, or &gui.no; for a USB mouse and press Enter. @@ -3114,15 +3202,356 @@ To change any of these settings later, edit /etc/rc.conf post-installation configuration. + + 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 + sysinstall can be used to add additional + packages. + + User Confirmation Requested + The FreeBSD package collection is a collection of hundreds of + ready-to-run applications, from text editors to games to WEB servers + and more. Would you like to browse the collection now? + + [ Yes ] No + + Selecting &gui.yes; and pressing + Enter will be + followed by the Package Selection screens: + +
+ Select Package Category + + + + + + +
+ + Only packages on the current installation media are + available for installation at any given time. + + All packages available will be displayed if + All is selected or you can select a + particular category. Highlight your selection with the arrow + keys and press Enter. + + A menu will display showing all the packages available for + the selection made: + +
+ Select Packages + + + + + + +
+ + The bash shell is shown selected. + Select as many as desired by highlighting the package and pressing the + Space key. A short description of each package will + appear in the lower left corner of the screen. + + Pressing the Tab key will toggle between the last + selected package, &gui.ok;, and &gui.cancel;. + + When you have finished marking the packages for installation, + press Tab once to toggle to the &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 + + + + + + +
+ + Use the Tab and arrow keys to select [ Install ] + and press Enter. You will then need to confirm + that you want to install the packages: + +
+ Confirm Package Installation + + + + + + +
+ + Selecting &gui.ok; and pressing Enter will start + the package installation. Installing messages will appear until + completed. Make note if there are any error messages. + + The final configuration continues after packages are + installed. If you end up not selecting any packages, and wish + to return to the final configuration, select + Install anyways. + + + + Add Users/Groups + + You should add at least one user during the installation so + that you can use the system without being logged 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 + at least one account for yourself at this stage is suggested since + working as the "root" user is dangerous (it is easy to do things which + adversely affect the entire system). + + [ Yes ] No + + Select &gui.yes; and press + Enter to continue with adding a user. + +
+ Select User + + + + + + +
+ + Select User with the arrow keys + and press Enter. + +
+ Add User 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: + + + + Login ID + + + The login name of the new user (mandatory). + + + + + UID + + + The numerical ID for this user (leave blank for + automatic choice). + + + + + Group + + + The login group name for this user (leave blank for + automatic choice). + + + + + Password + + + The password for this user (enter this field with + care!). + + + + + Full name + + + The user's full name (comment). + + + + + Member groups + + + The groups this user belongs to (i.e. gets access + rights for). + + + + + Home directory + + + The user's home directory (leave blank for + default). + + + + + Login shell + + The user's login shell (leave blank for + default, e.g. /bin/sh). + + + + + 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 try to use a shell that does not exist or you will + not be able to login. The most common shell used in the + BSD-world is the C shell, which can be indicated as + /bin/tcsh. + + The user was also added to the wheel group + to be able to become a superuser with root + privileges. + + When you are satisfied, press &gui.ok; and + the User and Group Management menu will redisplay: + +
+ Exit User and Group Management + + + + + + +
+ + Groups can also be added at this time if specific needs + are known. Otherwise, this may be accessed through using + sysinstall + after installation is + completed. + + When you are finished adding users, select + Exit with the arrow keys and press + Enter to continue the installation. + + + + Set the <username>root</username> Password + + Message + Now you must set the system manager's password. + This is the password you'll use to log in as "root". + + [ OK ] + + [ Press enter or space ] + + Press Enter to set the root + password. + + The password will need to be typed in twice correctly. Needless to + say, make sure you have a way of finding the password if you + forget. Notice that the password you type in is not echoed, nor + are asterisks displayed. + + New password: +Retype new password : + + The installation will continue after the password is + successfully entered. + + + + Exiting Install + + If you need to configure + additional network services + or any other configuration, you can do it at this point or + after installation with sysinstall. + + User Confirmation Requested + Visit the general configuration menu for a chance to set any last + options? + + Yes [ No ] + + Select &gui.no; with the arrow keys + and press Enter to return to the Main + Installation Menu. + +
+ Exit Install + + + + + + +
+ + Select [X Exit Install] with the arrow + keys and press Enter. You will be asked 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 you are 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. + + [ OK ] + [ Press enter or space ] + + The CDROM drive is locked until the machine + starts to reboot then the disk can + be removed from drive (quickly). Press &gui.ok; to reboot. + + The system will reboot so watch for any error messages that + may appear, see for more + details. + + - - - Tom - Rhodes - Contributed by - - + + + Tom + Rhodes + Contributed by + + Configure Additional Network Services @@ -3161,9 +3590,9 @@ To change any of these settings later, edit /etc/rc.conf
- The first option, Interfaces, was previously covered during - the , thus this option can - safely be ignored. + The first option, Interfaces, was + previously covered during the , + thus this option can safely be ignored. Selecting the AMD option adds support for the BSD automatic mount utility. @@ -3207,15 +3636,15 @@ To change any of these settings later, edit /etc/rc.conf The Gateway configuration menu will set the machine up to be a gateway as explained previously. This - can be used to unset the Gateway option if you accidentally - selected it during the installation process. + can be used to unset the Gateway option if + you accidentally selected it during the installation process. The Inetd option can be used to configure or completely disable the &man.inetd.8; daemon as discussed above. - The Mail option is used to configure the system's - default MTA or Mail Transfer Agent. + The Mail option is used to configure the + system's default MTA or Mail Transfer Agent. Selecting this option will bring up the following menu:
@@ -3236,8 +3665,8 @@ To change any of these settings later, edit /etc/rc.conf Selecting Sendmail will install the popular sendmail server which - is the &os; default. The Sendmail local option - will set sendmail to be the default + is the &os; default. The Sendmail local + option will set sendmail to be the default MTA, but disable its ability to receive incoming email from the Internet. The other options here, Postfix and @@ -3256,7 +3685,7 @@ To change any of these settings later, edit /etc/rc.conf NFS. An NFS server makes file systems available to other machines on the network via the NFS protocol. If this is - a stand alone machine, this option can remain unselected. + a stand-alone machine, this option can remain unselected. The system may require more configuration later; see for more information about client and server configuration. @@ -3367,942 +3796,20 @@ To change any of these settings later, edit /etc/rc.conf beneficial for stand alone machines. Now that you have configured the network services, you can - scroll up to the very top item which is Exit - and continue on to the next configuration section. + scroll up to the very top item which is + X Exit + and continue on to the next configuration item or simply exit + sysinstall in selecting + X Exit twice then [X + Exit Install]. - - Configure X Server - - - As of &os; 5.3-RELEASE, the X server configuration - facility has been removed from - sysinstall, you have to install - and configure the X server after the installation of &os;. - More information regarding the installation and the - configuration of a X server can be found in . You can skip this section if you are not - installing a &os; version prior to 5.3-RELEASE. - - - In order to use a graphical user interface such as - KDE, GNOME, - or others, the X server will need to be configured. - - - In order to run &xfree86; as a - non root user you will need to - have x11/wrapper installed. - This is installed by default beginning with FreeBSD 4.7. For - earlier versions this can be added - from the Package Selection menu. - - - To see whether your video card is supported, check the - &xfree86; web site. - - User Confirmation Requested - Would you like to configure your X server at this time? - - [ Yes ] No - - - It is necessary to know your monitor specifications and - video card information. Equipment damage can occur if settings - are incorrect. If you do not have this information, select - &gui.no; and perform the configuration - after installation when you have the information using - sysinstall (/stand/sysinstall - in &os; versions older than 5.2), selecting - Configure and then - XFree86. Improper configuration - of the X server at this time can leave the machine in a - frozen state. It is often advised to configure the X server - once the installation has completed. - - - - If you have graphics card and monitor information, select - &gui.yes; and press Enter - to proceed with configuring the X server. - -
- Select Configuration Method Menu - - - - - - -
- - There are several ways to configure the X server. - Use the arrow keys to select one of the methods and press - Enter. Be sure to read all instructions - carefully. - - The xf86cfg and - xf86cfg -textmode methods may make the screen - go dark and take a few seconds to start. Be patient. - - - The following will illustrate the use of the - xf86config configuration tool. The - configuration choices you make will depend on the hardware in the - system so your choices will probably be different than those - shown: - - Message - You have configured and been running the mouse daemon. - Choose "/dev/sysmouse" as the mouse port and "SysMouse" or - "MouseSystems" as the mouse protocol in the X configuration utility. - - [ OK ] - - [ Press enter to continue ] - - This indicates that the mouse daemon previously configured has been - detected. - Press Enter to continue. - - Starting xf86config will display - a brief introduction: - - This program will create a basic XF86Config file, based on menu selections you -make. - -The XF86Config file usually resides in /usr/X11R6/etc/X11 or /etc/X11. A sample -XF86Config file is supplied with XFree86; it is configured for a standard -VGA card and monitor with 640x480 resolution. This program will ask for a -pathname when it is ready to write the file. - -You can either take the sample XF86Config as a base and edit it for your -configuration, or let this program produce a base XF86Config file for your -configuration and fine-tune it. - -Before continuing with this program, make sure you know what video card -you have, and preferably also the chipset it uses and the amount of video -memory on your video card. SuperProbe may be able to help with this. - -Press enter to continue, or ctrl-c to abort. - - Pressing Enter will start the mouse - configuration. Be sure to follow the instructions and use - Mouse Systems as the mouse protocol and - /dev/sysmouse as the mouse port even if - using a PS/2 mouse is shown as an illustration. - - First specify a mouse protocol type. Choose one from the following list: - - 1. Microsoft compatible (2-button protocol) - 2. Mouse Systems (3-button protocol) & FreeBSD moused protocol - 3. Bus Mouse - 4. PS/2 Mouse - 5. Logitech Mouse (serial, old type, Logitech protocol) - 6. Logitech MouseMan (Microsoft compatible) - 7. MM Series - 8. MM HitTablet - 9. Microsoft IntelliMouse - -If you have a two-button mouse, it is most likely of type 1, and if you have -a three-button mouse, it can probably support both protocol 1 and 2. There are -two main varieties of the latter type: mice with a switch to select the -protocol, and mice that default to 1 and require a button to be held at -boot-time to select protocol 2. Some mice can be convinced to do 2 by sending -a special sequence to the serial port (see the ClearDTR/ClearRTS options). - -Enter a protocol number: 2 - -You have selected a Mouse Systems protocol mouse. If your mouse is normally -in Microsoft-compatible mode, enabling the ClearDTR and ClearRTS options -may cause it to switch to Mouse Systems mode when the server starts. - -Please answer the following question with either 'y' or 'n'. -Do you want to enable ClearDTR and ClearRTS? n - -You have selected a three-button mouse protocol. It is recommended that you -do not enable Emulate3Buttons, unless the third button doesn't work. - -Please answer the following question with either 'y' or 'n'. -Do you want to enable Emulate3Buttons? y - -Now give the full device name that the mouse is connected to, for example -/dev/tty00. Just pressing enter will use the default, /dev/mouse. -On FreeBSD, the default is /dev/sysmouse. - -Mouse device: /dev/sysmouse - - The keyboard is the next item to be configured. A generic - 101-key model is shown for illustration. Any name may be used - for the variant or simply press Enter to accept - the default value. - - Please select one of the following keyboard types that is the better -description of your keyboard. If nothing really matches, -choose 1 (Generic 101-key PC) - - 1 Generic 101-key PC - 2 Generic 102-key (Intl) PC - 3 Generic 104-key PC - 4 Generic 105-key (Intl) PC - 5 Dell 101-key PC - 6 Everex STEPnote - 7 Keytronic FlexPro - 8 Microsoft Natural - 9 Northgate OmniKey 101 - 10 Winbook Model XP5 - 11 Japanese 106-key - 12 PC-98xx Series - 13 Brazilian ABNT2 - 14 HP Internet - 15 Logitech iTouch - 16 Logitech Cordless Desktop Pro - 17 Logitech Internet Keyboard - 18 Logitech Internet Navigator Keyboard - 19 Compaq Internet - 20 Microsoft Natural Pro - 21 Genius Comfy KB-16M - 22 IBM Rapid Access - 23 IBM Rapid Access II - 24 Chicony Internet Keyboard - 25 Dell Internet Keyboard - -Enter a number to choose the keyboard. - -1 - - -Please select the layout corresponding to your keyboard - - - 1 U.S. English - 2 U.S. English w/ ISO9995-3 - 3 U.S. English w/ deadkeys - 4 Albanian - 5 Arabic - 6 Armenian - 7 Azerbaidjani - 8 Belarusian - 9 Belgian - 10 Bengali - 11 Brazilian - 12 Bulgarian - 13 Burmese - 14 Canadian - 15 Croatian - 16 Czech - 17 Czech (qwerty) - 18 Danish - -Enter a number to choose the country. -Press enter for the next page - -1 - - -Please enter a variant name for 'us' layout. Or just press enter -for default variant - -us - - -Please answer the following question with either 'y' or 'n'. -Do you want to select additional XKB options (group switcher, -group indicator, etc.)? n - - Next, we proceed to the configuration for the monitor. Do not - exceed the ratings of your monitor. Damage could occur. If you - have any doubts, do the configuration after you have the - information. - - Now we want to set the specifications of the monitor. The two critical -parameters are the vertical refresh rate, which is the rate at which the -whole screen is refreshed, and most importantly the horizontal sync rate, -which is the rate at which scanlines are displayed. - -The valid range for horizontal sync and vertical sync should be documented -in the manual of your monitor. If in doubt, check the monitor database -/usr/X11R6/lib/X11/doc/Monitors to see if your monitor is there. - -Press enter to continue, or ctrl-c to abort. - - - -You must indicate the horizontal sync range of your monitor. You can either -select one of the predefined ranges below that correspond to industry- -standard monitor types, or give a specific range. - -It is VERY IMPORTANT that you do not specify a monitor type with a horizontal -sync range that is beyond the capabilities of your monitor. If in doubt, -choose a conservative setting. - - hsync in kHz; monitor type with characteristic modes - 1 31.5; Standard VGA, 640x480 @ 60 Hz - 2 31.5 - 35.1; Super VGA, 800x600 @ 56 Hz - 3 31.5, 35.5; 8514 Compatible, 1024x768 @ 87 Hz interlaced (no 800x600) - 4 31.5, 35.15, 35.5; Super VGA, 1024x768 @ 87 Hz interlaced, 800x600 @ 56 Hz - 5 31.5 - 37.9; Extended Super VGA, 800x600 @ 60 Hz, 640x480 @ 72 Hz - 6 31.5 - 48.5; Non-Interlaced SVGA, 1024x768 @ 60 Hz, 800x600 @ 72 Hz - 7 31.5 - 57.0; High Frequency SVGA, 1024x768 @ 70 Hz - 8 31.5 - 64.3; Monitor that can do 1280x1024 @ 60 Hz - 9 31.5 - 79.0; Monitor that can do 1280x1024 @ 74 Hz -10 31.5 - 82.0; Monitor that can do 1280x1024 @ 76 Hz -11 Enter your own horizontal sync range - -Enter your choice (1-11): 6 - -You must indicate the vertical sync range of your monitor. You can either -select one of the predefined ranges below that correspond to industry- -standard monitor types, or give a specific range. For interlaced modes, -the number that counts is the high one (e.g. 87 Hz rather than 43 Hz). - - 1 50-70 - 2 50-90 - 3 50-100 - 4 40-150 - 5 Enter your own vertical sync range - -Enter your choice: 2 - -You must now enter a few identification/description strings, namely an -identifier, a vendor name, and a model name. Just pressing enter will fill -in default names. - -The strings are free-form, spaces are allowed. -Enter an identifier for your monitor definition: Hitachi - - The selection of a video card driver from a list is - next. If you pass your card on the list, continue to press - Enter and the list will repeat. Only an - excerpt from the list is shown: - - Now we must configure video card specific settings. At this point you can -choose to make a selection out of a database of video card definitions. -Because there can be variation in Ramdacs and clock generators even -between cards of the same model, it is not sensible to blindly copy -the settings (e.g. a Device section). For this reason, after you make a -selection, you will still be asked about the components of the card, with -the settings from the chosen database entry presented as a strong hint. - -The database entries include information about the chipset, what driver to -run, the Ramdac and ClockChip, and comments that will be included in the -Device section. However, a lot of definitions only hint about what driver -to run (based on the chipset the card uses) and are untested. - -If you can't find your card in the database, there's nothing to worry about. -You should only choose a database entry that is exactly the same model as -your card; choosing one that looks similar is just a bad idea (e.g. a -GemStone Snail 64 may be as different from a GemStone Snail 64+ in terms of -hardware as can be). - -Do you want to look at the card database? y - - - -288 Matrox Millennium G200 8MB mgag200 -289 Matrox Millennium G200 SD 16MB mgag200 -290 Matrox Millennium G200 SD 4MB mgag200 -291 Matrox Millennium G200 SD 8MB mgag200 -292 Matrox Millennium G400 mgag400 -293 Matrox Millennium II 16MB mga2164w -294 Matrox Millennium II 4MB mga2164w -295 Matrox Millennium II 8MB mga2164w -296 Matrox Mystique mga1064sg -297 Matrox Mystique G200 16MB mgag200 -298 Matrox Mystique G200 4MB mgag200 -299 Matrox Mystique G200 8MB mgag200 -300 Matrox Productiva G100 4MB mgag100 -301 Matrox Productiva G100 8MB mgag100 -302 MediaGX mediagx -303 MediaVision Proaxcel 128 ET6000 -304 Mirage Z-128 ET6000 -305 Miro CRYSTAL VRX Verite 1000 - -Enter a number to choose the corresponding card definition. -Press enter for the next page, q to continue configuration. - -288 - -Your selected card definition: - -Identifier: Matrox Millennium G200 8MB -Chipset: mgag200 -Driver: mga -Do NOT probe clocks or use any Clocks line. - -Press enter to continue, or ctrl-c to abort. - - - -Now you must give information about your video card. This will be used for -the "Device" section of your video card in XF86Config. - -You must indicate how much video memory you have. It is probably a good -idea to use the same approximate amount as that detected by the server you -intend to use. If you encounter problems that are due to the used server -not supporting the amount memory you have (e.g. ATI Mach64 is limited to -1024K with the SVGA server), specify the maximum amount supported by the -server. - -How much video memory do you have on your video card: - - 1 256K - 2 512K - 3 1024K - 4 2048K - 5 4096K - 6 Other - -Enter your choice: 6 - -Amount of video memory in Kbytes: 8192 - -You must now enter a few identification/description strings, namely an -identifier, a vendor name, and a model name. Just pressing enter will fill -in default names (possibly from a card definition). - -Your card definition is Matrox Millennium G200 8MB. - -The strings are free-form, spaces are allowed. -Enter an identifier for your video card definition: - - Next, the video modes are set for the resolutions - desired. Typically, useful ranges are 640x480, 800x600, and 1024x768 - but those are a function of video card capability, monitor size, - and eye comfort. When selecting a color depth, select the highest - mode that your card will support. - - For each depth, a list of modes (resolutions) is defined. The default -resolution that the server will start-up with will be the first listed -mode that can be supported by the monitor and card. -Currently it is set to: - -"640x480" "800x600" "1024x768" "1280x1024" for 8-bit -"640x480" "800x600" "1024x768" "1280x1024" for 16-bit -"640x480" "800x600" "1024x768" "1280x1024" for 24-bit - -Modes that cannot be supported due to monitor or clock constraints will -be automatically skipped by the server. - - 1 Change the modes for 8-bit (256 colors) - 2 Change the modes for 16-bit (32K/64K colors) - 3 Change the modes for 24-bit (24-bit color) - 4 The modes are OK, continue. - -Enter your choice: 2 - -Select modes from the following list: - - 1 "640x400" - 2 "640x480" - 3 "800x600" - 4 "1024x768" - 5 "1280x1024" - 6 "320x200" - 7 "320x240" - 8 "400x300" - 9 "1152x864" - a "1600x1200" - b "1800x1400" - c "512x384" - -Please type the digits corresponding to the modes that you want to select. -For example, 432 selects "1024x768" "800x600" "640x480", with a -default mode of 1024x768. - -Which modes? 432 - -You can have a virtual screen (desktop), which is screen area that is larger -than the physical screen and which is panned by moving the mouse to the edge -of the screen. If you don't want virtual desktop at a certain resolution, -you cannot have modes listed that are larger. Each color depth can have a -differently-sized virtual screen - -Please answer the following question with either 'y' or 'n'. -Do you want a virtual screen that is larger than the physical screen? n - - - -For each depth, a list of modes (resolutions) is defined. The default -resolution that the server will start-up with will be the first listed -mode that can be supported by the monitor and card. -Currently it is set to: - -"640x480" "800x600" "1024x768" "1280x1024" for 8-bit -"1024x768" "800x600" "640x480" for 16-bit -"640x480" "800x600" "1024x768" "1280x1024" for 24-bit - -Modes that cannot be supported due to monitor or clock constraints will -be automatically skipped by the server. - - 1 Change the modes for 8-bit (256 colors) - 2 Change the modes for 16-bit (32K/64K colors) - 3 Change the modes for 24-bit (24-bit color) - 4 The modes are OK, continue. - -Enter your choice: 4 - - - -Please specify which color depth you want to use by default: - - 1 1 bit (monochrome) - 2 4 bits (16 colors) - 3 8 bits (256 colors) - 4 16 bits (65536 colors) - 5 24 bits (16 million colors) - -Enter a number to choose the default depth. - -4 - - Finally, the configuration needs to be saved. Be sure - to enter /etc/X11/XF86Config as the location - for saving the configuration. - - I am going to write the XF86Config file now. Make sure you don't accidently -overwrite a previously configured one. - -Shall I write it to /etc/X11/XF86Config? y - - If the configuration fails, you can try the configuration again - by selecting &gui.yes; when the following - message appears: - - User Confirmation Requested -The XFree86 configuration process seems to have -failed. Would you like to try again? - - [ Yes ] No - - If you have trouble configuring &xfree86;, select - &gui.no; and press Enter - and continue with the installation process. After installation - you can use xf86cfg -textmode or - xf86config to access the command line - configuration utilities as root. There is - an additional method for configuring &xfree86; described in - . If you choose not to configure - &xfree86; at this time the next menu will be for package - selection. - - The default setting which allows the server to be killed - is the hotkey sequence - CtrlAlt - Backspace. This - can be executed if something is wrong with the server settings and - prevent hardware damage. - - The default setting that allows video mode switching will - permit changing of the mode while running X with the hotkey - sequence - - CtrlAlt+ - or - - CtrlAlt- - . - - - After you have &xfree86; - running, the display can be adjusted for height, width, - or centering by using xvidtune. - - There are warnings that improper settings can - damage your equipment. Heed them. If in doubt, do not do - it. Instead, use the monitor controls to adjust the display for - X Window. There may be some display differences when switching - back to text mode, but it is better than damaging equipment. - - Read the &man.xvidtune.1; manual page before making - any adjustments. - - Following a successful &xfree86; configuration, it will proceed - to the selection of a default desktop. - - - - Select Default X Desktop - - - As of &os; 5.3-RELEASE, the X desktop selection - facility has been removed from - sysinstall, you have to configure - the X desktop after the installation of &os;. More - information regarding the installation and the configuration - of a X desktop can be found in . You - can skip this section if you are not installing a &os; - version prior to 5.3-RELEASE. - - - There are a variety of window managers available. They range - from very basic environments to full desktop environments with a - large suite of software. Some require only minimal disk space and - low memory while others with more features require much more. The - best way to determine which is most suitable for you is to try a few - different ones. Those are available from the Ports Collection or as - packages and can be added after installation. - - You can select one of the popular desktops to be installed - and configured as the default desktop. This will allow you - to start it right after installation. - -
- Select Default Desktop - - - - - - -
- - Use the arrow keys to select a desktop and press - Enter. Installation of the selected desktop will - proceed. - - - - 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 - sysinstall (/stand/sysinstall - in &os; versions older than 5.2) can be used to add additional - packages. - - User Confirmation Requested - The FreeBSD package collection is a collection of hundreds of - ready-to-run applications, from text editors to games to WEB servers - and more. Would you like to browse the collection now? - - [ Yes ] No - - Selecting &gui.yes; and pressing - Enter will be - followed by the Package Selection screens: - -
- Select Package Category - - - - - - -
- - Only packages on the current installation media are - available for installation at any given time. - - All packages available will be displayed if - All is selected or you can select a - particular category. Highlight your selection with the arrow - keys and press Enter. - - A menu will display showing all the packages available for - the selection made: - -
- Select Packages - - - - - - -
- - The bash shell is shown selected. - Select as many as desired by highlighting the package and pressing the - Space key. A short description of each package will - appear in the lower left corner of the screen. - - Pressing the Tab key will toggle between the last - selected package, &gui.ok;, and &gui.cancel;. - - When you have finished marking the packages for installation, - press Tab once to toggle to the &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 - - - - - - -
- - Use the Tab and arrow keys to select [ Install ] - and press Enter. You will then need to confirm - that you want to install the packages: - -
- Confirm Package Installation - - - - - - -
- - Selecting &gui.ok; and pressing Enter will start - the package installation. Installing messages will appear until - completed. Make note if there are any error messages. - - The final configuration continues after packages are - installed. If you end up not selecting any packages, and wish - to return to the final configuration, select - Install anyways. - - - - Add Users/Groups - - You should add at least one user during the installation so - that you can use the system without being logged 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 - at least one account for yourself at this stage is suggested since - working as the "root" user is dangerous (it is easy to do things which - adversely affect the entire system). - - [ Yes ] No - - Select &gui.yes; and press - Enter to continue with adding a user. - -
- Select User - - - - - - -
- - Select User with the arrow keys - and press Enter. - -
- Add User 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: - - - - Login ID - - - The login name of the new user (mandatory). - - - - - UID - - - The numerical ID for this user (leave blank for - automatic choice). - - - - - Group - - - The login group name for this user (leave blank for - automatic choice). - - - - - Password - - - The password for this user (enter this field with - care!). - - - - - Full name - - - The user's full name (comment). - - - - - Member groups - - - The groups this user belongs to (i.e. gets access - rights for). - - - - - Home directory - - - The user's home directory (leave blank for - default). - - - - - Login shell - - The user's login shell (leave blank for - default, e.g. /bin/sh). - - - - - 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 try to use a shell that does not exist or you will - not be able to login. The most common shell used in the - BSD-world is the C shell, which can be indicated as - /bin/tcsh. - - The user was also added to the wheel group - to be able to become a superuser with root - privileges. - - When you are satisfied, press &gui.ok; and - the User and Group Management menu will redisplay: - -
- Exit User and Group Management - - - - - - -
- - Groups can also be added at this time if specific needs - are known. Otherwise, this may be accessed through using - sysinstall (/stand/sysinstall - in &os; versions older than 5.2) after installation is - completed. - - When you are finished adding users, select - Exit with the arrow keys and press - Enter to continue the installation. - - - - Set the <username>root</username> Password - - Message - Now you must set the system manager's password. - This is the password you'll use to log in as "root". - - [ OK ] - - [ Press enter to continue ] - - Press Enter to set the root - password. - - The password will need to be typed in twice correctly. Needless to - say, make sure you have a way of finding the password if you - forget. Notice that the password you type in is not echoed, nor - are asterisks displayed. - - Changing local password for root. -New password : -Retype new password : - - The installation will continue after the password is - successfully entered. - - - - Exiting Install - - If you need to configure additional network devices or - any other configuration, you can do it at this point or - after installation with sysinstall - (/stand/sysinstall in &os; versions older - than 5.2). - - User Confirmation Requested - Visit the general configuration menu for a chance to set any last - options? - - Yes [ No ] - - Select &gui.no; with the arrow keys - and press Enter to return to the Main - Installation Menu. - -
- Exit Install - - - - - - -
- - Select [X Exit Install] with the arrow - keys and press Enter. You will be asked to - confirm exiting the installation: - - User Confirmation Requested - Are you sure you wish to exit? The system will reboot (be sure to - remove any floppies from the drives). - - [ Yes ] No - - Select &gui.yes; and remove the floppy if - booting from the floppy. The CDROM drive is locked until the machine - starts to reboot. The CDROM drive is then unlocked and the disk can - be removed from drive (quickly). - - The system will reboot so watch for any error messages that - may appear. - - - FreeBSD Bootup + &os; Bootup - FreeBSD Bootup on the &i386; + &os;/&arch.i386; Bootup If everything went well, you will see messages scroll off the screen and you will arrive at a login prompt. You can view @@ -4321,131 +3828,131 @@ Retype new password : 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. + The Regents of the University of California. All rights reserved. Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 - Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> - AMD Features=0x80000800<SYSCALL,3DNow!> -real memory = 268435456 (262144K bytes) -config> di sn0 -config> di lnc0 -config> di le0 -config> di ie0 -config> di fe0 -config> di cs0 -config> di bt0 -config> di aic0 -config> di aha0 -config> di adv0 -config> q + Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> + AMD Features=0x80000800<SYSCALL,3DNow!> +real memory = 268435456 (262144K bytes) +config> di sn0 +config> di lnc0 +config> di le0 +config> di ie0 +config> di fe0 +config> di cs0 +config> di bt0 +config> di aic0 +config> di aha0 +config> di adv0 +config> q avail memory = 256311296 (250304K bytes) -Preloaded elf kernel "kernel" at 0xc0491000. -Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. -md0: Malloc disk +Preloaded elf kernel "kernel" at 0xc0491000. +Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. +md0: Malloc disk Using $PIR table, 4 entries at 0xc00fde60 -npx0: <math processor> on motherboard -npx0: INT 16 interface -pcib0: <Host to PCI bridge> on motherboard -pci0: <PCI bus> on pcib0 -pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 -pci1: <PCI bus> on pcib1 -pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11 -isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 -isa0: <ISA bus> on isab0 -atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 -ata0: at 0x1f0 irq 14 on atapci0 -ata1: at 0x170 irq 15 on atapci0 -uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci0 -usb0: <VIA 83C572 USB controller> on uhci0 -usb0: USB revision 1.0 -uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 -uhub0: 2 ports with 2 removable, self powered -chip1: <VIA 82C586B ACPI interface> at device 7.3 on pci0 +npx0: <math processor> on motherboard +npx0: INT 16 interface +pcib0: <Host to PCI bridge> on motherboard +pci0: <PCI bus> on pcib0 +pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 +pci1: <PCI bus> on pcib1 +pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11 +isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 +isa0: <ISA bus> on isab0 +atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 +ata0: at 0x1f0 irq 14 on atapci0 +ata1: at 0x170 irq 15 on atapci0 +uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci0 +usb0: <VIA 83C572 USB controller> on uhci0 +usb0: USB revision 1.0 +uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 +uhub0: 2 ports with 2 removable, self powered +chip1: <VIA 82C586B ACPI interface> at device 7.3 on pci0 ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 9 at -device 10.0 on pci0 -ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit) -isa0: too many dependant configs (8) -isa0: unexpected small tag 14 +device 10.0 on pci0 +ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit) +isa0: too many dependant configs (8) +isa0: unexpected small tag 14 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 -fdc0: FIFO enabled, 8 bytes threshold -fd0: <1440-KB 3.5" drive> on fdc0 drive 0 -atkbdc0: <keyboard controller (i8042)> at port 0x60-0x64 on isa0 -atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 -kbd0 at atkbd0 -psm0: <PS/2 Mouse> irq 12 on atkbdc0 -psm0: model Generic PS/2 mouse, device ID 0 +fdc0: FIFO enabled, 8 bytes threshold +fd0: <1440-KB 3.5" drive> on fdc0 drive 0 +atkbdc0: <keyboard controller (i8042)> at port 0x60-0x64 on isa0 +atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 +kbd0 at atkbd0 +psm0: <PS/2 Mouse> irq 12 on atkbdc0 +psm0: model Generic PS/2 mouse, device ID 0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 -sc0: <System console> at flags 0x1 on isa0 -sc0: VGA <16 virtual consoles, flags=0x300> -sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 -sio0: type 16550A -sio1 at port 0x2f8-0x2ff irq 3 on isa0 -sio1: type 16550A -ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 -ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode -ppc0: FIFO with 16/16/15 bytes threshold +sc0: <System console> at flags 0x1 on isa0 +sc0: VGA <16 virtual consoles, flags=0x300> +sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 +sio0: type 16550A +sio1 at port 0x2f8-0x2ff irq 3 on isa0 +sio1: type 16550A +ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 +ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode +ppc0: FIFO with 16/16/15 bytes threshold ppbus0: IEEE1284 device found /NIBBLE -Probing for PnP devices on ppbus0: -plip0: <PLIP network interface> on ppbus0 -lpt0: <Printer> on ppbus0 -lpt0: Interrupt-driven port +Probing for PnP devices on ppbus0: +plip0: <PLIP network interface> on ppbus0 +lpt0: <Printer> on ppbus0 +lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 -ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33 -ad2: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata1-master using UDMA33 -acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4 -Mounting root from ufs:/dev/ad0s1a -swapon: adding /dev/ad0s1b as swap device -Automatic boot in progress... -/dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS +ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33 +ad2: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata1-master using UDMA33 +acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4 +Mounting root from ufs:/dev/ad0s1a +swapon: adding /dev/ad0s1b as swap device +Automatic boot in progress... +/dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation) -/dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS +/dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation) /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation) -/dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS +/dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation) -Doing initial network setup: hostname. +Doing initial network setup: hostname. ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1 ether 52:54:05:de:73:1b -lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 - inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 - inet6 ::1 prefixlen 128 - inet 127.0.0.1 netmask 0xff000000 +lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 + inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 + inet6 ::1 prefixlen 128 + inet 127.0.0.1 netmask 0xff000000 Additional routing options: IP gateway=YES TCP keepalive=YES -routing daemons:. -additional daemons: syslogd. -Doing additional network setup:. -Starting final network daemons: creating ssh RSA host key +routing daemons:. +additional daemons: syslogd. +Doing additional network setup:. +Starting final network daemons: creating ssh RSA host key Generating public/private rsa1 key pair. -Your identification has been saved in /etc/ssh/ssh_host_key. -Your public key has been saved in /etc/ssh/ssh_host_key.pub. -The key fingerprint is: +Your identification has been saved in /etc/ssh/ssh_host_key. +Your public key has been saved in /etc/ssh/ssh_host_key.pub. +The key fingerprint is: cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com - creating ssh DSA host key + creating ssh DSA host key Generating public/private dsa key pair. -Your identification has been saved in /etc/ssh/ssh_host_dsa_key. -Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. -The key fingerprint is: +Your identification has been saved in /etc/ssh/ssh_host_dsa_key. +Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. +The key fingerprint is: f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib -/usr/local/lib -a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout +/usr/local/lib +a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout starting standard daemons: inetd cron sshd usbd sendmail. -Initial rc.i386 initialization:. -rc.i386 configuring syscons: blank_time screensaver moused. -Additional ABI support: linux. -Local package initialization:. -Additional TCP options:. +Initial rc.i386 initialization:. +rc.i386 configuring syscons: blank_time screensaver moused. +Additional ABI support: linux. +Local package initialization:. +Additional TCP options:. FreeBSD/i386 (k6-2.example.com) (ttyv0) -login: rpratt +login: rpratt Password: Generating the RSA and DSA keys may take some time on slower @@ -4457,30 +3964,6 @@ Password: the command line. - - - Bootup of FreeBSD on the Alpha - - Alpha - - Once the install procedure has finished, you will be - able to start FreeBSD by typing something like this to the - SRM prompt: - - >>>BOOT DKC0 - - This instructs the firmware to boot the specified - disk. To make FreeBSD boot automatically in the future, use - these commands: - - >>> SET BOOT_OSFLAGS A ->>> SET BOOT_FILE '' ->>> SET BOOTDEF_DEV DKC0 ->>> SET AUTO_ACTION BOOT - - The boot messages will be similar (but not identical) to - those produced by FreeBSD booting on the &i386;. - @@ -4494,16 +3977,17 @@ Password: Otherwise, login as root and use shutdown -h now. - The operating system has halted. + 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 + 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. You could also use the - + Ctrl Alt Del @@ -4514,31 +3998,6 @@ Please press any key to reboot. - - Supported Hardware - - hardware - FreeBSD currently runs on a wide variety of ISA, VLB, EISA, and PCI - bus-based PCs with Intel, AMD, Cyrix, or NexGen x86 - processors, as well as a number of machines based on the Compaq Alpha - processor. Support for generic IDE or ESDI drive configurations, - various SCSI controllers, PCMCIA cards, USB devices, and network and - serial cards is also provided. FreeBSD also supports IBM's microchannel - (MCA) bus. - - A list of supported hardware is provided with each FreeBSD release - in the FreeBSD 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 FreeBSD. Copies of the supported - hardware list for various releases and architectures can also be - found on the Release - Information page of the FreeBSD Web site. - - Troubleshooting @@ -4549,192 +4008,293 @@ 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 - &ms-dos;. + &ms-dos; or &windows;. What to Do If Something Goes Wrong Due to various limitations of the PC architecture, it is - impossible for probing to be 100% reliable, however, there are a - few things you can do if it fails. + impossible for probing to be 100% reliable, however, there are a + few things you can do if it fails. - Check the Hardware Notes document for your version of - FreeBSD to make sure your hardware is - supported. + Check the Hardware Notes + document for your version of &os; to make sure your + hardware is supported. If your hardware is supported and you still experience - lock-ups or other problems, reset your computer, and when the - visual kernel configuration option is given, choose it. This will - allow you to go through your hardware and supply information to the - system about it. The kernel on the boot disks is configured - assuming that most hardware devices are in their factory default - configuration in terms of IRQs, IO addresses, and DMA channels. If - your hardware has been reconfigured, you will most likely need to - use the configuration editor to tell FreeBSD where to find - things. + lock-ups or other problems, you will need to build a custom kernel. This will + allow you to add in support for devices which are not present in the + GENERIC kernel. The kernel on the boot disks + is configured assuming that most hardware devices are in their + factory default configuration in terms of IRQs, IO addresses, and + DMA channels. If your hardware has been reconfigured, you will most + likely need to edit the kernel configuration 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. + 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. The motherboard firmware may also be referred to - as BIOS and most of the motherboard or computer - manufactures have a website where the upgrades and upgrade information - may be located. + Some installation problems can be avoided or alleviated + by updating the firmware on various hardware components, most notably + the motherboard. The motherboard firmware may also be referred to + as BIOS and most of the motherboard or computer + manufactures have a website where the upgrades and upgrade + information may be located. - Most manufacturers strongly advise against upgrading the motherboard - BIOS unless there is a good reason for doing so, which - could possibly be a critical update of sorts. The upgrade process - can go wrong, causing permanent damage to the - BIOS chip. - - - - Do not disable any drivers you will need during the - installation, such as your screen (sc0). - If the installation wedges or fails mysteriously after leaving - the configuration editor, you have probably removed or changed - something you should not have. Reboot and try again. - - - In configuration mode, you can: - - - - List the device drivers installed in the kernel. - - - - Disable device drivers for hardware that is not present in - your system. - - - - Change IRQs, DRQs, and IO port addresses used by a device - driver. - - - - After adjusting the kernel to match your hardware - configuration, type Q to boot with the new - settings. Once the installation has completed, any changes you - made in the configuration mode will be permanent so you do not have - to reconfigure every time you boot. It is still highly likely that - you will eventually want to build a custom kernel. - - - - Dealing with Existing &ms-dos; Partitions - - DOS - Many users wish to install &os; on PCs inhabited by - µsoft; based operating systems. For those instances, &os; has a - utility known as FIPS. This utility can be found - in the tools directory on the install CD-ROM, or downloaded - from one of various &os; mirrors. - - The FIPS utility allows you to split an - existing &ms-dos; partition into two pieces, preserving the original - partition and allowing you to install onto the second free piece. - You first need to defragment your &ms-dos; partition using the &windows; - Disk Defragmenter utility (go into Explorer, right-click on - the hard drive, and choose to defrag your hard drive), or use - Norton Disk Tools. Now you can run the - FIPS utility. It will prompt you for the rest of - the information, just follow the on screen instructions. Afterwards, you can - reboot and install &os; on the new free slice. See the Distributions menu - for an estimate of how much free space you will need for the kind of - installation you want. - - There is also a very useful product from PowerQuest - (http://www.powerquest.com) called - &partitionmagic;. This application has far more - functionality than FIPS, and is highly recommended - if you plan to add/remove operating systems often. It does cost money, so if you - plan to install &os; and keep it installed, FIPS - will probably be fine for you. + Most manufacturers strongly advise against upgrading the + motherboard BIOS unless there is a good reason + for doing so, which + could possibly be a critical update of sorts. The upgrade process + can go wrong, causing permanent damage to the + BIOS chip. + Using &ms-dos; and &windows; File Systems - 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 + 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 > + located in the + Start> Programs > System Tools menu. - &os; can support &ms-dos; based file systems. This requires you use - the &man.mount.msdosfs.8; command - with the required parameters. The utility most common usage is: + &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 a call to the &man.mount.8; + utility with the appropriate parameters. - &prompt.root; mount_msdosfs /dev/ad0s1 /mnt + A typical line in /etc/fstab is: - In this example, the &ms-dos; file system is located on the first partition of - the primary hard disk. Your situation may be different, check the output from - the dmesg, and mount commands. They should - produce enough information to give an idea of the partition layout. + /dev/ad0sN /dos msdosfs rw 0 0 - Extended &ms-dos; file systems are usually mapped after the &os; - partitions. In other words, the slice number may be higher than the ones - &os; is using. For instance, the first &ms-dos; partition may be - /dev/ad0s1, the &os; partition may be - /dev/ad0s2, with the extended &ms-dos; partition being - located on /dev/ad0s3. To some, this can be confusing - at first. + The /dos directory must already + exist for this to work. For details about the format of + /etc/fstab, see &man.fstab.5;. + + A typicall call to &man.mount.8; for a &ms-dos; file system + looks like: + + &prompt.root; mount -t msdosfs /dev/ad0s1 /mnt + + In this example, the &ms-dos; file system is located on the first + partition of the primary hard disk. Your situation may be different, + check the output from the dmesg, and + mount commands. They should produce enough + information to give an idea of the partition layout. + + &os; may number disk slices (that is, &ms-dos; partitions) + differently than other operating systems. In particular, extended + &ms-dos; partitions are usually given higher slice numbers than + primary &ms-dos; partitions. The &man.fdisk.8; utility can help + determine which slices belong to &os; and which belong to other + operating systems. NTFS partitions can also be mounted in a similar manner using the &man.mount.ntfs.8; command. - Alpha User's Questions and Answers - - Alpha - - This section answers some commonly asked questions about - installing FreeBSD on Alpha systems. + Troubleshooting Questions and Answers - Can I boot from the ARC or Alpha BIOS Console? + My system hangs while probing hardware during boot, + or it behaves strangely during install, or the floppy + drive is not probed. - - ARC - Alpha BIOS - SRM - - No. &os;, like Compaq Tru64 and VMS, will only boot - from the SRM console. + &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 both the + ACPI driver and within system motherboards and BIOS. + The use of ACPI can be disabled by setting + the hint.acpi.0.disabled hint 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 the + file + /boot/loader.conf. More + information about the boot loader can be found + in . + + + + + I go to boot from the hard disk for the first time + after installing &os;, the kernel loads and probes my + hardware, but stops with messages like: + + changing root device to ad1s1a panic: cannot mount root + + What is wrong? What can I do? + + What is this + bios_drive:interface(unit,partition)kernel_name + thing that is displayed with the boot help? + + + There is a longstanding problem in the case where + 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. + + In the case where the boot disk is not the first + disk in the system, &os; can need some help finding it. + There are two common situations here, and in both of + these cases, you need to tell &os; where the root + filesystem is. You do this by specifying the BIOS disk + number, the disk type and the &os; disk number for that + type. + + The first situation is where you have two IDE disks, + each configured as the master on their respective IDE + busses, and wish to boot &os; from the second disk. The + BIOS sees these as disk 0 and disk 1, while &os; sees + them as ad0 and + ad2. + + &os; is on BIOS disk 1, of type + ad and the &os; disk number is 2, so + you would say: + + 1:ad(2,a)kernel + + Note that if you have a slave on the primary bus, + the above is not necessary (and is effectively + wrong). + + The second situation involves booting from a SCSI + disk when you have one or more IDE disks in the system. + In this case, the &os; disk number is lower than the + BIOS disk number. If you have two IDE disks as well as + the SCSI disk, the SCSI disk is BIOS disk 2, + type da and &os; disk number 0, so + you would say: + + 2:da(0,a)kernel + + To tell &os; that you want to boot from BIOS disk 2, + which is the first SCSI disk in the system. If you only + had one IDE disk, you would use 1: + instead. + + Once you have determined the correct values to use, + you can put the command exactly as you would have typed + it in the /boot.config file using a + standard text editor. Unless instructed otherwise, &os; + will use the contents of this file as the default + response to the boot: prompt. + + + + + I go to boot from the hard disk for the first time + after installing &os;, but the Boot Manager prompt just + prints F? at the boot menu each time + but the boot will not go any further. + + + The hard disk geometry was set incorrectly in the + partition editor when you installed &os;. Go back into + the partition editor and specify the actual geometry of + your hard disk. You must reinstall &os; again from the + beginning with the correct geometry. + + If you are failing entirely in figuring out the + correct geometry for your machine, here is a tip: Install + a small &ms-dos; partition at the beginning of the disk and + install &os; after that. The install program will see + the &ms-dos; partition and try to infer the correct geometry + from it, which usually works. + + The following tip is no longer recommended, but is + left here for reference: + +
+ If you are setting up a truly dedicated &os; + server or workstation where you do not care for + (future) compatibility with &ms-dos;, Linux or another + operating system, you also have got the option to use + the entire disk (A in the partition + editor), selecting the non-standard option where &os; occupies + the entire disk from the very first to the very last + sector. This will leave all geometry considerations + aside, but is somewhat limiting unless you're never + going to run anything other than &os; on a + disk. +
+ + + + + The system finds my &man.ed.4; network card, but I + keep getting device timeout errors. + + + Your card is probably on a different IRQ from what + is specified in + the /boot/device.hints file. The + &man.ed.4; driver does not use the soft + configuration by default (values entered using EZSETUP in + &ms-dos;), + but it will use the software configuration if you + specify -1 in the hints for the + interface. + + Either move the jumper on the card to a hard + configuration setting (altering the kernel settings if + necessary), or specify the IRQ as -1 + by setting the hint hint.ed.0.irq="-1". + This will tell the kernel to use the soft + configuration. + + Another possibility is that your card is at IRQ 9, + which is shared by IRQ 2 and frequently a cause of + problems (especially when you have a VGA card using IRQ + 2!). You should not use IRQ 2 or 9 if at all + possible. + + + color + contrast + - Help, I have no space! Do I need to delete - everything first? + When sysinstall is used + in an X11 terminal, the yellow font is difficult to read + against the light gray background. Is there a way to + provide higher contrast for this application? - - Unfortunately, yes. - - - - - - Can I mount my Compaq Tru64 or VMS filesystems? - - - - No, not at this time. + If you already have X11 installed and the default + colors chosen by sysinstall + make text illegible while using &man.xterm.1; or &man.rxvt.1;, + add the following to your ~/.Xdefaults to + get a darker background gray: XTerm*color7: + #c0c0c0 @@ -4751,6 +4311,15 @@ Please press any key to reboot. + + + + Marc + Fonvieille + Updated by + + + Advanced Installation Guide @@ -4760,69 +4329,116 @@ Please press any key to reboot. Installing FreeBSD on a System without a Monitor or - Keyboard + Keyboard - installation - headless (serial console) + installation + headless (serial console) 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 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 - system. To do this, just follow the steps to create - installation floppies, explained in . + serial console. A serial console is basically using another + machine to act as the main display and keyboard for a + system. To do this, just follow the steps to create + an installation USB memstick, explained in or download the correct + installation ISO image, see . - To modify these floppies to boot into a serial console, follow - these steps: + + To modify these media to boot into a serial console, follow + these steps (If you want to use a CDROM you can skip the first + step): - Enabling the Boot Floppies to Boot into a Serial Console - + Enabling the Installation USB Stick to Boot into a + Serial Console + mount - If you were to boot into the floppies that you just + 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 install. To do this, you have to mount the - kern.flp floppy onto your FreeBSD + USB disk onto your &os; system using the &man.mount.8; command. - &prompt.root; mount /dev/fd0 /mnt + &prompt.root; mount /dev/da0a /mnt - Now that you have the floppy mounted, you must - change into the /mnt directory: + + Adapt the device node and the mount point to your + situation. + - &prompt.root; cd /mnt + Now that you have the stick mounted, you must set + the USB stick to boot into a serial console. You have + to add to the loader.conf file of + the USB stick file system a line setting the serial + console as the system console: - Here is where you must set the floppy to boot into a - serial console. You have to make a file called - boot.config containing - /boot/loader -h. All this does is pass a flag to the bootloader to - boot into a serial console. + &prompt.root; echo 'console="comconsole"' >> /mnt/boot/loader.conf - &prompt.root; echo "/boot/loader -h" > boot.config - - Now that you have your floppy configured correctly, - you must unmount the floppy using the &man.umount.8; + Now that you have your USB stick configured correctly, + you must unmount the disk using the &man.umount.8; command: - &prompt.root; cd / -&prompt.root; umount /mnt + &prompt.root; umount /mnt - Now you can remove the floppy from the floppy - drive. + Now you can unplug the USB stick and jump directly + to the third step of this procedure. + + + + Enabling the Installation CD to Boot into a + Serial Console + + mount + + If you were to boot into the CD that you just + made from the installation ISO image (see ), &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 + extract, modify and regenerate the ISO image before + burning it on a CD-R media. + + From the &os; system where is saved the installation + ISO image, for example + &os;-&rel.current;-RELEASE-i386-disc1.iso, + use the &man.tar.1; utility to extract all the files: + + &prompt.root; mkdir /path/to/headless-iso +&prompt.root; tar -C /path/to/headless-iso -pxvf &os;-&rel.current;-RELEASE-i386-disc1.iso + + Now you must set the installation media to boot into a + serial console. You have to add to the + loader.conf file from the extracted + ISO image a line setting the serial console as the + system console: + + &prompt.root; echo 'console="comconsole"' >> /path/to/headless-iso/boot/loader.conf + + Then we can create a new ISO image from the modified + tree. The &man.mkisofs.8; tool from the sysutils/cdrtools port is + used: + + &prompt.root; mkisofs -v -b boot/cdboot -no-emul-boot -r -J -V "Headless_install" \ + -o Headless-&os;-&rel.current;-RELEASE-i386-disc1.iso /path/to/headless-iso + + Now that you have your ISO image configured correctly, + you can burn it on a CD-R with your favorite burning + application. Connecting Your Null-modem Cable - null-modem cable + null-modem cable You now need to connect a null-modem cable between the two machines. Just connect the cable to the serial @@ -4835,10 +4451,12 @@ Please press any key to reboot. Booting Up for the Install - It is now time to go ahead and start the install. Put - the kern.flp floppy in the floppy - drive of the machine you are doing the headless install - on, and power on the machine. + It is now time to go ahead and start the install. Plug in + the USB memstick on + the machine you are doing the headless install + on, and power on the machine. If you are using a + prepared CDROM, power on the machine and insert the disk + to boot on. @@ -4847,15 +4465,21 @@ Please press any key to reboot. cu Now you have to connect to that machine with - &man.cu.1;: + &man.cu.1;: + + &prompt.root; cu -l /dev/cuau0 + + On &os; 7.X use the following command + instead: + + &prompt.root; cu -l /dev/cuad0 - &prompt.root; cu -l /dev/cuaa0 That's it! You should now be able to control the headless machine - through your cu session. It will ask you to - put in the mfsroot.flp, and then it will come up + 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! @@ -4888,10 +4512,10 @@ Please press any key to reboot. - You have a FreeBSD disc, and FreeBSD does not recognize your CD/DVD - drive, but &ms-dos;/&windows; does. You want to copy the FreeBSD - installation files to a DOS partition on the same computer, and - then install FreeBSD using those files. + You have a FreeBSD disc, and FreeBSD 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. @@ -4910,8 +4534,9 @@ Please press any key to reboot. Creating an Installation CDROM - As part of each release, the FreeBSD project makes available two - CDROM images (ISO images). These images can be written + As part of each release, the FreeBSD 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. @@ -4920,119 +4545,124 @@ Please press any key to reboot. 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. - Substitute arch and + The ISO images for each release can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch/version or the closest mirror. + Substitute arch and version as appropriate. That directory will normally contain the following images: - FreeBSD 4.<replaceable>X</replaceable> ISO Image Names and Meanings + FreeBSD 7.<replaceable>X</replaceable> and 8.<replaceable>X</replaceable> + ISO Image Names and Meanings Filename - Contains + Contents - version-RELEASE-arch-miniinst.iso - - Everything you need to install FreeBSD. + &os;-version-RELEASE-arch-bootonly.iso + + This CD image allows you to start the installation + process by booting from a CD-ROM drive but it does not + contain the support for installing &os; from the CD + itself. You would need to perform a network based install + (e.g. from an FTP server) after booting from this CD. - version-RELEASE-arch-disc1.iso + &os;-version-RELEASE-arch-dvd1.iso.gz - Everything you need to install FreeBSD, and as many - additional third party packages as would fit on the - disc. + This DVD image contains everything necessary to + install the base FreeBSD operating system, a + collection of pre-built packages, and the + documentation. It also supports booting into a + livefs based rescue mode. - version-RELEASE-arch-disc2.iso + &os;-version-RELEASE-arch-memstick.img - A live filesystem, which is used in - conjunction with the Repair facility in - sysinstall. A copy of the - FreeBSD CVS tree. As many additional third party packages - as would fit on the disc. + This image can be written to an USB memory stick + and used to do an install on machines capable of booting + off USB drives. It also supports booting into a + livefs based rescue mode. The + documentation packages are provided but no other + packages. This image is not available for &os; 7.X. + + + + &os;-version-RELEASE-arch-disc1.iso + + This CD image contains the base &os; operating + system and the documentation packages but no other + packages. + + + + &os;-version-RELEASE-arch-disc2.iso + + A CD image with as many third-party packages + as would fit on the disc. This image is not + available for &os; 8.X. + + + + &os;-version-RELEASE-arch-disc3.iso + + Another CD image with as many third-party + packages as would fit on the disc. This image is + not available for &os; 8.X. + + + + version-RELEASE-arch-docs.iso + + The &os; documentation. + + + + &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.
- - FreeBSD 5.<replaceable>X</replaceable> ISO Image Names and Meanings - - - - - Filename - - Contains - - - - - - version-RELEASE-arch-bootonly.iso - - Everything you need to boot into a FreeBSD - kernel and start the installation interface. - The installable files have to be pulled over FTP - or some other supported source. - - - - version-RELEASE-arch-miniinst.iso - - Everything you need to install FreeBSD. - - - - version-RELEASE-arch-disc1.iso - - Everything you need to install &os; and a - live filesystem, which is used in - conjunction with the Repair facility - in sysinstall. - - - - version-RELEASE-arch-disc2.iso - - &os; documentation and as many third party packages as - would fit on the disc. - - - -
- - You must download one of either the miniinst - ISO image, or the image of disc one. Do not download both of them, - since the disc one image contains everything that the miniinst ISO - image contains. - - The miniinst ISO image is only available for releases prior - to 5.4-RELEASE. + &os; 7.X releases before + &os; 7.3 and &os; 8.0 used a + different naming convention. The names of their ISO + images are not prefixed with + &os;-. - Use the miniinst ISO if Internet access is cheap for you. It will - let you install FreeBSD, and you can then install third party + You must download one of either + the bootonly ISO image, + or the image of disc1. Do not download + both of them, since the disc1 image + contains everything that the bootonly + ISO image contains. + + Use the bootonly ISO if Internet + access is cheap for you. It will let you install &os;, and + you can then install third-party packages by downloading them using the ports/packages system (see ) as necessary. - Use the image of disc one if you want to install a &os; - release and want - a reasonable selection of third party packages on the disc - as well. + Use the image of dvd1 if you want to + install a &os; + release and want a reasonable selection of third-party packages + on the disc as well. The additional disc images are useful, but not essential, especially if you have high-speed access to the Internet. @@ -5042,9 +4672,9 @@ 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 - for more information (in - particular, and + doing this on another FreeBSD system then see + for more information (in + particular, and ). If you will be doing this on another platform then you will @@ -5055,15 +4685,15 @@ Please press any key to reboot. If you are interested in building a customized - release of FreeBSD, please see the Release Engineering - Article. + release of FreeBSD, please see the Release Engineering + Article. Creating a Local FTP Site with a FreeBSD Disc - + installation network @@ -5107,10 +4737,11 @@ Please press any key to reboot. If the boot media (floppy disks, usually) for your FTP clients is not precisely the same version as that provided - by the local FTP site, then sysinstall will not let you + by the local FTP site, then sysinstall + will not let you complete the installation. If the versions are not similar and - you want to override this, you must go into the Options menu - and change distribution name to + you want to override this, you must go into the + Options menu and change distribution name to any. @@ -5125,7 +4756,7 @@ Please press any key to reboot. - Creating Installation Floppies + Creating Installation Floppies installation @@ -5137,14 +4768,15 @@ Please press any key to reboot. hardware or simply because you insist on doing things the hard way, you must first prepare some floppies for the installation. - At a minimum, you will need as many 1.44 MB or 1.2 MB floppies + At a minimum, you will need as many 1.44 MB floppies as it takes to hold all the files in the - bin (binary distribution) directory. If - you are preparing the floppies from DOS, then they + base (base distribution) directory. If + you are preparing the floppies from &ms-dos;, then they must be formatted using the &ms-dos; FORMAT command. If you are using &windows;, use Explorer to format the disks (right-click on the - A: drive, and select Format). + A: drive, and select + Format). Do not trust factory pre-formatted floppies. Format them again yourself, just to be sure. Many @@ -5154,21 +4786,16 @@ Please press any key to reboot. If you are creating the floppies on another FreeBSD machine, a format is still not a bad idea, though you do not need to put - a DOS filesystem on each floppy. You can use the + a &ms-dos; filesystem on each floppy. You can use the bsdlabel and newfs commands to put a UFS filesystem on them instead, as the following sequence of commands (for a 3.5" 1.44 MB floppy) illustrates: &prompt.root; fdformat -f 1440 fd0.1440 -&prompt.root; bsdlabel -w -r fd0.1440 floppy3 +&prompt.root; bsdlabel -w fd0.1440 floppy3 &prompt.root; newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0 - - Use fd0.1200 and - floppy5 for 5.25" 1.2 MB disks. - - Then you can mount and write to them like any other filesystem. @@ -5179,8 +4806,16 @@ Please press any key to reboot. files as will fit on each one, until you have all of the distributions you want packed up in this fashion. Each distribution should go into a subdirectory on the floppy, e.g.: - a:\bin\bin.aa, - a:\bin\bin.ab, and so on. + a:\base\base.aa, + a:\base\base.ab, and so on. + + + The base.inf file also needs to go on the + first floppy of the base set since it is read + by the installation program in order to figure out how many + additional pieces to look for when fetching and concatenating the + distribution. + Once you come to the Media screen during the install process, select Floppy and you @@ -5188,7 +4823,7 @@ Please press any key to reboot. - Installing from an &ms-dos; Partition + Installing from an &ms-dos; Partition installation @@ -5196,10 +4831,10 @@ Please press any key to reboot. To prepare for an installation from an &ms-dos; partition, copy the files from the distribution into a directory - called freebsd in the root directory of the + called freebsd in the root directory of the partition. For example, c:\freebsd. The directory structure of the CDROM or FTP site must be partially - reproduced within this directory, so we suggest using the DOS + 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: @@ -5211,7 +4846,7 @@ Please press any key to reboot. Assuming that C: is where you have free space and E: is where your CDROM is mounted. - + If you do not have a CDROM drive, you can download the distribution from ftp.FreeBSD.org. @@ -5228,7 +4863,7 @@ Please press any key to reboot. - Creating an Installation Tape + Creating an Installation Tape installation @@ -5259,12 +4894,12 @@ Please press any key to reboot. - Before Installing over a Network + Before Installing over a Network installation network - serial (SLIP or PPP) + serial (PPP) installation @@ -5277,43 +4912,10 @@ Please press any key to reboot. Ethernet There are three types of network installations available. - Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)), - or Ethernet (a standard Ethernet controller (includes some - PCMCIA)). + Ethernet (a standard Ethernet controller), Serial port (PPP), or + Parallel port (PLIP (laplink cable)). - The SLIP support is rather primitive, and limited primarily - to hard-wired links, such as a serial cable running between a - laptop computer and another computer. The link should be - hard-wired as the SLIP installation does not currently offer a - dialing capability; that facility is provided with the PPP - utility, which should be used in preference to SLIP whenever - possible. - - If you are using a modem, then PPP is almost certainly - your only choice. Make sure that you have your service - provider's information handy as you will need to know it fairly - early in the installation process. - - If you use PAP or CHAP to connect your ISP (in other words, if - you can connect to the ISP in &windows; without using a script), then - all you will need to do is type in dial at the - ppp prompt. Otherwise, you will need to - know how to dial your ISP using the AT commands - specific to your modem, as the PPP dialer provides only a very - simple terminal emulator. Please refer to the user-ppp handbook and FAQ entries for further information. - 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 (2.0-R or - later) 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 - possible over a serial line (up to 50 kbytes/sec), thus resulting - in a quicker installation. - - Finally, for the fastest possible network installation, an + For the fastest possible network installation, an Ethernet adapter is always a good choice! FreeBSD supports most common PC Ethernet cards; a table of supported cards (and their required settings) is provided in the Hardware Notes for each @@ -5339,6 +4941,31 @@ Please press any key to reboot. or ISP before trying this type of installation. + If you are using a modem, then PPP is almost certainly + your only choice. Make sure that you have your service + provider's information handy as you will need to know it fairly + early in the installation process. + + If you use PAP or CHAP to connect your ISP (in other words, if + you can connect to the ISP in &windows; without using a script), then + all you will need to do is type in dial at the + ppp prompt. Otherwise, you will need to + know how to dial your ISP using the AT commands + specific to your modem, as the PPP dialer provides only a very + simple terminal emulator. Please refer to the user-ppp handbook and FAQ + entries for further information. + 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 + 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 + possible over a serial line (up to 50 kbytes/sec), thus + resulting in a quicker installation. + Before Installing via NFS @@ -5354,15 +4981,16 @@ Please press any key to reboot. If this server supports only privileged port (as is generally the default for Sun workstations), you will need to set the option NFS Secure in the - Options menu before installation can proceed. + Options menu before installation can + proceed. If you have a poor quality Ethernet card which suffers from very slow transfer rates, you may also wish to toggle the NFS Slow flag. In order for NFS installation to work, the server must - support subdir mounts, for example, if your FreeBSD &rel.current; distribution - directory lives on: + support subdir mounts, for example, if your + FreeBSD &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 @@ -5381,7 +5009,7 @@ Please press any key to reboot. -