Index: stable/4/release/doc/en_US.ISO8859-1/installation/alpha/Makefile =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/alpha/Makefile (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/alpha/Makefile (revision 82389) @@ -1,20 +1,20 @@ # $FreeBSD$ RELN_ROOT?= ${.CURDIR}/../../.. DOC?= article FORMATS?= html INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # SGML content SRCS+= article.sgml SRCS+= ../common/artheader.sgml +SRCS+= ../common/abstract.sgml SRCS+= ../common/install.sgml -SRCS+= ../common/floppies.sgml SRCS+= ../common/layout.sgml SRCS+= ../common/trouble.sgml SRCS+= ../common/upgrade.sgml .include "${RELN_ROOT}/share/mk/doc.relnotes.mk" .include "${DOC_PREFIX}/share/mk/doc.project.mk" Index: stable/4/release/doc/en_US.ISO8859-1/installation/alpha/article.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/alpha/article.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/alpha/article.sgml (revision 82389) @@ -1,27 +1,27 @@ %man; %authors; %mlists; %release; %sections; ]>
&artheader; +&abstract; §.install; §.layout; -§.floppies; §.upgrade; §.trouble;
Index: stable/4/release/doc/en_US.ISO8859-1/installation/common/floppies.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/common/floppies.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/common/floppies.sgml (nonexistent) @@ -1,83 +0,0 @@ - - - - Floppy Disk Image Instructions - - For a normal CDROM or network installation, all you need to - copy onto actual floppies from the floppies/ directory are the - kern.flp and mfsroot.flp - images (for 1.44MB floppies). - - Getting these images over the network is easy. simply fetch - the - release/floppies/kern.flp - and - release/floppies/mfsroot.flp - files from ftp://ftp.FreeBSD.org/pub/FreeBSD - or one of the many mirrors listed at http://www.FreeBSD.org/handbook/mirrors.html. - - - Get two blank, freshly formatted floppies and image copy - kern.flp onto one and mfsroot.flp onto the other. These images are - not DOS files! You cannot simply copy them to a DOS or UFS floppy - as regular files, you need to image copy them to the floppy with - fdimage.exe under DOS (see the - tools directory on your CDROM or &os; FTP - mirror) or the &man.dd.1; command in UNIX. - - For example, to create the kernel floppy image from DOS, you'd - do something like this: - - C> fdimage kern.flp a: - - Assuming that you'd copied fdimage.exe and kern.flp into a directory - somewhere. You would do the same for mfsroot.flp, of course. - - If you're creating the boot floppy from a UNIX machine, you - may find that: - - &prompt.root; dd if=floppies/kern.flp of=/dev/rfd0 - - or - - &prompt.root; dd if=floppies/kern.flp of=/dev/floppy - - work well, depending on your hardware and operating system - environment (different versions of UNIX have totally different names - for the floppy drive). - - If you're on an alpha machine that can network-boot its - floppy images or you have a 2.88MB or LS-120 floppy capable of - taking a 2.88MB image on an x86 machine, you may wish to use - the older (but now twice as large) boot.flp image which we also - provide. That contains the contents of kern.flp and mfsroot.flp on - a single floppy, essentially. This file should also be used as the - boot file for those mastering El Torito bootable CD images. See - the &man.mkisofs.8; command for more information. - - Going to two installation boot floppies is a step we - definitely would have rather avoided but we simply no longer could - due to general code bloat and &os;'s many new device drivers in - GENERIC. - - One positive side-effect of this new organizational scheme, - however, is that it also allows one to easily make one's own - kern.flp or mfsroot.flp floppies - should a need to customize some aspect of the installation process - or use a custom kernel for an otherwise unsupported piece of - hardware arise. As long as the kernel is compiled with - options MFS and options - MFS_ROOT, it will properly look for and boot an - mfsroot.flp image in memory when run (see how - /boot/loader.rc in - kern.flp does its thing). The - mfsroot.flp image is also just a gzip'd - filesystem image which is used as root, something which can be made - rather easily using &man.vnconfig.8;. If none of that makes any - sense to you then don't worry about it - just use the - kern.flp and mfsroot.flp - images as described above. - - Property changes on: stable/4/release/doc/en_US.ISO8859-1/installation/common/floppies.sgml ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: stable/4/release/doc/en_US.ISO8859-1/installation/common/install.ent =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/common/install.ent (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/common/install.ent (revision 82389) @@ -1,15 +1,15 @@ + - Index: stable/4/release/doc/en_US.ISO8859-1/installation/common/install.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/common/install.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/common/install.sgml (revision 82389) @@ -1,798 +1,893 @@ Installing &os; - - Quick Start + This section documents the process of installing a new + distribution of &os;. These instructions pay particular emphasis to + the process of obtaining the &os; &release.current; distribution and + to beginning the installation procedure. The Installing + FreeBSD + chapter of the FreeBSD + Handbook provides more in-depth information about the + installation program itself, including a guided walkthrough with + screenshots. - This manual documents the process of making a new - installation of &os; on your machine. If you are upgrading - from a previous release of &os;, please see - for important information on upgrading. If you are - not familiar with configuring hardware for &os;, you should - also read the HARDWARE.TXT file - it contains important - information which may save you a lot of grief. + If you are upgrading from a previous release + of &os;, please see for instructions on + upgrading. - If you're new to &os; then you should also read - everything listed in the Documentation menu - of the installer. 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 &os;. Note that on-line - versions of the FAQ and Handbook are also - available from the FreeBSD Project Web - site, if you have an Internet connection. See - README.TXT for more information on the - resources available to you. + + Getting Started + Probably the most important pre-installation step that can + be taken is that of reading the various instruction documents + provided with &os;. A roadmap of documents pertaining to this + release of &os; can be found in README.TXT, + which can usually be found in the same location as this file; most + of these documents, such as the release notes and the hardware + compatability list, are also accessible in the Documentation menu + of the installer. + + Note that on-line versions of the &os; FAQ and Handbook are also + available from the FreeBSD + Project Web site, if you have an Internet + connection. + + This collection of documents may seem daunting, but the time + spent reading them will likely be saved many times over. Being + familiar with what resources are available can also be helpful in + the event of problems during installation. + The best laid plans sometimes go awry, so if you run into trouble take a look at , which contains valuable troubleshooting information. You should also read - ERRATA.TXT before installing and follow the - pointers there carefully since this will stop you from falling - over any problems which have reported in the interim for your + an updated copy of + ERRATA.TXT before installing, + since this will alert you to + any problems which have reported in the interim for your particular release. While &os; 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 if you make a - mistake! Please do not proceed to the final &os; + mistake. Please do not proceed to the final &os; installation menu unless you've adequately backed up any - important data first! We really mean it! + important data first. + + Hardware Requirements + &os; for the &arch; requires a 386 or better processor to run (sorry, there is no support for 286 processors) and at least 5 megs of RAM to install and 4 megs of RAM to run. You will need at least 100MB of free hard drive space for the most minimal installation. See below for ways of shrinking existing DOS partitions in order to install &os;. &os; for the &arch; supports the alpha platforms described in HARDWARE.TXT. You will need a dedicated disk for FreeBSD/alpha. It is not possible to share a disk with another operating system at this time. This disk will need to be attached to a SCSI controller which is supported by the SRM firmware or an IDE disk assuming the SRM in your machine supports booting from IDE disks. Your root filesystem MUST be the first partition (partition a) on the disk to be bootable. You will need the SRM console firmware for your platform. In some cases, it is possible to switch between AlphaBIOS (or ARC) firmware and SRM. In others it will be necessary to download new firmware from the vendor's Web site. - + If you are + not familiar with configuring hardware for &os;, you should + be sure to read the HARDWARE.TXT file; + it contains important + information on what hardware is supported by &os;. + + + + Floppy Disk Image Instructions + + Depending on how you choose to install &os;, you may need to + create a set of floppy disks (usually two) to begin the installation + process. This section briefly describes how to create these disks, + either from a CDROM installation or from the Internet. Note that in + the common case of installing &os; from CDROM, on a machine that + supports bootable CDROMs, the steps outlined in this section will + not be needed and can be skipped. + + For a normal CDROM or network installation, all you need to + copy onto actual floppies from the floppies/ directory are the + kern.flp and mfsroot.flp + images (for 1.44MB floppies). + + Getting these images over the network is easy. Simply fetch + the + release/floppies/kern.flp + and + release/floppies/mfsroot.flp + files from + or one of the many mirrors listed at FTP + Sites section of the Handbook, or on the + Web pages. + + + Get two blank, freshly formatted floppies and image copy + kern.flp onto one and mfsroot.flp onto the other. These images are + not DOS files. You cannot simply copy them to a DOS or UFS floppy + as regular files, you need to image copy them to the floppy with + fdimage.exe under DOS (see the + tools directory on your CDROM or &os; FTP + mirror) or the &man.dd.1; command in UNIX. + + For example, to create the kernel floppy image from DOS, you'd + do something like this: + + C> fdimage kern.flp a: + + Assuming that you'd copied fdimage.exe and kern.flp into a directory + somewhere. You would do the same for mfsroot.flp, of course. + + If you're creating the boot floppy from a UNIX machine, you + may find that: + + &prompt.root; dd if=floppies/kern.flp of=/dev/rfd0 + + or + + &prompt.root; dd if=floppies/kern.flp of=/dev/floppy + + work well, depending on your hardware and operating system + environment (different versions of UNIX have different names + for the floppy drive). + + If you're on an alpha machine that can network-boot its + floppy images or you have a 2.88MB or LS-120 floppy capable of + taking a 2.88MB image on an x86 machine, you may wish to use + the single (but twice as large) boot.flp image. + It contains the contents of kern.flp and mfsroot.flp on + a single floppy. This file should also be used as the + boot file for those mastering El Torito bootable CD images. See + the &man.mkisofs.8; command for more information. + + + Installing &os; from CDROM or the Internet The easiest type of installation is from CDROM. If you have a supported CDROM drive and a &os; installation CDROM, there are 2 ways of starting the installation from it: 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, &os; supports the El Torrito bootable CD standard. Simply put the installation CD in your CDROM drive and boot the system to begin installation. Build a set of &os; boot floppies from the floppies/ directory in every &os; distribution. Either simply use the makeflp.bat script from DOS or read for more information on creating the bootable floppies under different operating systems. Then you simply boot from the first floppy and you should soon be in the &os; installation. + If you don't have a CDROM (or your computer does not + support booting from CDROM) and would like to simply install + over the net using PPP, SLIP or a dedicated connection. + You should start the installation by building + a set of FreeBSD boot floppy from the files + floppies/kern.flp and + floppies/mfsroot.flp using the instructions + found in . Restart your computer using + the kern.flp disk; when prompted, insert + the mfsroot.flp disk. Then, please go to + for additional tips on installing + via FTP or NFS. + The easiest type of installation is from CDROM. If you have a supported CDROM drive and a FreeBSD installation CDROM, you can boot FreeBSD directly from the CDROM. Insert the CDROM into the drive and type the following command to start the installation (substituting the name of the appropriate CDROM drive if necessary): >>>boot dka0 Alternatively you can boot the installation from floppy disk. You should start the installation by building a set of FreeBSD boot floppy from the files floppies/kern.flp and floppies/mfsroot.flp using the instructions found in . From the SRM console prompt (>>>), just insert the kern.flp floppy and type the following command to start the installation: >>>boot dva0 Insert the mfsroot.flp floppy when prompted and you will end up at the first screen of the install program. - - If you don't have a CDROM and would like to simply install - over the net using PPP, SLIP or a dedicated connection, see - for instructions on - making boot floppies. Then please go to - for additional tips on installing - via FTP or NFS. - - 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 &os; installation before, you are also encouraged to read some of the documentation in the Documentation submenu as well as the general Usage instructions on the first menu. - If you get stuck at a screen, hit the F1 key for online + If you get stuck at a screen, press the F1 key for online documentation relevant to that specific section. If you've never installed &os; before, or even if you have, the Standard 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 &os; 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. The &os; 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 are listed below. Once the install procedure has finished, you will be able to start &os;/&arch; by typing something like this to the SRM prompt: >>>boot dkc0 This instructs the firmware to boot the specified disk. To find the SRM names of disks in your machine, use the show device command: >>>show device dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476 dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658 dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015 dva0.0.0.0.1 DVA0 ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01 pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27 pqa0.0.0.4.0 PQA0 PCI EIDE pqb0.0.1.4.0 PQB0 PCI EIDE This example is from a Digital Personal Workstation 433au and shows three disks attached to the machine. The first is a CDROM called dka0 and the other two are disks and are called dkc0 and dkc100 repectively. You can specify which kernel file to load and what boot options to use with the and options, for example: >>> boot -file kernel.old -flags s To make &os;/&arch; boot automatically, use these commands: >>> set boot_osflags a >>> set bootdef_dev dkc0 >>> set auto_action BOOT Installing from a Network CDROM If you simply wish to install from a local CDROM drive - then see . If you don't have a CDROM + then see . If you don't have a CDROM drive on your system and wish to use a &os; distribution CD in the CDROM drive of another system to which you have network connectivity, there are also several ways of going about it: If you would be able to FTP install &os; directly from the CDROM drive in some &os; machine, it's quite easy: You simply add the following line to the password file (using the &man.vipw.8; command): ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin On the machine on which you are running the install, go to the Options menu and set Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking URL in the ftp sites menu. This may allow anyone on the local network (or Internet) to make anonymous FTP connections to this machine, which may not be desirable. 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). The example below allows the machine ziggy.foo.com to mount the CDROM directly via NFS during installation: /cdrom -ro ziggy.foo.com 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 &man.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, e.g. wiggy:/cdrom. 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 first prepare some floppies for the install. First, make your boot floppies as described in . Second, peruse 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 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 users in the past have resulted - from the use of improperly formatted media. + Frequently, floppy disks come factory + preformatted. While convenient, + many problems reported by users in the past have resulted + from the use of improperly formatted media. + Re-format them yourself, just to make sure. If you're creating the floppies from another &os; machine, a format is still not a bad idea though you don't need to put a DOS filesystem on each floppy. You can use the &man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a floppy, as the following sequence of commands 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 After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto 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've got all the distributions you want packed up in this fashion. Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ... The bin.inf file also needs to go on the first floppy of the bin set since it is read by the installation program in order to figure out how many additional pieces to look for when fetching and concatenating the distribution. When putting distributions onto floppies, the distname.inf file must occupy the first - floppy of each distribution set! This is also covered in + floppy of each distribution set. This is also covered in README.TXT. Once you come to the Media screen of the install, select Floppy and you'll be prompted for the rest. 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 FREEBSD on the Primary DOS partition (C:). For example, to do a minimal installation of &os; from DOS using files copied from the CDROM, you might do something like this: C:\> MD C:\FREEBSD -C:\>XCOPY /S E:\BIN C:\FREEBSD\BIN +C:\> XCOPY /S E:\BIN C:\FREEBSD\BIN Assuming that E: was where your CD was mounted. For as many distributions as you wish to install from DOS (and you have free space for), install each one in a directory under C:\FREEBSD - the BIN dist is only the minimal requirement. Once you've copied the directories, you can simply launch the installation from floppies as normal and select DOS as your media type when the time comes. Installing from QIC/SCSI Tape 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 use &man.tar.1; to get them onto the tape with a command something like this: &prompt.root; cd /where/you/have/your/dists &prompt.root; tar cvf /dev/rsa0 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'll be allowed to choose) to accommodate the full contents of the tape you've 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 + quite a bit of temporary storage. You should expect to require as much temporary storage as you have stuff written on tape. When going to do the installation, the tape must be in the drive before booting from the boot floppies. The installation probe may otherwise fail to find it. - Now create a boot floppy as described in and + Now create a boot floppy as described in and proceed with the installation. Installing over a Network using FTP or NFS After making the boot floppies 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, parallel port, or Ethernet. Serial Port SLIP support is rather primitive, and is limited primarily to hard-wired links, such as a serial cable running between two computers. The link must be hard-wired because the SLIP installation doesn't currently offer a dialing capability. If you need to dial out with a modem or otherwise dialog with the link before connecting to it, then I recommend that the PPP utility be used instead. If you're using PPP, make sure that you have your Internet Service Provider's IP address and DNS information handy as you'll need to know it fairly early in the installation process. You may also need to know your own IP address, though PPP supports dynamic address negotiation and may be able to pick up this information directly from your ISP if they support it. You will also need to know how to use the various AT commands for dialing out with your particular brand of modem as the PPP dialer provides only a very simple terminal emulator. Parallel Port If a hard-wired connection to another &os; 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. 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). If you use a Linux machine rather than a &os; machine as your PLIP peer, you will also have to specify in the TCP/IP setup screen's extra options for ifconfig field in order to be compatible with Linux's slightly different PLIP protocol. Ethernet - &os; supports most common PC Ethernet cards, a table - of supported cards (and their required settings) being - provided as part of the &os; Hardware Guide (see the - Documentation menu on the boot floppy or the top level + &os; supports many common Ethernet cards; a table + of supported cards is + provided as part of the &os; Hardware Notes (see + HARDWARE.TXT in + 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! &os; does + plugged in before the laptop is powered on. &os; 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 value for your subnet and the name of your machine. Your system administrator can tell you which values are appropriate to your particular network setup. If you will be referring to other hosts by name rather than IP address, you'll also need a name server and possibly the address of a gateway (if you're using PPP, it's your provider's IP address) to use in talking to it. If you want to install by FTP via an HTTP proxy (see below), you will also need the proxy's address. 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 at - dawn. + installation. Using a randomly chosen IP address or netmask + on a live network is almost guaranteed not to work, and will + probably result in a lecture from said system administrator. Once you have a network connection of some sort working, the installation can continue over NFS or FTP. NFS installation tips NFS installation is fairly straight-forward: Simply copy the &os; distribution files you want onto a server somewhere and then point the NFS media selection at it. If this server supports only privileged port access (this is generally the default for Sun and Linux 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 also support subdir mounts, e.g. if your &os; distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy 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 option. Other NFS servers may have different conventions. If you are getting Permission Denied messages from the server then it's likely that you don't have this - properly enabled! + properly enabled. FTP Installation tips FTP installation may be done from any mirror site containing a reasonably up-to-date version of &os;. A full menu of reasonable choices for almost any location in the world is 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 configured properly, you can also specify your own URL by selecting the URL choice in that menu. A URL can contain a hostname or an IP address, so something like the following would work in the absence of a name server: ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE There are three FTP installation modes you can use: FTP: This method uses the standard Active mode for transfers, in which the server initiates a connection to the client. This will not work through most firewalls but will often work best with older FTP servers that do not support passive mode. If your connection hangs with passive mode, try this - one! + one. FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening connections to the client. This option is best for users to pass through firewalls that do not allow incoming connections on random port addresses. FTP via an HTTP proxy: This option instructs &os; to use HTTP 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 an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP server. In the rare case that you have an FTP proxy that does not go through HTTP, you can specify the URL as something like: ftp://foo.bar.com:port/pub/FreeBSD In the URL above, port is the port number of the proxy FTP server. Tips for Serial Console Users If you'd like to install &os; on a machine using just a serial port (e.g. you don't have or wish to use a VGA card), please follow these steps: Connect some sort of ANSI (vt100) compatible terminal or terminal emulation program to the COM1 port of the PC you are installing &os; onto. Unplug the keyboard (yes, that's correct!) and then try to boot from floppy or the installation CDROM, depending on the type of installation media you have, with the keyboard unplugged. If you don't get any output on your serial console, plug the keyboard in again and wait for some beeps. If you are booting from the CDROM, proceed to as soon as you hear the beep. For a floppy boot, the first beep means to remove the kern.flp floppy and insert the mfsroot.flp floppy, after which you should press Enter and wait for another beep. Hit the space bar, then enter boot -h and you should now definitely be seeing everything on the serial port. If that still doesn't work, check your serial cabling as well as the settings on your terminal emulation program or actual terminal device. It should be set for 9600 baud, 8 bits, no parity. Question and Answer Section for &arch; Architecture Users 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 &os;'s installation, all is not lost! You may find the FIPS utility, provided in the tools/ subdirectory on the &os; CDROM or on the various &os; 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 &os; 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! :) + it's the right one by examining its size). 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. 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. Can I use compressed DOS filesystems from &os;? No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), &os; 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 extended partition and use this for communications between DOS and &os; if such is your desire. Can I mount my DOS extended partitions? Yes. DOS extended partitions are mapped in at the end of the other slices in &os;, 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. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: &prompt.root; mount -t msdos /dev/da0s5 /dos_d Can I run DOS binaries under &os;? Ongoing work with BSDI's &man.doscmd.1; utility will suffice in many cases, though it still has some rough edges. If you're interested in working on this, please send mail to the &a.emulation and indicate that you're interested in joining this ongoing effort! - There is also a neat utility called pcemu in the + The emulators/pcemu port/package in the &os; Ports Collection which emulates an 8088 and enough BIOS services to run DOS text mode applications. It requires the X Window System (XFree86) to operate. Can I boot from the ARC or Alpha BIOS Console? No. &os;, like Compaq Tru64 and VMS, will only boot from the SRM console. Help! I have no space! Do I need to delete everything first? Unfortunately, yes. Can I mount my Compaq Tru64 or VMS extended partitions? No, not at this time. What about support for Compaq Tru64 (OSF/1) binaries? &os; can run Tru64 applications very well using the - emulators/osf1_base port/package. + emulators/osf1_base port/package. What about support for Linux binaries? At the moment, &os; cannot run AlphaLinux. Support is currently being worked on. What about support for NT Alpha binaries? &os; is not able to run NT applications natively, although it has the ability to mount NT partitions. Index: stable/4/release/doc/en_US.ISO8859-1/installation/common/layout.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/common/layout.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/common/layout.sgml (revision 82389) @@ -1,133 +1,154 @@ Distribution Format A typical &os; distribution directory looks something like this: - -ABOUT.TXT bin compat3x games proflibs -HARDWARE.TXT compat1x info src tools -INSTALL.TXT compat20 dict manpages packages -README.TXT compat21 crypto doc -RELNOTES.TXT compat22 floppies ports -XF86336 +ERRATA.HTM README.TXT compat1x dict manpages +ERRATA.TXT RELNOTES.HTM compat20 doc packages +HARDWARE.HTM RELNOTES.TXT compat21 docbook.css ports +HARDWARE.TXT XF86336 compat22 floppies proflibs +INSTALL.HTM bin compat3x games src +INSTALL.TXT catpages compat4x info tools +README.HTM cdrom.inf crypto kernel If you want to do a CDROM, FTP or NFS installation from this distribution directory, all you need to do is make the 1.44MB boot floppies from the floppies directory (see for instructions on how to do this), boot them and follow the instructions. The rest of the data needed during the installation will be obtained automatically based on your selections. If you've never installed &os; before, you also want to read the entirety of this document (the installation instructions) file. If you're trying to do some other type of installation or are merely curious about how a distribution is organized, what follows is a more thorough description of each item in more detail: - The *.TXT files obviously contain - documentation (this file is INSTALL.TXT) and should be read - before starting an installation. + The *.TXT and + *.HTM files contain + documentation (for example, this document is contained in both + INSTALL.TXT and + INSTALL.HTM) and should be read + before starting an installation. The + *.TXT files are plain text, while the + *.HTM files are HTML files that can be + read by almost any Web browser. Some distributions may + contain documentation in other formats as well, such as PDF or + PostScript. + docbook.css is a Cascading Style + Sheet (CSS) file used by some Web browsers for formatting the + HTML documentation. + + The XF86336 directory contains the XFree86 project's 3.3.6 release and consists of a series of gzip'd tar files which contain each component of the XFree86 distribution. - The bin, dict, crypto, doc, games, info, manpages, - proflibs, and src directories contain the primary distribution + The bin, + catpages, + crypto, + dict, + doc, + games, + info, + manpages, + proflibs, and + src directories contain the primary distribution components of &os; itself and are split into smaller files for easy packing onto floppies (should that be necessary). - The compat1x, compat20, compat21, compat22, and compat3x + The compat1x, + compat20, + compat21, + compat22, + compat3x, and + compat4x directories contain distributions for compatibility with older releases and are distributed as single gzip'd tar files - they can be installed during release time or later by running their install.sh scripts. The floppies/ subdirectory contains the floppy installation images; further information on using them can be found in . The packages and ports directories contain the &os; - packages and ports collections. Packages may be installed from + Packages and Ports Collections. Packages may be installed from the packages directory by running the command: &prompt.root;/stand/sysinstall configPackages Packages can also be installed by feeding individual filenames in packages/ to the &man.pkg.add.1; command. - The ports collection may be installed like any other + The Ports Collection may be installed like any other distribution and requires about 100MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or locally from /usr/share/doc/handbook if you've installed the doc distribution. Last of all, the tools directory contains various DOS tools for discovering disk geometries, installing boot managers and the like. It is purely optional and provided only for user convenience. - A typical distribution (we'll use the info distribution as an - example) looks like this internally: + A typical distribution directory (for example, the info distribution) looks like this internally: CHECKSUM.MD5 info.ab info.ad info.inf install.sh info.aa info.ac info.ae info.mtree The CHECKSUM.MD5 file contains MD5 signatures for each file, should data corruption be suspected, and is purely for reference. It is not used by the actual installation and does not need to be copied with the rest of the distribution files. The info.a* files are split, gzip'd tar files, the contents of which can be viewed by doing: &prompt.root; cat info.a* | tar tvzf - During installation, they are automatically concatenated and extracted by the installation procedure. The info.inf file is also necessary since it is read by the installation program in order to figure out how many pieces to look for when fetching and concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set! The info.mtree file is another non-essential file which is provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be later used with the &man.mtree.8; program to verify the installation permissions and checksums against any possible modifications to the file. When used with the bin distribution, this can be an excellent way of detecting trojan horse attacks on your system. Finally, the install.sh file is for use by those who want to install the distribution after installation time. To install the info distribution from CDROM after a system was installed, for example, you'd do: &prompt.root; cd /cdrom/info &prompt.root; sh install.sh - - And that's all there is to it! Each distribution contains its - own install.sh file for this. - Index: stable/4/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml (revision 82389) @@ -1,529 +1,530 @@ Troubleshooting Repairing an Existing &os; Installation - &os; releases 2.2.1 and later feature a + &os; features a Fixit option in the top menu of the boot floppy. To use it, you will also need either a fixit.flp image floppy, generated in the same - fashion as the boot floppy, or the 2nd CDROM from Walnut Creek - CDROM's &os; distribution. + fashion as the boot floppy, or the live filesystem + CDROM; typically the second CDROM in a multi-disc &os; + distribution. To invoke fixit, simply boot the kern.flp floppy, choose 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! + use the fixit option. Common Installation Problems, Q&A I go to boot from the hard disk for the first time after installing &os;, the kernel loads and probes my hardware, but stops with messages like: changing root device to wd1s1a panic: cannot mount root What is wrong? What can I do? What is this bios_drive:interface(unit,partition)kernel_name thing that is displayed with the boot help? There is a longstanding problem in the case where the boot disk is not the first disk in the system. The BIOS uses a different numbering scheme to &os;, and working out which numbers correspond to which is difficult to get right. In the case where the boot disk is not the first disk in the system, &os; can need some help finding it. There are two common situations here, and in both of these cases, you need to tell &os; where the root filesystem is. You do this by specifying the BIOS disk number, the disk type and the &os; disk number for that type. The first situation is where you have two IDE disks, each configured as the master on their respective IDE busses, and wish to boot &os; from the second disk. The BIOS sees these as disk 0 and disk 1, while &os; sees them as wd0 and wd2. &os; is on BIOS disk 1, of type wd and the &os; disk number is 2, so you would say: 1:wd(2,a)kernel Note that if you have a slave on the primary bus, the above is not necessary (and is effectively wrong). The second situation involves booting from a SCSI disk when you have one or more IDE disks in the system. In this case, the &os; disk number is lower than the BIOS disk number. If you have two IDE disks as well as the SCSI disk, the SCSI disk is BIOS disk 2, type da and &os; disk number 0, so you would say: 2:da(0,a)kernel To tell &os; that you want to boot from BIOS disk 2, which is the first SCSI disk in the system. If you only had one IDE disk, you would use '1:' instead. Once you have determined the correct values to use, you can put the command exactly as you would have typed it in the /boot.config file using a standard text editor. Unless instructed otherwise, &os; will use the contents of this file as the default response to the boot: prompt. I go to boot from the hard disk for the first time after installing &os;, but the Boot Manager prompt just prints F? at the boot menu each time but the boot won't go any further. The hard disk geometry was set incorrectly in the Partition editor when you installed &os;. Go back into the partition editor and specify the actual geometry of your hard disk. You must reinstall &os; again from the beginning with the correct geometry. If you are failing entirely in figuring out the correct geometry for your machine, here's a tip: Install a small DOS partition at the beginning of the disk and install &os; after that. The install program will see the DOS partition and try to infer the correct geometry from it, which usually works. The following tip is no longer recommended, but is left here for reference:
If you are setting up a truly dedicated &os; server or workstation where you 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 &os; occupies the entire disk from the very first to the very last sector. This will leave all geometry considerations aside, but is somewhat limiting unless you're never going to run anything other than &os; on a disk.
Known Hardware Problems, Q&A Please send hardware tips for this section to &a.jkh;. The &man.mcd.4; driver keeps thinking that it has found a device and this stops my Intel EtherExpress card from working. Use the UserConfig utility (see HARDWARE.TXT) 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. &os; claims to support the 3Com PCMCIA card, but my card isn't recognized when it's plugged into my laptop. There are a couple of possible problems. First of all, &os; 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 &os;, and depend on the card's own configuration data stored in NVRAM to work. You must correctly configure &os;'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. &os; finds my PCMCIA network card, but no packets appear to be sent even though it claims to be working. 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, or will choose the correct network connector. You can set these in &man.sysinstall.8; by using the Extra options to ifconfig: field in the network setup screen. The system finds my &man.ed.4; network card, but I keep getting device timeout errors. Your card is probably on a different IRQ from what is specified in the 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 + (especially when you have a VGA card using IRQ 2!). You should not use IRQ 2 or 9 if at all possible. I have a Matsushita/Panasonic drive but it isn't recognized by the system. Make certain that the I/O port that the &man.matcd.4; 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. I booted the install floppy on my IBM ThinkPad (tm) laptop, and the keyboard is all messed up. Older IBM laptops use a non-standard keyboard controller, so you must tell the keyboard driver (atkbd0) to go into a special mode which works on the ThinkPads. Change the atkbd0 'Flags' to 0x4 in UserConfig and it should work fine. (Look in the Input Menu for 'Keyboard'.) When I try to boot the install floppy, I see the following message and nothing seems to be happening. I cannot enter anything from the keyboard either. Keyboard: no Due to lack of space, full support for old XT/AT (84-key) keyboards is no longer available in the bootblocks. Some notebook computers may also have this type of keyboard. If you are still using this kind of hardware, you will see the above message appears when you boot from the CD-ROM or an install floppy. As soon as you see this message, hit the space bar, and you will see the prompt: >> FreeBSD/i386 BOOT Default: x:xx(x,x)/boot/loader boot: Then enter -Dh, and things should proceed normally. 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. These CD-ROM drives are currently not supported by &os;. 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. I'm trying to install from a tape drive but all I get is something like this on the screen: sa0(aha0:1:0) NOT READY csi 40,0,0,0 There's a limitation in the current &man.sysinstall.8; that the tape must be in the drive while &man.sysinstall.8; is started or it won't be detected. Try again with the tape in the drive the whole time. I've installed &os; onto my system, but it hangs when booting from the hard drive with the message: Changing root to /dev/da0a his problem may occur in a system with a 3com 3c509 Ethernet adapter. The &man.ep.4; device driver appears to be sensitive to probes for other devices that also use address 0x300. Boot your &os; system by power cycling the machine (turn off and on). At the Boot: prompt specify the . This will invoke UserConfig (see 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 &os;. My system can not find my Intel EtherExpress 16 card. 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. When installing on an EISA HP Netserver, my on-board AIC-7xxx SCSI controller isn't detected. 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 option into UserConfig, but don't use the pretty visual mode but the plain old CLI mode. Type: eisa 12 quit 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 now also understands to save this value. 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. I have a Panasonic AL-N1 or Rios Chandler Pentium machine and I find that the system hangs before ever getting into the installation now. Your machine doesn't like the new i586_copyout and i586_copyin code for some reason. To disable this, boot the installation boot floppy and when it comes to the very first menu (the choice to drop into kernel UserConfig mode or not) choose the command-line interface (expert mode) version and type the following at it: flags npx0 1 Then proceed normally to boot. This will be saved into your kernel, so you only need to do it once. I have this CMD640 IDE controller that is said to be broken. Yes, it is. &os; does not support this controller except through the legacy wdc driver. On a Compaq Aero notebook, I get the message No floppy devices found! Please check ... when trying to install from floppy. 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 existence of the first floppy drive (as a 1.44 MB drive) to the driver without asking the CMOS at all. 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. There appears to be a bug in the BIOS on at least some of these boards, this bug results in the &os; 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 compatiblemode and install BootEasy during the &os; installation to avoid the bug, or upgrade the BIOS (see Intel's website for details). When installing on an Dell Poweredge XE, Dell proprietary RAID controller DSA (Dell SCSI Array) isn't recognized. Configure the DSA to use AHA-1540 emulation using EISA configuration utility. After that &os; detects the DSA as an Adaptec AHA-1540 SCSI controller, with irq 11 and port 340. Under emulation mode system will use DSA RAID disks, but you cannot use DSA-specific features such as watching RAID health. My Ethernet adapter is detected as an AMD PCnet-FAST (or similar) but it doesn't work. (Eg. onboard Ethernet on IBM Netfinity 5xxx or 7xxx) The &man.lnc.4; driver is currently faulty, and will often not work correctly with the PCnet-FAST and PCnet-FAST+. You need to install a different Ethernet adapter. I have an IBM EtherJet PCI card, it is detected by the &man.fxp.4; driver correctly, but the lights on the card don't come on and it doesn't connect to the network. We don't understand why this happens. Neither do IBM (we asked them). The card is a standard Intel EtherExpress Pro/100 with an IBM label on it, and these cards normally work just fine. You may see these symptoms only in some IBM Netfinity servers. The only solution is to install a different Ethernet adapter. When I configure the network during installation on an IBM Netfinity 3500, the system freezes. There is a problem with the onboard Ethernet in the Netfinity 3500 which we have not been able to identify at this time. It may be related to the SMP features of the system being misconfigured. You will have to install another Ethernet adapter and avoid attempting to configure the onboard adapter at any time. When I install onto a drive managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a read error message). There is a bug in the Mylex driver which results in it ignoring the 8GB geometry mode setting in the BIOS. Use the 2GB mode instead. Index: stable/4/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml (revision 82389) @@ -1,255 +1,202 @@ Upgrading &os; These instructions describe a procedure for doing a binary upgrade from an older version of &os;. While the &os; 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. These notes assume that you are using the version of &man.sysinstall.8; supplied with the version of &os; to which you intend to upgrade. Using a mismatched version of &man.sysinstall.8; is almost guaranteed to cause problems and has been known to leave systems in an unusable state. The most commonly made mistake in this regard is the use of an old copy of &man.sysinstall.8; from an existing installation to upgrade to a newer version of &os;. This is not recommended. - - Furthermore, if you are upgrading from &os; 2.2.5 or - earlier, see for important details regarding changes - to the /etc/fstab file required during the upgrade procedure. - + Introduction The upgrade procedure replaces distributions selected by the user with those corresponding to the new &os; 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 section in its entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or loss of data. 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, +XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, -daily, +cvsupfile, disktab, dm.conf, +dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, +host.conf, hosts.equiv, hosts.lpd, inetd.conf, kerberosIV, localtime, login.access, +login.conf, +mail, mail.rc, make.conf, manpath.config, master.passwd, -mib.txt, modems, -monthly, motd, namedb, networks, +newsyslog.conf, nsswitch.conf, +pam.conf, passwd, -phones, +periodic, ppp, printcap, profile, -protocols, pwd.db, -rc, +rc.conf, +rc.conf.local, rc.firewall, -rc.i386, rc.local, -rc.network, -rc.conf, remote, resolv.conf, rmt, -security, sendmail.cf, +sendmail.cw, services, shells, skeykeys, spwd.db, -supfile, +ssh, syslog.conf, -termcap, ttys, -uucp, -weekly +uucp + 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. Procedure This section details the upgrade procedure. Particular attention is given to items which substantially differ from a normal installation. 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. 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 notset the newfs flag for any filesystems, as this will cause data loss. 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. 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 &os; kernel with a GENERIC kernel, - and a custom kernel may need to be generated to suit the local - system configuration. - - - &os; 2.2.6 introduced 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 - from a version prior to &os; 2.2.6. - - 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 &os; 2.2.6 and later, this format changes so that - the device for / is consistent with - others. Also, the driver for the ATA-drives has changed from - &man.wd.4; to &man.ad.4;, so the new file could look something - like: - -# Device Mountpoint FStype Options Dump Pass# -/dev/ad0s2b none swap sw 0 0 -/dev/ad0s2a / ufs rw 1 1 -/dev/ad0s2f /local0 ufs rw 1 1 -/dev/ad0s2e /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. - 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. Index: stable/4/release/doc/en_US.ISO8859-1/installation/i386/Makefile =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/i386/Makefile (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/i386/Makefile (revision 82389) @@ -1,20 +1,20 @@ # $FreeBSD$ RELN_ROOT?= ${.CURDIR}/../../.. DOC?= article FORMATS?= html INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # SGML content SRCS+= article.sgml SRCS+= ../common/artheader.sgml +SRCS+= ../common/abstract.sgml SRCS+= ../common/install.sgml -SRCS+= ../common/floppies.sgml SRCS+= ../common/layout.sgml SRCS+= ../common/trouble.sgml SRCS+= ../common/upgrade.sgml .include "${RELN_ROOT}/share/mk/doc.relnotes.mk" .include "${DOC_PREFIX}/share/mk/doc.project.mk" Index: stable/4/release/doc/en_US.ISO8859-1/installation/i386/article.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/installation/i386/article.sgml (revision 82388) +++ stable/4/release/doc/en_US.ISO8859-1/installation/i386/article.sgml (revision 82389) @@ -1,27 +1,27 @@ %man; %authors; %mlists; %release; %sections; ]>
&artheader; +&abstract; §.install; §.layout; -§.floppies; §.upgrade; §.trouble;