diff options
| author | jkh <jkh@FreeBSD.org> | 1998-05-24 20:00:27 +0000 |
|---|---|---|
| committer | jkh <jkh@FreeBSD.org> | 1998-05-24 20:00:27 +0000 |
| commit | b5fb0aed2787b1af5aabd2d3a684d1b464b873fa (patch) | |
| tree | 565a0b8e883b21dc4d6fbb484cf5318c3de08b96 /release | |
| parent | 98226219a181e4864ad2851bf82038f81c0f88dd (diff) | |
| download | FreeBSD-src-b5fb0aed2787b1af5aabd2d3a684d1b464b873fa.zip FreeBSD-src-b5fb0aed2787b1af5aabd2d3a684d1b464b873fa.tar.gz | |
Sync documentation with 2.2 updates.
Diffstat (limited to 'release')
| -rw-r--r-- | release/sysinstall/help/distributions.hlp | 2 | ||||
| -rw-r--r-- | release/sysinstall/help/fixit.hlp | 2 | ||||
| -rw-r--r-- | release/sysinstall/help/hardware.hlp | 389 | ||||
| -rw-r--r-- | release/sysinstall/help/install.hlp | 642 | ||||
| -rw-r--r-- | release/sysinstall/help/network_device.hlp | 2 | ||||
| -rw-r--r-- | release/sysinstall/help/readme.hlp | 103 | ||||
| -rw-r--r-- | release/sysinstall/help/register.hlp | 4 | ||||
| -rw-r--r-- | release/sysinstall/help/shortcuts.hlp | 2 | ||||
| -rw-r--r-- | release/sysinstall/help/trouble.hlp | 2 | ||||
| -rw-r--r-- | release/sysinstall/help/upgrade.hlp | 205 | ||||
| -rw-r--r-- | release/sysinstall/help/usage.hlp | 15 |
11 files changed, 683 insertions, 685 deletions
diff --git a/release/sysinstall/help/distributions.hlp b/release/sysinstall/help/distributions.hlp index 01d0fc8..16c095b 100644 --- a/release/sysinstall/help/distributions.hlp +++ b/release/sysinstall/help/distributions.hlp @@ -2,7 +2,7 @@ DISTRIBUTION INFORMATION ------------------------ An ``X-'' prefixed before a distribution set means that the XFree86 -3.3.1 base distribution, libraries, manual pages, SVGA server and a +3.3.2 base distribution, libraries, manual pages, SVGA server and a set of default fonts will be selected in addition to the set itself. If you select such a set, you will also be presented with a set of menus for customizing the selections to your desired X Window System diff --git a/release/sysinstall/help/fixit.hlp b/release/sysinstall/help/fixit.hlp index 2ec1765..e47394e 100644 --- a/release/sysinstall/help/fixit.hlp +++ b/release/sysinstall/help/fixit.hlp @@ -5,5 +5,3 @@ commands under /mnt2 as well as a more complete set of device files in therefore require you to go to /mnt2/dev and use the entries there rather than assuming that they will be present in the default /dev (which came from the boot floppy and is very minimal). - -When you're done, exit the shell to reboot. diff --git a/release/sysinstall/help/hardware.hlp b/release/sysinstall/help/hardware.hlp index 150795c..cb4f61a 100644 --- a/release/sysinstall/help/hardware.hlp +++ b/release/sysinstall/help/hardware.hlp @@ -1,14 +1,12 @@ -Hardware Documentation Guide: $Id: hardware.hlp,v 1.33 1998/03/27 03:11:23 yokota Exp $ - -Contents last changed: Jan 14th, 1997 - Table of Contents ----------------- 0. Document Conventions 1. Default Configuration (GENERIC kernel) 2. Using UserConfig to change FreeBSD kernel settings -3. LINT - other possible configurations. -4. Known Hardware Problems. +3. LINT - other possible configurations +4. Supported Hardware + +See TROUBLE.TXT for Q&A on known hardware problems. ========================================================================= @@ -22,17 +20,15 @@ throughout this document to differentiate it from the machine output. -- ------------------------------- The following table contains a list of all of the devices that are -present in the GENERIC kernel, that being the kernel (the operating -system) that was placed in your root partition during the FreeBSD +present in the GENERIC kernel. This is the essential part of the +operating system that is placed in your root partition during the installation process. A compressed version of the GENERIC kernel is also used on the installation floppy diskette and DOS boot image. The table describes the various parameters used by the driver to communicate with the hardware in your system. There are four parameters in the table, though not all are used by each and every -device. - -Detail: +device: Port The starting I/O port used by the device, shown in hexadecimal. @@ -48,7 +44,8 @@ Detail: If an entry in the table has `n/a' for a value then it means that the parameter in question does not apply to that device. A value of `dyn' means that the correct value should be determined automatically by the -kernel when the system boots. +kernel when the system boots and that you don't need to worry about +it. FreeBSD GENERIC kernel: @@ -88,7 +85,7 @@ lpt1 dyn dyn n/a n/a Printer Port 1 de0 n/a n/a n/a n/a DEC DC21x40 PCI based cards (including 21140 100bT cards) -ed0 280 10 dyn d8000 WD & SMC 80xx; Novell NE1000 & +ed0 280 10 dyn d8000 WD & SMC 80xx; Novell NE1000 & NE2000; 3Com 3C503; HP PC Lan+ eg0 310 5 dyn dyn 3Com 3C505 ep0 300 10 dyn dyn 3Com 3C509 @@ -258,7 +255,7 @@ ctx: Cortex-I frame grabber cx: Cronyx/Sigma multiport sync/async cy: Cyclades high-speed serial driver el: 3Com 3C501 -fea: DEV DEFEA EISA FDDI adater +fea: DEV DEFEA EISA FDDI adapter fpa: DEC DEFPA PCI FDDI adapter gp: National Instruments AT-GPIB and AT-GPIB/TNT board gsc: Genius GS-4500 hand scanner @@ -266,10 +263,12 @@ gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX gusxvi: Gravis Ultrasound 16-bit PCM joy: Joystick labpc: National Instrument's Lab-PC and Lab-PC+ -meteor: Matrox Meteor frame-grabber card +meteor: Matrox Meteor frame-grabber card +bktr: Brooktree Bt848 based frame-grabber cards. mpu: Roland MPU-401 stand-alone card mse: Microsoft, Logitech, ATI bus mouse ports mss: Microsoft Sound System +nic: Dr Neuhaus NICCY 3008, 3009 & 5000 ISDN cards opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum pas: ProAudioSpectrum PCM and MIDI pca: PCM audio ("/dev/audio") through your PC speaker @@ -278,6 +277,7 @@ rc: RISCom/8 multiport card sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum sbmidi: SoundBlaster 16 MIDI interface sbxvi: SoundBlaster 16 +si: Specialix SI/XIO/SX (old and enhanced ISA, PCI, EISA) serial spigot: Creative Labs Video Spigot video-acquisition board uart: Stand-alone 6850 UART for MIDI wds: Western Digital WD7000 IDE @@ -285,225 +285,200 @@ wds: Western Digital WD7000 IDE --- end of list --- -4. Known Hardware Problems, Q & A: --- ------------------------------- +4. Supported Hardware +-- ------------------ + +FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus +based PC's, ranging from 386sx to Pentium class machines (though the +386sx is not recommended). Support for generic IDE or ESDI drive +configurations, various SCSI controller, network and serial cards is +also provided. + +What follows is a list of all peripherals currently known to work with +FreeBSD. Other configurations may also work, we have simply not as yet +received confirmation of this. + + +4.1. Disk Controllers +---- ---------------- + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) +IDE +ATA + +Adaptec 1535 ISA SCSI controllers +Adaptec 154x series ISA SCSI controllers +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. +Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI +controllers. +Adaptec AIC7850 on-board SCSI controllers. + +Support for the following controllers is rather weak: +Adaptec 1510 series ISA SCSI controllers (not for bootable devices) +Adaptec 152x series ISA SCSI controllers +Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x +and SoundBlaster SCSI cards. + +** Note: You cannot boot from the SoundBlaster cards as they have no + on-board BIOS, such being necessary for mapping the boot device into the + system BIOS I/O vectors. They're perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 based card + without a boot ROM. Some systems DO have a boot ROM, which is generally + indicated by some sort of message when the system is first powered up + or reset, and in such cases you *will* also be able to boot from them. + Check your system/board documentation for more details. + +Buslogic 545S & 545c +Buslogic 445S/445c VLB SCSI controller +Buslogic 742A, 747S, 747c EISA SCSI controller. +Buslogic 946c PCI SCSI controller +Buslogic 956c PCI SCSI controller + +SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI +controllers: + ASUS SC-200 + Data Technology DTC3130 (all variants) + NCR cards (all) + Symbios cards (all) + Tekram DC390W, 390U and 390F + Tyan S1365 + +Tekram DC390 and DC390T controllers (maybe other cards based on the +AMD 53c974 as well). + +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +UltraStor 14F, 24F and 34F SCSI controllers. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +WD7000 SCSI controller. + +FreeBSD 2.2.5 will be accompanied by a contributed driver for the +Future Domain 36C20 / Adaptec AHA2920 controller. This is not fully +supported (yet), but basically functional. Look into the /xperimnt +section of the CD-ROM. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT and 8mm Exabyte) and CD ROM drives. + +The following CD-ROM type systems are supported at this time: +(cd) SCSI interface (also includes ProAudio Spectrum and + SoundBlaster SCSI) +(mcd) Mitsumi proprietary interface (all models, driver is rather stale) +(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary + interface (562/563 models) +(scd) Sony proprietary interface (all models) +(wcd) ATAPI IDE interface. + + +4.2. Ethernet cards +---- -------------- + +Allied-Telesis AT1700 and RE2000 cards + +AMD PCnet/PCI (79c970 & 53c974 or 79c974) + +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. SMC Elite Ultra is also supported. + +DEC EtherWORKS III NICs (DE203, DE204, and DE205) +DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) +DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) +DEC FDDI (DEFPA/DEFEA) NICs + +Fujitsu MB86960A/MB86965A + +HP PC Lan+ cards (model numbers: 27247B and 27252A). + +Intel EtherExpress (not recommended due to driver instability) +Intel EtherExpress Pro/10 +Intel EtherExpress Pro/100B PCI Fast Ethernet + +Isolan AT 4141-0 (16 bit) +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. -Q: mcd0 keeps thinking that it has found a device and this stops my Intel - EtherExpress card from working. - -A: Use the UserConfig utility (see section 1.0) and disable the probing of - the mcd0 and mcd1 devices. Generally speaking, you should only leave - the devices that you will be using enabled in your kernel. - - -Q: FreeBSD claims to support the 3Com PCMCIA card, but my card isn't - recognized when it's plugged into my laptop. - -A: There are a couple of possible problems. First of all, FreeBSD does - not support multi-function cards, so if you have a combo - ethernet/modem card (such as the 3C562), it won't work. The - default driver for the 3C589 card was written just like all of the - other drivers in FreeBSD, and depend on the card's own configuration - data stored in NVRAM to work. You must correctly configure FreeBSD's - driver to match the IRQ, port, and IOMEM stored in NVRAM. - Unfortunately, the only program capable of reading them is the - 3COM supplied DOS program. This program must be run on a absolutely - clean system (no other drivers must be running), and the program will - whine about CARD-Services not being found, but it will continue. - This is necessary to read the NVRAM values. You want to know the - IRQ, port, and IOMEM values (the latter is called the CIS tuple by - 3COM). The first two can be set in the program, the third is - un-settable, and can only be read. Once you have these values, set - them in UserConfig and your card will be recognized. - -Q: FreeBSD finds my PCMCIA network card, but no packets appear to - be sent even though it claims to be working. - -A: Many PCMCIA cards have the ability to use either the 10-Base2 (BNC) - or 10-BaseT connectors for connecting to the network. The driver is - unable to 'auto-select' the correct connector, so you must tell it - which connector to use. In order to switch between the two - connectors, the link flags must be set. Depending on the model of - the card, '-link0 link1' or 'link0 -link1' will choose the correct - network connector. You can set these in sysinstall by using the - 'Extra options to ifconfig:' field in the network setup screen. - - -Q: The system finds my ed network card, but I keep getting device - timeout errors. - -A: Your card is probably on a different IRQ from what is specified in the - kernel configuration. The ed driver does not use the `soft' configuration - by default (values entered using EZSETUP in DOS), but it will use the - software configuration if you specify `?' in the IRQ field of your kernel - config file. - - Either move the jumper on the card to a hard configuration setting - (altering the kernel settings if necessary), or specify the IRQ as - `-1' in UserConfig or `?' in your kernel config file. This will - tell the kernel to use the soft configuration. - - Another possibility is that your card is at IRQ 9, which is shared - by IRQ 2 and frequently a cause of problems (especially when you - have a VGA card using IRQ 2! :). You should not use IRQ 2 or 9 if at - all possible. - - -Q: I go to boot from the hard disk for the first time after installing - FreeBSD, but the Boot Manager prompt just prints `F?' at the boot menu - each time but the boot won't go any further. - -A: The hard disk geometry was set incorrectly in the Partition editor when - you installed FreeBSD. Go back into the partition editor and specify - the actual geometry of your hard disk. You must reinstall FreeBSD - again from the beginning with the correct geometry. - - If you are failing entirely in figuring out the correct geometry for - your machine, here's a tip: Install a small DOS partition at the - beginning of the disk and install FreeBSD after that. The install - program will see the DOS partition and try to infer the correct - geometry from it, which usually works. - - If you are setting up a truly dedicated FreeBSD server or work- - station where you don't care for (future) compatibility with DOS, - Linux or another operating system, you've also got the option to use - the entire disk (`A' in the partition editor), selecting the - non-standard option where FreeBSD occupies the entire disk from - the very first to the very last sector. This will leave all geometry - considerations aside, but is somewhat limiting unless you're never - going to run anything other than FreeBSD on a disk. - -Q: I have a Matsushita/Panasonic drive but it isn't recognized by the - system. - -A: Make certain that the I/O port that the matcd driver is set to is - correct for the host interface card you have. (Some SoundBlaster DOS - drivers report a hardware I/O port address for the CD-ROM interface - that is 0x10 lower than it really is.) - - If you are unable to determine the settings for the card by examining - the board or documentation, you can use UserConfig to change the 'port' - address (I/O port) to -1 and start the system. This setting causes the - driver to look at a number of I/O ports that various manufacturers - use for their Matsushita/Panasonic/Creative CD-ROM interfaces. - Once the driver locates the address, you should run UserConfig again - and specify the correct address. Leaving the 'port' parameter set to -1 - increases the amount of time that it takes the system to boot, and - this could interfere with other devices. - - The double-speed Matsushita CR-562 and CR-563 are the only drives - that are supported. - - -Q: I booted the install floppy on my IBM ThinkPad (tm) laptop, and the - keyboard is all messed up. - -A: Older IBM laptops use a non-standard keyboard controller, so you must - tell the console driver (sc0) to go into a special mode which works - on the ThinkPads. Change the sc0 'Flags' to 0x10 in UserConfig and - it should work fine. (Look in the Input Menu for 'Syscons Console - Driver'.) - - -Q: I have a Matsushita/Panasonic CR-522, a Matsushita/Panasonic CR-523 or - a TEAC CD55a drive, but it is not recognized even when the correct I/O - port is set. +3Com 3C501 cards -A: These CD-ROM drives are currently not supported by FreeBSD. The command - sets for these drives are not compatible with the double-speed CR-562 - and CR-563 drives. - - The single-speed CR-522 and CR-523 drives can be identified by their - use of a CD-caddy. +3Com 3C503 Etherlink II +3Com 3c505 Etherlink/+ -Q: I'm trying to install from a tape drive but all I get is something like: - st0(aha0:1:0) NOT READY csi 40,0,0,0 - on the screen. Help! +3Com 3C507 Etherlink 16/TP -A: There's a limitation in the current sysinstall that the tape MUST - be in the drive while sysinstall is started or it won't be detected. - Try again with the tape in the drive the whole time. +3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA +(Fast) Etherlink III / (Fast) Etherlink XL +Toshiba ethernet cards -Q: I've installed FreeBSD onto my system, but it hangs when booting from - the hard drive with the message: ``Changing root to /dev/sd0a''. +PCMCIA ethernet cards from IBM and National Semiconductor are also +supported. -A: This problem may occur in a system with a 3com 3c509 Ethernet adaptor. - The ep0 device driver appears to be sensitive to probes for other - devices that also use address 0x300. Boot your FreeBSD system by power - cycling the machine (turn off and on). At the ``Boot:'' prompt specify - the ``-c''. This will invoke UserConfig (see Section 1. above). Use - the ``disable'' command to disable the device probes for all devices - at address 0x300 except the ep0 driver. On exit, your machine should - successfully boot FreeBSD. +Note that NO token ring cards are supported at this time as we're +still waiting for someone to donate a driver for one of them. Any +takers? -Q: My system hangs during boot, right after the "fd0: [my floppy drive]" - line. +4.3. Misc +---- ---- -A: This is not actually a hang, simply a very LONG "wdc0" probe that - often takes a long time to complete on certain systems (where there - usually _isn't_ a WD controller). Be patient, your system will boot! - To eliminate the problem, boot with the -c flag and eliminate the wdc0 - device, or compile a custom kernel. +AST 4 port serial card using shared IRQ. +ARNET 8 port serial card using shared IRQ. +ARNET (now Digiboard) Sync 570/i high-speed serial. -Q: My system can not find my Intel EtherExpress 16 card. +Boca BB1004 4-Port serial card (Modems NOT supported) +Boca IOAT66 6-Port serial card (Modems supported) +Boca BB1008 8-Port serial card (Modems NOT supported) +Boca BB2016 16-Port serial card (Modems supported) -A: You must set your Intel EtherExpress 16 card to be memory mapped at - address 0xD0000, and set the amount of mapped memory to 32K using - the Intel supplied softset.exe program. +Cyclades Cyclom-y Serial Board. +STB 4 port card using shared IRQ. -Q: When installing on an EISA HP Netserver, my on-board AIC-7xxx - SCSI controller isn't detected. +SDL Communications Riscom/8 Serial Board. +SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. -A: This is a known problem, and will hopefully be fixed in the future. - In order to get your system installed at all, boot with the -c - option into UserConfig, but _don't_ use the pretty visual mode but - the plain old CLI mode. Type +Specialix SI/XIO/SX multiport serial cards, with both the older +SIHOST2.x and the new "enhanced" (transputer based, aka JET) host cards. +ISA, EISA and PCI are supported. - eisa 12 - quit +Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, +ONboard 4/16 and Brumby. - there at the prompt. (Instead of `quit', you might also type - `visual', and continue the rest of the configuration session in - visual mode.) While it's recommended to compile a custom kernel, - dset(8) now also understands to save this value. +Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. - Refer to the FAQ topic 3.16 for an explanation of the problem, and - for how to continue. Remember that you can find the FAQ on your - local system in /usr/share/doc/FAQ, provided you have installed the - `doc' distribution. +Connectix QuickCam +Matrox Meteor Video frame grabber +Creative Labs Video Spigot frame grabber +Cortex1 frame grabber +Various Frame grabbers based on Brooktree Bt848 chip. +HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. -Q: I have this CMD640 IDE controller that is said to be broken. +Bus mice -A: Yes, it is. There's a workaround available now and it is enabled - automatically if this chip is used on your system. - For the details refer to the manual page of the disk driver (man 4 wd). +PS/2 mice +Standard PC Joystick -Q: On a Compaq Aero notebook, I get the message "No floppy devices found! - Please check ..." when trying to install from floppy. +X-10 power controllers -A: With Compaq being always a little different from other systems, they - do not announce their floppy drive in the CMOS RAM of an Aero notebook. - Therefore, the floppy disk driver assumes there is no drive configured. - Go to the UserConfig screen, and set the Flags value of the fdc0 device - to 0x1. This pretends the existance of the first floppy drive (as a - 1.44 MB drive) to the driver without asking the CMOS at all. +GPIB and Transputer drivers. +Genius and Mustek hand scanners. -Q: When I go to boot my Intel AL440LX ("Atlanta") -based system from the - hard disk the first time, it stops with a "Read Error" message. +Floppy tape drives (some rather old models only, driver rather stale) -A: There appears to be a bug in the BIOS on at least some of these boards, - this bug results in the FreeBSD bootloader thinking that it is booting - from a floppy disk. - This is only a problem if you are not using the BootEasy boot manager. - Slice the disk in 'compatible' mode and install BootEasy during the - FreeBSD installation to avoid the bug. -[ Please add more hardware tips to this Q&A section! ] +FreeBSD currently does NOT support IBM's microchannel (MCA) bus. diff --git a/release/sysinstall/help/install.hlp b/release/sysinstall/help/install.hlp index 4f153c8..11a39d5 100644 --- a/release/sysinstall/help/install.hlp +++ b/release/sysinstall/help/install.hlp @@ -2,229 +2,179 @@ | | | Table of Contents: | | | -| 0.0 Quick Start | -| 0.1 Installing FreeBSD for the impatient. | +| 0.0 Quick Start: | +| 0.1 Installing FreeBSD from CDROM or the Internet. | | | -| 1.0 DOS User's Q&A section. | -| 1.1 How do I make space for FreeBSD? | -| 1.2 Can I use compressed DOS filesystems from FreeBSD? | -| 1.3 Can I use DOS extended partitions? | -| 1.4 Can I run DOS executables under FreeBSD? | +| 1.0 Detail on various installation types: | +| 1.1 Installing from a network CDROM | +| 1.2 Installing from Floppies | +| 1.3 Installing from a DOS partition | +| 1.4 Installing from QIC/SCSI tape | +| 1.5 Installing over a network using NFS or FTP | +| 1.5.1 NFS Installation tips | +| 1.5.2 FTP Installation tips | | | -| 2.0 Preparing for the installation. | -| 2.1 Before installing from CDROM | -| 2.2 Before installing from Floppy | -| 2.3 Before installing from a DOS partition | -| 2.4 Before installing from QIC/SCSI tape | -| 2.5 Before installing over a network | -| 2.5.1 Preparing for NFS Installation | -| 2.5.2 Preparing for FTP Installation | -| | -| 3.0 Installing FreeBSD. | -| | -| 3.1 Repairing an existing FreeBSD installation. | -| | -| 3.2 Upgrading from earlier releases of FreeBSD. | +| 2.0 DOS User's Q&A section. | +| 2.1 How do I make space for FreeBSD? | +| 2.2 Can I use compressed DOS filesystems from FreeBSD? | +| 2.3 Can I use DOS extended partitions? | +| 2.4 Can I run DOS executables under FreeBSD? | | | +=====================================================================+ +Author: Jordan K. Hubbard +Last updated: Tue Mar 24 00:56:14 PST 1998 0.0 Quick Start -=== =========== - -This manual documents the process of installing FreeBSD on your -machine. Please also see the Hardware Guide (HARDWARE.TXT, or the -"Hardware" selection in the Documentation submenu of the boot floppy) -for hardware-specific installation instructions if you're not sure how -to configure your hardware or don't know what sorts of things one -should watch out for with PC UNIXes in general or FreeBSD in -particular. - - -0.1 Installing FreeBSD for the impatient: - -So, you'd like to get started right away and a 3-chapter installation -guide is not for you, eh? No problem. First off, you need to get -yourself into the FreeBSD installation procedure. Assuming that you -have either a supported CDROM drive and an installation CD, or you -have a fast, reliable Internet connection to one of the FreeBSD mirror -sites, then this can be easily accomplished in one of three ways: +--- ----------- + +This manual documents the process of making a new installation of +FreeBSD on your machine. If you are upgrading from a previous +release of FreeBSD, please see the file UPGRADE.TXT for important +information on upgrading. If you are not familiar with configuring +PC hardware for FreeBSD, you should also read the HARDWARE.TXT file - +it contains important information which may save you a lot of grief. + +If you're new to FreeBSD then you should also read EVERYTHING listed +in the Documentation menu on the boot floppy. It may seem like a lot +to read, but the time you spend now reading the documents will be made +up many times over because you were adequately prepared. Also, you will +know the types of information available should you get stuck later. +Once the system is installed, you can also revisit this menu and use a +WEB browser to read the installed FAQ (Frequently Asked Questions) and +Handbook HTML documentation sets for FreeBSD. You can also use the +browser to visit other WEB sites on the net (like http://www.freebsd.org) +if you have an Internet connection. See ABOUT.TXT for more information +on the resources available to you. + +The best laid plans sometimes go awry, so if you run into trouble take a +look at TROUBLE.TXT which contains valuable troubleshooting information. + +DISCLAIMER: While FreeBSD does its best to safeguard against +accidental loss of data, it's still more than possible to WIPE OUT +YOUR ENTIRE DISK with this installation! Please do not proceed to the +final FreeBSD installation menu unless you've adequately backed up any +important data first! We really mean it! + +FreeBSD requires a 386 or better processor to run (sorry, there is no +support for '286 processors), 5 megs of RAM to install and 4 megs of +ram to run. You will need at least 80 megs of hard drive space free +on either a dedicated disk or a "primary," (not extended partition, +to use the DOS terminology). See below for ways to shrink existing +DOS partitions to install FreeBSD. + + +0.1 Installing FreeBSD from CDROM or the Internet +--- --------------------------------------------- + +The easiest type of installation is from CD. If you have a supported +CDROM drive and a FreeBSD installation CD from Walnut Creek CDROM, +there are 3 ways of starting the installation from it: 1. If your system supports bootable CDROM media (usually an option which can be selectively enabled in the controller's setup menu or in the PC BIOS for some systems) and you have it enabled, FreeBSD 2.2.1 and later CDs support the "El Torrito" bootable - CD standard and simply having the 1st CD in your CDROM drive - during system boot will cause the installation to be executed. + CD standard. Simply put the installation CD in your CDROM drive + and boot the system to begin installation. - - 2. If you have a FreeBSD distribution CD which you can see - from DOS, first disable any fancy memory managers you may - have configured and do this: + 2. If you have drivers which allow you to see your CDROM drive + from from DOS, first disable any fancy memory managers you may + have configured, change directory to the CDROM (E:\ in the example + below) and then type this: E> install - You should boot directly into the FreeBSD installation - screen. - - NOTE: If this fails for any reason, go to step 3: + and you should boot directly into the FreeBSD installation. + If either steps fail, please go on to step 3. 3. Build a FreeBSD boot floppy from the floppies/boot.flp - file in a FreeBSD distribution. If you have a CD distribution, - simply run the ``makeflp.bat'' script, otherwise read - floppies/README.TXT for information on how to "image copy" - this file onto a floppy. Then simply boot directly from the - floppy and you should go into the installation after making a - stop at the kernel configuration menu. - - -Once you're in the installation screen, you should be able to follow -the various menu prompts and go from there. If you've never used the -FreeBSD installation before, you are also encouraged to read some of -the documentation in the first "Usage" menu choice, as well as the -various docs in the Documentation submenu (though if you're reading -this section, you're probably not about to do any of that :-). - -Remember: If you get stuck at a screen, hit F1 for the online -documentation for that section. It may not always be the best -written doc around, but it's usually a lot better than nothing! - -If you have a network connection (either ppp/slip or dedicated) the -installation will manage the outgoing connection for you in fetching -any additional distribution bits you may need along the way. If -you're using a CDROM, this is even more painless as no network -connection is needed unless you require DES bits or other -export-restricted software (all of which are available without -restriction as after-installation components from -ftp.internat.freebsd.org). If you're going to do a DOS install, -you should simply run the ``setup.exe'' program now and follow -its instructions. - -The FreeBSD installer supports the direct use of floppy, DOS, tape, -CDROM, FTP, NFS and UFS partitions as installation media, and further -information on installing from each type of media is contained below -if this "quick start" section is not enough to get you going. See the -appropriate section in the table of contents. - - - -1.0 DOS user's Question and Answer section -=== ====================================== - -1.1 Help! I have no space! Do I need to delete everything first? - -If your machine is already running DOS and has little or no free space -available for FreeBSD's installation, all is not lost! You may find -the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD -CDROM or on the various FreeBSD ftp sites, to be quite useful. - -FIPS allows you to split an existing DOS partition into two pieces, -preserving the original partition and allowing you to install onto the -second free piece. You first "defrag" your DOS partition, using the -DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS. It -will prompt you for the rest of the information it needs. Afterwards, -you can reboot and install FreeBSD on the new partition. Also note -that FIPS will create the second partition as a "clone" of the first, -so you'll actually see that you now have two DOS Primary partitions -where you formerly had one. Don't be alarmed! You can simply delete -the extra DOS Primary partition (making sure it's the right one by -examining its size! :) - -See the Distributions menu for an estimation of how much free space -you'll need for the kind of installation you want. + file in a FreeBSD distribution. Either simply use the + ``makeflp.bat'' script from DOS or read floppies/README.TXT + for more information on creating bootable floppies under + different operating systems. Then you simply boot + from the floppy and you should go into the FreeBSD + installation. +If you don't have a CDROM and would like to simply install over the +net using PPP, slip or a dedicated connection, simply fetch the +<FreeBSD-release>/floppies/boot.flp file from: -1.2 Can I use compressed 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/dblspaced file!). DO NOT -REMOVE THAT FILE as you will probably regret it greatly! - -It is probably better to create another uncompressed DOS primary -partition and use this for communications between DOS and FreeBSD if -such is your desire. + ftp://ftp.freebsd.org/pub/FreeBSD +or one of its many mirrors (http://www.freebsd.org/handbook/mirrors.html) +and follow step 3 above. You should also read the floppies/README.TXT +file as it contains important information for downloaders. -1.3 Can I mount my DOS extended partitions? +Once you have a boot floppy made, please go to section 1.5 of this +document for additional tips on installing via FTP or NFS. -Yes. DOS extended partitions are mapped in at the end of the other -``slices'' in FreeBSD, e.g. your D: drive might be /dev/sd0s5, your E: -drive /dev/sd0s6, and so on. This example assumes, of course, that -your extended partition is on SCSI drive 0. For IDE drives, substitute -``wd'' for ``sd'' appropriately. You otherwise mount extended -partitions exactly like you would mount any other DOS drive, e.g.: -mount -t msdos /dev/sd0s5 /dos_d +1.0 Detail on various installation types +--- ------------------------------------ +Once you've gotten yourself to the initial installation screen +somehow, you should be able to follow the various menu prompts and go +from there. If you've never used the FreeBSD installation before, you +are also encouraged to read some of the documentation in the the +Documentation submenu as well as the general "Usage" instructions on +the first menu. -1.4 Can I run DOS binaries under FreeBSD? + REMEMBER: If you get stuck at a screen, hit F1 for the online + documentation for that section. -Not yet! We'd like to add support for this someday, but are still -lacking anyone to actually do the work. Ongoing work with BSDI's -RUNDOS utility may bring this much closer to being a reality sometime -soon. Send mail to freebsd-hackers@FreeBSD.org if you're interested in -joining this effort! +If you've never installed FreeBSD before, or even if you have, the +"Novice" installation mode is the most recommended since it makes sure +that you'll visit all the various important checklist items along the +way. If you're much more comfortable with the FreeBSD installation +process and know _exactly_ what you want to do, use the Express or +Custom installation options. If you're upgrading an existing system, +use the Upgrade option. -There is, however, a neat utility called "pcemu" in the ports -collection which emulates an 8088 and enough BIOS services to run DOS -text mode applications. It requires the X Window System (provided as -XFree86 3.2) to operate. - - - -2.0 Preparing for the installation -=== ============================== - -2.1 Before installing from CDROM: +The FreeBSD installer supports the direct use of floppy, DOS, tape, +CDROM, FTP, NFS and UFS partitions as installation media, further tips +on installing from each type of media listed below. -If your CDROM is of an unsupported type, then please skip to section -2.3 which describes how to install from a DOS partition. -There is not a lot of preparatory work that needs to be done to -successfully install from one of Walnut Creek's FreeBSD CDROMs (other -CDROM distributions may work as well, though we cannot say for certain -as we have no hand or say in how they're created). You can either -boot into the CD installation directly from DOS using Walnut Creek's -supplied ``install.bat'' batch file or you can make a boot floppy with -the ``makeflp.bat'' command. +1.1 Installing from a network CDROM +--- ------------------------------- -For the easiest interface of all (from DOS), type "view". This will -bring up a DOS menu utility that leads you through all the available -options. +If you simply wish to install from a local CDROM drive then see the +Quick Start section. If you don't have a CDROM drive on your system +and wish to use a FreeBSD distribution CD in the CDROM drive of +another system to which you have network connectivity, there are +several ways of going about it: -Once you've booted from DOS or floppy, you should then be able to -select CDROM as the media type in the Media menu and load the entire -distribution from CDROM (note: If you have only one CDROM drive, and -the appropriate FreeBSD CDROM is detected in it, it will be selected -automatically as your media). +1. If you would be able to FTP install FreeBSD directly from the CDROM + drive in some FreeBSD machine, it's quite easy: You simply add the + following line to the password file (using the vipw command): -After your system is fully installed and you have rebooted from the -hard disk, you can also mount the cdrom at any time by typing: ``mount -/cdrom''. Before removing the CD again, also note that it's necessary -to first type ``umount /cdrom''. Don't just remove it from the drive! + ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin -SPECIAL NOTE: Before invoking the installation, be sure that the CDROM -is in the drive so that the "probe" can find it! This is also true if -you wish the CDROM to be added to the default system configuration -automatically during the install (whether or not you actually use it -as the installation media). +And anyone else on your network will now be able to chose a Media type +of FTP and type in: ``ftp://<machine with CDROM drive>'' after picking +"Other" in the ftp sites menu. -INSTALLATION TIP: If you would like people to be able to FTP install -FreeBSD directly from the CDROM in your machine, you'll 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): +2. If you would rather use NFS to export the CDROM directly to the + machine(s) you'll be installing from, you need to first add an + entry to the /etc/exports file (on the machine with the CDROM drive) + which looks something like this: - ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent + /cdrom -ro ziggy.foo.com -Anyone else at your site will now be able to chose a Media type of FTP -and type in: ftp://<your machine> after picking "Other" in the ftp -sites menu to install directly from the CD in your machine. + To allow the machine "ziggy.foo.com" to mount the CDROM directly + via NFS during installation. The machine with the CDROM must also + be configured as an NFS server, of course, and if you're not sure how + to do that then an NFS installation is probably not the best choice + for you unless you're willing to read up on rc.conf(5) and configure + things appropriately. Assuming that this part goes smoothly, you + should be able to enter: <cdrom-host>:/cdrom as the path for an NFS + installation when the target machine is installed. -2.2 Before installing from Floppy: +1.2 Installing from Floppies +--- ------------------------ If you must install from floppy disks, either due to unsupported hardware or just because you enjoy doing things the hard way, you must @@ -232,6 +182,10 @@ first prepare some floppies for the install. First, make a boot floppy as described in floppies/README.TXT +Second, read the file LAYOUT.TXT and pay special attention to the +"Distribution format" section since it describes which files you're +going to need to put onto floppy and which you can safely skip. + Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files in the bin (binary distribution) directory. If you're preparing these floppies under DOS, then THESE floppies *must* be @@ -239,7 +193,7 @@ formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File Manager format command. Don't trust Factory Preformatted floppies! Format them again -yourself, just to make sure! Many problems reported by our users in +yourself, just to make sure. Many problems reported by our users in the past have resulted from the use of improperly formatted media, which is why I'm taking such special care to mention it here! @@ -273,7 +227,8 @@ Once you come to the Media screen of the install, select "Floppy" and you'll be prompted for the rest. -2.3 Before installing from a DOS partition: +1.3 Installing from a DOS partition +--- ------------------------------- To prepare for installation from an MS-DOS partition you should simply copy the files from the distribution into a directory called @@ -304,14 +259,13 @@ this - disable QEMM or EMM386 if they're running before trying this) or making a boot floppy as described in section 0.1. +1.4 Installing from QIC/SCSI Tape +--- ----------------------------- -2.4 Before installing from QIC/SCSI Tape: - -Installing from tape is probably the easiest method, short of an -on-line install using FTP or a CDROM. The installation program -expects the files to be simply tar'ed onto the tape, so after getting -all of the files for the distributions you're interested in, simply -tar them onto the tape with a command like: +When installing from tape, the installation program expects the files +to be simply tar'ed onto it, so after fetching all of the files for +the distributions you're interested in, simply tar them onto the tape +with a command something like this: cd /where/you/have/your/dists tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 @@ -332,20 +286,20 @@ Now create a boot floppy as described in section 0.1 and proceed with the installation. -2.5 Before installing over a network: +1.5 Installing over a network using FTP or NFS +--- ------------------------------------------ -After making a boot floppy, as described in section 2.1, you can load -the rest of the installation over a network. - -You can do network installations over 3 types of connections: +After making a boot floppy as described in the first section, you can +load the rest of the installation over a network using one of 3 types +of connections: Serial port: SLIP / PPP Parallel port: PLIP (using ``laplink'' style cable) Ethernet: A standard Ethernet controller (including - some PCMCIA). + certain PCCARD devices). -Serial Port: ------------- +Serial Port +----------- SLIP support is rather primitive, and is limited primarily to hard-wired links, such as a serial cable running between two @@ -366,31 +320,34 @@ dialing out with your particular brand of modem as the PPP dialer provides only a very simple terminal emulator. -Parallel Port: --------------- +Parallel Port +------------- If a hard-wired connection to another FreeBSD (2.0R or later) or Linux machine is available, you might also consider installing over a "laplink" style parallel port cable. The data rate over the parallel port is much higher than what is typically possible over a serial line -(up to 50k/sec), thus resulting in a quicker installation. +(up to 50k/sec), thus resulting in a quicker installation. It's not +typically necessary to use "real" IP addresses when using a +point-to-point parallel cable in this way and you can generally just +use RFC 1918 style addresses for the ends of the link (e.g. 10.0.0.1, +10.0.0.2, etc). -IMPORTANT NOTE: If you use a Linux machine as your PLIP peer, you will -also have to specify "link0" in the TCP/IP setup screen's ``extra -options for ifconfig'' field. +IMPORTANT NOTE: If you use a Linux machine rather than a FreeBSD +machine as your PLIP peer, you will also have to specify "link0" in +the TCP/IP setup screen's ``extra options for ifconfig'' field. -Ethernet: ---------- +Ethernet +-------- -For the fastest possible network installation, an Ethernet adaptor is -always a good choice! FreeBSD supports most common PC Ethernet cards, -a table of supported cards (and their required settings) being -provided as part of the FreeBSD Hardware Guide (see the Documentation -menu on the boot floppy or the top level directory of the CDROM). If -you are using one of the supported PCMCIA Ethernet cards, also be sure -that it's plugged in _before_ the laptop is powered on! FreeBSD does -not, unfortunately, currently support "hot insertion" of PCMCIA cards. +FreeBSD supports most common PC Ethernet cards, a table of supported +cards (and their required settings) being provided as part of the +FreeBSD Hardware Guide (see the Documentation menu on the boot floppy +or the top level directory of the CDROM). If you are using one of the +supported PCMCIA Ethernet cards, also be sure that it's 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. @@ -403,13 +360,15 @@ provider's IP address) to use in talking to it. If you do not know the answers to these questions then you should really probably talk to your system administrator _first_ before trying this type of installation! Using a randomly chosen IP address -or netmask on a live network will almost certainly get you shot. +or netmask on a live network will almost certainly get you shot at +dawn. Once you have a network connection of some sort working, the installation can continue over NFS or FTP. -2.5.1 Preparing for NFS installation: +1.5.1 NFS installation tips +----- --------------------- NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution files you want onto a server somewhere @@ -437,12 +396,13 @@ installation can continue over NFS or FTP. properly enabled! -2.5.2 Preparing for FTP Installation +1.5.2 FTP Installation tips +----- --------------------- FTP installation may be done from any mirror site containing a - reasonably up-to-date version of FreeBSD 2.2. A full menu of + reasonably up-to-date version of FreeBSD. A full menu of reasonable choices for almost any location in the world is - provided in the FTP site menu. + provided in the FTP site menu during installation. If you are installing from some other FTP site not listed in this menu, or you are having troubles getting your name server @@ -480,183 +440,77 @@ installation can continue over NFS or FTP. Where "1234" is the port number of the proxy ftp server. +2.0 DOS user's Question and Answer section +--- -------------------------------------- + +2.1 Help! I have no space! Do I need to delete everything first? +--- -------------------------------------------------------------- + +If your machine is already running DOS and has little or no free space +available for FreeBSD's installation, all is not lost! You may find +the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD +CDROM or on the various FreeBSD ftp sites, to be quite useful. + +FIPS allows you to split an existing DOS partition into two pieces, +preserving the original partition and allowing you to install onto the +second free piece. You first "defrag" your DOS partition, using the +DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS. It +will prompt you for the rest of the information it needs. Afterwards, +you can reboot and install FreeBSD on the new partition. Also note +that FIPS will create the second partition as a "clone" of the first, +so you'll actually see that you now have two DOS Primary partitions +where you formerly had one. Don't be alarmed! You can simply delete +the extra DOS Primary partition (making sure it's the right one by +examining its size! :) -3.0 Installing FreeBSD ---- ------------------ - -Once you've taken note of the appropriate preinstallation steps, you -should be able to install FreeBSD without any further trouble. - -Should the installation fail at some stage, then you may wish to go -back and re-read the relevant preparation section (section 2.x) for -the installation media type you're trying to use. Perhaps there's a -helpful hint there that you missed the first time? If you're having -hardware trouble or FreeBSD refuses to boot at all, then read the -Hardware Guide again for a list of possible solutions. - -The FreeBSD boot floppy contains all the on-line documentation you -should need to be able to navigate through an installation, and if it -doesn't then I'd like to know what you found most confusing so that I -can fix it in future releases! It is the objective of the FreeBSD -installation program (sysinstall) to be self-documenting enough that -painful "step-by-step" guides are no longer necessary. +NOTE: FIPS does NOT currently work with FAT32 or VFAT style partitions +as used by newer versions of Windows 95. To split up such a +partition, you will need a commercial product such as Partition Magic +3.0. Sorry, but this is just the breaks if you've got a Windows +partition hogging your whole disk and you don't want to reinstall from +scratch. -Installation type overview: +2.2 Can I use compressed DOS filesystems from FreeBSD? +--- -------------------------------------------------- -o Custom installation: +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/dblspaced file!). DO NOT +REMOVE THAT FILE as you will probably regret it greatly! + +It is probably better to create another uncompressed DOS primary +partition and use this for communications between DOS and FreeBSD if +such is your desire. + + +2.3 Can I mount my DOS extended partitions? +--- --------------------------------------- + +Yes. DOS extended partitions are mapped in at the end of the other +``slices'' in FreeBSD, e.g. your D: drive might be /dev/sd0s5, your E: +drive /dev/sd0s6, and so on. This example assumes, of course, that +your extended partition is on SCSI drive 0. For IDE drives, substitute +``wd'' for ``sd'' appropriately. You otherwise mount extended +partitions exactly like you would mount any other DOS drive, e.g.: + +mount -t msdos /dev/sd0s5 /dos_d + + +2.4 Can I run DOS binaries under FreeBSD? +--- ------------------------------------- + +Not yet! We'd like to add support for this someday, but are still +lacking anyone to actually do the work. Ongoing work with BSDI's +doscmd utility is bringing this much closer to being a reality in +FreeBSD-current (AKA 3.0) and you should send mail to +freebsd-hackers@FreeBSD.org if you're interested in joining this +effort! -You can do anything you like in this menu without altering your system -_except_ for "Commit", which will perform any pending actions you may -have selected. Some of the menu options will also have direct `Write' -commands available for committing an operation immediately, but they -should only be used if you're *absolutely sure* it's necessary. It's -generally safer to stack up your changes and then commit them all at -once so that you're left with the option of changing your mind up to -the very last moment. In particular, the (W)rite options in the fdisk -and label screens WILL NOT WORK for a new installation! They're meant -for tweaking *existing* installations, not doing new ones. Use the -final commit option as there is no advantage whatsoever to be gained -in writing the information out stage by stage in a new installation. - -If you're confused at any point, the F1 key will pull up what is -hopefully some helpful information for the screen you're in. +There is also a neat utility called "pcemu" in the ports collection +which emulates an 8088 and enough BIOS services to run DOS text mode +applications. It requires the X Window System (provided as XFree86 +3.2) to operate. -o Express installation: - -This installation will invoke all the appropriate steps in order as if -you'd selected them one by one from the custom installation menu. It -assumes that you *know what you are doing* and have run the -installation at least once before. If this is not the case, the -Novice installation method is recommended. - - -o Novice installation: - -The Novice installation leads you through the required stages in the -proper order and presents you with various helpful prompts in between. -Once the system is installed, it will also present you with the -opportunity to perform a variety of "post install" actions. - -A quick synopsis of the stages involved in a novice installation -follows: - - o The first step is the `Partition Editor', which allows - you to chose how your drives will be used for FreeBSD. - If you're dedicating an entire drive to FreeBSD, the - `A' command is probably all you need to type here, otherwise - move to a partition marked `Unused' (or delete an existing one) - and use the `C' command to create a FreeBSD partition in its - place. - - o Next, with the `Label Editor', you can specify how the space - in any FreeBSD partitions should be used by FreeBSD. You - can also mount any non-FreeBSD partitions (such as DOS) in this - screen. If you want the standard layout, simply type `A' for - the defaults. - - o Next, the `Distributions' menu allows you to specify how much - of FreeBSD you'd like to load. A good choice is the "User" - distribution for a small system or the "Developer" distribution - for someone wanting a more programmer-oriented configuration. - If none of the existing collections seem applicable, select - Custom to choose the component distributions yourself. - - o Next, the `Media' menu allows you to specify what kind of - media you wish to install from. If a given media type requires - extra information, such as networking information for an FTP - or NFS install, it will also be asked for at this point. - - o Finally, you'll be prompted to commit all of these actions at - once (nothing has been written to your disk so far, nor will - it until you give the final confirmation). - - All new or changed partition information will be written - out, file systems will be created and/or non-destructively - labeled (depending on how you set their newfs flags in the - Label Editor) and all selected distributions will be - extracted. - - o After the system is fully installed, you'll then have the - option to configure the system in various ways, install a - WEB server, etc. - -At this point, you're generally done with the sysinstall utility and -can reboot the system. If you elected to install the boot manager, -you should now see a small boot menu with an `F?' prompt. Press the -function key corresponding to the BSD partition and you should boot up -into FreeBSD off the hard disk. - -If this fails to happen for some reason, see the Q & A section of the -Hardware Guide for possible clues! The most likely problem is a -mis-matched disk geometry, which will have to be corrected with a -second pass through the install, using the (G) command in the fdisk -menu to properly set the geometry the next time. - -Should you wish to re-enter this installation later, you will find it -under /stand/sysinstall on the installed system. - -Good luck! If you really get stuck, you may send mail to our support -mailing list - freebsd-questions@FreeBSD.org. We'll do our best to help you! - - -3.1 Repairing an existing FreeBSD installation. ---- ------------------------------------------- - -FreeBSD 2.2 now features a "Fixit" option in the top menu of the boot -floppy. To use it, you will also need a fixit.flp image floppy, -generated in the same fashion as the boot floppy, or the 2nd CDROM -from Walnut Creek CDROM's FreeBSD distribution. - -To invoke fixit, simply boot the boot floppy, chose the "Fixit" item -and insert the fixit floppy or CDROM when asked. You will then be -placed into a shell with a wide variety of commands available (in the -/stand and /mnt2/stand directories) for checking, repairing and -examining file systems and their contents. Some UNIX administration -experience *is* required to use the fixit option! - - -3.2 Upgrading from earlier releases of FreeBSD. ---- ------------------------------------------- - -It must first be said that the system installation boot floppy's -"Upgrade" option DOES NOT take a particularly sophisticated approach to -the problem of upgrading, it being more of an attempt to provide the very -minimum in what is necessary to upgrade from one release to the next. -A more polished upgrade that dealt properly with the broad spectrum of -installed 2.1 systems would be nice to have, but until that gets -written what you get is this - the brute-force approach! - -What this upgrade will attempt to do is best summarized thusly: - - 1. fsck and mount all file systems chosen in the label editor. - 2. Ask for a location to preserve your /etc directory into and do so. - 3. Extract all selected distributions on top of your existing system. - 4. Copy certain obvious files back from the preserved /etc, leaving the - rest of the /etc file merge up to the user. - 5. Drop user in a shell so that they may perform that merge before - rebooting into the new system. - -And that's it! This "upgrade" is not going to hold your hand in all -major respects, it's simply provided to make one PART of the upgrade -easier. - -IMPORTANT NOTE: What this upgrade procedure may also do, in fact, is -completely destroy your system (though much more quickly than you -would have been able to destroy it yourself). It is simply impossible -to guarantee that this procedure's crude form of upgrade automation -will work in all cases and if you do this upgrade without proper -BACKUPS for any important data then you really must like living life -close to the edge, that's all we can say! - -NOTE to 2.0 users: We're sorry, but the "slice" changes that were -added in FreeBSD 2.0.5 made automated upgrades pretty difficult due to -the fact that a complete reinstall is pretty much called for. Things -may still *work* after a 3.0 upgrade, but you will also no doubt -receive many warnings at boot time about non-aligned slices and such; -we really do recommend a fresh installation for 2.0 systems! (But -back up your user data first :-). - - Jordan - ---- End of Installation Guide --- diff --git a/release/sysinstall/help/network_device.hlp b/release/sysinstall/help/network_device.hlp index 7151e91..3519c0f 100644 --- a/release/sysinstall/help/network_device.hlp +++ b/release/sysinstall/help/network_device.hlp @@ -33,7 +33,7 @@ If a hard-wired connection to another FreeBSD (2.0R 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, and speeds -of up to 50KB/sec are not uncommon. +of over 50KB/sec are not uncommon. Finally, for the fastest possible network installation, an Ethernet adaptor is always a good choice! FreeBSD supports most common PC diff --git a/release/sysinstall/help/readme.hlp b/release/sysinstall/help/readme.hlp index 91ebff0..900079a 100644 --- a/release/sysinstall/help/readme.hlp +++ b/release/sysinstall/help/readme.hlp @@ -13,41 +13,84 @@ FreeBSD development community. O O ) / | Feedback or offers to help with anything <----. __ / __ \ you see in this release are most welcome <----|====O)))==) \) /==== and should be sent to one of the approp- <----' `--' `.__,' \ -riate mailing lists (see notes below). | | - \ / /\ -Please note that SNAPSHOT releases, as much ______( (_ / \______/ -as we enjoy seeing them tested in serious ,' ,-----' | -situations, are NOT recommended for production `--{__________) -environments! They are first and foremost test -vehicles used by the project to periodically give testers or developers -access to the latest -current technology. They are not put through the -same quality assurance mechanisms that full releases are! - -For the latest errata information (security hole & fix information, -bugs fixes, documentation updates, etc.), should there be any for this -release, please see: +riate mailing lists - please see the | | +ABOUT.TXT file for more information. \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + - http://www.freebsd.org/releases/[releaseversion]/errata.html + Most files here are also in the Documentation + Menu of the boot floppy -Or the file: +ROAD MAP: - ERRATA.TXT + README.TXT This file -In the base directory of the distribution. + ABOUT.TXT All about FreeBSD, including contact information + RELNOTES.TXT Release Notes - what's new & different in this + release -** Most files here are also in the Documentation Menu of the boot floppy ** + LAYOUT.TXT Information about the layout of the release + directory. If you are installing from floppies, + it is especially important that you + *read this section!* -ROAD MAP: + ERRATA.TXT Any late-breaking errata information for this + release. On FTP sites, this file may be frequently + updated so it's a good idea to check it first + (the master copy is always on ftp.freebsd.org) + before reporting problems + + HARDWARE.TXT Information about the configuration of the + GENERIC kernel and supported hardware + + INSTALL.TXT How to make a new installation of FreeBSD + on your PC using the data you see here + + UPGRADE.TXT How to upgrade an existing FreeBSD + installation + + TROUBLE.TXT Troubleshooting information + + +o For new installation instructions, see the INSTALL.TXT + and HARDWARE.TXT files. + +o If you are upgrading from a previous FreeBSD version, + please take a look at UPGRADE.TXT. + +o It is also important to check the ERRATA.TXT file for any + late-breaking issues with this release. This file contains + the latest information on upgrade, security or other problems + which an administrator should be aware of. + +o Information regarding problems which arise after the CD + is printed can be found at: + ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/ERRATA.TXT + +For the most up-to-date software along the RELENG_2_2 branch +(also known as -Stable) which is now proceeding onwards toward +the release of FreeBSD 2.2.7, please install from: + + ftp://releng22.freebsd.org/pub/FreeBSD/ + +Or for the latest 3.0-Current (HEAD branch) snapshot releases, +please install from: + + ftp://current.freebsd.org/pub/FreeBSD + +If you plan to run either -Stable or -Current you MUST be +subscribed to the appropriate mailing list, either +freebsd-stable or freebsd-current. For information on +subscribing to either list (or both), send an e-mail to +majordomo@freebsd.org with the following in the body, not +the subject of the letter as appropriate: + +subscribe freebsd-stable +subscribe freebsd-current +end - ERRATA.TXT Errata information for this release (optional file). - README.TXT This file. - ABOUT.TXT All about FreeBSD and the physical organization - of this distribution. - INSTALL.TXT How to install FreeBSD on your PC using the files - you'll find here. - HARDWARE.TXT PC Hardware information & troubleshooting guide. - RELNOTES.TXT Release Notes - what's new & different in this - release. - ---- +We hope you enjoy using FreeBSD as much as we enjoyed +creating it. :) diff --git a/release/sysinstall/help/register.hlp b/release/sysinstall/help/register.hlp index a7b397c..3f360c3 100644 --- a/release/sysinstall/help/register.hlp +++ b/release/sysinstall/help/register.hlp @@ -72,5 +72,5 @@ contender. Regards, - Jordan Hubbard, - FreeBSD PR Officer + Jordan Hubbard, + FreeBSD PR Officer diff --git a/release/sysinstall/help/shortcuts.hlp b/release/sysinstall/help/shortcuts.hlp index 34a9eec..40cd1a4 100644 --- a/release/sysinstall/help/shortcuts.hlp +++ b/release/sysinstall/help/shortcuts.hlp @@ -97,7 +97,7 @@ mediaSetFtpUserPass Prompt for FTP username and password mediaSetCPIOVerbosity Prompt for CPIO verbosity mediaGetType Prompt for media type optionsEditor Go to options editor -register Go to registration editor. +register Go to registration editor. Examples: diff --git a/release/sysinstall/help/trouble.hlp b/release/sysinstall/help/trouble.hlp index 62061d9..b550165 100644 --- a/release/sysinstall/help/trouble.hlp +++ b/release/sysinstall/help/trouble.hlp @@ -244,7 +244,7 @@ A: With Compaq being always a little different from other systems, they do not announce their floppy drive in the CMOS RAM of an Aero notebook. Therefore, the floppy disk driver assumes there is no drive configured. Go to the UserConfig screen, and set the Flags value of the fdc0 device - to 0x1. This pretends the existance of the first floppy drive (as a + to 0x1. This pretends the existence of the first floppy drive (as a 1.44 MB drive) to the driver without asking the CMOS at all. diff --git a/release/sysinstall/help/upgrade.hlp b/release/sysinstall/help/upgrade.hlp index 282a382..9920948 100644 --- a/release/sysinstall/help/upgrade.hlp +++ b/release/sysinstall/help/upgrade.hlp @@ -1,38 +1,167 @@ -Welcome to the 2.2.5 upgrade procedure! - -It must first be said that this upgrade DOES NOT take a particularly -sophisticated approach to the upgrade problem, it being more a -question of providing what seemed "good enough" at the time. A truly -polished upgrade that deals properly with the broad spectrum of -installed 2.x systems would be nice to have, but until that gets -written what you get is this - the brute-force approach! - -What this upgrade will attempt to do is best summarized thusly: - - 1. fsck and mount all file systems chosen in the label editor. - 2. Ask for a location to preserve your /etc directory into. - 3. Extract all selected distributions on top of your existing system. - 4. Copy certain obvious files back from the preserved /etc, leaving the - rest of the /etc file merge up to the user. - 5. Drop user in a shell so that they may perform that merge before - rebooting into the new system. - -And that's it! This "upgrade" is not going to hold your hand to any -major degree, it's simply provided to make one PART of the upgrade -easier. - -IMPORTANT NOTE: What this upgrade procedure may also do, in fact, is -completely destroy your system (though much more quickly than you -would have been able to destroy it yourself). It is simply impossible -to guarantee that this procedure's crude form of upgrade automation -will work in all cases and if you do this upgrade without proper -BACKUPS for any important data then you really must like living life -close to the edge, that's all we can say! - -NOTE to 2.0 users: We're sorry, but the "slice" changes that were -added in FreeBSD 2.0.5 made automated upgrades pretty difficult due to -the fact that a complete reinstall is pretty much called for. Things -may still *work* after an upgrade, but you will also no doubt receive -many warnings at boot time about non-aligned slices and such; we -really do recommend a fresh installation for 2.0 systems! (But back -up your user data first :-). ++===================== Upgrading FreeBSD ==========================+ +| | +| 0.0 Preface | +| 0.1 DISCLAIMER | +| 0.2 IMPORTANT NOTE | +| | +| 1.0 Introduction | +| 1.1 Upgrade Overview | +| | +| 2.0 Procedure | +| 2.1 Backup | +| 2.2 Mount Filesystems | +| 2.3 Select Distributions | +| 2.4 After Installation | +| | +| 3.0 Alternative Upgrade Techniques | +| | ++=====================================================================+ + +0.1 DISCLAIMER +--- ---------- + +While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to WIPE OUT YOUR +ENTIRE DISK with this installation! Please do not accept the final +confirmation request unless you have adequately backed up any important +data files. + +0.2 IMPORTANT NOTE +--- -------------- + +See section 2.4 for important details regarding changes to the +/etc/fstab file required during the upgrade procedure. + +1.0 Introduction +--- ------------ + +The upgrade procedure replaces distributions selected by the user +with those corresponding to the new FreeBSD release. It preserves +standard system configuration data, as well as user data, installed +packages and other software. + +Administrators contemplating an upgrade are encouraged to study this +document in its entirety before commencing an upgrade. Failure to do so +may result in a failed upgrade or loss of data. + +1.1 Upgrade Overview +--- ---------------- +Upgrading of a distribution is performed by extracting the new version of +the component over the top of the previous version. Files belonging to +the old distribution are not deleted. + +System configuration is preserved by retaining and restoring the +previous version of the following files: + + Xaccel.ini, adduser.conf, aliases, aliases.db, amd.map, crontab, + csh.cshrc, csh.login, csh.logout, daily, disktab, dm.conf, exports, + fbtab, fstab, ftpusers, gettytab, gnats, group, host.conf, hosts, + hosts.equiv, hosts.lpd, inetd.conf, kerberosIV, localtime, login.access, + mail.rc, make.conf, manpath.config, master.passwd, mib.txt, modems, + monthly, motd, namedb, networks, passwd, phones, ppp, printcap, + profile, protocols, pwd.db, rc, rc.firewall, rc.i386, rc.local, + rc.network, rc.conf, remote, resolv.conf, rmt, security, sendmail.cf, + services, shells, skeykeys, spwd.db, supfile, syslog.conf, termcap, + ttys, uucp, weekly + +The versions of these files which correspond to the new version are +moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files +are interdependent, and the best merge procedure is to copy all +site-specific data from the current files into the new. + +During the upgrade procedure, the administrator is prompted for a +location into which all files from /etc/ are saved. In the event that +local modifications have been made to other files, they may be +subsequently retrieved from this location. + +2.0 Procedure +--- --------- + +This section details the upgrade procedure. Particular attention is +given to items which substantially differ from a normal installation. + +2.1 Backup +--- ------ + +User data and system configuration should be backed up before +upgrading. While the upgrade procedure does its best to prevent +accidental mistakes, it is possible to partially or completely destroy +data and configuration information. + +2.2 Mount Filesystems +--- ----------------- + +The disklabel editor is entered with the nominated disk's filesystem +devices listed. Prior to commencing the upgrade, the administrator +should make a note of the device names and corresponding mountpoints. +These mountpoints should be entered here. DO NOT set the 'newfs flag' +for any filesystems, as this will cause data loss. + +2.3 Select Distributions +--- -------------------- + +When selecting distributions, there are no constraints on which must be +selected. As a general rule, the 'bin' distribution should be selected +for an update, and the 'man' distribution if manpages are already +installed. Other distributions may be selected beyond those originally +installed if the administrator wishes to add additional functionality. + +2.4 After Installation +--- ------------------ + +Once the installation procedure has completed, the administrator is +prompted to examine the new configuration files. At this point, checks +should be made to ensure that the system configuration is valid. In +particular, the /etc/rc.conf and /etc/fstab files should be checked. + +Read the following, but DO NOT update /etc/fstab as described below +until the new system has booted correctly. The upgrade procedure +replaces the previous FreeBSD kernel with a GENERIC kernel, and a custom +kernel may need to be generated to suit the local system configuration. + +IMPORTANT NOTE: +============== +FreeBSD 2.2.6 introduces a change in the naming of the device from +which the root filesystem is mounted. This change affects all systems, +however user intervention is only required for systems undergoing an +upgrade installation. + +Previously, the root filesystem was always mounted from the +compatibility slice, while other partitions on the same disk were +mounted from their true slice. This might, for example, have resulted +in an /etc/fstab file like: + +# Device Mountpoint FStype Options Dump Pass# +/dev/wd0s2b none swap sw 0 0 +/dev/wd0a / ufs rw 1 1 +/dev/wd0s2f /local0 ufs rw 1 1 +/dev/wd0s2e /usr ufs rw 1 1 + +For FreeBSD 2.2.6 and later, this format changes so that the device for +'/' is consistent with others, ie. + +# Device Mountpoint FStype Options Dump Pass# +/dev/wd0s2b none swap sw 0 0 +/dev/wd0s2a / ufs rw 1 1 +/dev/wd0s2f /local0 ufs rw 1 1 +/dev/wd0s2e /usr ufs rw 1 1 + + +If /etc/fstab is not updated manually in this case, the system will +issue a warning message whenever / is mounted (normally at startup) +indicating the change that must be made. In addition, trouble may be +experienced if the root filesystem is not correctly unmounted, whereby +the root filesystem will not be marked clean at the next reboot. + +This change should be made as soon as the upgraded system has been +successfully rebooted. + +3.0 Alternative Upgrade Techniques +--- ------------------------------ + +Those interested in an upgrade method that allows more flexibility and +sophistication should take a look at the "Upgrading FreeBSD from source" +tutorial found at http://www.freebsd.org/docs.html. This method +requires reliable network connectivity, extra disk space and spare time, +but has advantages for networks and other more complex installations. diff --git a/release/sysinstall/help/usage.hlp b/release/sysinstall/help/usage.hlp index 6b9a1e8..4d94520 100644 --- a/release/sysinstall/help/usage.hlp +++ b/release/sysinstall/help/usage.hlp @@ -59,11 +59,10 @@ it's also useful when dealing with sub-shells or other "wizard modes" that don't use menus and tend to scroll their output off the top of the screen. -Once the system is fully installed and running multi-user, you will -find that you have multiple "virtual consoles" which you can use to in -order to have several active sessions at once. Use ALT-F<n> to switch -between screens, where `F<n>' is the function key corresponding to the -screen you wish to see. By default, the system comes with 3 virtual -consoles enabled - you can enable more by editing the /etc/ttys file -and turning the "off" field to "on" in the relevant vty entries (up to -12). +FreeBSD also supports multiple "virtual consoles" which you can use to +in order to have several active sessions at once. Use ALT-F<n> to +switch between screens, where `F<n>' is the function key corresponding +to the screen you wish to see. By default, the system comes with 3 +virtual consoles enabled - you can enable more by editing the +/etc/ttys file and turning the "off" field to "on" in the relevant vty +entries (up to 12). |
