Index: head/en_US.ISO8859-1/books/handbook/install/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml (nonexistent) @@ -1,4625 +0,0 @@ - - - - - Installing &os; 8.<replaceable>X</replaceable> - - - JimMockRestructured, - reorganized, and parts rewritten by - - - - RandyPrattThe - sysinstall walkthrough, screenshots, and general copy by - - - - - - Synopsis - - installation - - &os; provides a text-based, easy to use installation - program. &os; 9.0-RELEASE and later use the installation - program known as &man.bsdinstall.8; while - &os; 8.X uses - &man.sysinstall.8;. This chapter describes how to use - &man.sysinstall.8;. The use of &man.bsdinstall.8; is covered in - . - - After reading this chapter, you will know: - - - - How to create the &os; installation media. - - - - How &os; refers to and subdivides hard disks. - - - - How to start &man.sysinstall.8;. - - - - The questions &man.sysinstall.8; asks, what they mean, - and how to answer them. - - - - Before reading this chapter, you should: - - - - Read the supported hardware list that shipped with the - version of &os; to install, and verify that the system's - hardware is supported. - - - - - In general, these installation instructions are written - for the &i386; and &os;/&arch.amd64; architectures. Where - applicable, instructions specific to other platforms will be - listed. There may be minor differences between the installer - and what is shown here. This chapter should be used as a - general guide rather than a literal installation - manual. - - - - - - 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 chosen to install &os;, - a floppy drive, CDROM drive, or network adapter may be needed. - Instructions on how to prepare the installation media can be - found in . - - - &os;/&arch.i386; and &os;/&arch.pc98; - - Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 - or better processor, at least 24 MB of RAM, and at - least 150 MB of free hard drive space for the most - minimal installation. - - - In the case of older hardware, installing more RAM and - more hard drive space is often more important than 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, and - &amd.opteron; or better processors. - - The second class of processors includes those using the - &intel; EM64T architecture. Examples of these processors - include the &intel; &core; 2 Duo, Quad, Extreme - processor families, and the &intel; &xeon; 3000, 5000, - and 7000 sequences of processors. - - If the machine is based on an nVidia nForce3 Pro-150, - the BIOS setup must be used to disable - the IO APIC. If this option does not exist, disable ACPI - instead as there are bugs in the Pro-150 chipset. - - - - &os;/&arch.sparc64; - - To install &os;/&arch.sparc64;, use a supported platform - (see ). - - A dedicated disk is needed for &os;/&arch.sparc64; as it - is not possible to share a disk with another operating - system at this time. - - - - - 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 - &man.sysinstall.8;'s documentation menu. It lists, for a - given architecture, which hardware devices are known to be - supported by each release of &os;. Copies of the supported - hardware list for various releases and architectures can also - be found on the Release - Information page of the &os; website. - - - - - Pre-installation Tasks - - - Inventory the Computer - - Before installing &os; it is recommended to inventory the - components in the computer. The &os; installation routines - will show components such as hard disks, network cards, and - CDROM drives with their model number and manufacturer. &os; - will also attempt to determine the correct configuration for - these devices, including information about IRQ and I/O port - usage. Due to the vagaries of computer hardware, this process - is not always completely successful, and &os; may need some - manual configuration. - - If another operating system is already installed, use the - facilities provided by that operating systems to view the - hardware configuration. If the settings of an expansion card - are not obvious, check if they are printed on the card itself. - Popular IRQ numbers are 3, 5, and 7, and I/O port addresses - are normally written as hexadecimal numbers, such as - 0x330. - - It is recommended to print or write down this information - before installing &os;. It may help to use a table, as seen - in this example: - - - Sample Device Inventory - - - - - - - - - Device Name - - IRQ - - I/O port(s) - - Notes - - - - - - First hard disk - - N/A - - N/A - - 40 GB, made by Seagate, first IDE - master - - - - CDROM - - N/A - - N/A - - First IDE slave - - - - Second hard disk - - N/A - - N/A - - 20 GB, made by IBM, second IDE - master - - - - First IDE controller - - 14 - - 0x1f0 - - - - - Network card - - N/A - - N/A - - &intel; 10/100 - - - - Modem - - N/A - - N/A - - &tm.3com; 56K faxmodem, on COM1 - - - - … - - - -
- - Once the inventory of the components in the computer is - complete, check if it matches the hardware requirements of the - &os; release to install. - - - - Make a Backup - - If the computer contains valuable data, ensure it is - backed up, and that the backup has been tested before - installing &os;. The &os; installer will prompt before - writing any data to disk, but once that process has started, - it cannot be undone. - - - - Decide Where to Install &os; - - If &os; is to be installed on the entire hard disk, skip - this section. - - However, if &os; will co-exist with other operating - systems, a rough understanding of how data is laid out on the - disk is useful. - - - Disk Layouts for &os;/&arch.i386; - - A PC disk can be divided into discrete chunks known as - partitions. Since &os; also has - partitions, naming can quickly become confusing. Therefore, - these disk chunks are referred to as slices in &os;. For - example, the &os; version of &man.fdisk.8; refers to slices - instead of partitions. By design, the PC only supports four - partitions per disk. These partitions are called - primary partitions. To work around - this limitation and allow more than four partitions, a new - partition type was created, the extended - partition. A disk may contain only one - extended partition. Special partitions, called - logical partitions, can be created - inside this extended partition. - - Each partition has a partition - ID, which is a number used to identify the - type of data on the partition. &os; partitions have the - partition ID of 165. - - In general, each operating system will identify - partitions in a particular way. For example, &windows;, - assigns each primary and logical partition a - drive letter, starting with - C:. - - &os; must be installed into a primary partition. If - there are multiple disks, a &os; partition can be created on - all, or some, of them. When &os; is installed, at least one - partition must be available. This might be a blank - partition or it might be an existing partition whose data - can be overwritten. - - If all the partitions on all the disks are in use, free - one of them for &os; using the tools provided by an existing - operating system, such as &windows; - fdisk. - - If there is a spare partition, use that. If it is too - small, shrink one or more existing partitions to create more - available space. - - A minimal installation of &os; takes as little as - 100 MB of disk space. However, that is a - very minimal install, leaving almost no - space for files. A more realistic minimum is 250 MB - without a graphical environment, and 350 MB or more for - a graphical user interface. If other third-party software - will be installed, even more space is needed. - - You can use a tool such as - GParted to resize your partitions - and make space for &os;. GParted - is known to work on NTFS and is available - on a number of Live CD Linux distributions, such as SystemRescueCD. - - - Incorrect use of a shrinking tool can delete the data - on the disk. Always have a recent, working backup before - using this type of tool. - - - - Using an Existing Partition Unchanged - - Consider a computer with a single 4 GB disk that - already has a version of &windows; installed, where the - disk has been split into two drive letters, - C: and D:, each - of which is 2 GB in size. There is 1 GB of data - on C:, and 0.5 GB of data on - D:. - - This disk has two partitions, one per drive letter. - Copy all existing data from D: to - C:, which will free up the second - partition, ready for &os;. - - - - Shrinking an Existing Partition - - Consider a computer with a single 4 GB disk that - already has a version of &windows; installed. When - &windows; was installed, it created one large partition, - a C: drive that is 4 GB in size. - Currently, 1.5 GB of space is used, and &os; should - have 2 GB of space. - - In order to install &os;, either: - - - - Backup the &windows; data and then reinstall - &windows;, asking for a 2 GB partition at install - time. - - - - Use one of the tools described above to shrink - your &windows; partition. - - - - - - - - Collect the Network Configuration Details - - Before installing from an FTP site or an - NFS server, make note of the network - configuration. The installer will prompt for this information - so that it can connect to the network to complete the - installation. - - - Connecting to an Ethernet Network or Cable/DSL - Modem - - If using an Ethernet network or an Internet connection - using an Ethernet adapter via cable or DSL, the following - information is needed: - - - - IP address - - - - IP address of the default gateway - - - - Hostname - - - - DNS server IP addresses - - - - Subnet Mask - - - - If this information is unknown, ask the system - administrator or service provider. Make note if this - information is assigned automatically using - DHCP. - - - - Connecting Using a Modem - - If using a dialup modem, &os; can still be installed - over the Internet, it will just take a very long - time. - - You will need to know: - - - - The phone number to dial the Internet Service - Provider (ISP) - - - - The COM: port the modem is connected to - - - - The username and password for the - ISP account - - - - - - Check for &os; Errata - - Although the &os; Project strives to ensure that each - release of &os; is as stable as possible, bugs do occasionally - creep into the process. On rare occasions those bugs affect - the installation process. As these problems are discovered - and fixed, they are noted in the &os; - Errata, which is found on the &os; website. Check - the errata before installing to make sure that there are no - late-breaking problems to be aware of. - - Information about all releases, including the errata for - each release, can be found on the release - information section of the &os; - website. - - - - Obtain the &os; Installation Files - - The &os; installer can install &os; from files located in - any of the following places: - - - Local Media - - - A CDROM or DVD - - - - A USB Memory Stick - - - - A &ms-dos; partition on the same computer - - - - Floppy disks (&os;/&arch.pc98; only) - - - - - Network - - - An FTP site through a firewall or using an HTTP - proxy - - - - An NFS server - - - - A dedicated parallel or serial connection - - - - If installing from a purchased &os; CD/DVD, skip ahead to - . - - To obtain the &os; installation files, skip ahead to which explains how to prepare - the installation media. After reading that section, come back - here and read on to . - - - - Prepare the Boot Media - - The &os; installation process is started by booting the - computer into the &os; installer. It is not a program that - can be run within another operating system. The computer - normally boots using the operating system installed on the - hard disk, but it can also be configured to boot from a CDROM - or from a USB disk. - - - If installing from a CD/DVD to a computer whose BIOS - supports booting from the CD/DVD, skip this section. The - &os; CD/DVD images are bootable and can be used to install - &os; without any other special preparation. - - - To create a bootable memory stick, follow these - steps: - - - - Acquire the Memory Stick Image - - Memory stick images for - &os; 8.X 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 to install. For example, the - memory stick images for - &os;/&arch.i386; &rel2.current;-RELEASE are - available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img. - - - A different directory path is used for - &os; 9.0-RELEASE and later versions. How to - download and install - &os; 9.X - is covered in . - - - The memory stick image has a .img - extension. The ISO-IMAGES/ directory - contains a number of different images and the one to - use depends on the version of &os; and the type of media - supported by the hardware being installed to. - - - Before proceeding, back up the - data on the USB stick, as this procedure will - erase it. - - - - - Write the Image File to the Memory Stick - - - Using &os; to Write the Image - - - The example below lists - /dev/da0 as the target device - where the image will be written. Be very careful that - you have the correct device as the output target, or - you may destroy your existing data. - - - - Writing the Image with &man.dd.1; - - The .img file is - not a regular file that can just - be copied to the memory stick. It is an image of the - complete contents of the disk. This means that - &man.dd.1; must be used to write the image directly to - the disk: - - &prompt.root; dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k - - If an Operation not - permitted error is displayed, make - certain that the target device is not in use, mounted, - or being automounted by another program. Then try - again. - - - - - Using &windows; to Write the Image - - - Make sure to use the correct drive letter as the - output target, as this command will overwrite and - destroy any existing data on the specified - device. - - - - Obtaining <application>Image Writer for - Windows</application> - - Image Writer for - Windows is a free application that can - correctly write an image file to a memory stick. - Download it from https://launchpad.net/win32-image-writer/ - 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 the boot floppy images for a &os;/&arch.pc98; - installation, follow these steps: - - - - Acquire the Boot Floppy Images - - The &os;/&arch.pc98; boot disks can be downloaded from - the floppies directory, - ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/version-RELEASE/floppies/. - Replace version with the - version number to install. - - The floppy images have a .flp - extension. floppies/ contains a number - of different images. Download - boot.flp as well as the number of - files associated with the type of installation, such as - kern.small* or - kern*. - - - The FTP program must use binary - mode to download these disk images. Some - web browsers use text or - ASCII mode, which will be apparent - if the disks are not bootable. - - - - - Prepare the Floppy Disks - - Prepare one floppy disk per downloaded image file. It - is imperative that these disks are free from defects. The - easiest way to test this is to reformat the disks. Do not - trust pre-formatted floppies. The format utility in - &windows; will not tell about the presence of bad blocks, - it simply marks them as bad and ignores - them. It is advised to use brand new floppies. - - - If the installer crashes, freezes, or otherwise - misbehaves, one of the first things to suspect is the - floppies. Write the floppy image files to new disks and - try again. - - - - - Write the Image Files to the Floppy Disks - - The .flp files are - not regular files that can be copied - to the disk. They are images of the complete contents of - the disk. Specific tools must be used to write the - images directly to the disk. - - DOS - &os; provides a tool called rawrite - for creating the floppies on a computer running &windows;. - This tool can be downloaded from - ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/ - version-RELEASE/tools/ on the - &os; FTP site. Download this tool, insert a floppy, then - specify the filename to write to the floppy drive: - - C:\> rawrite boot.flp A: - - Repeat this command for each .flp - file, replacing the floppy disk each time, being sure to - label the disks with the name of the file. Adjust the - command line as necessary, depending on where the - .flp files are located. - - When writing the floppies on a &unix;-like system, - such as another &os; system, use &man.dd.1; to write the - image files directly to disk. On &os;, run: - - &prompt.root; dd if=boot.flp of=/dev/fd0 - - On &os;, /dev/fd0 refers to the - first floppy disk. Other &unix; variants might have - different names for the floppy disk device, so check the - documentation for the system as necessary. - - - - You are now ready to start installing &os;. - - - - - Starting the Installation - - - By default, the installer will not make any changes to - the disk(s) until after the following message: - - Last Chance: Are you SURE you want 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! - -We can take no responsibility for lost disk contents! - - The install can be exited at any time prior to this final - warning without changing the contents of the hard drive. If - there is a concern that something is configured incorrectly, - turn the computer off before this point, and no damage will be - done. - - - - Booting - - - Booting for the &i386; - - - - Turn on the computer. As it starts it should - display an option to enter the system set up menu, or - BIOS, commonly reached by keys like F2, - F10, Del, or - - Alt - S - . Use whichever keystroke is indicated on - screen. In some cases the computer may display a - graphic while it starts. Typically, pressing - Esc will dismiss the graphic and - display the boot messages. - - - - Find the setting that controls which devices the - system boots from. This is usually labeled as the - Boot Order and commonly shown as a list - of devices, such as Floppy, - CDROM, First Hard - Disk, and so on. - - If booting from the CD/DVD, make sure that the - CDROM drive is selected. If booting from a USB disk, - make sure that it is selected instead. When in doubt, - consult the manual that came with the computer or its - motherboard. - - Make the change, then save and exit. The computer - should now restart. - - - - If using a prepared a bootable USB - stick, as described in , plug in the USB stick - before turning on the computer. - - If booting from CD/DVD, turn on the computer, and - insert the CD/DVD at the first opportunity. - - - For &os;/&arch.pc98;, installation boot floppies - are available and can be prepared as described in - . The first - floppy disc will contain - boot.flp. Put this floppy in the - floppy drive to boot into the installer. - - - If the computer starts up as normal and loads the - existing operating system, then either: - - - - The disks were not inserted early enough in the - boot process. Leave them in, and try restarting the - computer. - - - - The BIOS changes did not work correctly. Redo - that step until the right option is selected. - - - - That particular BIOS does not support booting - from the desired media. - - - - - - &os; will start to boot. If booting from CD/DVD, - messages will be displayed, similar to these: - - Booting from CD-Rom... -645MB medium detected -CD Loader 1.2 - -Building the boot loader arguments -Looking up /BOOT/LOADER... Found -Relocating the loader and the BTX -Starting the BTX loader - -BTX loader 1.00 BTX version is 1.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] -\ - - If booting from floppy disc, a display similar to - this will be shown: - - Booting from Floppy... -Uncompressing ... done - -BTX loader 1.00 BTX version is 1.01 -Console: internal video/keyboard -BIOS drive A: is disk0 -BIOS drive C: is disk1 -BIOS 639kB/261120kB available memory - -FreeBSD/i386 bootstrap loader, Revision 1.1 - -Loading /boot/defaults/loader.conf -/kernel text=0x277391 data=0x3268c+0x332a8 | - -Insert disk labelled "Kernel floppy 1" and press any key... - - Remove the boot.flp floppy, - insert the next floppy, and press - Enter. When prompted, insert the other - disks as required. - - - - The boot process will then display the &os; boot - loader menu: - -
- &os; Boot Loader Menu - - - - - - -
- - Either wait ten seconds, or press - Enter. - - - - - - Booting for &sparc64; - - Most &sparc64; systems are set to boot automatically - from disk. To install &os;, boot over the network or from a - CD/DVD and wait until the boot message appears. The message - depends on the model, but should look similar to: - - Sun Blade 100 (UltraSPARC-IIe), Keyboard Present -Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. -OpenBoot 4.2, 128 MB memory installed, Serial #51090132. -Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - - If the system proceeds to boot from disk, press - L1A - or StopA - on the keyboard, or send a BREAK over the - serial console using ~# in &man.tip.1; or - &man.cu.1; to get to the PROM prompt. It looks like - this: - - ok -ok {0} - - - - This is the prompt used on systems with just one - CPU. - - - - This is the prompt used on SMP systems and the - digit indicates the number of the active CPU. - - - - At this point, place the CD/DVD into the drive and from - the PROM prompt, type boot cdrom. - - - - - Reviewing the Device Probe Results - - The last few hundred lines that have been displayed on - screen are stored and can be reviewed. - - To review this buffer, press Scroll Lock - to turn on scrolling in the display. Use the arrow keys or - PageUp and PageDown to view - the results. Press Scroll Lock again to stop - scrolling. - - Do this now, to review the text that scrolled off the - screen when the kernel was carrying out the device probes. - Text similar to will be - displayed, although it will differ depending on the devices in - the computer. - -
- Typical Device Probe Results - - 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 -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 pci -0 -usb0: <VIA 83572 USB controller> on uhci0 -usb0: USB revision 1.0 -uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1 -uhub0: 2 ports with 2 removable, self powered -pci0: <unknown card> (vendor=0x1106, dev=0x3040) at 7.3 -dc0: <ADMtek AN985 10/100BaseTX> port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir -q 11 at device 8.0 on pci0 -dc0: Ethernet address: 00:04:5a:74:6b:b5 -miibus0: <MII bus> on dc0 -ukphy0: <Generic IEEE 802.3u media interface> on miibus0 -ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto -ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xec00-0xec1f 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 -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 -atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 -atkbd0: <AT Keyboard> flags 0x1 irq1 on atkbdc0 -kbd0 at atkbd0 -psm0: <PS/2 Mouse> irq 12 on atkbdc0 -psm0: model Generic PS/@ mouse, device ID 0 -vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 -sc0: <System console> at flags 0x100 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 -pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode -ppc0: FIFO with 16/16/15 bytes threshold -plip0: <PLIP network interface> on ppbus0 -ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master UDMA33 -acd0: CD-RW <LITE-ON LTR-1210B> at ata1-slave PIO4 -Mounting root from ufs:/dev/md0c -/stand/sysinstall running as init on vty0 -
- - Check the probe results carefully to make sure that &os; - found all the devices. If a device was not found, it will - not be listed. A custom kernel can be used to - add in support for devices which are not in the - GENERIC kernel. - - After the device probe, the menu shown in will be displayed. Use the - arrow key to choose a country, region, or group. Then press - Enter to set the country. - -
- Selecting Country Menu - - - - - - -
- - If United States is selected - as the country, the standard American keyboard map will be - used. If a different country is chosen, the following menu - will be displayed. Use the arrow keys to choose the correct - keyboard map and press Enter. - -
- Selecting Keyboard Menu - - - - - - -
- - After the country selection, the &man.sysinstall.8; - main menu will display. - - - - - Introducing &man.sysinstall.8; - - The &os; 8.X installer, - &man.sysinstall.8;, is console based and is divided into a - number of menus and screens that can be used to configure and - control the installation process. - - This menu system is controlled by the arrow keys, - Enter, Tab, - Space, and other keys. To view a detailed - description of these keys and what they do, ensure that the - Usage entry is highlighted and that - the [Select] button is selected, as shown - in , then press - Enter. - - The instructions for using the menu system will be - displayed. After reviewing them, press Enter - to return to the Main Menu. - -
- Selecting Usage from Sysinstall Main Menu - - - - - - -
- - - Selecting the Documentation Menu - - From the Main Menu, select Doc - with the arrow keys and press Enter. - -
- Selecting Documentation Menu - - - - - - -
- - This will display the Documentation Menu. - -
- Sysinstall Documentation Menu - - - - - - -
- - It is important to read the documents provided. To view a - document, select it with the arrow keys and press - Enter. When finished reading a document, - press Enter to return to the Documentation - Menu. - - To return to the Main Installation Menu, select - Exit with the arrow keys and press - Enter. - - - - Selecting the Keymap Menu - - To change the keyboard mapping, use the arrow keys to - select Keymap from the menu and - press Enter. This is only required when - using a non-standard or non-US keyboard. - -
- Sysinstall Main Menu - - - - - - -
- - A different keyboard mapping may be chosen by selecting - the menu item using the up and down arrow keys and pressing - Space. Pressing Space again - will unselect the item. When finished, choose the &gui.ok; - using the arrow keys and press Enter. - - Only a partial list is shown in this screen - representation. Selecting &gui.cancel; by pressing - Tab will use the default keymap and return to - the Main Install Menu. - -
- Sysinstall Keymap Menu - - - - - - -
- - - - Installation Options Screen - - Select Options and press - Enter. - -
- Sysinstall Main Menu - - - - - - -
- -
- Sysinstall Options - - - - - - -
- - The default values are usually fine for most users and do - not need to be changed. The release name will vary according - to the version being installed. - - The description of the selected item will appear at the - bottom of the screen highlighted in blue. Notice that one of - the options is Use Defaults to - reset all values to startup defaults. - - Press F1 to read the help screen about - the various options. - - Press Q to return to the Main Install - menu. - - - - Begin a Standard Installation - - The Standard installation is - the option recommended for those new to &unix; or &os;. Use - the arrow keys to select Standard - and then press Enter to start the - installation. - -
- Begin Standard Installation - - - - - - -
- - - - - Allocating Disk Space - - The first task is to allocate disk space for &os;, and label - that space so that &man.sysinstall.8; can prepare it. In order - to do this you need to know how &os; expects to find - information on the disk. - - - BIOS Drive Numbering - - Before installing and configuring &os; it is important to - be aware how &os; deals with BIOS drive mappings. - - MS-DOS - Microsoft Windows - In a PC running a BIOS-dependent operating system such as - µsoft.windows;, the BIOS is able to abstract the normal - disk drive order and the operating system goes along with the - change. This allows the user to boot from a disk drive other - than the "primary master". This is especially convenient for - users buy an identical second hard drive, and perform routine - copies of the first drive to the second drive. If the first - drive fails, is attacked by a virus, or is scribbled upon by - an operating system defect, they can easily recover by - instructing the BIOS to logically swap the drives. It is like - switching the cables on the drives, without having to open the - case. - - SCSI - BIOS - Systems with SCSI controllers often include BIOS - extensions which allow the SCSI drives to be re-ordered in a - similar fashion for up to seven drives. - - A user who is accustomed to taking advantage of these - features may become surprised when the results with &os; are - not as expected. &os; does not use the BIOS, and does not - know the logical BIOS drive mapping. This can - lead to perplexing situations, especially when drives are - physically identical in geometry and have been made as data - clones of one another. - - When using &os;, always restore the BIOS to natural drive - numbering before installing &os;, and then leave it that way. - If drives need to be switched around, take the time to open - the case and move the jumpers and cables. - - - An Illustration from the Files of Bill and Fred's - Exceptional Adventures: - - Bill breaks-down an older Wintel box to make another - &os; box for Fred. Bill installs a single SCSI drive as - SCSI unit zero and installs &os; on it. - - Fred begins using the system, but after several days - notices that the older SCSI drive is reporting numerous - errors. - - To address the situation, Bill grabs an identical SCSI - drive and installs this drive as SCSI unit four and makes an - image copy from drive zero to drive four. Now that the new - drive is installed and functioning, Bill decides to start - using it, so he uses features in the SCSI BIOS to re-order - the disk drives so that the system boots from SCSI unit - four. &os; boots and runs just fine. - - Fred continues his work and soon decides that it is time - to upgrade to a newer version of &os;. Bill removes SCSI - unit zero because it was a bit flaky and replaces it with - another identical disk drive. Bill then installs the new - version of &os; onto the new SCSI unit zero and the - installation goes well. - - Fred uses the new version of &os; for a few days, and - certifies that it is good enough for use in the engineering - department. It is time to copy all of his work from the old - version, so Fred mounts SCSI unit four which should contain - the latest copy of the older &os; version. Fred is dismayed - to find that none of his work is present on SCSI unit - four. - - It turns out that when Bill made an image copy of the - original SCSI unit zero onto SCSI unit four, unit four - became the new clone. When Bill re-ordered - the SCSI BIOS so that he could boot from SCSI unit four, - &os; was still running on SCSI unit zero. Making this kind - of BIOS change causes some or all of the boot and loader - code to be fetched from the selected BIOS drive. But when - the &os; kernel drivers take over, the BIOS drive numbering - is ignored, and &os; transitions back to normal drive - numbering. In this example, the system continued to operate - on the original SCSI unit zero, and all of Fred's data was - there, not on SCSI unit four. The fact that the system - appeared to be running on SCSI unit four was simply an - artifact of human expectations. - - Fortunately, the older SCSI unit zero was retrieved and - all of Fred's work was restored. - - Although SCSI drives were used in this illustration, the - concepts apply equally to IDE drives. - - - - - Creating Slices Using FDisk - - After choosing to begin a standard installation in - &man.sysinstall.8;, this message will appear: - - Message - In the next menu, you will need to set up a DOS-style ("fdisk") - partitioning scheme for your hard disk. If you simply wish to devote - all disk space to FreeBSD (overwriting anything else that might be on - 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 ] - - [ Press enter or space ] - - Press Enter and a list of all the hard - drives that the kernel found when it carried out the device - probes will be displayed. shows an example from a - system with two IDE disks called ad0 and - ad2. - -
- Select Drive for FDisk - - - - - - -
- - Note that ad1 is not listed - here. - - Consider two IDE hard disks where one is the master on the - first IDE controller and one is the master on the second IDE - controller. If &os; numbered these as - ad0 and ad1, - everything would work. - - But if a third disk is later added as the slave device on - the first IDE controller, it would now be - ad1, and the previous - ad1 would become - ad2. Because device names are used to - find filesystems, some filesystems may no longer appear - correctly, requiring a change to the &os; - configuration. - - To work around this, the kernel can be configured to name - IDE disks based on where they are and not the order in which - they were found. With this scheme, the master disk on the - second IDE controller will always be - ad2, even if there are no - ad0 or ad1 - devices. - - This configuration is the default for the &os; kernel, - which is why the display in this example shows - ad0 and ad2. The - machine on which this screenshot was taken had IDE disks on - both master channels of the IDE controllers and no disks on - the slave channels. - - Select the disk on which to install &os;, and then press - &gui.ok;. FDisk will start, with a - display similar to that shown in . - - The FDisk display is broken - into three sections. - - The first section, covering the first two lines of the - display, shows details about the currently selected disk, - including its &os; name, the disk geometry, and the total size - of the disk. - - The second section shows the slices that are currently on - the disk, where they start and end, how large they are, the - name &os; gives them, and their description and sub-type. - This example shows two small unused slices which are artifacts - of disk layout schemes on the PC. It also shows one large - FAT slice, which appears as - C: in &windows;, and an extended slice, - which may contain other drive letters in &windows;. - - The third section shows the commands that are available in - FDisk. - -
- Typical Default <application>FDisk</application> - Partitions - - - - - - -
- - This step varies, depending on how the disk is to be - sliced. - - To install &os; to the entire disk, which will delete all - the other data on this disk, press A, which - corresponds to the Use Entire Disk - option. The existing slices will be removed and replaced with - a small area flagged as unused and one - large slice for &os;. Then, select the newly created &os; - slice using the arrow keys and press S to - mark the slice as being bootable. The screen will then look - similar to . Note the - A in the Flags column, - which indicates that this slice is - active, and will be booted from. - - If an existing slice needs to be deleted to make space for - &os;, select the slice using the arrow keys and press - D. Then, press C to be - prompted for the size of the slice to create. Enter the - appropriate value and press Enter. The - default value in this box represents the largest possible - slice to make, which could be the largest contiguous block of - unallocated space or the size of the entire hard disk. - - If you have already made space for &os; then you can press - C to create a new slice. Again, you will be - prompted for the size of slice you would like to - create. - -
- Fdisk Partition Using Entire Disk - - - - - - -
- - When finished, press Q. Any changes will - be saved in &man.sysinstall.8;, but will not yet be written to - disk. - - - - Install a Boot Manager - - The next menu provides the option to install a boot - manager. In general, install the &os; boot manager if: - - - - There is more than one drive and &os; will be - installed onto a drive other than the first one. - - - - &os; will be installed alongside another operating - system on the same disk, and you want to choose whether to - start &os; or the other operating system when the computer - starts. - - - - If &os; is going to be the only operating system on this - machine, installed on the first hard disk, then the - Standard boot manager will suffice. - Choose None if using a third-party - boot manager capable of booting &os;. - - Make a selection and press Enter. - -
- Sysinstall Boot Manager Menu - - - - - - -
- - The help screen, reached by pressing F1, - discusses the problems that can be encountered when trying to - share the hard disk between operating systems. - - - - Creating Slices on Another Drive - - If there is more than one drive, it will return to the - Select Drives screen after the boot manager selection. To - install &os; on to more than one disk, select another disk and - repeat the slice process using - FDisk. - - - If installing &os; on a drive other than the first - drive, the &os; boot manager needs to be installed on both - drives. - - -
- Exit Select Drive - - - - - - -
- - Use Tab to toggle between the last drive - selected, &gui.ok;, and &gui.cancel;. - - Press Tab once to toggle to &gui.ok;, - then press Enter to continue with the - installation. - - - - Creating Partitions Using - <application>Disklabel</application> - - Next, create some partitions inside each slice. - Remember that each partition is lettered, from - a through to h, and that - partitions b, c, and - d have conventional meanings that should be - adhered to. - - Certain applications can benefit from particular partition - schemes, especially when laying out partitions across more - than one disk. However, for a first &os; installation, do not - give too much thought to how to partition the disk. It is - more important to install &os; and start learning how to use - it. You can always re-install &os; to change the partition - scheme after becoming more familiar with the operating - system. - - The following scheme features four partitions: one for - swap space and three for filesystems. - - - Partition Layout for First Disk - - - - - - - - - - Partition - - Filesystem - - Size - - Description - - - - - - a - - / - - 1 GB - - This is the root filesystem. Every other - filesystem will be mounted somewhere under this one. - 1 GB is a reasonable size for this filesystem as - user files should not be stored here and a regular - &os; install will put about 128 MB of data - here. - - - - b - - N/A - - 2-3 x RAM - - The system's swap space is kept on the - b partition. Choosing the right - amount of swap space can be a bit of an art. A good - rule of thumb is that swap space should be two or - three times as much as the available physical memory - (RAM). There should be at least 64 MB of swap, - so if there is less than 32 MB of RAM in the - computer, set the swap amount to 64 MB. If there - is more than one disk, swap space can be put on each - disk. &os; will then use each disk for swap, which - effectively speeds up the act of swapping. In this - case, calculate the total amount of swap needed and - divide this by the number of disks to give the amount - of swap to put on each disk. - - - - e - - /var - - 512 MB to 4096 MB - - /var contains files that are - constantly varying, such as log files and other - administrative files. Many of these files are read - from or written to extensively during &os;'s - day-to-day running. Putting these files on another - filesystem allows &os; to optimize the access of these - files without affecting other files in other - directories that do not have the same access - pattern. - - - - f - - /usr - - Rest of disk (at least 8 GB) - - All other files will typically be stored in - /usr and its - subdirectories. - - - -
- - - 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 installing &os; on to more than one disk, create - partitions in the other configured slices. The easiest way to - do this is to create two partitions on each disk, one for the - swap space, and one for a filesystem. - - - Partition Layout for Subsequent Disks - - - - - - - - - - Partition - - Filesystem - - Size - - Description - - - - - - b - - N/A - - See description - - Swap space can be split across each disk. Even - though the a partition is free, - convention dictates that swap space stays on the - b partition. - - - - e - - /diskn - - Rest of disk - - The rest of the disk is taken up with one big - partition. This could easily be put on the - a partition, instead of the - e partition. However, convention - says that the a partition on a - slice is reserved for the filesystem that will be the - root (/) filesystem. Following - this convention is not necessary, but - &man.sysinstall.8; uses it, so following it makes the - installation slightly cleaner. This filesystem can be - mounted anywhere; this example mounts it as /diskn, - where n is a number that - changes for each disk. - - - -
- - Having chosen the partition layout, create it using - &man.sysinstall.8;. - - 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 (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. - - [ OK ] - [ Press enter or space ] - - Press Enter to start the &os; partition - editor, called Disklabel. - - shows the display when - Disklabel starts. The display is - divided into three sections. - - The first few lines show the name of the disk being - worked on and the slice that contains the partitions to - create. At this point, Disklabel - calls this the Partition name rather than - slice name. This display also shows the amount of free space - within the slice; that is, space that was set aside in the - slice, but that has not yet been assigned to a - partition. - - The middle of the display shows the partitions that have - been created, the name of the filesystem that each partition - contains, their size, and some options pertaining to the - creation of the filesystem. - - The bottom third of the screen shows the keystrokes that - are valid in Disklabel. - -
- Sysinstall Disklabel Editor - - - - - - -
- - Disklabel can automatically - create partitions and assign them default sizes. The default - sizes are calculated with the help of an internal partition - sizing algorithm based on the disk size. Press - A to see a display similar to that shown in - . Depending on the size of - the disk, the defaults may or may not be appropriate. - - - The default partitioning assigns - /tmp its own partition instead of - being part of the / partition. This - helps avoid filling the / partition - with temporary files. - - -
- Sysinstall Disklabel Editor with Auto Defaults - - - - - - -
- - To replace the default partitions, use the arrow keys to - select the first partition and press D to - delete it. Repeat this to delete all the suggested - partitions. - - To create the first partition, a, - mounted as /, make sure the proper disk - slice at the top of the screen is selected and press - C. A dialog box will appear, prompting for - the size of the new partition, as shown in . The size can be entered - as the number of disk blocks to use or as a number followed by - either M for megabytes, - G for gigabytes, or C - for cylinders. - -
- Free Space for Root Partition - - - - - - -
- - The default size shown will create a partition that takes - up the rest of the slice. If using the partition sizes - described in the earlier example, delete the existing figure - using Backspace, and then type in - 512M, as shown in . Then press - &gui.ok;. - -
- Edit Root Partition Size - - - - - - -
- - After choosing the partition's size, the installer will - ask whether this partition will contain a filesystem or swap - space. The dialog box is shown in . This first partition - will contain a filesystem, so check that - FS is selected and press - Enter. - -
- Choose the Root Partition Type - - - - - - -
- - Finally, tell Disklabel where - the filesystem will be mounted. The dialog box is shown in - . Type - /, and then press - Enter. - -
- Choose the Root Mount Point - - - - - - -
- - The display will then update to show the newly created - partition. Repeat this procedure for the other partitions. - When creating the swap partition, it will not prompt for the - filesystem mount point. When creating the final partition, - /usr, leave the suggested size as is to - use the rest of the slice. - - The final &os; DiskLabel Editor screen will appear similar - to , although the values - chosen may be different. Press Q to - finish. - -
- Sysinstall Disklabel Editor - - - - - - -
- - - - - Choosing What to Install - - - Select the Distribution Set - - Deciding which distribution set to install will depend - largely on the intended use of the system and the amount of - disk space available. The predefined options range from - installing the smallest possible configuration to everything. - Those who are new to &unix; or &os; should select one of these - canned options. Customizing a distribution set is typically - for the more experienced user. - - Press F1 for more information on the - distribution set options and what they contain. When finished - reviewing the help, press Enter to return to - the Select Distributions Menu. - - If a graphical user interface is desired, the - configuration of &xorg; and - selection of a default desktop must be done after the - installation of &os;. More information regarding the - installation and configuration of a - &xorg; can be found in . - - If compiling a custom kernel is anticipated, select an - option which includes the source code. For more information - on why a custom kernel should be built or how to build a - custom kernel, see . - - The most versatile system is one that includes everything. - If there is adequate disk space, select - All, as shown in , by using the arrow keys and - pressing Enter. If there is a concern about - disk space, consider using an option that is more suitable for - the situation. Do not fret over the perfect choice, as other - distributions can be added after installation. - -
- Choose Distributions - - - - - - -
- - - - Installing the Ports Collection - - After selecting the desired distribution, an opportunity - to install the &os; Ports Collection is presented. The Ports - Collection is an easy and convenient way to install software - as it provides a collection of files that automate the - downloading, compiling, and installation of third-party - software packages. discusses how to - use the Ports Collection. - - The installation program does not check to see if you have - adequate space. Select this option only if you have - adequate hard disk space. As of &os; &rel.current;, the &os; - Ports Collection takes up about &ports.size; of disk space. - You can safely assume a larger value for more recent versions - of &os;. - - User Confirmation Requested - Would you like to install the FreeBSD ports collection? - - This will give you ready access to over &os.numports; ported software packages, - 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). - - 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. - - For more information on the Ports Collection & the latest ports, - visit: - http://www.FreeBSD.org/ports - - [ Yes ] No - - Select &gui.yes; with the arrow keys to install the Ports - Collection or &gui.no; to skip this option. Press - Enter to continue. The Choose Distributions - menu will redisplay. - -
- Confirm Distributions - - - - - - -
- - Once satisfied with the options, select - Exit with the arrow keys, ensure - that &gui.ok; is highlighted, and press - Enter to continue. - - - - - Choosing the Installation Media - - If installing from a CD/DVD, use the arrow keys to highlight - Install from a &os; CD/DVD. Ensure - that &gui.ok; is highlighted, then press Enter - to proceed with the installation. - - For other methods of installation, select the appropriate - option and follow the instructions. - - Press F1 to display the Online Help for - installation media. Press Enter to return - to the media selection menu. - -
- Choose Installation Media - - - - - - -
- - - FTP Installation Modes - - - installation - network - FTP - - - There are three FTP installation modes to choose from: - active FTP, passive FTP, or via a HTTP proxy. - - - - FTP Active: Install from an FTP - server - - - This option makes all FTP transfers use - Active mode. This will not work through - firewalls, but will often work with older FTP servers - that do not support passive mode. If the connection - hangs with passive mode (the default), try using active - mode. - - - - - FTP Passive: Install from an FTP server - through a firewall - - - This option instructs &man.sysinstall.8; to use - passive mode - FTP - 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 - - - This option instructs &man.sysinstall.8; to use the - HTTP protocol to connect to a proxy for all FTP - operations. The proxy will translate the requests and - send them to the FTP server. This allows the user to - pass through firewalls that do not allow FTP, but offer - a HTTP proxy - FTP - via a HTTP proxy - . In this case, specify the proxy in - addition to the FTP server. - - - - - For a proxy FTP server, give the name of the server as - part of the username, after an @ sign. The - proxy server then fakes the real server. For - example, to install from ftp.FreeBSD.org, using the - proxy FTP server foo.example.com, listening - on port 1234, go to the options menu, set the FTP username to - ftp@ftp.FreeBSD.org and the password to an - email address. As the installation media, specify FTP (or - passive FTP, if the proxy supports it), and the URL - ftp://foo.example.com:1234/pub/FreeBSD. - - Since /pub/FreeBSD from ftp.FreeBSD.org is proxied - under foo.example.com, the proxy - will fetch the files from ftp.FreeBSD.org as the - installer requests them. - - - - - Committing to the Installation - - The installation can now proceed if desired. This is also - the last chance for aborting the installation to prevent changes - to the hard drive. - - User Confirmation Requested - 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! - - We can take no responsibility for lost disk contents! - - [ Yes ] No - - 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 - -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. - -If you wish to re-enter this utility after the system is up, you may -do so by typing: /usr/sbin/sysinstall. - - [ OK ] - - [ Press enter or space ] - - Press Enter to proceed with - post-installation configurations. - - Selecting &gui.no; and pressing Enter will - abort the installation so no changes will be made to the system. - The following message will appear: - - Message -Installation complete with some errors. You may wish to scroll -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. - - [ OK ] - - This message is generated because nothing was installed. - Pressing Enter will return to the Main - Installation Menu to exit the installation. - - - - Post-installation - - Configuration of various options can be performed after a - successful installation. An option can be configured by - re-entering the configuration menus before booting the new &os; - system or after boot using &man.sysinstall.8; and then selecting - the Configure menu. - - - Network Device Configuration - - If PPP was previously configured for an FTP install, this - screen will not display and can be configured after boot as - described above. - - For detailed information on Local Area Networks and - configuring &os; as a gateway/router refer to the Advanced Networking - chapter. - - User Confirmation Requested - Would you like to configure any Ethernet or PPP network devices? - - [ Yes ] No - - To configure a network device, select &gui.yes; and press - Enter. Otherwise, select &gui.no; to - continue. - -
- Selecting an Ethernet Device - - - - - - -
- - Select the interface to be configured with the arrow keys - and press Enter. - - User Confirmation Requested - Do you want to try IPv6 configuration of the interface? - - Yes [ No ] - - In this private local area network, the current Internet - type protocol (IPv4) was sufficient and - &gui.no; was selected with the arrow keys and - Enter pressed. - - If connected to an existing IPv6 - network with an RA server, choose - &gui.yes; and press Enter. It will take - several seconds to scan for RA servers. - - User Confirmation Requested - Do you want to try DHCP configuration of the interface? - - Yes [ No ] - - If Dynamic Host Configuration Protocol - DHCP) is not required, select &gui.no; with - the arrow keys and press Enter. - - Selecting &gui.yes; will execute &man.dhclient.8; and, if - successful, will fill in the network configuration information - automatically. Refer to for - more information. - - The following Network Configuration screen shows the - configuration of the Ethernet device for a system that will - act as the gateway for a Local Area Network. - -
- Set Network Configuration for - <replaceable>ed0</replaceable> - - - - - - -
- - Use Tab to select the information fields - and fill in appropriate information: - - - - Host - - - The fully-qualified hostname, such as k6-2.example.com in - this case. - - - - - Domain - - - The name of the domain that the machine is in, such - as example.com for this - case. - - - - - IPv4 Gateway - - - IP address of host forwarding packets to non-local - destinations. This must be filled in if the machine is - a node on the network. Leave this field - blank if the machine is the gateway to the - Internet for the network. The IPv4 Gateway is also - known as the default gateway or default route. - - - - - Name server - - - IP address of the local DNS server. There is no - local DNS server on this private local area network so - the IP address of the provider's DNS server - (208.163.10.2) was - used. - - - - - IPv4 address - - - The IP address to be used for this interface was - 192.168.0.1 - - - - - Netmask - - - The address block being used for this local area - network is 192.168.0.0 - - 192.168.0.255 - with a netmask of 255.255.255.0. - - - - - Extra options to &man.ifconfig.8; - - - Any additional interface-specific options to - &man.ifconfig.8;. There were none in this case. - - - - - - Use Tab to select &gui.ok; when finished - and press Enter. - - User Confirmation Requested - Would you like to bring the ed0 interface up right now? - - [ Yes ] No - - Choosing &gui.yes; and pressing Enter - will bring the machine up on the network so it is ready for - use. However, this does not accomplish much during - installation, since the machine still needs to be - rebooted. - - - - Configure Gateway - - User Confirmation Requested - Do you want this machine to function as a network gateway? - - [ Yes ] No - - If the machine will be acting as the gateway for a local - area network and forwarding packets between other machines, - select &gui.yes; and press Enter. If the - machine is a node on a network, select &gui.no; and press - Enter to continue. - - - - Configure Internet Services - - User Confirmation Requested -Do you want to configure inetd and the network services that it provides? - - Yes [ No ] - - If &gui.no; is selected, various services will not be - enabled. These services can be enabled after installation by - editing /etc/inetd.conf with a text - editor. See for more - information. - - Otherwise, select &gui.yes; to configure these services - during install. An additional confirmation will - display: - - User Confirmation Requested -The Internet Super Server (inetd) allows a number of simple Internet -services to be enabled, including finger, ftp and telnetd. Enabling -these services may increase risk of security problems by increasing -the exposure of your system. - -With this in mind, do you wish to enable inetd? - - [ Yes ] No - - Select &gui.yes; to continue. - - User Confirmation Requested -inetd(8) relies on its configuration file, /etc/inetd.conf, to determine -which of its Internet services will be available. The default FreeBSD -inetd.conf(5) leaves all services disabled by default, so they must be -specifically enabled in the configuration file before they will -function, even once inetd(8) is enabled. Note that services for -IPv6 must be separately enabled from IPv4 services. - -Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to -use the current settings. - - [ Yes ] No - - Selecting &gui.yes; allows services to be enabled by - deleting the # at the beginning of the - lines representing those services. - -
- Editing <filename>inetd.conf</filename> - - - - - - -
- - Once the edits are complete, press Esc to - display a menu which will exit the editor and save 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 - for OpenSSH. This allows secure - remote access to the machine. For more information about - OpenSSH, see . - - - - Anonymous FTP - - - FTP - anonymous - - - User Confirmation Requested - 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. - - - - Allow Anonymous FTP - - Anyone can access the machine if anonymous FTP - connections are allowed. The security implications should - be considered before enabling this option. For more - information about security, see . - - To allow anonymous FTP, use the arrow keys to select - &gui.yes; and press Enter. 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 indicates that the FTP service will also - have to be enabled in /etc/inetd.conf - to allow anonymous FTP connections. Select &gui.yes; and - press Enter to continue. The following - screen will display: - -
- Default Anonymous FTP Configuration - - - - - - -
- - Use Tab to select the information - fields and fill in appropriate information: - - - - UID - - - The user ID to assign to the anonymous FTP user. - All files uploaded will be owned by this ID. - - - - - Group - - - Which group to place the anonymous FTP user - into. - - - - - Comment - - - String describing this user in - /etc/passwd. - - - - - FTP Root Directory - - - Where files available for anonymous FTP will be - kept. - - - - - Upload Subdirectory - - - Where files uploaded by anonymous FTP users will - go. - - - - - The FTP root directory will be put in - /var by default. If there is not - enough room there for the anticipated FTP needs, use - /usr instead by setting the FTP root - directory to /usr/ftp. - - Once satisfied with the values, press - Enter to continue. - - User Confirmation Requested - Create a welcome message file for anonymous FTP users? - - [ Yes ] No - - If &gui.yes; is selected, press Enter - and the &man.ee.1; editor will automatically start. - -
- Edit the FTP Welcome Message - - - - - - -
- - Use the instructions to change the message. Note the - file name location at the bottom of the editor - screen. - - Press Esc and a pop-up menu will - default to a) leave editor. - Press Enter to exit and continue. Press - Enter again to save any changes. - - - - - Configure the Network File System - - The Network File System (NFS) allows - sharing of files across a network. A machine can be - configured as a server, a client, or both. Refer to for more information. - - - NFS Server - - User Confirmation Requested - Do you want to configure this machine as an NFS server? - - Yes [ No ] - - If there is no need for a NFS server, - select &gui.no; and press Enter. - - If &gui.yes; is chosen, a message will pop-up indicating - that /etc/exports must be - created. - - Message -Operating as an NFS server means that you must first configure an -/etc/exports file to indicate which hosts are allowed certain kinds of -access to your local filesystems. -Press [Enter] now to invoke an editor on /etc/exports - [ OK ] - - Press Enter to continue. A text editor - will start, allowing /etc/exports to be - edited. - -
- Editing <filename>exports</filename> - - - - - - -
- - Use the instructions to add the exported filesystems. - Note the file name location at the bottom of the editor - screen. - - Press Esc and a pop-up menu will - default to a) leave editor. - Press Enter to exit and continue. - - - - <acronym>NFS</acronym> Client - - The NFS client allows the machine to - access NFS servers. - - User Confirmation Requested - Do you want to configure this machine as an NFS client? - - Yes [ No ] - - With the arrow keys, select &gui.yes; or &gui.no; as - appropriate and press Enter. - - - - - System Console Settings - - There are several options available to customize the - system console. - - User Confirmation Requested - Would you like to customize your system console settings? - - [ Yes ] No - - To view and configure the options, select &gui.yes; and - press Enter. - -
- System Console Configuration Options - - - - - - -
- - A commonly used option is the screen saver. Use the arrow - keys to select Saver and then press - Enter. - -
- Screen Saver Options - - - - - - -
- - Select the desired screen saver using the arrow keys and - then press Enter. The System Console - Configuration menu will redisplay. - - The default time interval is 300 seconds. To change the - time interval, select Saver again. - At the Screen Saver Options menu, select - Timeout using the arrow keys and - press Enter. A pop-up menu will - appear: - -
- Screen Saver Timeout - - - - - - -
- - The value can be changed, then select &gui.ok; and press - Enter to return to the System Console - Configuration menu. - -
- System Console Configuration Exit - - - - - - -
- - Select Exit and press - Enter to continue with the post-installation - configuration. - - - - Setting the Time Zone - - Setting the time zone allows the system to automatically - correct for any regional time changes and perform other time - zone related functions properly. - - The example shown is for a machine located in the Eastern - time zone of the United States. The selections will vary - according to the geographic location. - - User Confirmation Requested - Would you like to set this machine's time zone now? - - [ Yes ] No - - Select &gui.yes; and press Enter to set - the time zone. - - 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! - - Yes [ No ] - - Select &gui.yes; or &gui.no; according to how the - machine's clock is configured, then press - Enter. - -
- Select the Region - - - - - - -
- - The appropriate region is selected using the arrow keys - and then pressing Enter. - -
- Select the Country - - - - - - -
- - Select the appropriate country using the arrow keys and - press Enter. - -
- Select the Time Zone - - - - - - -
- - The appropriate time zone is selected using the arrow - keys and pressing Enter. - - Confirmation - Does the abbreviation 'EDT' look reasonable? - - [ Yes ] No - - Confirm that the abbreviation for the time zone is - correct. If it looks okay, press Enter to - continue with the post-installation configuration. - - - - Mouse Settings - - This option allows cut and paste in the console and user - programs using a 3-button mouse. If using a 2-button mouse, - refer to &man.moused.8; for details on emulating the 3-button - style. This example depicts a non-USB mouse - configuration: - - User Confirmation Requested - Does this system have a PS/2, serial, or bus mouse? - - [ Yes ] No - - Select &gui.yes; for a PS/2, serial, or bus mouse, or - &gui.no; for a USB mouse, then press - Enter. - -
- Select Mouse Protocol Type - - - - - - -
- - Use the arrow keys to select - Type and press - Enter. - -
- Set Mouse Protocol - - - - - - -
- - The mouse used in this example is a PS/2 type, so the - default Auto is appropriate. To - change the mouse protocol, use the arrow keys to select - another option. Ensure that &gui.ok; is highlighted and press - Enter to exit this menu. - -
- Configure Mouse Port - - - - - - -
- - Use the arrow keys to select - Port and press - Enter. - -
- Setting the Mouse Port - - - - - - -
- - This system had a PS/2 mouse, so the default - PS/2 is appropriate. To change the - port, use the arrow keys and then press - Enter. - -
- Enable the Mouse Daemon - - - - - - -
- - Last, use the arrow keys to select - Enable, and press - Enter to enable and test the mouse - daemon. - - -
- Test the Mouse Daemon - - - - - - -
- - Move the mouse around the screen to verify that the cursor - responds properly. If it does, select &gui.yes; and press - Enter. If not, the mouse has not been - configured correctly. Select &gui.no; and try using different - configuration options. - - Select Exit with the arrow keys - and press Enter to continue with the - 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, &man.sysinstall.8; 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 - - Select &gui.yes; and press Enter to be - presented with 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. Otherwise, select - a particular category. Highlight the 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 as - selected. Select as many packages as desired by highlighting - the package and pressing Space. A short - description of each package will appear in the lower left - corner of the screen. - - Press Tab to toggle between the last - selected package, &gui.ok;, and &gui.cancel;. - - Once finished marking the packages for installation, press - Tab once to toggle to &gui.ok; and press - Enter to return to the Package Selection - menu. - - The left and right arrow keys will also toggle between - &gui.ok; and &gui.cancel;. This method can also be used to - select &gui.ok; and press Enter to return to - the Package Selection menu. - -
- Install Packages - - - - - - -
- - Use the Tab and arrow keys to select - [ Install ] and press - Enter to see the installation confirmation - message: - -
- Confirm Package Installation - - - - - - -
- - Select &gui.ok; and press Enter to start - the package installation. Installation messages will appear - until all of the installations have completed. Make note if - there are any error messages. - - The final configuration continues after packages are - installed. If no packages are selected, select - Install to return to the final - configuration. - - - - Add Users/Groups - - Add at least one user during the installation so that the - system can be used without logging in as root. The root partition is - generally small and running applications as root can quickly fill it. A - bigger danger is noted below: - - 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. - - - - - Home directory - - - The user's home directory (leave blank for - default). - - - - - Login shell - - The user's login shell (leave blank for - default of /bin/sh). - - - - - In this example, the login shell was changed from - /bin/sh to - /usr/local/bin/bash to use the - bash shell that was previously - installed as a package. Do not use a shell that does not - exist or the user will not be able to login. The most common - shell used in &os; is the C shell, - /bin/tcsh. - - The user was also added to the wheel group to be able to - become a superuser with root privileges. - - Once satisfied, press &gui.ok; and the User and Group - Management menu will redisplay: - -
- Exit User and Group Management - - - - - - -
- - Groups can also be added at this time. Otherwise, this - menu may be accessed using &man.sysinstall.8; at a later - time. - - When finished adding users, select - Exit with the arrow keys and press - Enter to continue the installation. - - - - Set the <systemitem class="username">root</systemitem> - 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. - Do not forget this password. Notice that the typed password - is not echoed, nor are asterisks displayed. - - New password: -Retype new password : - - The installation will continue after the password is - successfully entered. - - - - Exiting Install - - A message will ask if configuration is complete: - - 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. The installer - will prompt to confirm exiting the installation: - - User Confirmation Requested - Are you sure you wish to exit? The system will reboot. - - [ Yes ] No - - Select &gui.yes;. If booting from the CDROM drive, the - following message will remind you to remove the disk: - - 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 quickly be removed from the drive. - Press &gui.ok; to reboot. - - The system will reboot so watch for any error messages - that may appear, see for more - details. - - - - - Configure Additional Network Services - - - TomRhodesContributed - by - - - - Configuring network services can be a daunting task for - users that lack previous knowledge in this area. Since - networking and the Internet are critical to all modern - operating systems, it is useful to have some understanding of - &os;'s extensive networking capabilities. - - Network services are programs that accept input from - anywhere on the network. Since there have been cases where - bugs in network services have been exploited by attackers, it - is important to only enable needed network services. If in - doubt, do not enable a network service until it is needed. - Services can be enabled with &man.sysinstall.8; or by editing - /etc/rc.conf. - - Selecting the Networking option will - display a menu similar to the one below: - -
- Network Configuration Upper-level - - - - - - -
- - The first option, Interfaces, - is covered in . - - Selecting the AMD option adds - support for &man.amd.8;. This is usually used in conjunction - with NFS for automatically mounting remote - filesystems. - - Next is the AMD Flags option. - When selected, a menu will pop up where specific - AMD flags can be entered. The menu already - contains a set of default options: - - -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map - - sets the default mount location which - is specified here as /.amd_mnt. - specifies the default - log; however, when &man.syslogd.8; is - used, all log activity will be sent to the system log daemon. - /host is used to mount an exported file - system from a remote host, while /net - is used to mount an exported filesystem from an - IP address. The default options for - AMD exports are defined in - /etc/amd.map. - - - FTP - anonymous - - - The Anon FTP option permits - anonymous FTP connections. Select this - option to make this machine an anonymous - FTP server. Be aware of the security risks - involved with this option. Another menu will be displayed to - explain the security risks and configuration in depth. - - The Gateway menu will configure - the machine to be a gateway. This menu can also be used to - unset the Gateway option if it was - accidentally selected during installation. - - The Inetd option can be used to - configure or completely disable &man.inetd.8;. - - The Mail option is used to - configure the system's default Mail Transfer Agent - (MTA). Selecting this option will bring up - the following menu: - -
- Select a Default MTA - - - - - - -
- - This menu offers a choice as to which - MTA to install and set as the default. An - MTA is a mail server which delivers email - to users on the system or the Internet. - - Select Sendmail to install - Sendmail as the default - MTA. Select Sendmail - local to set - Sendmail as the default - MTA, but disable its ability to receive - incoming email from the Internet. The other options, - Postfix and - Exim, provide alternatives to - Sendmail. - - The next menu after the MTA menu is - NFS client. This menu is used to - configure the system to communicate with a - NFS server which in turn is used to - make filesystems available to other machines on the network - over the NFS protocol. See for more information about client - and server configuration. - - Below that option is the NFS - server option, for setting the system up as an - NFS server. This adds the required - information to start up the Remote Procedure Call - RPC services. RPC is - used to coordinate connections between hosts and - programs. - - Next in line is the Ntpdate - option, which deals with time synchronization. When selected, - a menu like the one below shows up: - -
- Ntpdate Configuration - - - - - - -
- - From this menu, select the server which is geographically - closest. This will make the time synchronization more - accurate as a farther server may have more connection - latency. - - The next option is the PCNFSD - selection. This option will install the - net/pcnfsd package from the Ports - Collection. This is a useful utility which provides - NFS authentication services for systems - which are unable to provide their own, such as Microsoft's - &ms-dos; operating system. - - Now, scroll down a bit to see the other options: - -
- Network Configuration Lower-level - - - - - - -
- - RPC communication between - NFS servers and clients is managed by - &man.rpcbind.8; which is required for NFS - servers to operate correctly. Status monitoring is provided - by &man.rpc.statd.8; and the reported status is usually held - in /var/db/statd.status. The next option - is for &man.rpc.lockd.8; which provides file locking - services. This is usually used with &man.rpc.statd.8; to - monitor which hosts are requesting locks and how frequently - they request them. While these last two options are useful - for debugging, they are not required for - NFS servers and clients to operate - correctly. - - The next menu, Routed, - configures the routing daemon. &man.routed.8;, manages - network routing tables, discovers multicast routers, and - supplies a copy of the routing tables to any physically - connected host on the network upon request. This is mainly - used for machines which act as a gateway for the local - network. If selected, a menu will request the default - location of the utility. To accept the default location, - press Enter. Yet another menu will ask for - the flags to pass to &man.routed.8;. The default of - should appear on the screen. - - The next menu, Rwhod, starts - &man.rwhod.8; during system initialization. This utility - broadcasts system messages across the network periodically, or - collects them when in consumer mode. More - information can be found in &man.ruptime.1; and - &man.rwho.1;. - - The next to last option in the list is for &man.sshd.8;, - the secure shell server for - OpenSSH. It is highly recommended - over the standard &man.telnetd.8; and &man.ftpd.8; servers as - it is used to create a secure, encrypted connection from one - host to another. - - The final option is TCP - Extensions which are defined in - RFC 1323 and - RFC 1644. While on many hosts this - can speed up connections, it can also cause some connections - to be dropped. It is not recommended for servers, but may be - beneficial for stand alone machines. - - Once the network services are configured, scroll up to the - very top item which is X Exit and - continue on to the next configuration item or simply exit - &man.sysinstall.8; by selecting X - Exit twice then [X - Exit Install]. - - - - &os; Bootup - - - &os;/&arch.i386; Bootup - - If everything went well, messages will scroll along the - screen and a login prompt will appear. To view these - messages, press Scroll-Lock then use - PgUp and PgDn. Press - Scroll-Lock again to return to the - prompt. - - All of the messages may not display due to buffer - limitations, but they can be read after logging using - &man.dmesg.8;. - - Login using the username and password which were set - during installation. Avoid logging in as root except when - necessary. - - Typical boot messages (version information - omitted): - - 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. - -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 -avail memory = 256311296 (250304K bytes) -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 -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 -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 -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 -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 -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 -/dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation) -/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: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation) -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 -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 -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: -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 -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: -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 -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:. - -FreeBSD/i386 (k6-2.example.com) (ttyv0) - -login: rpratt -Password: - - Generating the RSA and DSA keys may take some time on - slower machines. This happens only on the initial boot-up - of a new installation. Subsequent boots will be - faster. - - If &xorg; has been configured - and a default desktop chosen, it can be started by typing - startx at the command line. - - - - - &os; Shutdown - - It is important to properly shutdown the operating system. - Do not just turn off the power. First, become the superuser - using &man.su.1; and entering the root password. This will work - only if the user is a member of wheel. Otherwise, login as - root. To shutdown - the system, type shutdown -h now. - - The operating system has halted. -Please press any key to reboot. - - It is safe to turn off the power after the shutdown - command has been issued and the message Please press - any key to reboot appears. If any key is pressed - instead of turning off the power switch, the system will - reboot. - - The - Ctrl - Alt - Del - key combination can also be used to reboot the - system; however, this is not recommended. - - - - - Troubleshooting - - - installation - troubleshooting - - This section covers basic installation troubleshooting of - common problems. There are also a few questions and answers for - people wishing to dual-boot &os; with &windows;. - - - If Something Goes Wrong - - Due to various limitations of the PC architecture, it is - impossible for device probing to be 100% reliable. However, - there are a few things to try if it fails. - - Check the Hardware - Notes document for the version of &os; to make sure - the hardware is supported. - - If the hardware is supported but still experiences - lock-ups or other problems, build a custom kernel to add in - support for devices which are not present in the - GENERIC kernel. The default kernel - assumes that most hardware devices are in their factory - default configuration in terms of IRQs, I/O addresses, and - DMA channels. If the hardware has been reconfigured, create a - custom kernel configuration file and recompile to tell &os; - where to find things. - - 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. - - - Some installation problems can be avoided or alleviated - by updating the firmware on various hardware components, - most notably the motherboard BIOS. Most - motherboard and computer manufacturers have a website where - upgrade information may be located. - - Most manufacturers strongly advise against upgrading the - motherboard BIOS unless there is a good - reason for doing so, such as a critical update. The upgrade - process can go wrong, causing permanent - damage to the BIOS chip. - - - - - Using &windows; Filesystems - - At this time, &os; does not support file systems - compressed with the - Double Space™ application. - Therefore the file system will need to be uncompressed before - &os; can access the data. This can be done by running the - Compression Agent located in the - Start> - Programs > - System Tools menu. - - &os; can support &ms-dos; file systems (sometimes called - FAT file systems). The &man.mount.msdosfs.8; command grafts - such file systems onto the existing directory hierarchy, - allowing the file system's contents to be accessed. The - &man.mount.msdosfs.8; program is not usually invoked directly; - instead, it is called by the system through a line in - /etc/fstab or by using &man.mount.8; with - the appropriate parameters. - - A typical line in /etc/fstab - is: - - /dev/ad0sN /dos msdosfs rw 0 0 - - - /dos must already exist for this to - work. For details about the format of - /etc/fstab, see &man.fstab.5;. - - - A typical call to &man.mount.8; for a FAT filesystem looks - like: - - &prompt.root; mount -t msdosfs /dev/ad0s1 /mnt - - In this example, the FAT filesystem is located on the - first partition of the primary hard disk. The output from - &man.dmesg.8; and &man.mount.8; should produce enough - information to give an idea of the partition layout. - - - &os; may number FAT partitions differently than other - operating systems. In particular, extended partitions are - usually given higher slice numbers than primary partitions. - Use &man.fdisk.8; to help determine which slices belong to - &os; and which belong to other operating systems. - - - - - Troubleshooting Questions and Answers - - - - - My system hangs while probing hardware during boot - or it behaves strangely during install. - - - &os; makes extensive use of the system ACPI service - on the i386, amd64, and ia64 platforms to aid in system - configuration if it is detected during boot. - Unfortunately, some bugs still exist in the ACPI driver - and various system motherboards. The use of ACPI can be - disabled by setting - hint.acpi.0.disabled in the third - stage boot loader: - - 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 - /boot/loader.conf to make this - change permanent. More information about the boot - loader can be found in . - - - - - When booting from the hard disk for the first time - after installing &os;, the kernel loads and probes - hardware, but stops with messages like: - - changing root device to ad1s1a panic: cannot mount root - - What is wrong? - - - This can occur when the boot disk is not the first - disk in the system. The BIOS uses a different numbering - scheme to &os;, and working out which numbers correspond - to which is difficult to get right. - - If this occurs, tell &os; where the root filesystem - is by specifying the BIOS disk number, the disk type, - and the &os; disk number for that type. - - Consider two IDE disks, each configured as the - master on their respective IDE bus, where &os; should be - booted from the second disk. The BIOS sees these as - disk 0 and disk 1, while &os; sees them as - ad0 and - ad2. - - If &os; is on BIOS disk 1, of type - ad and the &os; disk number is 2, - this is the correct value: - - 1:ad(2,a)kernel - - Note that if there is 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 there are one or more IDE disks in the system. - In this case, the &os; disk number is lower than the - BIOS disk number. For two IDE disks and a SCSI disk, - where the SCSI disk is BIOS disk 2, type - da, and &os; disk number 0, the - correct value is: - - 2:da(0,a)kernel - - This tells &os; to boot from BIOS disk 2, which is - the first SCSI disk in the system. If there is only IDE - disk, use 1: instead. - - Once the correct value to use is determined, put the - command in /boot.config using a - text editor. Unless instructed otherwise, &os; will use - the contents of this file as the default response to the - boot: prompt. - - - - - When booting from the hard disk for the first time - after installing &os;, the Boot Manager prompt just - prints F? at the boot menu and the - boot will not go any further. - - - The hard disk geometry was set incorrectly in the - partition editor when &os; was installed. Go back into - the partition editor and specify the actual geometry of - the hard disk. &os; must be reinstalled again from the - beginning with the correct geometry. - - For a dedicated &os; system that does not need - future compatibility with another operating system, use - the entire disk by selecting - A in the installer's - partition editor. - - - - - The system finds the &man.ed.4; network card but - continuously displays device timeout errors. - - - The card is probably on a different IRQ from what - is specified in - /boot/device.hints. The - &man.ed.4; driver does not use software configuration by - default, but it will if -1 is - specified in the hints for the interface. - - Either move the jumper on the card to the - configuration setting or specify the IRQ as - -1 by setting the hint - hint.ed.0.irq="-1". This tells the - kernel to use the software configuration. - - Another possibility is that the card is at IRQ 9, - which is shared by IRQ 2 and frequently a cause of - problems, especially if a VGA card is using IRQ 2. Do - not use IRQ 2 or 9 if at all possible. - - - - - - - When &man.sysinstall.8; is usedin an - &xorg; terminal, the yellow - font is difficult to read against the light gray - background. Is there a way to provide higher - contrastcolor - contrast for this - application? - - - If the default colors chosen by &man.sysinstall.8; - make text illegible while using - x11/xterm or - x11/rxvt, add the following to - ~/.Xdefaults to get a darker - background gray: XTerm*color7: - #c0c0c0 - - - - - - - - - Advanced Installation Guide - - - ValentinoVaschettoContributed - by - - - - - MarcFonvieilleUpdated - by - - - - This section describes how to install &os; in exceptional - cases. - - - Installing &os; on a System Without a Monitor or - Keyboard - - - installation - headless (serial console) - - serial console - This type of installation is called a headless - install because the machine to be installed does not - have either an attached monitor or a VGA output. This type of - installation is possible using a serial console, another - machine which acts as the main display and keyboard. To do - this, follow the steps to create an installation USB stick, - explained in , or download - the correct installation ISO image as described in . - - To modify the installation media to boot into a serial - console, follow these steps. If using a CD/DVD media, skip - the first step): - - - - Enabling the Installation USB Stick to Boot into a - Serial Console - - - &man.mount.8; - - By default, booting into the USB stick boots into the - installer. To instead boot into a serial console, mount - the USB disk onto a &os; system using - &man.mount.8;: - - &prompt.root; mount /dev/da0a /mnt - - - Adapt the device node and the mount point to the - situation. - - - Once the USB stick is mounted, set it to boot into a - serial console. Add this line to - /boot/loader.conf on the USB - stick: - - &prompt.root; echo 'console="comconsole"' >> /mnt/boot/loader.conf - - Now that the USB is stick configured correctly, - unmount the disk using &man.umount.8;: - - &prompt.root; umount /mnt - - Now, unplug the USB stick and jump directly to the - third step of this procedure. - - - - Enabling the Installation CD/DVD to Boot into a - Serial Console - - - &man.mount.8; - - By default, when booting into the installation CD/DVD, - &os; boots into its normal install mode. To instead boot - into a serial console, extract, modify, and regenerate the - ISO image before burning it to the CD/DVD media. - - From the &os; system with the saved installation ISO - image, use &man.tar.1; to extract all the files: - - &prompt.root; mkdir /path/to/headless-iso -&prompt.root; tar -C /path/to/headless-iso -pxvf &os;-&rel.current;-RELEASE-i386-disc1.iso - - Next, set the installation media to boot into a - serial console. Add this line to the - /boot/loader.conf of the extracted - ISO image: - - &prompt.root; echo 'console="comconsole"' >> /path/to/headless-iso/boot/loader.conf - - Then, create a new ISO image from the modified tree. - This example uses &man.mkisofs.8; from the - sysutils/cdrtools package or - port: - - &prompt.root; mkisofs -v -b boot/cdboot -no-emul-boot -r -J -V "Headless_install" \ - -o Headless-&os;-&rel2.current;-RELEASE-i386-disc1.iso /path/to/headless-iso - - Now that the ISO image is configured correctly, burn - it to a CD/DVD media using a burning application. - - - - Connecting the Null-modem Cable - - null-modem cable - Connect a null-modem cable to - the serial ports of the two machines. A - normal serial cable will not work. A - null-modem cable is required. - - - - Booting Up for the Install - - It is now time to go ahead and start the install. - Plug in the USB stick or insert the CD/DVD media in the - headless install machine and power it on. - - - - Connecting to the Headless Machine - - - &man.cu.1; - - - Next, connect to that machine with &man.cu.1;: - - &prompt.root; cu -l /dev/cuau0 - - - - - The headless machine can now be controlled using - &man.cu.1;. It will load the kernel and then display a - selection of which type of terminal to use. Select the &os; - color console and proceed with the installation. - - - - - - Preparing Custom Installation Media - - Some situations may require a customized &os; installation - media and/or source. This might be physical media or a source - that &man.sysinstall.8; can use to retrieve the installation - files. Some example situations include: - - - - A local network with many machines has a private FTP - server hosting the &os; installation files which the - machines should use for installation. - - - - &os; does not recognize the CD/DVD drive but &windows; - does. In this case, copy the &os; installation files to a - &windows; partition on the same computer, and then install - &os; using those files. - - - - The computer to install does not have a CD/DVD drive or - a network card, but can be connected using a null-printer - cable to a computer that does. - - - - A tape will be used to install &os;. - - - - - Creating an Installation ISO - - As part of each release, the &os; Project provides ISO - images for each supported architecture. These images can be - written (burned) to CD or DVD media using a - burning application, and then used to install &os;. If a - CD/DVD writer is available, this is the easiest way to install - &os;. - - - - 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 - version as appropriate. - - An image directory normally contains the following - images: - - - &os; - ISO Image Names and Meanings - - - - - Filename - - Contents - - - - - - &os;-version-RELEASE-arch-bootonly.iso - - This CD image starts the installation process - by booting from a CD-ROM drive but it does not - contain the support for installing &os; from the - CD itself. Perform a network based install, such - as from an FTP server, after booting from this - CD. - - - - &os;-version-RELEASE-arch-dvd1.iso.gz - - This DVD image contains everything necessary - to install the base &os; operating system, a - collection of pre-built packages, and the - documentation. It also supports booting into a - livefs based rescue mode. - - - - &os;-version-RELEASE-arch-memstick.img - - This image can be written to a USB memory - stick in order to install machines capable of - booting from USB drives. It also supports booting - into a livefs based rescue mode. - The only included package is the documentation - package. - - - - &os;-version-RELEASE-arch-disc1.iso - - This image can be written to a USB memory - stick in order to install machines capable of - booting from USB drives. Similar to the - bootonly.iso image, it does - not contain the distribution sets on the medium - itself, but does support network-based - installations (for example, via ftp). - - - - &os;-version-RELEASE-arch-disc1.iso - - This CD image contains the base &os; - operating system and the documentation package 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; 9.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; 9.X. - - - - &os;-version-RELEASE-arch-livefs.iso - - This CD image contains support for booting - into a livefs based rescue mode but - does not support doing an install from the CD - itself. - - - -
- - When performing a CD installation, download either - the bootonly ISO image or - disc1. Do not download both, since - disc1 contains everything that the - bootonly ISO image contains. - - Use the bootonly ISO to perform a - network install over the Internet. Additional software - can be installed as needed using the Ports Collection as - described in . - - Use dvd1 to install &os; and a - selection of third-party packages from the disc. - - - - Burn the Media - - Next, write the downloaded image(s) to disc. If using - another &os; system, refer to - for instructions. - - If using another platform, use any burning utility - that exists for that platform. The images are in the - standard ISO format which most CD writing applications - support. - - - - To build a customized release of &os;, refer to the - Release Engineering - Article. - - - - Creating a Local FTP Site with a &os; Disc - - - installation - network - FTP - - - &os; discs are laid out in the same way as the FTP site. - This makes it easy to create a local FTP site that can be used - by other machines on a network to install &os;. - - - - On the &os; computer that will host the FTP site, - ensure that the CD/DVD is in the drive and mounted: - - &prompt.root; mount /cdrom - - - - Create an account for anonymous FTP. Use &man.vipw.8; - to insert this line: - - ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent - - - - Ensure that the FTP service is enabled in - /etc/inetd.conf. - - - - Anyone with network connectivity to the machine can now - chose a media type of FTP and type in - ftp://your - machine after picking - Other in the FTP sites menu during the - install. - - - If the boot media for the FTP clients is not precisely - the same version as that provided by the local FTP site, - &man.sysinstall.8; will not complete the installation. To - override this, go into the Options menu - and change the distribution name to - any. - - - - This approach is acceptable for a machine on the local - network which is protected by a firewall. Offering - anonymous FTP services to other machines over the Internet - exposes the computer to increased security risks. It is - strongly recommended to follow good security practices when - providing services over the Internet. - - - - - Installing from an &windows; Partition - - - installation - from &windows; - - To prepare for an installation from a &windows; partition, - copy the files from the distribution into a directory in the - root directory of the partition, such as - c:\freebsd. Since the directory - structure must be reproduced, it is recommended to use - robocopy when copying from a CD/DVD. For - example, to prepare for a minimal installation of &os;: - - C:\> md c:\freebsd -C:\> robocopy e:\bin c:\freebsd\bin\ /s -C:\> robocopy e:\manpages c:\freebsd\manpages\ /s - - This example assumes that C: has - enough free space and E: is where the - CD/DVD is mounted. - - Alternatively, download the distribution from ftp.FreeBSD.org. - Each distribution is in its own directory; for example, the - base distribution can be found in the - &rel2.current;/base/ - directory. - - Copy the distributions to install from a &windows; - partition to c:\freebsd. Both the - base and kernel - distributions are needed for the most minimal - installation. - - - - Before Installing over a Network - - - installation - network - serial (PPP) - - - installation - network - parallel (PLIP) - - - installation - network - Ethernet - - There are three types of network installations - available: Ethernet, PPP, and PLIP. - - For the fastest possible network installation, use an - Ethernet adapter. &os; supports most common Ethernet cards. - A list of supported cards is provided in the Hardware Notes - for each release of &os;. If using a supported PCMCIA - Ethernet card, be sure that it is plugged in - before the system is powered on as &os; - does not support hot insertion of PCMCIA cards during - installation. - - Make note of the system's IP address, subnet mask, - hostname, default gateway address, and DNS server addresses if - these values are statically assigned. If installing by FTP - through a HTTP proxy, make note of the proxy's address. If - you do not know these values, ask the system administrator or - ISP before trying this type of - installation. - - If using a dialup modem, have the service provider's PPP - information handy as it is needed early in the installation - process. - - If PAP or CHAP are used to connect to the - ISP without using a script, type - dial at the &os; - ppp prompt. Otherwise, know how to - dial the ISP using the AT - commands specific to the modem, as the PPP dialer - provides only a simple terminal emulator. Refer to and &url.books.faq;/ppp.html - for further information. Logging can be directed to the - screen using set log local .... - - If a hard-wired connection to another &os; machine is - available, the installation can occur over a null-modem - parallel port cable. The data rate over the parallel port is - higher than what is typically possible over a serial - line. - - - Before Installing via <acronym>NFS</acronym> - - - installation - network - NFS - - To perform an NFS installation, copy - the needed &os; distribution files to an - NFS server and then point the installer's - NFS media selection to it. - - If the server supports only a privileged - port, set the option NFS Secure - in the Options menu so that the - installation can proceed. - - If using a poor quality Ethernet card which suffers - from slow transfer rates, toggle the - NFS Slow flag to on. - - In order for an NFS installation to - work, the server must support subdir mounts. For example, - if the &os; &rel.current; distribution lives on: - ziggy:/usr/archive/stuff/FreeBSD, - ziggy will have to allow the direct - mounting of /usr/archive/stuff/FreeBSD, - not just /usr or - /usr/archive/stuff. - - In &os;, this is controlled by using - in - /etc/exports. Other - NFS servers may have different - conventions. If the server is displaying - permission denied messages, it is - likely that this is not enabled properly. - - - - Property changes on: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Deleted: svn:mime-type ## -1 +0,0 ## -text/sgml \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/disk-layout.kil =================================================================== Binary files head/en_US.ISO8859-1/books/handbook/install/disk-layout.kil (revision 47278) and head/en_US.ISO8859-1/books/handbook/install/disk-layout.kil (nonexistent) differ Property changes on: head/en_US.ISO8859-1/books/handbook/install/disk-layout.kil ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/example-dir1.dot =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/example-dir1.dot (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/example-dir1.dot (nonexistent) @@ -1,7 +0,0 @@ -// $FreeBSD$ - -digraph directory { - root [label="Root\n/"]; - root -> "A1/"; - root -> "A2/"; -} Property changes on: head/en_US.ISO8859-1/books/handbook/install/example-dir1.dot ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/example-dir2.dot =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/example-dir2.dot (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/example-dir2.dot (nonexistent) @@ -1,8 +0,0 @@ -// $FreeBSD$ - -digraph directory { - root [label="Root\n/"]; - root -> "A1/" -> "B1/"; - "A1/" -> "B2/"; - root -> "A2/"; -} Property changes on: head/en_US.ISO8859-1/books/handbook/install/example-dir2.dot ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/example-dir3.dot =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/example-dir3.dot (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/example-dir3.dot (nonexistent) @@ -1,8 +0,0 @@ -// $FreeBSD$ - -digraph directory { - root [label="Root\n/"]; - root -> "A1/"; - root -> "A2/" -> "B1/"; - "A2/" -> "B2/"; -} Property changes on: head/en_US.ISO8859-1/books/handbook/install/example-dir3.dot ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/example-dir4.dot =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/example-dir4.dot (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/example-dir4.dot (nonexistent) @@ -1,9 +0,0 @@ -// $FreeBSD$ - -digraph directory { - root [label="Root\n/"]; - root -> "A1/"; - root -> "A2/" -> "B1/" -> "C1/"; - "B1/" -> "C2/"; - "A2/" -> "B2/"; -} Property changes on: head/en_US.ISO8859-1/books/handbook/install/example-dir4.dot ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/example-dir5.dot =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/example-dir5.dot (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/example-dir5.dot (nonexistent) @@ -1,9 +0,0 @@ -// $FreeBSD$ - -digraph directory { - root [label="Root\n/"]; - root -> "A1/" -> "C1/"; - "A1/" -> "C2/"; - root -> "A2/" -> "B1/"; - "A2/" -> "B2/"; -} Property changes on: head/en_US.ISO8859-1/books/handbook/install/example-dir5.dot ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/books/handbook/install/Makefile =================================================================== --- head/en_US.ISO8859-1/books/handbook/install/Makefile (revision 47278) +++ head/en_US.ISO8859-1/books/handbook/install/Makefile (nonexistent) @@ -1,15 +0,0 @@ -# -# Build the Handbook with just the content from this chapter. -# -# $FreeBSD$ -# - -CHAPTERS= install/chapter.xml - -VPATH= .. - -MASTERDOC= ${.CURDIR}/../${DOC}.${DOCBOOKSUFFIX} - -DOC_PREFIX?= ${.CURDIR}/../../../.. - -.include "../Makefile" Property changes on: head/en_US.ISO8859-1/books/handbook/install/Makefile ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property