diff --git a/release/doc/en_US.ISO8859-1/installation/common/install.sgml b/release/doc/en_US.ISO8859-1/installation/common/install.sgml index e31563b4151..14c82a391e6 100644 --- a/release/doc/en_US.ISO8859-1/installation/common/install.sgml +++ b/release/doc/en_US.ISO8859-1/installation/common/install.sgml @@ -77,10 +77,10 @@ from {alpha,i386}/INSTALL.TXT. - &os; for the &arch.print; 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 + &os; for the &arch.print; requires a 486 or better + processor to install and run (although &os; can run on 386 processors with + a custom kernel) and at least 8 megs of RAM to install and 7 megs to + run. You will need at least 150MB of free hard drive space for the most minimal installation. See below for ways of shrinking existing DOS partitions in order to install &os;. @@ -139,7 +139,7 @@ from {alpha,i386}/INSTALL.TXT. 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 + create a set of floppy disks (usually three) 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 @@ -148,23 +148,20 @@ from {alpha,i386}/INSTALL.TXT. For most CDROM or network installations, all you need to copy onto actual floppies from the floppies/ directory are the - kern.flp and mfsroot.flp - images (for 1.44MB floppies). Depending on your hardware, you may - also need to make the third drivers.flp image - to provide necessary device drivers. + boot.flp and kernX.flp + images (for 1.44MB floppies). 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) or kern-small.flp and - mfsroot-small.flp images (for 1.2MB floppies). + directory are the boot.flp and kernX.flp + images (for 1.44MB floppies) or boot-small.flp and + kern-small.flp images (for 1.2MB floppies). Getting these images over the network is easy. Simply fetch the - release/floppies/kern.flp, - release/floppies/mfsroot.flp, - and - release/floppies/drivers.flp + release/floppies/boot.flp, + and all of the + release/floppies/kernX.flp files from or one of the many mirrors listed at Web pages. - Get two blank, freshly formatted floppies and image copy - kern.flp onto one and mfsroot.flp onto the other. These images are + Get approximately three blank, freshly formatted floppies and image copy + boot.flp onto one and the kernX.flp files + onto the others. 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. - Get two blank, freshly formatted floppies and image copy - kern.flp onto one and mfsroot.flp onto the other. These images are + Get approximately three blank, freshly formatted floppies and image copy + boot.flp onto one and the kernX.flp files + onto the others. 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 rawrite.exe under DOS (see the @@ -192,39 +191,34 @@ from {alpha,i386}/INSTALL.TXT. For example, to create the kernel floppy image from DOS, you'd do something like this: - C> fdimage kern.flp a: + C> fdimage boot.flp a: A> rawrite - Assuming that you'd copied fdimage.exe and kern.flp into a directory - somewhere. You would do the same for mfsroot.flp, of course. + Assuming that you'd copied fdimage.exe and boot.flp into a directory + somewhere. You would do the same for the kernX.flp files, of course. - Assuming that you'd copied rawrite.exe and kern.flp into a directory - somewhere. You would do the same for mfsroot.flp, of course. + Assuming that you'd copied rawrite.exe and boot.flp into a directory + somewhere. You would do the same for the kernX.flp files, 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 - &prompt.root; dd if=floppies/kern.flp of=/dev/rfd0.1440 + &prompt.root; dd if=floppies/boot.flp of=/dev/rfd0 + &prompt.root; dd if=floppies/boot.flp of=/dev/rfd0.1440 + + or + + &prompt.root; dd if=floppies/boot.flp of=/dev/fd0 or - &prompt.root; dd if=floppies/kern.flp of=/dev/floppy - &prompt.root; dd if=floppies/kern-small.flp of=/dev/rfd0.1200 + &prompt.root; dd if=floppies/boot.flp of=/dev/floppy + &prompt.root; dd if=floppies/boot-small.flp of=/dev/rfd0.1200 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. - Floppy disk based install is not supported on &os;/&arch;. @@ -240,19 +234,15 @@ from {alpha,i386}/INSTALL.TXT. 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 Torito bootable CD standard. Simply - put the installation CD in your CDROM drive and boot the - system to begin installation. + If your system supports the CDBOOT standard for + bootable CDROM media and you have booting from CD enabled, + simply put the &os; 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 + distribution. Read for more information on creating the bootable floppies under different operating systems. Then you simply boot from the first floppy and you should @@ -280,26 +270,26 @@ from {alpha,i386}/INSTALL.TXT. 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 + over the net using PPP, SLIP or a dedicated connection, + you should start the installation by building a set of &os; boot floppies from the files - floppies/kern.flp and - floppies/mfsroot.flp using the instructions + floppies/boot.flp and + floppies/kernX.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 + the boot.flp disk; when prompted, insert + the other disks as required. Then, please go to for additional tips on installing via FTP or NFS. If you don't have a CDROM and would like to - simply install over the net using PPP, SLIP or a dedicated connection. - You should start the installation by building + simply install over the net using PPP, SLIP or a dedicated connection, + you should start the installation by building a set of &os; boot floppies from the files - floppies/kern.flp and - floppies/mfsroot.flp using the instructions + floppies/boot.flp and + floppies/kernX.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 + the boot.flp disk; when prompted, insert + the other disks as required. Then, please go to for additional tips on installing via FTP or NFS. @@ -316,18 +306,18 @@ from {alpha,i386}/INSTALL.TXT. Alternatively you can boot the installation from floppy disk. You should start the installation by building - a set of &os; boot floppies from the files - floppies/kern.flp and - floppies/mfsroot.flp using the instructions + a set of &os; boot floppies from the + floppies/boot.flp and + floppies/kernX.flp files using the instructions found in . From the SRM console prompt (>>>), just insert the - kern.flp floppy and type the following + boot.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 + Insert the other floppies when prompted and + you will end up at the first screen of the install program. @@ -462,7 +452,8 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 + easy: You ensure an FTP server is running and then + simply add the following line to the password file (using the &man.vipw.8; command): ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin @@ -545,17 +536,15 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 + &prompt.root; fdformat -f 1440 fd0 +&prompt.root; disklabel -w fd0 floppy3 +&prompt.root; newfs -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, + need to copy the files onto them. + The distribution files are sized so that a floppy disk will hold + a single file. + 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, ... @@ -565,8 +554,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 - README.TXT. + floppy of each distribution set. Once you come to the Media screen of the install, select @@ -618,7 +606,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE this: &prompt.root; cd /where/you/have/your/dists -&prompt.root; tar cvf /dev/rsa0 dist1 .. dist2 +&prompt.root; tar cvf /dev/sa0 dist1 .. dist2 When you go to do the installation, you should also make sure that you leave enough room in some temporary directory @@ -654,8 +642,8 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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. + dialog with the link before connecting to it, then the PPP + utility should be used instead. If you're using PPP, make sure that you have your Internet Service Provider's IP address and DNS information @@ -699,7 +687,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE Ethernet - &os; supports many common Ethernet cards; a table + &os; supports most common Ethernet cards; a table of supported cards is provided as part of the &os; Hardware Notes (see HARDWARE.TXT in @@ -741,7 +729,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 + may 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 @@ -842,19 +830,21 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 + plug the keyboard in again. 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. + If booting from floppies, when access to the disk stops, insert + the first of the kernX.flp disks and press + Enter. When access to this disk finishes, insert + the next kernX.flp disk and press Enter, + and repeat until all kernX.flp disks have been + inserted. When disk activity finishes, reinsert the boot.flp + floppy disk and press Enter. - Hit the space bar, then enter + Once a beep is heard, hit the number 6, then enter boot -h @@ -965,7 +955,10 @@ pqb0.0.1.4.0 PQB0 PCI EIDE 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 + it still has some rough edges. The + emulators/doscmd port/package + can be found in the &os; Ports Collection. + 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! @@ -976,6 +969,38 @@ pqb0.0.1.4.0 PQB0 PCI EIDE X Window System (XFree86) to operate. + + + + Can I run µsoft.windows; applications under &os;? + + + + There are several ports/packages in the &os; Ports Collection + which can enable the use of many &windows; applications. + The emulators/wine port/package + provides a compatibility layer on top of &os; which allow many + &windows; applications to be run within X Windows (XFree86). + + + + + + Can I run other Operating Systems under &os;? + + + + Again, there are several ports/packages in the &os; Ports Collection + which simulate "virtual machines" and allow other operating systems to run + on top of &os;. + The emulators/bochs port/package + allows µsoft.windows;, Linux and even other copies of &os; to be run within a + window on the &os; desktop. + The emulators/vmware2 and + emulators/vmware3 ports/packages + allow the commercial VMware virtual machine software to be run on &os;. + + diff --git a/release/doc/en_US.ISO8859-1/installation/common/layout.sgml b/release/doc/en_US.ISO8859-1/installation/common/layout.sgml index 09c3d4a5c15..75bab9b59ea 100644 --- a/release/doc/en_US.ISO8859-1/installation/common/layout.sgml +++ b/release/doc/en_US.ISO8859-1/installation/common/layout.sgml @@ -93,7 +93,7 @@ README.HTM cdrom.inf crypto info tools filenames in packages/ to the &man.pkg.add.1; command. The Ports Collection may be installed like any other - distribution and requires about 100MB unpacked. More + distribution and requires about 190MB 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