diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index 389b5b4b24..468ab239c5 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -1,3505 +1,3505 @@ Jim Mock Restructured, reorganized, and parts rewritten by Installing FreeBSD Synopsis installation The following chapter will attempt to guide you through the installation of FreeBSD on your system. It can be installed through a variety of methods, including anonymous FTP (assuming you have network connectivity via modem or local network), CDROM, floppy disk, tape, an MS-DOS partition, or even NFS. No matter which method you choose, you will need to get started by creating the installation disks as described in the next section. Booting into the FreeBSD installer, even if you are not planning on installing FreeBSD right away, will provide important information about compatibility with your hardware. This information may dictate which installation options are even possible for you. It can also provide clues early-on in the process to potential problems you may come across later. installation network anonymous FTP If you plan to install FreeBSD via anonymous FTP, the only things you will need are the installation floppies. The installation program itself will handle anything else that is required. For more information about obtaining FreeBSD, see the Obtaining FreeBSD section of the Appendix. By now, you are probably wondering what exactly it is you need to do. Continue on to the installation guide. Preparing for Installation The following sections will guide you through preparing for and actually installing FreeBSD. If you find something missing, please let us know about it by sending email to the &a.doc;. Preparing for the Installation There are various things you should do in preparation for the installation. The following describes what needs to be done prior to each type of installation. The first thing to do is to make sure your hardware is supported by FreeBSD. The Hardware Notes document for your release of FreeBSD (which is usually named HARDWARE.TXT) should come in handy here. It would also be a good idea to make a list of any special cards you have installed, such as SCSI controllers, Ethernet cards, sound cards, etc.. The list should include their IRQs and IO port addresses. Creating the Installation Floppies installation boot floppies installation CDROM You may need to prepare some floppy disks. These disks will be used to boot your computer in to the FreeBSD install process. This step is not necessary if you are installing from CDROM, and your computer supports booting from the CDROM. If you do not meet these requirements then you will need to create some floppies to boot from. If you are not sure whether your computer can boot from the CDROM it does not hurt to try. Just insert the CDROM as normal and restart your computer. You might need to adjust some options in your BIOS so that your computer will try and boot from the CDROM drive before the hard disk. Even if you have the CDROM it might make sense for you to download the files. There have been occasions where bugs in the FreeBSD installer have been discovered after the CDs have been released. When this happens the copies of the images on the FTP site will be fixed as soon as possible. Obviously, it is not possible to update the CDs after they have been pressed. Acquire the Boot Floppy Images These are files with a .flp extension. If you have a CDROM release of FreeBSD then you will find the files in the floppies subdirectory. Alternatively, you can download the images from the floppies directory of the FreeBSD FTP site or your local mirror. The names of the files you will need varies between FreeBSD releases (sometimes) and the architecture you will be installing on. The installation boot image information on the FTP site provides up-to-the-minute information about the specific files you will need. Prepare the Floppy Disks You must prepare one floppy disk per image file you had to download. It is imperative that these disks are free from defects. The easiest way to test this is to format the disks for yourself. Do not trust pre-formatted floppies. If you try to install FreeBSD and the installation program crashes, freezes, or otherwise misbehaves one of the first things to suspect is the floppies. Try writing the floppy image files to some other disks, and try again. Write the Image Files to the Floppy Disks. The image files, such as kern.flp, are not regular files you copy to the disk. Instead, they are images of the complete contents of the disk. This means that you can not use commands like DOS' copy to write the files. Instead, you must use specific tools to write the images directly to the disk. DOS If you are creating the floppies on a computer running DOS then we provide a tool to do this called fdimage. If you are using the floppies from the CDROM, and your CDROM is the E: drive then you would run this: E:\> tools\fdimage floppies\kern.flp A: Repeat this command for each .flp file, replacing the floppy disk each time. Adjust the command line as necessary, depending on where you have placed the .flp files. If you do not have the CDROM then fdimage can be downloaded from the tools directory on the FreeBSD FTP site. If you are writing the floppies on a Unix system (such as another FreeBSD system) you can use the &man.dd.1; command to write the image files directly to disk. On FreeBSD you would run: &prompt.root; dd if=kern.flp of=/dev/fd0 On FreeBSD /dev/fd0 refers to the first floppy disk (the A: drive). /dev/fd1 would be the B: drive, and so on. Other Unix variants might have different names for the floppy disk devices, and you will need to check the documentation for the system as necessary. Before Installing from CDROM If your CDROM is of an unsupported type, please skip ahead to the MS-DOS Preparation section. There is not a whole lot of preparation needed if you are installing from a FreeBSD CDROM. You can either boot into the CD installation directly from DOS using the install.bat or you can make floppies with the makeflp.bat command. If the CD has El Torito boot support and your system supports booting directly from the CDROM drive (many older systems do NOT), simply insert the first CD of the set into the drive and reboot your system. You will be put into the installation menu directly from the CD. DOS If you are installing from an MS-DOS partition and have the proper drivers to access your CD, run the install.bat script provided on the CDROM. This will attempt to boot the FreeBSD installation directly from DOS. You must do this from actual DOS (i.e., boot in DOS mode) and not from a DOS window under Windows. For the easiest interface of all (from DOS), type view. This will bring up a DOS menu utility that leads you through all of the available options. Unix If you are creating the boot floppies from a Unix machine, see the Creating the Boot Floppies section of this guide for examples. Once you have booted from DOS or floppy, you should then be able to select CDROM as the media type during the install process and load the entire distribution from CDROM. No other types of installation media should be required. After your system is fully installed and you have rebooted (from the hard disk), you can mount the CDROM at any time by typing: &prompt.root; mount /cdrom Before removing the CD from the drive again, you must first unmount it. This is done with the following command: &prompt.root; umount /cdrom Do not just remove it from the drive! Before invoking the installation, be sure that the CDROM is in the drive so that the install probe can find it. This is also true if you wish the CDROM to be added to the default system configuration automatically during the installation (whether or not you actually use it as the installation media). installation network FTP Finally, if you would like people to be able to FTP install FreeBSD directly from the CDROM in your machine, you will find it quite easy. After the machine is fully installed, you simply need to add the following line to the password file (using the vipw command): ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Anyone with network connectivity to your 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 you choose to enable anonymous FTP during the installation of your system, the installation program will do the above for you. Before Installing from Floppies installation floppies If you must install from floppy disk (which we suggest you do NOT do), either due to unsupported hardware or simply because you insist on doing things the hard way, you must first prepare some floppies for the installation. At a minimum, you will need as many 1.44MB or 1.2MB floppies as it takes to hold all the files in the bin (binary distribution) directory. If you are preparing the floppies from DOS, then they MUST be formatted using the MS-DOS FORMAT command. If you are using Windows, use Explorer to format the disks (right-click on the A: drive, and select "Format". Do NOT trust factory pre-formatted floppies! Format them again yourself, just to be sure. Many problems reported by our users in the past have resulted from the use of improperly formatted media, which is why we are making a point of it now. If you are creating the floppies on another FreeBSD machine, a format is still not a bad idea, though you do not need to put a DOS filesystem on each floppy. You can use the disklabel and newfs commands to put a UFS filesystem on them instead, as the following sequence of commands (for a 3.5" 1.44MB floppy) illustrates: &prompt.root; fdformat -f 1440 fd0.1440 &prompt.root; disklabel -w -r fd0.1440 floppy3 &prompt.root; newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0 Use fd0.1200 and floppy5 for 5.25" 1.2MB disks. Then you can mount and write to them like any other filesystem. After you have formatted the floppies, you will need to copy the files to them. The distribution files are split into chunks conveniently sized so that 5 of them will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many files as will fit on each one, until you have all of the distributions you want packed up in this fashion. Each distribution should go into a subdirectory on the floppy, e.g.: a:\bin\bin.aa, a:\bin\bin.ab, and so on. Once you come to the Media screen during the install process, select Floppy and you will be prompted for the rest. Before Installing from MS-DOS installation from MS-DOS To prepare for an installation from an MS-DOS partition, copy the files from the distribution into a directory named, for example, c:\FreeBSD. The directory structure of the CDROM or FTP site must be partially reproduced within this directory, so we suggest using the DOS xcopy command if you are copying it from a CD. For example, to prepare for a minimal installation of FreeBSD: C:\> md c:\FreeBSD C:\> xcopy e:\bin c:\FreeBSD\bin\ /s C:\> xcopy e:\manpages c:\FreeBSD\manpages\ /s Assuming that C: is where you have free space and E: is where your CDROM is mounted. If you do not have a CDROM drive, you can download the distribution from ftp.FreeBSD.org. Each distribution is in its own directory; for example, the bin distribution can be found in the &rel.current;/bin directory. For as many distributions you wish to install from an MS-DOS partition (and you have the free space for), install each one under c:\FreeBSD — the BIN distribution is the only one required for a minimum installation. Before Installing from QIC/SCSI Tape installation from QIC/SCSI Tape Installing from tape is probably the easiest method, short of an online FTP install or CDROM install. The installation program expects the files to be simply tarred onto the tape, so after getting all of the distribution files you are interested in, simply tar them onto the tape like so: &prompt.root; cd /freebsd/distdir &prompt.root; tar cvf /dev/rwt0 dist1 ... dist2 When you go to do the installation, you should also make sure that you leave enough room in some temporary directory (which you will be allowed to choose) to accommodate the full contents of the tape you have created. Due to the non-random access nature of tapes, this method of installation requires quite a bit of temporary storage. You should expect to require as much temporary storage as you have stuff written on tape. When starting the installation, the tape must be in the drive before booting from the boot floppy. The installation probe may otherwise fail to find it. Before Installing over a Network installation network serial (SLIP or PPP) installation network parallel (PLIP) installation network Ethernet There are three types of network installations you can do. Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)), or Ethernet (a standard Ethernet controller (includes some PCMCIA)). The SLIP support is rather primitive, and limited primarily to hard-wired links, such as a serial cable running between a laptop computer and another computer. The link should be hard-wired as the SLIP installation does not currently offer a dialing capability; that facility is provided with the PPP utility, which should be used in preference to SLIP whenever possible. If you are using a modem, then PPP is almost certainly your only choice. Make sure that you have your service provider's information handy as you will need to know it fairly early in the installation process. If you use PAP or CHAP to connect your ISP (in other words, if you can connect to the ISP in Windows without using a script), then all you will need to do is type in dial at the ppp prompt. Otherwise, you will need to know how to dial your ISP using the AT commands specific to your modem, as the PPP dialer provides only a very simple terminal emulator. Please refer to the user-ppp handbook and FAQ entries for further information. If you have problems, logging can be directed to the screen using the command set log local .... If a hard-wired connection to another FreeBSD (2.0-R or later) machine is available, you might also consider installing over a laplink parallel port cable. The data rate over the parallel port is much higher than what is typically possible over a serial line (up to 50kbytes/sec), thus resulting in a quicker installation. Finally, for the fastest possible network installation, an Ethernet adapter is always a good choice! FreeBSD supports most common PC Ethernet cards; a table of supported cards (and their required settings) is provided in the Hardware Notes for each release of FreeBSD. If you are using one of the supported PCMCIA Ethernet cards, also be sure that it is plugged in before the laptop is powered on! FreeBSD does not, unfortunately, currently support hot insertion of PCMCIA cards during installation. You will also need to know your IP address on the network, the netmask value for your address class, and the name of your machine. If you are installing over a PPP connection and do not have a static IP, fear not, the IP address can be dynamically assigned by your ISP. Your system administrator can tell you which values to use for your particular network setup. If you will be referring to other hosts by name rather than IP address, you will also need a name server and possibly the address of a gateway (if you are using PPP, it is your provider's IP address) to use in talking to it. If you want to install by FTP via a HTTP proxy (see below), you will also need the proxy's address. If you do not know the answers to all or most of these questions, then you should really probably talk to your system administrator or ISP before trying this type of installation. Before Installing via NFS installation network NFS The NFS installation is fairly straight-forward. Simply copy the FreeBSD distribution files you want onto a server somewhere and then point the NFS media selection at it. If this server supports only privileged port (as is generally the default for Sun workstations), you will need to set this option in the Options menu before installation can proceed. If you have a poor quality Ethernet card which suffers from very slow transfer rates, you may also wish to toggle the appropriate Options flag. In order for NFS installation to work, the server must support subdir mounts, e.g., if your FreeBSD 3.4 distribution directory lives on:ziggy:/usr/archive/stuff/FreeBSD, then ziggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. In FreeBSD's /etc/exports file, this is controlled by the . Other NFS servers may have different conventions. If you are getting permission denied messages from the server, then it is likely that you do not have this enabled properly. Before Installing via FTP installation network FTP FTP installation may be done from any FreeBSD mirror site containing a reasonably up-to-date version of FreeBSD. A full list of FTP mirrors located all over the world is provided during the install process. If you are installing from an FTP site not listed in this menu, or are having trouble getting your name server configured properly, you can also specify a URL to use by selecting the choice labeled Other in that menu. You can also use the IP address of a machine you wish to install from, so the following would work in the absence of a name server: ftp://209.55.82.20/pub/FreeBSD/&rel.current;-RELEASE There are three FTP installation modes you can choose from: active or passive FTP or via a HTTP proxy. FTP Active This option will make all FTP transfers use Active mode. This will not work through firewalls, but will often work with older FTP servers that do not support passive mode. If your connection hangs with passive mode (the default), try active! FTP Passive FTP Passive mode This option instructs FreeBSD to use Passive mode for all FTP operations. This allows the user to pass through firewalls that do not allow incoming connections on random port addresses. FTP via a HTTP proxy FTP via a HTTP proxy This option instructs FreeBSD to use the HTTP protocol (like a web browser) to connect to a proxy for all FTP operations. The proxy will translate the requests and send them to the FTP server. This allows the user to pass through firewalls that do not allow FTP at all, but offer a HTTP proxy. In this case, you have to specify the proxy in addition to the FTP server. There is another type of FTP proxy other tha HTTP proxies. This type is very uncommon, though. If you are not absolutely certain, you can assume that you have a HTTP proxy as described above. For a proxy FTP server, you should usually give the name of the server you really want as a part of the username, after an @ sign. The proxy server then fakes the real server. For example, assuming you want to install from ftp.FreeBSD.org, using the proxy FTP server foo.bar.com, listening on port 1024. In this case, you go to the options menu, set the FTP username to ftp@ftp.FreeBSD.org, and the password to your email address. As your installation media, you specify FTP (or passive FTP, if the proxy supports it), and the URL ftp://foo.bar.com:1234/pub/FreeBSD. Since /pub/FreeBSD from ftp.FreeBSD.org is proxied under foo.bar.com, you are able to install from that machine (which will fetch the files from ftp.FreeBSD.org as your installation requests them. Check Your BIOS Drive Numbering If you have used features in your BIOS to renumber your disk drives without re-cabling them then you should read first to avoid confusion. Installing FreeBSD Once you have completed the pre-installation step relevant to your situation, you are ready to install FreeBSD! Although you should not experience any difficulty, there is always the chance that you may, no matter how slight it is. If this is the case in your situation, then you may wish to go back and re-read the relevant preparation section or sections. Perhaps you will come across something you missed the first time. If you are having hardware problems, or FreeBSD refuses to boot at all, read the Hardware Guide for a list of possible solutions. sysinstall The FreeBSD boot floppies contain all of the online documentation you should need to be able to navigate through an installation. If it does not, please let us know what you found to be the most confusing or most lacking. Send your comments to the &a.doc;. It is the objective of the installation program (sysinstall) to be self-documenting enough that painful step-by-step guides are no longer necessary. It may take us a little while to reach that objective, but nonetheless, it is still our objective. Meanwhile, you may also find the following typical installation sequence to be helpful: Boot the kern.flp floppy and when asked, remove it and insert the mfsroot.flp and hit return. After a boot sequence which can take anywhere from 30 seconds to 3 minutes, depending on your hardware, you should be presented with a menu of initial choices. If the kern.flp floppy does not boot at all or the boot hangs at some stage, read the Q&A section of the Hardware Guide for possible causes. Press F1. You should see some basic usage instructions on the menu screen and general navigation. If you have not used this menu system before then please read this thoroughly. Select the Options item and set any special preferences you may have. installation standard installation express installation custom Select a Standard, Express, or Custom install, depending on whether or not you would like the installation to help you through a typical installation, give you a high degree of control over each step, or simply whiz through it (using reasonable defaults when possible) as fast as possible. If you have never used FreeBSD before, the Standard installation method is most recommended. The final configuration menu choice allows you to further configure your FreeBSD installation by giving you menu-driven access to various system defaults. Some items, like networking, may be especially important if you did a CDROM, tape, or floppy install and have not yet configured your network interfaces (assuming you have any). Properly configuring such interfaces here will allow FreeBSD to come up on the network when you first reboot from the hard disk. Pre-Installation Starting the installation will not make any changes to the system until this warning message appears : Last Chance: Are you SURE your 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 the final warning without changing the contents of the hard drive. Starting The Installation Process If booting from floppies, put the kern.flp disk in the floppy drive before booting the system. If the CDROM drive is a bootable type, it is not necessary to make the boot floppies. The CD must be in the drive before you boot in order to be sure it is found by the hardware probe. BIOS settings may need to be adjusted. It may be necessary to enter the BIOS setup and set it to use the CDROM or the floppy drive as the appropriate boot option. Be sure to change it back after installation to boot from the appropriate drive. It might also be necessary to turn off the BIOS Plug and Play (PnP) option so that some hardware will be detected correctly. Power down and restart the system. The normal BIOS startup screens display until it starts booting from the floppy or CDROM. If you are booting from floppies, it will ask for the mfsroot.flp floppy disk next, after which the installation will proceed. The "twirling baton" that is seen indicates that the installation program is loading. Typical booting from CDROM Verifying DMI Pool Data ........ Boot from ATAPI CD-ROM : 1. FD 2.88MB System Type-(00) /boot.config: -P Keyboard: yes BTX loader 1.00& BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive B: is disk1 BIOS drive C: is disk2 BIOS drive C: is disk3 BIOS 639kB/64512kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (jkh@bento.freebsd.org, Mon Nov 20 11:41:23 GMT 2000) | Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _ Typical booting from floppies Verifying DMI Pool Data ........ BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/261120kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (jkh@narf.osd.bsdi.com, Sat Apr 21 08:46:19 GMT 2001) /kernel text=0x24f1bb data=0x307ac+0x2062c | Please insert MFS root floppy and press enter: A beep will sound and a screen message will say to remove the kern.flp disk, insert the mfsroot.flp disk and press ENTER. The loading of the installation program will then continue. Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _ Regardless of how the installation program is started, the boot prompt will appear with a countdown to boot. Do nothing and in about 10 seconds, it will continue to boot or press ENTER to continue immediately. Starting UserConfig This starts the UserConfig program which is used to tell the system what hardware to probe and where to look. The best way to learn the UserConfig is to practice a few times. The method recommended for new users is "Start kernel configuration in full screen Visual mode". Press the down arrow key to highlight the item and then press ENTER.
Start Kernel Configuration Menu
Layout of UserConfig The first screen shows the layout of UserConfig and indicates the number of hardware conflicts present. The categories of device drivers (Storage, Network, etc.) are initially shown as a collapsed lists and can be expanded.
UserConfig
As the menu at the bottom indicates, pressing ? will display information about screen layout, moving around, altering the list/parameters, and saving changes. When finished reviewing the instructions, press Q to return to the UserConfig kernel settings editor. Resolve Hardware Conflicts The first operating system kernel installed is a "GENERIC" kernel. It includes a wide variety of hardware probes for different system hardware configurations. Probing is the name used for the process of detecting the presence of particular hardware. The drivers included in the GENERIC kernel often have the same IRQ/Port information and will be indicated as "Conflicts". The UserConfig utility is used to disable the unnecessary hardware probes and eliminate the conflicts. The objective is to specify the hardware probes to be "Active" in the system and have no conflicts between them. Certain situations will have "permitted conflicts" and will be indicated at the bottom of the Editor screen. Pressing X will expand all of the collapsed fields so the conflicts can be examined in detail.
Typical Hardware Conflicts
Most of the conflicts are generated by hardware that is not present and should be eliminated first. In general, do not disable the Keyboard (atkbd0) or the Syscons console driver (sc0). You need these. If a USB keyboard is being used, it may be necessary to disable the atkbd0 keyboard driver. Disable unused drivers by highlighting and pressing DELETE. This will move the driver to the Inactive Driver list and reduce the total number of conflicts if one had existed. Eliminate all the unused drivers first. The conflicts that are left need to be examined. If they do not have the indication of an "allowed conflict" in the message area, then either the IRQ/address for device probe will need to be changed - or - the IRQ/address on the hardware will need to be changed. Start Hardware Probe When the hardware conflicts have been resolved, the probe is started. In this example, moving all the unused device probes to the "Inactive" list left no conflicts.
User Config Completed
The actual probing can now be started by pressing Q to quit. A message will appear : Save these parameters before exiting? ([Y]es/[N]o/[C]ancel) Answer Y to save the parameters and the probing will start. The results will scroll off the screen and the Main Installation screen will display. Viewing Probe Results
Sysinstall Main Menu
The results of the probing can be viewed by pressing the SCROLL LOCK and using PageUp and PageDown to view the results. Pressing SCROLL LOCK again will return to the Main Installation screen. Typical hardware probe results: avail memory = 58880000 (57500K bytes) Preloaded elf kernel "kernel" at 0xc065d000. md1: Malloc disk 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 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 isa0: too many dependant configs (8) isa0: unexpected small tag 14 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq6 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-0x6f 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-0c3df 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 irq3 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 ppi0: <Parallel I/O> on ppbus0 plip0: <PLIP network interface> on ppbus0 ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33 acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4 Mounting root from ufs:/dev/md0c /stand/sysinstall running as init on vty0 The results of the hardware probing will depend on the system hardware. Check it carefully to confirm it found the hardware. Hardware problems should be corrected before continuing with the installation. It might be useful to record the probe results until the system is up and running. This installation produced messages which needed checking. Information regarding these messages were found by searching the mailing lists (questions and bugs). The unexpected tag 14 or unexpected small tag 14 indication can be ignored. This should disappear in future releases. An ISA-device (AWE64 sound card) gave too many proposals for possible PnP-Configurations and produced isa0: too many dependant configs (8). This should be harmless. Support for the sound card can be added after installation by building a new kernel with the sound driver or by loading the sound modules dynamically. Changing UserConfig Device Probing If you need to make changes to the UserConfig device probing, its easy to exit the sysinstall program - and start over again. Its also a good way to become more familar + and start over again. Its also a good way to become more familiar with the process.
Select Sysinstall Exit
Use the arrow keys to select "Exit Install" from the Main Install Screen menu. The following message will display: User Confirmation Requested Are you sure you wish to exit? The system will reboot (be sure to remove any floppies from the drives). [ Yes ] No The install program will start again if the CDROM is left in the drive and [Yes] is selected. If booting from floppies, to restart the installation it will be necessary to remove the mfs.root floppy and replace it with kern.flp before rebooting. This will allow trying the device probing a few times and fine-tune it before continuing with the installation process. How To Use Sysinstall
Select Usage From Main Menu
To learn how to use the menu system, use the arrow keys to select "Usage" and press ENTER. The instructions for using the menu system will display. After reviewing, pressing ENTER will return to the 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, pressing ENTER will 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
Sysinstall Main Menu
A different keyboard mapping may be chosen by selecting the menu item using up/down arrow keys and pressing SPACE. Pressing SPACE again will unselect the item. When finished, choose the [OK] item using the arrow keys and press ENTER. Only a partial list is shown in this screen representation. Selecting [CANCEL] 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 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. Pressing Q will return to the Main Install menu. Installation Begin A Standard Installation The "Standard" installation is the option recommended for those - new to unix or FreeBSD. Use the arrow keys to select "Standard" and + new to Unix or FreeBSD. Use the arrow keys to select "Standard" and then press ENTER to start the installation.
Begin Standard Installation
FDISK Partition Editor 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 (Quit. 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 to continue ]
Select Drive for FDISK
The following instructions for FDISK are for using the entire hard disk for the FreeBSD installation. If you want to use multiple operating systems, please refer to the tutorials at http://www.freebsd.org/tutorials FDISK Partition Editor The FDISK Partition Editor will display the current hard disk settings. The appearance of the screen will vary depending on the size of the hard disk installed and how it was set up previously. The following screen representation would be similar to a system which had DOS/Windows installed. Pressing F1 will display important information about using the FDISK Partition Editor.
Typical Fdisk Partitions Before Editing
Creating a FreeBSD Slice using the Entire Disk The tutorial Installing and Using FreeBSD With Other Operating Systems provides information on multi-os installations. For this particular system, A was selected to use the entire disk for the FreeBSD installation. Remember, all data currently on the hard disk will be lost using this method. The following illustrates how a FDISK Partition Editor screen will appear after choosing to use the entire hard disk and to remain compatible with future operating systems. The first line indicates the space allocated for the master boot record. The FreeBSD slice was created as shown on the second line. The next step is to set the freebsd slice as bootable.
Fdisk Partition Using Entire Disk
Use the arrow keys to highlight the FreeBSD slice and press S to set the slice as bootable. The illustration below shows the FreeBSD Slice as set as bootable. The flags should indicate "CA" before you leave this screen. When finished, press Q to save the changes and quit and continue with the installation. Install a Boot Manager First, highlight the boot manager option desired using the - arrow keys, then press SPACE. An asterik "*" will + arrow keys, then press SPACE. An asterisk "*" will indicate the selection chosen. This installation was solely FreeBSD so a boot manager was not needed. When finished, select [OK] and press ENTER.
Sysinstall Boot Manager Menu
The help screen discusses the problems that can be encountered when trying to share the hard disk between operating systems. If there is more than one drive, it will return to the Select Drives screen after the boot manager selection.
Exit Select Drive
Make sure [OK] is highlighted, then press ENTER to continue with the installation. Initial Disklabel Screen Message Now, you need to create BSD partitions inside of the fdisk partition(s) just created. If you have a reasonable amount of disk space (200MB or more) and don't have any special requirements, simply 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 to continue ] There are no partitions shown when you first enter the editor.
Sysinstall Disklabel Editor
Pressing F1 will give instructions for using the DiskLabel Editor. Press Q to continue. Auto Defaults for Partitions Pressing A displayed the suggested disklabels for this particular disk size. If a small hard disk is being used, the default values may be appropriate.
Sysinstall Disklabel Editor With Auto Defaults
Creating Custom Partitions Write down the auto defaults for all the file systems (/, swap, /var, /usr). Using the arrow keys, select the first partition ( / ) and press D to delete the partition. Delete all the partitions in the same manner. It is easiest to create the partitions in the same order shown by the auto default. Example Custom Partition To create the root partition, first press C and a dialog box will appear showing the total space available in blocks :
Free Space For Root Partition
This example will set the root partition to 100M. First, delete the entry using the BACKSPACE and enter the desired value :
Edit Root Partition Size
With [OK] highlighted, then press ENTER. The following dialog box will display :
Choose The Root Partition Type
The root partition needs to be a file system. With "FS" and [OK] highlighted, press ENTER. The next dialog box to appear is to enter the mount point for the root partition. Enter "/" for the root partition mount point. With the [OK] highlighted, press ENTER.
Choose The Root Mount Point
The swap, /var and /usr partitions are created in the same way. Be sure to choose "swap" as the filesystem type for the swap partition. Generally the swap value is twice the amount of RAM in the system. For this system, the "swap" partition will be set to 516M. The "/var" partition will be set to 100M and the "/usr" partition will get the remaining amount of disk space. Your final FreeBSD DiskLabel Editor screen will appear similar although your values chosen may be different. Press Q to finish.
Sysinstall Disklabel Editor
Select The Distribution Set I chose to install everything using the "All" option since I had the hard drive space. If you're concerned about space, consider the other distribution options. Select "All" using the arrow keys to highlight the item and press the SPACEBAR. Notice that the instructions below give pressing [ENTER] as a means to exit.
Choose Distributions
Installing The Ports Collection User Confirmation Requested Would you like to install the FreeBSD ports collection? This will give you ready access to over 5000 ported software packages, at a cost of around 70MB 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 CDROM 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 The installation program does not check to see if you have adequate space. Select this option only if you have adequate hard disk space. The ports can be added as needed later. The install program returns to the Choose Distributions screen. Select "EXIT" with the arrow keys and press ENTER to continue with the installation.
Confirm Distributions
Installation Media If Installing from a CDROM, use the arrow keys to highlight the "Install from a FreeBSD CDROM" option. Make sure [OK] is highlighted, then press ENTER to proceed with installation.
Choose Installation Media
Press F1 to display the Online Help for installation media. Press ENTER to return to the media selection menu. Final Warning The installation can now proceed if desired. This is also the last chance for aborting the installation to prevent changes to the hard drive. This is the point of no return. 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 Continuing The Installation Select "Yes" and Press ENTER to proceed. The installation time will vary according to the distribution chosen and installation media used. There will be a series of messages displayed indicating the status. When 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: /stand/sysinstall . [ OK ] [ Press enter to continue ] Press ENTER to proceed with post-installation configurations. Aborting The Installation Selecting [No] and pressing ENTER will abort the installation so no changes will be made to your 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 try and retry whichever operations have failed. [ OK ] Pressing ENTER will return to the Main Installation Menu to exit the installation. Post-installation Configuration of various options follows the successful installation. A option can be configured by re-entering the configuration options before booting the new FreeBSD system or after installation using /stand/sysinstall. Network Device Configuration If you previously configured PPP for an FTP install, this screen will not re-appear. For detailed information on Local Area Networks and configuring FreeBSD as a gateway/router refer to the tutorial PPP- Pendantic PPP Primer. User Confirmation Requested Would you like to configure Ethernet or SLIP/PPP network devices? [ Yes ] No This option allows configuration of network devices by selecting [Yes] and pressing ENTER
Selecting An Ethernet Device
Select the appropriate interface 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 "No" was selected with the arrow keys and ENTER pressed. If you want to try the new Internet protocol (IPv6), choose [Yes] and press ENTER. If yes is chosen, it will take several seconds for scanning RA servers. User Confirmation Requested Do you want to try DHCP configuration of the interface? Yes [ No ] There is no DHCP (Dynamic Host Configuration Protocol) so "No" was selected with the arrow keys and ENTER pressed. Answering [Yes] will execute dhclient, and if successful, will fill in the network configuration information automatically. Refer to the FreeBSD Handbook for more information. The following Network Configuration screen shows the - configuration of the ethernet device for a system that will act + configuration of the Ethernet device for a system that will act as the gateway for a Local Area Network.
Set Network Configuration For ed0
Use TAB to select the information fields and fill in appropriate information: Host The fully-qualified hostname, e.g. k6-2.weeble.com in this case. Domain The name of the domain that your machine is in, e.g. weeble.com for this case. IPv4 Gateway IP address of host forwarding packets to non-local destinations. Fill this in only 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. Name server IP address of your 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 a Class C block (192.168.0.0 - 192.168.255.255). The default netmask is for a Class C network (255.255.255.0). Extra options to ifconfig Any interface-specific options to ifconfig you would like to add. There were none in this case. Use TAB to select [OK] when finished and press ENTER. User Confirmation Requested Would you like to Bring Up the ed0 interface right now? [ Yes ] No Choosing [Yes] and pressing ENTER will bring the machine up on the network and be ready for use after leaving leaving the installation. Configure Gateway User Confirmation Requested Do you want this machine to function as a network gateway? [ Yes ] No [Yes] was selected and ENTER pressed since this machine will be acting as the gateway for a local area network and forwarding packets between other machines. Anonymous FTP Deny Anonymous FTP Selecting [No] and pressing ENTER will still allow users who have accounts with passwords to use ftp. User Confirmation Requested Do you want to have anonymous FTP access to this machine? Yes [ No ] With [No] highlighted, press ENTER to continue with post-installation configuration. Allow Anonymous FTP User Confirmation Requested Do you want to have anonymous FTP access to this machine? [ Yes ] No If you select [Yes] and press ENTER you would be allowing anonymous ftp connections. Be aware of the security considerations if you elect to allow this. To allow anonymous FTP, use the arrow keys to select [Yes] and press ENTER. The following screens (or similar) will appear :
Default Anonymous FTP Configuration
Pressing F1 will display the help : This screen allows you to configure the anonymous FTP user. The following configuration values are editable: UID: The user ID you wish to assign to the anonymous FTP user. All files uploaded will be owned by this ID. Group: Which group you wish the anonymous FTP user to be in. 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 you do not have enough room there for the anticipated FTP needs, the /usr directory could be used by setting the FTP Root Directory to /usr/ftp. When you are satisfied with the values, press ENTER to continue. User Confirmation Requested Create a welcome message file for anonymous FTP users? [ Yes ] No If you select [Yes] and press ENTER, an editor will automatically start allowing you to edit the message.
Edit The FTP Welcome Message
This is a text editor called ee. Use the instructions to change the message or change the message later using a text editor of your choice. Note the file name/location at the bottom. Press ESC and a pop-up menu will default to "a) leave editor". Press ENTER to exit and continue. Configure Network File Services 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 Network File System server or client, select [No] and press ENTER. If [Yes] is chosen, a message will pop-up indicating that the the exports file must be created. Press Enter to continue. 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 file systems. Press [ENTER] now to invoke an editor on /etc/exports [ OK ] A text editor will start allowing the exports file to be created and edited.
Editing the Exports File
Use the instructions to add the actual exported filesystems now or later using a text editor of your choice. Note the filename/location at the bottom. Press ESC and a pop-up menu will default to "a) leave editor". Press ENTER to exit and continue. NFS Client With the arrow keys, select [Yes] or [No] as appropriate and press ENTER. This example shows the NFS client option as [No]. User Confirmation Requested Do you want to configure this machine as an NFS client? Yes [ No ] Security Profile A "security profile" is a set of configuration options that attempts to achieve the desired ratio of security to convenience by enabling and disabling certain programs and other settings. Refer to the FAQ for more information. Selecting [No] and pressing ENTER will set the security profile to "medium" (recommended for new users) and continue the installation. User Confirmation Requested Do you want to select a default security profile for this host (select No for "medium" security)? [ Yes ] No Selecting [Yes] and pressing ENTER will allow selecting a different security profile.
Security Profile Options
Press F1 to display the help. Press ENTER to return to selection menu. Use the arrow keys to choose the medium level [DEFAULT] unless your are sure that another level is required for your needs. With [OK] highlighted, press ENTER. Message Moderate security settings have been selected. This means that most "popular" network services and mechanisms like inetd(8) have been enabled by default for a comfortable user experience but with possible trade-offs in system security. If this bothers you and you know exactly what your are doing, select the high high security profile instead. To change any of these settings later, edit /etc/rc.conf. [ OK ] [ Press enter to continue ] Press ENTER to continue with the post-installation configuration. System Console Settings There are several options available to customize the system console. To view and configure the options, select [Yes] and press ENTER. User Confirmation Requested Would you like to customize your system console settings? [ Yes ] No A commonly used option is the screensaver. Use the arrow keys to select "Saver" and then press ENTER.
Screensaver Options
First, select the desired screen saver using the arrow keys and then press SPACE. The "X" will indicate the selected screensaver.
Screensaver Options
The default time interval is 300 seconds. To change the time interval, select "Timeout" using the arrow keys and press SPACE. A pop-up menu will appear :
Screensaver Timeout
The value can be changed, then select [OK] and press ENTER to return to the System Screensaver options menu. At the Screensaver Menu, select [OK] and press ENTER again to return to the System Console options menu.
System Console Configuration Exit
Selecting [EXIT] and pressing ENTER will continue with the post-installation configurations. Setting The Time Zone Setting the timezone for your machine will allow it to automatically correct for any regional time changes and perform other timezone related functions properly. The selection menus will vary according to your geographical selections. User Confirmation Requested Would you like to set this machine's time zone now? [ Yes ] No Select [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 please choose NO here! Yes [ No ] If the machine's CMOS clock is set to local time select [No] with the arrow keys and then press ENTER. If the CMOS clock is set to GMT or UTC, select [Yes] and press ENTER.
Select Your Region
The appropriate region is selected using the arrow keys and then press ENTER.
Select Your Country
Select the appropriate country using the arrow keys and press ENTER. This is a partial chart of the country selection menu.
Select Your Timezone
The appropriate time zone is selected using the arrow keys and pressing ENTER. Again, this is a partial chart. Confirmation Does the abbreviation 'EDT' look reasonable? [ Yes ] No Confirm the abbreviation for the time zone is correct. If it looks okay, press ENTER to continue with the post-installation configuration. Linux Compatibility User Confirmation Requested Would you like to enable Linux binary compatibility? [ Yes ] No Selecting [Yes] and pressing ENTER will allow running Linux software on FreeBSD. The install will proceed to add the appropriate packages for Linux compatibility. If installing by FTP, the machine will need to be connected to - the internet. Sometimes a remote ftp site will not have all the + the Internet. Sometimes a remote ftp site will not have all the distributions like the Linux binary compatibility. This can be installed later if necessary. Mouse Settings This option will allow you to cut and past text in the console and user programs with a 3-button mouse. If using a 2-button mouse, refer to manual page, &man.moused.8;, after installation for details on emulating the 3-button style. This example depicts a non-USB mouse. User Confirmation Requested Does this system have a non-USB mouse attached to it? [ Yes ] No Select [Yes] for a non-USB mouse or [No] for a USB mouse and press ENTER.
Select Mouse Protocol Type
Use the arrow keys to select "Type" and press ENTER
Set Mouse Protocol
The mouse in this example is a PS/2 type, so the default "Auto" was appropriate. To change protocol, use the arrow keys and then press SPACE. Select [OK] 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" was appropriate. To change the port, use the arrow keys and then press the space bar. Select [OK] and press ENTER to exit this menu.
Enable The Mouse Daemon
Last, the mouse daemon is enabled and tested.
Test The Mouse Daemon
The cursor moved around the screen so the mouse daemon is running: Select [YES] to return to the previous menu then select "Exit" with the arrow keys and press ENTER to return to continue with the post-installation configuration. Configure X-Server User Confirmation Requested Would you like to configure your X server at this time? [ Yes ] No This can be done later using /stand/sysinstall if you don't have graphics card and monitor information handy. Equipment damage can occur if settings are incorrect. Select [Yes] and press ENTER to proceed with configuring the X server. Select Configuration Method
Select Configuration Method Menu
There are several ways to configure the X server. XF86Setup is fully graphical and probably the easiest. Use the arrow keys to select the "XF86Setup" option and press ENTER. Message You have configured and been running the mouse daemon. Choose "/dev/sysmouse" as the mouse port and "SysMouse" or "MouseSystems" as the mouse protocol in the X configuration utility. [ OK ] [ Press enter to continue ] The mouse daemon previously configured has been detected. Press ENTER to continue. Press [Enter] to switch to graphics mode. This may take a while... [ OK ] Press ENTER to switch to the graphics mode and continue. It will not try to switch to the graphics mode until ENTER is pressed. The screen will go black and then shortly a screen with a large "X" in the center will appear. Be patient and wait. After a few more moments, the XF86 Setup Introduction will appear. Read all instructions carefully. Press ENTER to continue. X-Mouse The mouse is the first item to be configured. The mouse daemon was already running and "Emulate3Buttons" was added for my mouse type. Click on "Apply" and check the mouse actions are working properly. X-Keyboard Click on the "Keyboard" menu item. The default settings were fine for my keyboard. Select the options appropriate for your situation then click on "Apply". Video Card Click on the "Card" menu item. Select the appropriate video card from the list using the scrollbar. Clicking on your card will show as "Card selected:" above the list box. Next, the "Detailed Setup" was selected just to check any details. Monitor Click on the "Monitor" menu item. There are two ways to proceed. One method requires that you enter the horizontal and vertical sweep capabilities of your monitor. Choosing one of the options listed that the monitor is the method used in the illustration. Do not exceed the ratings of your monitor. Damage could occur. If you have doubts select "ABORT" and get the information. The remainder of the installation process will be unaffected and configuring the X-Server can be done later using /stand/sysinstall. After selecting a listed option, the screen will display the horizontal and vertical sweep rates that will be used. Compare those to the monitor specifications. The monitor must be capable of using those ranges. Video Mode Selection Click on the "Modeselection" menu item. Selected the modes and color depth appropriate for the system. Other These are generally reasonable values. Verify all the settings once again and select "Done". It will then attempt to switch to x-mode to verify the settings. If nothing appears or appears wrong, kill the x-server using CTRLALTBACKSPACE and adjust the settings or revisit them after installation. Saving Configuration After selecting [DONE] the following message will display: If you've finished configuring everything press the Okay button to start the X server using the configuration you've selected. If you still wish to configure some things, press one of the buttons at the top and then press "Done" again, when you've finished. After selecting [OKAY], some messages will briefly appear advising to wait and attempting to start the x-server. This process takes a few moments, so be patient. The screen will go blank for a short period of time and then the following should appear: "Congratulations, you've got a running server! The configuration can now be saved in the location indicated and continue with the installation. If the monitor display needs adjusted, xvidtune can be ran to adjust them. There are warnings that improper settings can damage your equipment. Heed them. If in doubt, don't do it. Instead, use the monitor controls to adjust the display for x-windows. There may be some display differences when switching back to text mode, but it's better than damaging equipment. The xvidtune can be ran later using /stand/sysinstall. If it doesn't appear or is distorted, kill the server with CTRLALTBACKSPACE to continue and configure the x-server after installation using /stand/sysinstall. The installation program will create the 'X' link to the server by selecting [Yes]: Do you want to create an 'X' link to the SVGA server? (the link will be created in the directory: /usr/X11R6/bin) Okay? [ Yes ] No Link created successfully. [ OK ] Press [ENTER] to continue configuration. Select Default X Desktop I selected the K Desktop Environment with the arrow keys and then pressed ENTER to set it as my default window manager.
Select Default Desktop
The selected desktop package will then be loaded on they system. Install Packages Only one package is shown being added for purposes of illustration. Additional packages can also be added at this time if desired. After installation /stand/sysinstall can be used to add additional packages. User Confirmation Requested The FreeBSD package collection is a collection of hundreds of ready-to-run applications, from text editors to games to WEB servers and more. Would you like to browse the collection now? [ Yes ] No Selecting [Yes] and pressing ENTER will be followed by the Package Selection screens:
Select Package Category
All packages available will be displayed if "All" is chosen. Additional packages may be on other CDs. These can also be added later using /stand/sysinstall. The bash shell is shown selected. Select as many as desired by highlighting the item and pressing the SPACE. A short description of each package will appear in the lower left corner of the screen.
Select Packages
When the package(s) are selected, select [OK] and then press ENTER to return to the Package Selection menu.
Install Packages
Use the arrow keys to select [INSTALL] and pressing ENTER will ask for confirmation.
Confirm Package Installation
Selecting [OK] and pressing ENTER will start the package installation. Installing messages will appear until completed. Make note if there are any error messages. The final configuration continues after packages are installed. Add User/Groups 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 "Add User" with the arrow keys then and press ENTER.
Select Add User
Add User Information
The following descriptions will appear in the lower part of the screen as the items are selected with TAB Login ID The login name of the new user (mandatory) UID The numerical ID for this user (leave blank for automatic choice) Group The login group name for this user (leave blank for automatic choice) Password The password for this user (enter this field with care!) Full name The user's full name (comment) Member groups The groups this user belongs to (i.e. gets access rights for) Home directory The user's home directory (leave blank for default) Login shell The user's login shell (leave blank for default). (/bin/sh) The login shell was changed from /bin/sh to /usr/local/bin/bash to use the bash shell that was previously installed as a package. The user was also added to the group "wheel" to be able to become a superuser with root privileges. Groups could also be added at this time if specific needs are known. Otherwise, this may be accessed through using /stand/sysinstall after installation is completed.
Exit User and Group Management
I selected [Exit] with the arrow keys then [OK] and pressed ENTER to continue the installation. Set Root Password Message Now you must set the system manager's password. This is the password you'll use to log in as "root". [ OK ] [ Press enter to continue ] The password will need to be typed in twice correctly. Needless to say, make sure you have a way of finding the password if you forget. Changing local password for root. New password : Retype new password : The installation will continue after the password is successfully entered. Exiting Install User Confirmation Requested Visit the general configuration menu for a chance to set any last options? Yes [ No ] Selecting [No] with the arrow keys and pressing - ENTER returns to the Main Installallation Menu + ENTER returns to the Main Installation Menu
Exit Install
Select [EXIT INSTALL] with the arrow keys and press ENTER. User Confirmation Requested Are you sure you wish to exit? The system will reboot (be sure to remove any floppies from the drives). [ Yes ] No Select [Yes] and remove floppy if booting from floppy. The CDROM drive is locked until you select yes to exit and press ENTER. The CDROM drive is then unlocked and can be removed from drive (quickly). The system will reboot so watch for any error messages that may appear. FreeBSD Bootup If everything goes well, you will see similar messages scroll off the screen and you'll arrive at a login prompt. You can view the content of the messages by pressing SCROLL-LOCK and using PgUp and PgDn. Pressing SCROLL-LOCK again will return to the prompt. The entire message may not display (buffer limitation) but can be viewed from the command line after logging in by typing dmesg at the prompt will get similar information. Login using the user/password you set during installation (rpratt, in this example). Avoid logging in as root except when necessary. Typical boot messages : Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001 jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC 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 ata1 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 256983040 (250960K bytes) Preloaded elf kernel "kernel" at 0xc044d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc044d09c. md0: Malloc disk 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-0x6f 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 ppi0: <Parallel I/O> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port plip0: <PLIP network interface> 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, 70119 free (655 frags, 8683 blocks, 0.7% fragmentation) /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 6976313 free (51774 frags, 829297 blocks, 0.7% fragmentation) /dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 97952 free (9 frags, 12381 blocks, 0.0% fragmentation) Doing initial network setup: hostname. 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: tcp extensions=NO IP gateway=YES TCP keepalive=YES routing daemons:. additional daemons: syslogd. Doing additional network setup: portmap. Starting final network daemons: creating ssh RSA host key Generating RSA keys: Key generation complete. 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: 2d:02:37:d2:0e:68:93:8f:9c:46:de:92:f4:be:60:0a root@k6-2.weeble.com creating ssh DSA host key Generating DSA parameter and key. 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: 38:af:d2:1f:63:14:00:d8:83:fd:dd:4b:97:1c:43:6d root@k6-2.weeble.com. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout starting standard daemons: inetd cron sendmail sshd usbd. Initial rc.i386 initialization: linux. rc.i386 configuring syscons: blank_time screensaver moused. Additional ABI support: linux. Local package initilization:. Additional TCP options:. 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 the X server has been configured and a Default Desktop chosen, it can be started by typing startx at the command line. FreeBSD Shutdown It is important to properly shutdown the operating system. Do not just turn off power. First, become a superuser by typing su at the command line and entering the root password. This will work only if the user is a member of the group wheel. Otherwise, login as root and use 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. Supported Hardware hardware FreeBSD currently runs on a wide variety of ISA, VLB, EISA, and PCI bus-based PCs with Intel, AMD, Cyrix, or NexGen x86 processors, as well as a number of machines based on the Compaq Alpha processor. Support for generic IDE or ESDI drive configurations, various SCSI controllers, PCMCIA cards, USB devices, and network and serial cards is also provided. FreeBSD also supports IBM's microchannel (MCA) bus. A list of supported hardware is provided with each FreeBSD release in the FreeBSD Hardware Notes. This document can usually be found in a file named HARDWARE.TXT, in the top-level directory of a CDROM or FTP distribution or in sysinstall's documentation menu. It lists, for a given architecture, what hardware devices are known to be supported by each release of FreeBSD. Troubleshooting installation troubleshooting The following section covers basic installation troubleshooting, such as common problems people have reported. There are also a few questions and answers for people wishing to dual-boot FreeBSD with MS-DOS. What to Do If Something Goes Wrong... Due to various limitations of the PC architecture, it is impossible for probing to be 100% reliable, however, there are a few things you can do if it fails. Check the Hardware Notes document for your version of FreeBSD to make sure your hardware is supported. If your hardware is supported and you still experience lock-ups or other problems, reset your computer, and when the visual kernel configuration option is given, choose it. This will allow you to go through your hardware and supply information to the system about it. The kernel on the boot disks is configured assuming that most hardware devices are in their factory default configuration in terms of IRQs, IO addresses, and DMA channels. If your hardware has been reconfigured, you will most likely need to use the configuration editor to tell FreeBSD where to find things. 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. Do not disable any drivers you will need during the installation, such as your screen (sc0). If the installation wedges or fails mysteriously after leaving the configuration editor, you have probably removed or changed something you should not have. Reboot and try again. In configuration mode, you can: List the device drivers installed in the kernel. Change device drivers for hardware that is not present in your system. Change IRQs, DRQs, and IO port addresses used by a device driver. After adjusting the kernel to match your hardware configuration, type Q to boot with the new settings. Once the installation has completed, any changes you made in the configuration mode will be permanent so you do not have to reconfigure every time you boot. It is still highly likely that you will eventually want to build a custom kernel. MS-DOS User's Questions and Answers DOS Many users wish to install FreeBSD on PCs inhabited by MS-DOS. Here are some commonly asked questions about installing FreeBSD on such systems. Help, I have no space! Do I need to delete everything first? If your machine is already running MS-DOS and has little or no free space available for the FreeBSD installation, all hope is not lost! You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or various FreeBSD FTP sites to be quite useful. FIPS FIPS allows you to split an existing MS-DOS partition into two pieces, preserving the original partition and allowing you to install onto the second free piece. You first defragment your MS-DOS partition using the Windows DEFRAG utility (go into Explorer, right-click on the hard drive, and choose to defrag your hard drive), or Norton Disk Tools. You then must run FIPS. It will prompt you for the rest of the information it needs. Afterwards, you can reboot and install FreeBSD on the new free slice. See the Distributions menu for an estimate of how much free space you will need for the kind of installation you want. Partition Magic There is also a very useful product from PowerQuest called Partition Magic. This application has far more functionality than FIPS, and is highly recommended if you plan to often add/remove operating systems (like me). However, it does cost money, and if you plan to install FreeBSD once and then leave it there, FIPS will probably be fine for you. Can I use compressed MS-DOS filesystems from FreeBSD? No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will only be able to use whatever portion of the filesystem you leave uncompressed. The rest of the filesystem will show up as one large file (the stacked/double spaced file!). Do not remove that file or you will probably regret it greatly! It is probably better to create another uncompressed primary MS-DOS partition and use this for communications between MS-DOS and FreeBSD. Can I mount my extended MS-DOS partition? partitions slices Yes. DOS extended partitions are mapped in at the end of the other slices in FreeBSD, e.g., your D: drive might be /dev/da0s5, your E: drive, /dev/da0s6, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE drives, substitute ad for da appropriately if installing 4.0-RELEASE or later, and substitute wd for da if you are installing a version of FreeBSD prior to 4.0. You otherwise mount extended partitions exactly like you would any other DOS drive, for example: &prompt.root; mount -t msdos /dev/ad0s5 /dos_d Valentino Vaschetto Contributed by Advanced Installation Guide This section describes how to install FreeBSD in exceptional cases. Installing FreeBSD 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 that you are trying to install FreeBSD on either doesnt have a monitor attached to it, or doesnt even have a VGA output. How is this possible you ask? Using a serial console. A serial console is basically using another machine to act as the main display and keyboard for a system. To do this, just follow these steps: Fetch the Right Boot Floppy Images First you will need to get the right disk images so that you can boot into the install program. The secret with using a serial console is that you tell the boot loader to send I/O through a serial port instead of displaying console output to the VGA device and trying to read input from a local keyboard. Enough of that now, let's get back to getting these disk images. You will need to get kern.flp and mfsroot.flp from the floppies directory. Write the Image Files to the Floppy Disks. The image files, such as kern.flp, are not regular files that you copy to the disk. Instead, they are images of the complete contents of the disk. This means that you can not use commands like DOS' copy to write the files. Instead, you must use specific tools to write the images directly to the disk. fdimage If you are creating the floppies on a computer running DOS then we provide a tool to do this called fdimage. If you are using the floppies from the CDROM, and your CDROM is the E: drive then you would run this: E:\> tools\fdimage floppies\kern.flp A: Repeat this command for each .flp file, replacing the floppy disk each time. Adjust the command line as necessary, depending on where you have placed the .flp files. If you do not have the CDROM then fdimage can be downloaded from the tools directory on the FreeBSD FTP site. If you are writing the floppies on a Unix system (such as another FreeBSD system) you can use the &man.dd.1; command to write the image files directly to disk. On FreeBSD you would run: &prompt.root; dd if=kern.flp of=/dev/fd0 On FreeBSD /dev/fd0 refers to the first floppy disk (the A: drive). /dev/fd1 would be the B: drive, and so on. Other Unix variants might have different names for the floppy disk devices, and you will need to check the documentation for the system as necessary. Enabling the Boot Floppies to Boot into a Serial Console Do not try to mount the floppy if it is write-protected mount If you were to boot into the floppies that you just made, FreeBSD would boot into its normal install mode. We want FreeBSD to boot into a serial console for our install. To do this, you have to mount the kern.flp floppy onto your FreeBSD system using the &man.mount.8; command. &prompt.root; mount /dev/fd0 /mnt Now that you have the floppy mounted, you must change into the floppy directory &prompt.root; cd /mnt Here is where you must set the floppy to boot into a serial console. You have to make a file called boot.config containing "/boot/loader -h". All this does is pass a flag to the bootloader to boot into a serial console. &prompt.root; echo "/boot/loader -h" > boot.config Now that you have your floppy configured correctly, you must unmount the floppy using the &man.umount.8; command &prompt.root; cd / &prompt.root; umount /mnt Now you can remove the floppy from the floppy drive Connecting Your Null Modem Cable null-modem cable You now need to connect a null modem cable between the two machines. Just connect the cable to the serial ports of the 2 machines. A normal serial cable will not work here, you need a null modem cable because it has some of the wires inside crossed over. Booting Up for the Install It's now time to go ahead and start the install. Put the kern.flp floppy in the floppy drive of the machine you're doing the headless install on, and power on the machine. Connecting to Your Headless Machine cu Now you have to connect to that machine with &man.cu.1;: &prompt.root; cu -l /dev/cuaa0 That's it! You should be able to control the headless machine through your cu session now. It will ask you to put in the mfsroot.flp, and then it will come up with a selection of what kind of terminal to use. Just select the FreeBSD color console and proceed with your install!