diff options
| author | bmah <bmah@FreeBSD.org> | 2007-08-15 03:14:43 +0000 |
|---|---|---|
| committer | bmah <bmah@FreeBSD.org> | 2007-08-15 03:14:43 +0000 |
| commit | 0fdb831d0b0e6c41731a61445f8ce21034513f21 (patch) | |
| tree | bfeb4aece859596c582546ab2fa5121730c6608e /release | |
| parent | c6643682213952dcd9ef5533a395d33a5af6d27a (diff) | |
| download | FreeBSD-src-0fdb831d0b0e6c41731a61445f8ce21034513f21.zip FreeBSD-src-0fdb831d0b0e6c41731a61445f8ce21034513f21.tar.gz | |
Remove the installation notes, which have not truly been maintained
for quite some time. All relevant content has been moved to the
installation chapter of the FreeBSD Handbook, which will be the
single source of FreeBSD installation instructions.
In addition to removing redundancy, this change also removes the last
of the machine-dependent documents in the release documentation
set (the release notes and hardware notes were unified to produce
machine-independent documents).
Approved by: re (blanket for installation notes removal)
Nods from: blackend, brueffer, simon, trhodes
No objections on: doc@
Helpful hints from: blackend
Diffstat (limited to 'release')
22 files changed, 0 insertions, 2753 deletions
diff --git a/release/doc/en_US.ISO8859-1/installation/Makefile b/release/doc/en_US.ISO8859-1/installation/Makefile deleted file mode 100644 index 9a12f73..0000000 --- a/release/doc/en_US.ISO8859-1/installation/Makefile +++ /dev/null @@ -1,13 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../.. - -SUBDIR= amd64 -SUBDIR+= ia64 -SUBDIR+= i386 -SUBDIR+= pc98 -SUBDIR+= powerpc -SUBDIR+= sparc64 - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO8859-1/installation/Makefile.inc b/release/doc/en_US.ISO8859-1/installation/Makefile.inc deleted file mode 100644 index 535d4a4..0000000 --- a/release/doc/en_US.ISO8859-1/installation/Makefile.inc +++ /dev/null @@ -1,7 +0,0 @@ -# $FreeBSD$ - -.ifdef NO_LANGCODE_IN_DESTDIR -DESTDIR?= ${DOCDIR}/installation/${.CURDIR:T} -.else -DESTDIR?= ${DOCDIR}/en_US.ISO8859-1/installation/${.CURDIR:T} -.endif diff --git a/release/doc/en_US.ISO8859-1/installation/amd64/Makefile b/release/doc/en_US.ISO8859-1/installation/amd64/Makefile deleted file mode 100644 index 36f855e..0000000 --- a/release/doc/en_US.ISO8859-1/installation/amd64/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $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/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" diff --git a/release/doc/en_US.ISO8859-1/installation/amd64/article.sgml b/release/doc/en_US.ISO8859-1/installation/amd64/article.sgml deleted file mode 100644 index 7e71f15..0000000 --- a/release/doc/en_US.ISO8859-1/installation/amd64/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN"> -%articles.ent; - -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> -%sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "amd64"> -<!ENTITY arch.print "AMD64"> - -]> - -<article> -&artheader; -&abstract; -§.install; -§.layout; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO8859-1/installation/common/abstract.sgml b/release/doc/en_US.ISO8859-1/installation/common/abstract.sgml deleted file mode 100644 index 527d9ea..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/abstract.sgml +++ /dev/null @@ -1,8 +0,0 @@ -<!-- $FreeBSD$ --> - -<abstract> - <para>This article gives some brief instructions on installing - &os;/&arch; &release.current;, with particular - emphasis given to obtaining a &os; distribution. Some notes on - troubleshooting and frequently-asked questions are also given.</para> -</abstract> diff --git a/release/doc/en_US.ISO8859-1/installation/common/artheader.sgml b/release/doc/en_US.ISO8859-1/installation/common/artheader.sgml deleted file mode 100644 index 41aee98..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/artheader.sgml +++ /dev/null @@ -1,20 +0,0 @@ -<!-- $FreeBSD$ --> - -<articleinfo> - <title>&os;/&arch; &release.current; Installation Instructions</title> - - <corpauthor> - The &os; Project - </corpauthor> - - <copyright> - <year>2000</year> - <year>2001</year> - <year>2002</year> - <year>2003</year> - <year>2004</year> - <year>2005</year> - <year>2006</year> - <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder> - </copyright> -</articleinfo> diff --git a/release/doc/en_US.ISO8859-1/installation/common/install.ent b/release/doc/en_US.ISO8859-1/installation/common/install.ent deleted file mode 100644 index 3e6060d..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/install.ent +++ /dev/null @@ -1,15 +0,0 @@ -<!-- -*- sgml -*- --> - -<!-- $FreeBSD$ --> - -<!-- Text constants which probably don't need to be changed.--> - -<!-- Files to be included --> - -<!ENTITY artheader SYSTEM "artheader.sgml"> -<!ENTITY abstract SYSTEM "abstract.sgml"> -<!ENTITY sect.install SYSTEM "install.sgml"> -<!ENTITY sect.layout SYSTEM "layout.sgml"> -<!ENTITY sect.upgrade SYSTEM "upgrade.sgml"> -<!ENTITY sect.trouble SYSTEM "trouble.sgml"> - diff --git a/release/doc/en_US.ISO8859-1/installation/common/install.sgml b/release/doc/en_US.ISO8859-1/installation/common/install.sgml deleted file mode 100644 index 84f937b..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/install.sgml +++ /dev/null @@ -1,1077 +0,0 @@ -<!-- - -$FreeBSD$ - -install.sgml - -This file has architecture-dependent installation instructions, culled -from {alpha,i386}/INSTALL.TXT. - ---> - -<sect1 id="install"> - <title>Installing &os;</title> - - <para>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 <ulink - url="&url.books.handbook;/install.html"><quote>Installing - &os;</quote></ulink> - chapter of the <ulink - url="&url.books.handbook;/">&os; - Handbook</ulink> provides more in-depth information about the - installation program itself, including a guided walkthrough with - screenshots.</para> - - <para>If you are upgrading from a previous release - of &os;, please see <xref linkend="upgrading"> for instructions on - upgrading.</para> - - <sect2 id="getting-started"> - <title>Getting Started</title> - - <para>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 <filename>README.TXT</filename>, - which can usually be found in the same location as this file; most - of these documents, such as the release notes and the hardware - compatibility list, are also accessible in the Documentation menu - of the installer.</para> - - <para>Note that on-line versions of the &os; <ulink - url="&url.books.faq;/">FAQ</ulink> and <ulink - url="&url.books.handbook;/">Handbook</ulink> are also - available from the <ulink url="&url.base;/">&os; - Project Web site</ulink>, if you have an Internet - connection.</para> - - <para>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.</para> - - <para>The best laid plans sometimes go awry, so if you run into - trouble take a look at <xref linkend="trouble">, which contains - valuable troubleshooting information. You should also read - an updated copy of - <filename>ERRATA.TXT</filename> before installing, - since this will alert you to - any problems which have reported in the interim for your - particular release.</para> - - <important> - <para>While &os; does its best to safeguard against - accidental loss of data, it's still more than possible to - <emphasis>wipe out your entire disk</emphasis> - with this installation if you make a - mistake. Please do not proceed to the final &os; - installation menu unless you've adequately backed up any - important data first.</para> - </important> - </sect2> - - <sect2> - <title>Hardware Requirements</title> - -<!-- i386/pc98 text starts here --> - - <para arch="i386,pc98">&os; for the &arch.print; requires a 486 or better - processor and at least 24 MB of RAM. - 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;.</para> - -<!-- alpha text starts here --> - - <para arch="alpha">&os; for the &arch.print; supports the platforms - described in <filename>HARDWARE.TXT</filename>.</para> - - <para arch="alpha">You will need a dedicated disk for - &os;/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.</para> - - <para arch="alpha">Your root filesystem MUST be the first - partition (partition <literal>a</literal>) on the disk to be - bootable.</para> - - <para arch="alpha">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.</para> - -<!-- sparc64 text starts here --> - - <para arch="sparc64">&os; for the &arch.print; supports the platforms - described in <filename>HARDWARE.TXT</filename>.</para> - - <para arch="sparc64">You will need a dedicated disk for - &os;/sparc64. It is not possible to share a disk with another - operating system at this time.</para> - -<!-- amd64 text starts here --> - <para arch="amd64">&os; for the &arch.print; requires an - Athlon64, Athlon64-FX, Opteron or better processor to run.</para> - - <para arch="amd64">If you have an machine based on an - nVidia nForce3 Pro-150, you MUST use the BIOS setup to - disable the IO APIC. If you do not have an option - to do this, you will likely have to disable ACPI - instead. There are bugs in the Pro-150 chipset that - we have not found a workaround for yet.</para> - -<!-- generic text starts here --> - - <para>If you are - not familiar with configuring hardware for &os;, you should - be sure to read the <filename>HARDWARE.TXT</filename> file; - it contains important - information on what hardware is supported by &os;.</para> - </sect2> - - <sect2 id="floppies"> - <title>Floppy Disk Image Instructions</title> - - <para arch="i386,alpha,pc98">Depending on how you choose to install &os;, you may need to - create a set of floppy disks (usually four) 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.</para> - - <para arch="i386,alpha">For most CDROM or network installations, all you need to - copy onto actual floppies from the <filename>floppies/</filename> directory are the - <filename>boot.flp</filename> and <filename>kern<replaceable>X</replaceable>.flp</filename> - images (for 1.44MB floppies).</para> - - <para arch="pc98">For a normal CDROM or network installation, all you need - to copy onto actual floppies from the <filename>floppies/</filename> - directory are the <filename>boot.flp</filename> and <filename>kern<replaceable>X</replaceable>.flp</filename> - images (for 1.44MB floppies) or <filename>boot-small.flp</filename> and - <filename>kern-small.flp</filename> images (for 1.2MB floppies).</para> - - <para arch="i386,alpha,pc98">Getting these images over the network is easy. Simply fetch - the - <replaceable>release</replaceable><filename>/floppies/boot.flp</filename>, - and all of the - <replaceable>release</replaceable><filename>/floppies/kern<replaceable>X</replaceable>.flp</filename> - files from <ulink - url="&release.url;"></ulink> - or one of the many mirrors listed at <ulink - url="&url.books.handbook;/mirrors-ftp.html">FTP - Sites</ulink> section of the Handbook, or on the - <ulink url="http://mirrorlist.FreeBSD.org/"></ulink> Web pages. - </para> - - <para arch="i386,alpha">Get several blank, freshly formatted floppies and image copy - <filename>boot.flp</filename> onto one and the <filename>kern<replaceable>X</replaceable>.flp</filename> files - onto the others. These images are - <emphasis>not</emphasis> DOS files. You cannot simply copy them to a DOS or UFS floppy - as regular files, you need to <quote>image</quote> copy them to the floppy with - <filename>fdimage.exe</filename> under DOS (see the - <filename>tools</filename> directory on your CDROM or &os; FTP - mirror) or the &man.dd.1; command in UNIX.</para> - - <para arch="pc98">Get several blank, freshly formatted floppies and image copy - <filename>boot.flp</filename> onto one and the <filename>kern<replaceable>X</replaceable>.flp</filename> files - onto the others. These images are - <emphasis>not</emphasis> DOS files. You cannot simply copy them to a DOS or UFS floppy - as regular files, you need to <quote>image</quote> copy them to the floppy with - <filename>rawrite.exe</filename> under DOS (see the - <filename>tools</filename> directory on your CDROM or &os; FTP - mirror) or the &man.dd.1; command in UNIX.</para> - - <para arch="i386,alpha,pc98">For example, to create the kernel floppy image from DOS, you'd - do something like this:</para> - - <screen arch="i386,alpha"><prompt>C></prompt> <userinput>fdimage boot.flp a:</userinput></screen> - <screen arch="pc98"><prompt>A></prompt> <userinput>rawrite</userinput></screen> - - <para arch="i386,alpha">Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>boot.flp</filename> into a directory - somewhere. You would do the same for the <filename>kern<replaceable>X</replaceable>.flp</filename> files, of course.</para> - - <para arch="pc98">Assuming that you'd copied <filename>rawrite.exe</filename> and <filename>boot.flp</filename> into a directory - somewhere. You would do the same for the <filename>kern<replaceable>X</replaceable>.flp</filename> files, of course.</para> - - <para arch="i386,alpha,pc98">If you're creating the boot floppy from a UNIX machine, you - may find that:</para> - - <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0</userinput></screen> - <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0.1440</userinput></screen> - - <para arch="i386,alpha">or</para> - - <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/fd0</userinput></screen> - - <para arch="i386,alpha,pc98">or</para> - - <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/floppy</userinput></screen> - <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot-small.flp of=/dev/rfd0.1200</userinput></screen> - - <para arch="i386,alpha,pc98">work well, depending on your hardware and operating system - environment (different versions of UNIX have different names - for the floppy drive).</para> - - <para arch="amd64,sparc64">Floppy disk based install is not supported - on &os;/&arch;.</para> - </sect2> - - <sect2 id="start-installation"> - <title>Installing &os; from CDROM or the Internet</title> - -<!-- i386/pc98 text starts here --> - - <para arch="i386,amd64">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: - <itemizedlist> - <listitem> - <para>If your system supports the <quote>CDBOOT</quote> 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.</para> - </listitem> - <listitem> - <para>Build a set of &os; boot floppies from the - <filename>floppies/</filename> directory in every &os; - distribution. Read - <xref linkend="floppies"> 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.</para> - </listitem> - </itemizedlist> - </para> - - <para arch="pc98">The easiest type of installation is from - CDROM. If you have a supported CDROM drive and a &os; - installation CDROM, there is a next way of starting the - installation from it: - <itemizedlist> - <listitem> - <para>Build a set of &os; boot floppies from the - <filename>floppies/</filename> directory in every &os; - distribution. Read <xref linkend="floppies"> 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.</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">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 &os; boot floppies from the files - <filename>floppies/boot.flp</filename> and - <filename>floppies/kern<replaceable>X</replaceable>.flp</filename> using the instructions - found in <xref linkend="floppies">. Restart your computer using - the <filename>boot.flp</filename> disk; when prompted, insert - the other disks as required. Then, please go to - <xref linkend="ftpnfs"> for additional tips on installing - via FTP or NFS.</para> - - <para arch="pc98">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 - a set of &os; boot floppies from the files - <filename>floppies/boot.flp</filename> and - <filename>floppies/kern<replaceable>X</replaceable>.flp</filename> using the instructions - found in <xref linkend="floppies">. Restart your computer using - the <filename>boot.flp</filename> disk; when prompted, insert - the other disks as required. Then, please go to - <xref linkend="ftpnfs"> for additional tips on installing - via FTP or NFS.</para> - -<!-- alpha text starts here --> - - <para arch="alpha">The easiest type of installation is from - CDROM. If you have a supported CDROM drive and a &os; - installation CDROM, you can boot &os; 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):</para> - - <screen arch="alpha">>>><userinput>boot dka0</userinput></screen> - - <para arch="alpha">Alternatively you can boot the installation - from floppy disk. You should start the installation by building - a set of &os; boot floppies from the - <filename>floppies/boot.flp</filename> and - <filename>floppies/kern<replaceable>X</replaceable>.flp</filename> files using the instructions - found in <xref linkend="floppies">. From the SRM console prompt - (<literal>>>></literal>), just insert the - <filename>boot.flp</filename> floppy and type the following - command to start the installation:</para> - - <screen arch="alpha">>>><userinput>boot dva0</userinput></screen> - - <para arch="alpha">Insert the other floppies when prompted and - you will end up at the first screen of - the install program.</para> - -<!-- sparc64 text starts here --> - - <para arch="sparc64">Most &arch; systems are set up to boot automatically from - disk. To install &os;, you need to boot over the network or - from a CDROM, which requires you to break into the PROM - (OpenFirmware).</para> - - <para arch="sparc64">To do this, reboot the system, and wait until the boot - message appears. It depends on the model, but should look about - like:</para> - - <screen arch="sparc64">Sun Blade 100 (UltraSPARC-IIe), Keyboard Present -Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. -OpenBoot 4.2, 128 MB memory installed, Serial #51090132. -Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen> - - <para arch="sparc64">If your system proceeds to boot from disk at this point, you - need to press <keycombo - action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo> - or <keycombo - action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo> - on the keyboard, or send a <command>BREAK</command> over the - serial console (using for example <command>~#</command> in - &man.tip.1; or &man.cu.1;) to get to the PROM prompt. It looks - like this:</para> - - <screenco arch="sparc64"> - <areaspec> - <area id="prompt-single" coords="1 5"> - <area id="prompt-smp" coords="2 5"> - </areaspec> - - <screen><prompt>ok </prompt> -<prompt>ok {0} </prompt></screen> - - <calloutlist> - <callout arearefs="prompt-single"> - <para>This is the prompt used on systems with just one - CPU.</para> - </callout> - - <callout arearefs="prompt-smp"> - <para>This is the prompt used on SMP systems, the digit - indicates the number of the active CPU.</para> - </callout> - </calloutlist> - </screenco> - - <para arch="sparc64">At this point, place the CDROM into your - drive, and from the PROM prompt, type <command>boot - cdrom</command>.</para> - - </sect2> - <sect2> - <title>Detail on various installation types</title> - - <para>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 <quote>Usage</quote> instructions on the first menu.</para> - - <note> - <para>If you get stuck at a screen, press the <keycap>F1</keycap> key for online - documentation relevant to that specific section.</para> - </note> - - <para>If you've never installed &os; before, or even if you - have, the <quote>Standard</quote> 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 <emphasis>exactly</emphasis> what you - want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If - you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para> - - <para>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.</para> - - <para arch="alpha">Once the install procedure has finished, you will be able - to start &os;/&arch; by typing something like this to the SRM - prompt:</para> - - <screen arch="alpha">>>><userinput>boot dkc0</userinput></screen> - - <para arch="alpha">This instructs the firmware to boot the specified disk. To - find the SRM names of disks in your machine, use the <literal>show - device</literal> command:</para> - - <screen arch="alpha">>>><userinput>show device</userinput> -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</screen> - - <para arch="alpha">This example is from a Digital Personal Workstation 433au - and shows three disks attached to the machine. The first is a - CDROM called <devicename>dka0</devicename> and the other two are - disks and are called <devicename>dkc0</devicename> and - <devicename>dkc100</devicename> respectively.</para> - - <para arch="alpha">You can specify which kernel file to load and what boot - options to use with the <option>-file</option> and - <option>-flags</option> options, for example:</para> - - <screen arch="alpha"><prompt>>>></prompt> <userinput>boot -file kernel.old -flags s</userinput></screen> - - <para arch="alpha">To make &os;/&arch; boot automatically, use these commands:</para> - - <screen arch="alpha"><prompt>>>></prompt> <userinput>set boot_osflags a</userinput> -<prompt>>>></prompt> <userinput>set bootdef_dev dkc0</userinput> -<prompt>>>></prompt> <userinput>set auto_action BOOT</userinput></screen> - - <sect3> - <title>Installing from a Network CDROM</title> - - <para>If you simply wish to install from a local CDROM drive - then see <xref linkend="start-installation">. 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:</para> - - <itemizedlist> - <listitem> - <para>If you would be able to FTP install &os; directly - from the CDROM drive in some &os; machine, it's quite - 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):</para> - - <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen> - - <para>On the machine on which you are running the install, - go to the Options menu and set Release Name to - <literal>any</literal>. You may then choose a Media type of - <literal>FTP</literal> and type in - <filename>ftp://<replaceable>machine</replaceable></filename> - after picking <quote>URL</quote> in the ftp sites - menu.</para> - - <warning> - <para>This may allow anyone on the local network (or Internet) to - make <quote>anonymous FTP</quote> connections to this - machine, which may not be desirable.</para> - </warning> - </listitem> - - <listitem> - <para>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 - <filename>/etc/exports</filename> file (on the machine with - the CDROM drive). The example below allows the machine - <hostid role="hostname">ziggy.foo.com</hostid> to mount the - CDROM directly via NFS during installation:</para> - - <screen>/cdrom -ro ziggy.foo.com</screen> - - <para>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: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for - an NFS installation when the target machine is installed, - e.g. <filename>wiggy:/cdrom</filename>.</para> - </listitem> - </itemizedlist> - </sect3> - - <sect3> - <title>Installing from Floppies</title> - - <para>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.</para> - - <para>First, make your boot floppies as described in - <xref linkend="floppies">.</para> - - <para>Second, peruse <xref linkend="layout"> and pay special attention - to the <quote>Distribution Format</quote> section since it describes which - files you're going to need to put onto floppy and which you can - safely skip.</para> - - <para>Next you will need, at minimum, as many 1.44MB floppies as - it takes to hold all files in the <filename>bin</filename> - (binary distribution) directory. If you're preparing these - floppies under DOS, then these floppies - <emphasis>must</emphasis> be formatted using the MS-DOS - <filename>FORMAT</filename> command. If you're using Windows, - use the Windows File Manager format command.</para> - - <important> - <para>Frequently, floppy disks come <quote>factory - preformatted</quote>. 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.</para> - </important> - - <para>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:</para> - - <screen>&prompt.root; <userinput>fdformat -f 1440 fd0</userinput> -&prompt.root; <userinput>disklabel -w fd0 floppy3</userinput> -&prompt.root; <userinput>newfs -i 65536 /dev/fd0</userinput></screen> - - <para>After you've formatted the floppies for DOS or UFS, you'll - 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.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para> - - <important> - <para>The <filename>bin.inf</filename> file also needs to go on the first floppy of - the <filename>bin</filename> 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 - <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first - floppy of each distribution set.</para> - </important> - - <para>Once you come to the Media screen of the install, select - <quote>Floppy</quote> and you'll be prompted for the rest.</para> - </sect3> - - <sect3 arch="i386,pc98,amd64"> - <title>Installing from a DOS partition</title> - - <para arch="i386,amd64">To prepare for installation from an MS-DOS partition you - should simply copy the files from the distribution into a - directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from - DOS using files copied from the CDROM, you might do something - like this:</para> - - <para arch="pc98">To prepare for installation from an MS-DOS partition you - should simply copy the files from the distribution into a - directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>A:</devicename>). For example, to do a minimal installation of &os; from - DOS using files copied from the CDROM, you might do something - like this:</para> - - <screen arch="i386,amd64"><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput> -<prompt>C:\></prompt> <userinput>XCOPY /S E:\BASE C:\FREEBSD\BASE</userinput></screen> - <screen arch="pc98"><prompt>A:\></prompt> <userinput>MD A:\FREEBSD</userinput> -<prompt>A:\></prompt> <userinput>XCOPY /S E:\BASE A:\FREEBSD\BASE</userinput></screen> - - <para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para> - - <para arch="i386,amd64">For as many distributions as you wish to install from DOS (and - you have free space for), install each one in a directory under - <filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para> - - <para arch="pc98">For as many distributions as you wish to install from DOS (and - you have free space for), install each one in a directory under - <filename>A:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para> - - <para>Once you've copied the directories, you can simply launch - the installation from floppies as normal and select <quote>DOS</quote> as - your media type when the time comes.</para> - </sect3> - - <sect3> - <title>Installing from QIC/SCSI Tape</title> - - <para>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:</para> - - <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput> -&prompt.root; <userinput>tar cvf /dev/sa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen> - - <para>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 <emphasis>full</emphasis> - 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 - as much temporary storage as you have stuff written on tape.</para> - - <note> - <para>When going to do the installation, the tape must be in - the drive <emphasis>before</emphasis> booting from the boot floppies. The - installation <quote>probe</quote> may otherwise fail to find it.</para> - </note> - - <para>Now create a boot floppy as described in <xref linkend="floppies"> and - proceed with the installation.</para> - </sect3> - - <sect3 id="ftpnfs"> - <title>Installing over a Network using FTP or NFS</title> - - <para>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.</para> - - <sect4> - <title>Serial Port</title> - - <para>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 the PPP - utility should be used instead.</para> - - <para>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.</para> - - <para>You will also need to know how to use the various <quote>AT - commands</quote> for dialing out with your particular brand of modem - as the PPP dialer provides only a very simple terminal - emulator.</para> - </sect4> - - <sect4> - <title>Parallel Port</title> - - <para>If a hard-wired connection to another &os; or Linux - machine is available, you might also consider installing over - a <quote>laplink</quote> 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 - <quote>real</quote> 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. <hostid - role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>, - etc).</para> - - <important> - <para>If you use a Linux machine rather than a &os; - machine as your PLIP peer, you will also have to specify - <option>link0</option> in the TCP/IP setup screen's <quote>extra options for - ifconfig</quote> field in order to be compatible with Linux's - slightly different PLIP protocol.</para> - </important> - - </sect4> - - <sect4> - <title>Ethernet</title> - - <para>&os; supports most common Ethernet cards; a table - of supported cards is - provided as part of the &os; Hardware Notes (see - <filename>HARDWARE.TXT</filename> 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 <emphasis>before</emphasis> the laptop is powered on. &os; does - not, unfortunately, currently support <quote>hot insertion</quote> of - PCMCIA cards during installation.</para> - - <para>You will also need to know your IP address on the - network, the <option>netmask</option> 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.</para> - - <para>If you do not know the answers to these questions then - you should really probably talk to your system administrator - <emphasis>first</emphasis> before trying this type of - 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.</para> - - <para>Once you have a network connection of some sort working, the - installation can continue over NFS or FTP.</para> - </sect4> - - <sect4> - <title>NFS installation tips</title> - - <para>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.</para> - - <para>If this server supports only <quote>privileged port</quote> access (this is - generally the default for Sun and Linux workstations), you - may need to set this option in the Options menu before - installation can proceed.</para> - - <para>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.</para> - - <para>In order for NFS installation to work, the server must - also support <quote>subdir mounts</quote>, e.g. if your &os; - distribution directory lives on - <filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then - <hostid role="hostname">wiggy</hostid> will have to allow - the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just - <filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para> - - <para>In &os;'s <filename>/etc/exports</filename> file this is controlled by the - <option>-alldirs</option> option. Other NFS servers may have different - conventions. If you are getting <literal>Permission Denied</literal> messages - from the server then it's likely that you don't have this - properly enabled.</para> - </sect4> - - <sect4> - <title>FTP Installation tips</title> - - <para>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.</para> - - <para>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 <quote>URL</quote> 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:</para> - - <screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen> - - <para>There are three FTP installation modes you can use:</para> - <itemizedlist> - <listitem> - <para>FTP: This method uses the standard - <quote>Active</quote> 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.</para> - </listitem> - <listitem> - <para>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.</para> - </listitem> - <listitem> - <para>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.</para> - - <para>In the rare case that you have an FTP proxy that - does not go through HTTP, you can specify the URL as - something like:</para> - - <screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen> - - <para>In the URL above, <replaceable>port</replaceable> - is the port number of the proxy FTP server.</para> - </listitem> - </itemizedlist> - - </sect4> - </sect3> - <sect3 arch="i386,alpha,amd64"> - <title>Tips for Serial Console Users</title> - - <para>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:</para> - - <procedure> - <step> - <para>Connect some sort of ANSI (vt100) compatible terminal - or terminal emulation program to the <devicename>COM1</devicename> port of the PC you - are installing &os; onto.</para> - </step> - <step> - <para>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.</para> - </step> - <step> - <para>If you don't get any output on your serial console, - plug the keyboard in again. If you are booting from the - CDROM, proceed to <xref linkend="hitspace"> as soon as you - hear the beep.</para> - </step> - <step> - <para>If booting from floppies, when access to the disk stops, insert - the first of the <filename>kern<replaceable>X</replaceable>.flp</filename> disks and press - <keycap>Enter</keycap>. When access to this disk finishes, insert - the next <filename>kern<replaceable>X</replaceable>.flp</filename> disk and press <keycap>Enter</keycap>, - and repeat until all <filename>kern<replaceable>X</replaceable>.flp</filename> disks have been - inserted. When disk activity finishes, reinsert the <filename>boot.flp</filename> - floppy disk and press <keycap>Enter</keycap>.</para> - </step> - <step id="hitspace"> - <para>Once a beep is heard, hit the number <keycap>6</keycap>, then enter</para> - - <screen><userinput>boot -h</userinput></screen> - - <para>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.</para> - </step> - </procedure> - </sect3> - </sect2> - - <sect2> - <title>Question and Answer Section for &arch.print; Architecture Users</title> - - <qandaset arch="i386,amd64"> - <qandaentry> - <question> - <para>Help! I have no space! Do I need to delete - everything first?</para> - </question> - <answer> - <para>If your machine is already running DOS and has little - or no free space available for &os;'s installation, there - are several alternatives for resizing existing partitions so - that you can install &os;.</para> - - <para>The <application>FIPS</application> - utility, provided in the <filename>tools/</filename> - subdirectory on the &os; CDROM or on the various &os; ftp - sites, can resize an existing FAT partition. It 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 <quote>defrag</quote> your DOS - partition, using the DOS 6.xx <filename>DEFRAG</filename> - utility or the <application>Norton Disk Tools</application>, - 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 <quote>clone</quote> 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).</para> - - <para>For systems with NTFS partitions, a different tool, - such as <application>ntfsresize</application> or the - commercially-available <application>Partition - Magic</application>, is - required. <application>ntfsresize</application>, as well as - the <application>GParted</application> graphical interface - for partition resizing, is available on a number of Live CD - Linux distributions, such as - <ulink url="http://www.sysresccd.org/">SystemRescueCD</ulink>.</para> - - <para>Problems have been reported resizing Microsoft Vista - partitions. Having a Vista installation CDROM handy when - attempting such an operation is recommended. As with all - such disk maintenance tasks, a current set of backups is - also strongly advised.</para> - - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I use compressed DOS filesystems from - &os;?</para> - </question> - - <answer> - <para>No. If you are using a utility such as - <application>Stacker</application>(tm) or - <application>DoubleSpace</application>(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!). <emphasis>Do - not remove that file</emphasis> as you will probably regret - it greatly!</para> - - <para>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.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I mount my DOS extended partitions?</para> - </question> - - <answer> - <para>Yes. DOS extended partitions are mapped in at the end - of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might - be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This - example assumes, of course, that your extended partition is - on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for - <literal>da</literal> appropriately. You otherwise mount extended - partitions exactly like you would mount any other DOS drive, - e.g.:</para> - - <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da0s5 /dos_d</userinput></screen> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I run DOS binaries under &os;?</para> - </question> - - <answer> - <para>Ongoing work with BSDI's &man.doscmd.1; utility will - suffice in many cases, though - it still has some rough edges. The - <filename role="package">emulators/doscmd</filename> 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!</para> - - <para>The <filename role="package">emulators/pcemu</filename> 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.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I run µsoft.windows; applications under &os;?</para> - </question> - - <answer> - <para>There are several ports/packages in the &os; Ports Collection - which can enable the use of many &windows; applications. - The <filename role="package">emulators/wine</filename> port/package - provides a compatibility layer on top of &os; which allow many - &windows; applications to be run within X Windows (XFree86). - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I run other Operating Systems under &os;?</para> - </question> - - <answer> - <para>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 <filename role="package">emulators/bochs</filename> port/package - allows µsoft.windows;, Linux and even other copies of &os; to be run within a - window on the &os; desktop. - The <filename role="package">emulators/vmware2</filename> and - <filename role="package">emulators/vmware3</filename> ports/packages - allow the commercial VMware virtual machine software to be run on &os;.</para> - </answer> - </qandaentry> - </qandaset> - - <qandaset arch="alpha"> - <qandaentry> - <question> - <para>Can I boot from the ARC or Alpha BIOS Console?</para> - </question> - - <answer> - <para>No. &os;, like Compaq Tru64 and VMS, will only boot - from the SRM console.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Help! I have no space! Do I need to delete - everything first?</para> - </question> - - <answer> - <para>Unfortunately, yes.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I mount my Compaq Tru64 or VMS extended partitions?</para> - </question> - - <answer> - <para>No, not at this time.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>What about support for Compaq Tru64 (OSF/1) binaries?</para> - </question> - - <answer> - <para>&os; can run Tru64 applications very well using the - <filename role="package">emulators/osf1_base</filename> port/package.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>What about support for Linux binaries?</para> - </question> - - <answer> - <para>&os; can run AlphaLinux binaries with the assistance - of the <filename role="package">emulators/linux_base</filename> - port/package.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>What about support for NT Alpha binaries?</para> - </question> - - <answer> - <para>&os; is not able to run NT applications natively, - although it has the ability to mount NT partitions.</para> - </answer> - </qandaentry> - </qandaset> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO8859-1/installation/common/layout.sgml b/release/doc/en_US.ISO8859-1/installation/common/layout.sgml deleted file mode 100644 index f0bf69d..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/layout.sgml +++ /dev/null @@ -1,160 +0,0 @@ -<!-- - $FreeBSD$ - - This section contains the contents of the old LAYOUT.TXT file. ---> -<sect1 id="layout"> - <title>Distribution Format</title> - - <para>A typical &os; distribution directory looks something like - this (exact details may vary depending on version, architecture, - and other factors):</para> - -<screen>ERRATA.HTM README.TXT compat1x dict kernel -ERRATA.TXT RELNOTES.HTM compat20 doc manpages -HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages -HARDWARE.TXT base compat22 filename.txt ports -INSTALL.HTM boot compat3x floppies proflibs -INSTALL.TXT catpages compat4x games src -README.HTM cdrom.inf crypto info tools</screen> - - <para>These same files are contained in the first CDROM of a - multi-disk set, but they are laid out slightly differently on the - disk. On most architectures, the installation CDROM also contains - a <quote>live filesystem</quote> in addition to the distribution - files. The live filesystem is useful when repairing or - troubleshooting an existing &os; installation (see <xref - linkend="trouble"> for how to use this).</para> - - <para>The <filename>floppies</filename> directory will be of - particular interest to users who are unable to boot from the CDROM - media (but are able to read the CDROM by other means). It is easy - to generate a set of 1.44MB boot - floppies from the <filename>floppies</filename> directory (see - <xref linkend="floppies"> for instructions on how to - do this) and use these to start an installation from CDROM, FTP, or - NFS. 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.</para> - - <para>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 some of these items in more detail:</para> - <orderedlist> - <listitem> - <para>The <filename>*.TXT</filename> and - <filename>*.HTM</filename> files contain - documentation (for example, this document is contained in both - <filename>INSTALL.TXT</filename> and - <filename>INSTALL.HTM</filename>) and should be read - before starting an installation. The - <filename>*.TXT</filename> files are plain text, while the - <filename>*.HTM</filename> 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.</para> - </listitem> - <listitem> - <para><filename>docbook.css</filename> is a Cascading Style - Sheet (CSS) file used by some Web browsers for formatting the - HTML documentation.</para> - </listitem> - <listitem> - <para>The <filename>base</filename>, - <filename>catpages</filename>, - <filename>crypto</filename>, - <filename>dict</filename>, - <filename>doc</filename>, - <filename>games</filename>, - <filename>info</filename>, - <filename>manpages</filename>, - <filename>proflibs</filename>, and - <filename>src</filename> directories contain the primary distribution - components of &os; itself and are split into smaller files - for easy packing onto floppies (should that be - necessary).</para> - </listitem> - <listitem> - <para>The <filename>compat1x</filename>, - <filename>compat20</filename>, - <filename>compat21</filename>, - <filename>compat22</filename>, - <filename>compat3x</filename>, and - <filename>compat4x</filename> - 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 - <filename>install.sh</filename> scripts.</para> - </listitem> - <listitem> - <para>The <filename>floppies/</filename> subdirectory contains the floppy - installation images; further information on using them can be - found in <xref linkend="floppies">.</para> - </listitem> - <listitem> - <para>The <filename>packages</filename> and <filename>ports</filename> directories contain the &os; - Packages and Ports Collections. Packages may be installed from - the packages directory by running the command:</para> - - <screen>&prompt.root; <userinput>sysinstall configPackages</userinput></screen> - - <para>Packages can also be installed by feeding individual - filenames in <filename>packages</filename>/ to the &man.pkg.add.1; command.</para> - - <para>The Ports Collection may be installed like any other - distribution and requires about 190MB unpacked. More - information on the ports collection may be obtained from - <ulink url="&url.base;/ports/">http://www.FreeBSD.org/ports/</ulink> or locally from - <filename>/usr/share/doc/handbook</filename> if you've installed the <filename>doc</filename> - distribution.</para> - </listitem> - <listitem> - <para>Last of all, the <filename>tools</filename> 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.</para> - </listitem> - </orderedlist> - - <para>A typical distribution directory (for example, the <filename>info</filename> distribution) looks like this internally:</para> - -<screen>CHECKSUM.MD5 info.ab info.ad info.inf install.sh -info.aa info.ac info.ae info.mtree</screen> - - <para>The <filename>CHECKSUM.MD5</filename> 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 <filename>info.a*</filename> files - are split, gzip'd tar files, the contents of which can be viewed by - doing:</para> - - <screen>&prompt.root; <userinput>cat info.a* | tar tvzf -</userinput></screen> - - <para>During installation, they are automatically concatenated and - extracted by the installation procedure.</para> - - <para>The <filename>info.inf</filename> 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 <filename>.inf</filename> file <emphasis>must</emphasis> occupy the first - floppy of each distribution set!</para> - - <para>The <filename>info.mtree</filename> file is another non-essential file which is - provided for user reference. It contains the MD5 signatures of the - <emphasis>unpacked</emphasis> 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 <filename>base</filename> distribution, - this can be an excellent way of detecting trojan horse attacks on - your system.</para> - - <para>Finally, the <filename>install.sh</filename> 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:</para> - - <screen>&prompt.root; <userinput>cd /cdrom/info</userinput> -&prompt.root; <userinput>sh install.sh</userinput></screen> -</sect1> diff --git a/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml b/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml deleted file mode 100644 index 8c086b7..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml +++ /dev/null @@ -1,392 +0,0 @@ -<!-- - $FreeBSD$ - - This file contains the comments of the old TROUBLE.TXT file. ---> -<sect1 id="trouble"> - <title>Troubleshooting</title> - - <sect2 id="repairing"> - <title>Repairing an Existing &os; Installation</title> - - <para>&os; features a <quote>fixit</quote> option in the top menu - of the &man.sysinstall.8; installation program. It provides a - shell with common programs from the &os; base system; this - environment is useful for repairing or troubleshooting an - existing &os; installation. To use fixit mode, you will also - need either the <filename>fixit.flp</filename> floppy, generated - in the same fashion as the boot floppies, or the <quote>live - filesystem</quote> CDROM. In multi-disk &os; distributions, the - live filesystem image is typically located on the installation - disk. Note that some UNIX system administration experience is - required to use the fixit option.</para> - - <para>Generally, there are two ways of invoking fixit mode. Users - who can boot from the &os; installation CDROM, should do so and - then choose the <quote>fixit</quote> item from the main - &man.sysinstall.8; menu. Then select the - <quote>CDROM/DVD</quote> option from the fixit menu.</para> - - <para>Users who cannot boot from CDROM, but can boot from floppy - disk, require a few more steps. In addition to the - <filename>boot.flp</filename> and - <filename>kern<replaceable>X</replaceable>.flp</filename> disks - required for installation, create the - <filename>fixit.flp</filename> floppy disk, in the same way as - the other floppy disks. Follow the instructions for booting the - installation program from floppy disk until reaching the main - &man.sysinstall.8; menu. At that point, choose the - <quote>fixit</quote> item from the main &man.sysinstall.8; menu. - Then select the <quote>Floppy</quote> option from the fixit - menu, and insert the <filename>fixit.flp</filename> floppy disk - when prompted to do so.</para> - - <para>The CDROM and floppy fixit environments are similar, but not - identical. Both offer a shell with a variety of commands - available for checking, repairing and examining filesystems and - their contents. The CDROM version of fixit provides all of the - commands and programs available in the &os; base system, through - the live filesystem. By contrast, the floppy fixit environment - can only offer a subset of commands due to space constraints.</para> - - <para>In the floppy version of fixit, some standalone utilities - can be found in <filename>/stand</filename> or - <filename>/mnt2/stand</filename>. In the CDROM version of - fixit, these same programs can be found in - <filename>/stand</filename> or - <filename>/mnt2/rescue</filename> (as well as the rest of - the programs from the live filesystem, which can be found under - <filename>/mnt</filename>).</para> - - </sect2> - - <sect2> - <title>Common Installation Problems for &arch.print; Architecture Users</title> - - <qandaset arch="i386"> - <qandaentry> - <question> - <para>My system hangs while probing hardware during boot, or it - behaves strangely during install, or the floppy drive isn't - probed.</para> - </question> - <answer> - <para>&os; 5.0 and above makes extensive use of the system ACPI - service on the i386, amd64 and ia64 platforms to aid in system - configuration if it's detected during boot. Unfortunately, - some bugs still exist in both the ACPI driver and within system - motherboards and BIOS. The use of ACPI can be disabled by setting - the <quote>hint.acpi.0.disabled</quote> hint in the third stage - boot loader:</para> - - <screen>set hint.acpi.0.disabled="1"</screen> - - <para>This is reset each time the system is booted, so it is - necessary to add <literal>hint.acpi.0.disabled="1"</literal> - to the file - <filename>/boot/loader.conf</filename>. More information about the - boot loader can be found in the &os; Handbook.</para> - </answer> - </qandaentry> - <qandaentry arch="i386,pc98,alpha,sparc64"> - <question> - <para>My legacy ISA device used to be recognized in previous versions - of &os;, but now it's not. What happened?</para> - </question> - <answer> - <para>Some device drivers, like matcd, were removed over time due to - lack of maintainership or other reasons. Others still exist but - are disabled because of their intrusive hardware probe routines. - The following ISA device drivers fall into this category and can - re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed, - cs, sn, ie, fe, le, and lnc. To do this, stop the loader during - it's 10 second countdown and enter the following at the - prompt:</para> - - <screen>unset hint.foo.0.disabled</screen> - - <para>where <replaceable>foo</replaceable> is the name of the driver - to re-enable. This can be set permanently by editing the file - <filename>/boot/device.hints</filename> and removing the appropriate - <quote>disabled</quote> entry.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>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:</para> - - <screen>changing root device to ad1s1a panic: cannot mount root</screen> - <para>What is wrong? What can I do?</para> - - <para>What is this - <literal>bios_drive:interface(unit,partition)kernel_name</literal> - thing that is displayed with the boot help?</para> - </question> - <answer> - <para>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.</para> - - <para>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.</para> - - <para>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 <devicename>ad0</devicename> and - <devicename>ad2</devicename>.</para> - - <para>&os; is on BIOS disk 1, of type - <literal>ad</literal> and the &os; disk number is 2, so - you would say:</para> - - <screen><userinput>1:ad(2,a)kernel</userinput></screen> - - <para>Note that if you have a slave on the primary bus, the - above is not necessary (and is effectively wrong).</para> - - <para>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 <literal>da</literal> and - &os; disk number 0, so you would say:</para> - - <screen><userinput>2:da(0,a)kernel</userinput></screen> - - <para>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.</para> - - <para>Once you have determined the correct values to use, - you can put the command exactly as you would have typed it - in the <filename>/boot.config</filename> file using a - standard text editor. Unless instructed otherwise, &os; - will use the contents of this file as the default response - to the <literal>boot:</literal> prompt.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I go to boot from the hard disk for the first time - after installing &os;, but the Boot Manager prompt just - prints <literal>F?</literal> at the boot menu each time but - the boot won't go any further.</para> - </question> - <answer> - <para>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.</para> - - <para>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.</para> - - <para>The following tip is no longer recommended, but is left here - for reference:</para> - - <blockquote> - <para>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.</para> - </blockquote> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>The &man.mcd.4; driver keeps thinking that it has - found a device and this stops my Intel EtherExpress card - from working.</para> - </question> - <answer> - <para>Set the hints - <quote>hint.mcd.0.disabled="1"</quote> and - <quote>hint.mcd.1.disabled="1"</quote> - in the third stage boot loader to disable the probing - of the <devicename>mcd0</devicename> and - <devicename>mcd1</devicename> devices. Generally speaking, - you should only leave the devices that you will be using - enabled in your kernel.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>The system finds my &man.ed.4; network card, but I - keep getting device timeout errors.</para> - </question> - <answer> - <para>Your card is probably on a different IRQ from what is - specified in the <filename>/boot/device.hints</filename> file. 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 <literal>-1</literal> in the hints - for the interface.</para> - - <para>Either move the jumper on the card to a hard - configuration setting (altering the kernel settings if - necessary), or specify the IRQ as <literal>-1</literal> - by setting the hint <quote>hint.ed.0.irq="-1"</quote> - This will tell the kernel to - use the soft configuration.</para> - - <para>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.</para> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>I booted the install floppy on my IBM ThinkPad (tm) - laptop, and the keyboard is all messed up.</para> - </question> - <answer> - <para>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. Set the - hint <quote>hint.atkbd.0.flags="4"</quote> and it should work - fine.</para> - </answer> - </qandaentry> - <qandaentry arch="i386,pc98,alpha,sparc64"> - <question> - <para>My system can not find my Intel EtherExpress 16 card.</para> - </question> - <answer> - <para>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 - <filename>softset.exe</filename> program.</para> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>When installing on an EISA HP Netserver, my on-board - AIC-7xxx SCSI controller isn't detected.</para> - </question> - <answer> - <para>This is a known problem, and will hopefully be fixed - in the future. In order to get your system installed at - all, set the hint <quote>hw.eisa_slots="12"</quote> in the - third stage loader.</para> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>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.</para> - </question> - <answer> - <para>Your machine doesn't like the new - <literal>i586_copyout</literal> and - <literal>i586_copyin</literal> code for some reason. To - disable this, set the hint <quote>hint.npx.0.flags="1"</quote></para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I have this CMD640 IDE controller that is said to be - broken.</para> - </question> - <answer> - <para>&os; does not support this controller.</para> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>On a Compaq Aero notebook, I get the message <quote>No - floppy devices found! Please check ...</quote> when trying to - install from floppy.</para> - </question> - <answer> - <para>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. Set the hint - <quote>hint.fdc.0.flags="1"</quote> - This pretends the existence of the first floppy drive (as a - 1.44 MB drive) to the driver without asking the CMOS at - all.</para> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>When installing on a Dell Poweredge XE, Dell - proprietary RAID controller DSA (Dell SCSI Array) isn't - recognized.</para> - </question> - <answer> - <para>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.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>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.</para> - </question> - <answer> - <para>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.</para> - </answer> - </qandaentry> - <qandaentry arch="i386"> - <question> - <para>When I configure the network during installation on an - IBM Netfinity 3500, the system freezes.</para> - </question> - <answer> - <para>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.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When I install onto a drive managed by a Mylex PCI - RAID controller, the system fails to boot (eg. with a - <literal>read error</literal> message).</para> - </question> - <answer> - <para>There is a bug in the Mylex driver which results in it - ignoring the <quote>8GB</quote> geometry mode setting in the - BIOS. Use the 2GB mode instead.</para> - </answer> - </qandaentry> - </qandaset> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml b/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml deleted file mode 100644 index b721a9c..0000000 --- a/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml +++ /dev/null @@ -1,223 +0,0 @@ -<!-- - $FreeBSD$ - - This section contains the contents of the old UPGRADE.TXT - file. ---> -<sect1 id="upgrading"> - <title>Upgrading &os;</title> - - <para>These instructions describe a procedure for doing a binary - upgrade from an older version of &os;.</para> - - <warning> - <para>While the &os; upgrade procedure does its best to - safeguard against accidental loss of data, it is still more than - possible to <emphasis>wipe out your entire disk</emphasis> with - this installation! Please do not accept the final confirmation - request unless you have adequately backed up any important data - files.</para> - </warning> - - <important> - <para>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 <emphasis>not</emphasis> recommended.</para> - </important> - - <warning> - <para>Binary upgrades to &os; &release.current; from &os; 4-STABLE - are not supported at this time. There are some files present in - a &os; 4-STABLE whose presence can be disruptive, but are not - removed by a binary upgrade. One notable example is that an old - <filename>/usr/include/g++</filename> directory will cause C++ - programs to compile incorrectly (or not at all).</para> - - <para>These upgrade instructions are provided for the use of users - upgrading from relatively recent &os; &release.branch; - snapshots.</para> - </warning> - - <sect2> - <title>Introduction</title> - - <para>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.</para> - - <para>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.</para> - - <sect3> - <title>Upgrade Overview</title> - - <para>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.</para> - - <para>System configuration is preserved by retaining and - restoring the previous version of the following files:</para> - - <para><filename>Xaccel.ini</filename>, -<filename>XF86Config</filename>, -<filename>adduser.conf</filename>, -<filename>aliases</filename>, -<filename>aliases.db</filename>, -<filename>amd.map</filename>, -<filename>crontab</filename>, -<filename>csh.cshrc</filename>, -<filename>csh.login</filename>, -<filename>csh.logout</filename>, -<filename>cvsupfile</filename>, -<filename>dhclient.conf</filename>, -<filename>disktab</filename>, -<filename>dm.conf</filename>, -<filename>dumpdates</filename>, -<filename>exports</filename>, -<filename>fbtab</filename>, -<filename>fstab</filename>, -<filename>ftpusers</filename>, -<filename>gettytab</filename>, -<filename>gnats</filename>, -<filename>group</filename>, -<filename>hosts</filename>, -<filename>hosts.allow</filename>, -<filename>hosts.equiv</filename>, -<filename>hosts.lpd</filename>, -<filename>inetd.conf</filename>, -<filename>localtime</filename>, -<filename>login.access</filename>, -<filename>login.conf</filename>, -<filename>mail</filename>, -<filename>mail.rc</filename>, -<filename>make.conf</filename>, -<filename>manpath.config</filename>, -<filename>master.passwd</filename>, -<filename>motd</filename>, -<filename>namedb</filename>, -<filename>networks</filename>, -<filename>newsyslog.conf</filename>, -<filename>nsmb.conf</filename>, -<filename>nsswitch.conf</filename>, -<filename>pam.conf</filename>, -<filename>passwd</filename>, -<filename>periodic</filename>, -<filename>ppp</filename>, -<filename>printcap</filename>, -<filename>profile</filename>, -<filename>pwd.db</filename>, -<filename>rc.conf</filename>, -<filename>rc.conf.local</filename>, -<filename>rc.firewall</filename>, -<filename>rc.local</filename>, -<filename>remote</filename>, -<filename>resolv.conf</filename>, -<filename>rmt</filename>, -<filename>sendmail.cf</filename>, -<filename>sendmail.cw</filename>, -<filename>services</filename>, -<filename>shells</filename>, -<filename>skeykeys</filename>, -<filename>spwd.db</filename>, -<filename>ssh</filename>, -<filename>syslog.conf</filename>, -<filename>ttys</filename>, -<filename>uucp</filename> -</para> - - <para>The versions of these files which correspond to the new - version are moved to <filename>/etc/upgrade/</filename>. 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.</para> - - <para>During the upgrade procedure, the administrator is - prompted for a location into which all files from - <filename>/etc/</filename> are saved. In the event that local - modifications have been made to other files, they may be - subsequently retrieved from this location.</para> - - </sect3> - </sect2> - - <sect2> - <title>Procedure</title> - - <para>This section details the upgrade procedure. Particular - attention is given to items which substantially differ from a - normal installation.</para> - - <sect3> - <title>Backup</title> - - <para>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.</para> - </sect3> - - <sect3> - <title>Mount Filesystems</title> - - <para>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. <emphasis>Do not</emphasis> set the <quote>newfs - flag</quote> for any filesystems, as this will cause data - loss.</para> - </sect3> - - <sect3> - <title>Select Distributions</title> - - <para>When selecting distributions, there are no constraints - on which must be selected. As a general rule, the <literal>base</literal> - distribution should be selected for an update, and the <literal>man</literal> - distribution if manpages are already installed. Other - distributions may be selected beyond those originally - installed if the administrator wishes to add additional - functionality.</para> - </sect3> - - <sect3 id="fstab"> - <title>After Installation</title> - - <para>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 - <filename>/etc/rc.conf</filename> and - <filename>/etc/fstab</filename> files should be checked.</para> - </sect3> - </sect2> - - <sect2> - <title>Upgrading from Source Code</title> - - <para>Those interested in an upgrade method that allows more - flexibility and sophistication should take a look at - <ulink - url="&url.books.handbook;/cutting-edge.html">The - Cutting Edge</ulink> in the &os; Handbook. This procedure involves - rebuilding all of &os; from source code. It requires reliable - network connectivity, extra disk space, and time, but has - advantages for networks and other more complex - installations. This is roughly the same procedure as is used for - track the -STABLE or -CURRENT development branches.</para> - - <para><filename>/usr/src/UPDATING</filename> contains important - information on updating a &os; system from source code. It lists - various issues resulting from changes in &os; that may affect an - upgrade.</para> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO8859-1/installation/i386/Makefile b/release/doc/en_US.ISO8859-1/installation/i386/Makefile deleted file mode 100644 index 36f855e..0000000 --- a/release/doc/en_US.ISO8859-1/installation/i386/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $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/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" diff --git a/release/doc/en_US.ISO8859-1/installation/i386/article.sgml b/release/doc/en_US.ISO8859-1/installation/i386/article.sgml deleted file mode 100644 index c113a8c..0000000 --- a/release/doc/en_US.ISO8859-1/installation/i386/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN"> -%articles.ent; - -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> -%sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "i386"> -<!ENTITY arch.print "i386"> - -]> - -<article> -&artheader; -&abstract; -§.install; -§.layout; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO8859-1/installation/ia64/Makefile b/release/doc/en_US.ISO8859-1/installation/ia64/Makefile deleted file mode 100644 index 36f855e..0000000 --- a/release/doc/en_US.ISO8859-1/installation/ia64/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $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/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" diff --git a/release/doc/en_US.ISO8859-1/installation/ia64/article.sgml b/release/doc/en_US.ISO8859-1/installation/ia64/article.sgml deleted file mode 100644 index 0a0e54c..0000000 --- a/release/doc/en_US.ISO8859-1/installation/ia64/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN"> -%articles.ent; - -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> -%sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "ia64"> -<!ENTITY arch.print "IA-64"> - -]> - -<article> -&artheader; -&abstract; -§.install; -§.layout; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO8859-1/installation/pc98/Makefile b/release/doc/en_US.ISO8859-1/installation/pc98/Makefile deleted file mode 100644 index 36f855e..0000000 --- a/release/doc/en_US.ISO8859-1/installation/pc98/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $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/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" diff --git a/release/doc/en_US.ISO8859-1/installation/pc98/article.sgml b/release/doc/en_US.ISO8859-1/installation/pc98/article.sgml deleted file mode 100644 index 84ff87e..0000000 --- a/release/doc/en_US.ISO8859-1/installation/pc98/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN"> -%articles.ent; - -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> -%sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "pc98"> -<!ENTITY arch.print "NEC PC-98x1"> - -]> - -<article> -&artheader; -&abstract; -§.install; -§.layout; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO8859-1/installation/powerpc/Makefile b/release/doc/en_US.ISO8859-1/installation/powerpc/Makefile deleted file mode 100644 index 36f855e..0000000 --- a/release/doc/en_US.ISO8859-1/installation/powerpc/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $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/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" diff --git a/release/doc/en_US.ISO8859-1/installation/powerpc/article.sgml b/release/doc/en_US.ISO8859-1/installation/powerpc/article.sgml deleted file mode 100644 index bfe0110..0000000 --- a/release/doc/en_US.ISO8859-1/installation/powerpc/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN"> -%articles.ent; - -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> -%sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "powerpc"> -<!ENTITY arch.print "PowerPC"> - -]> - -<article> -&artheader; -&abstract; -§.install; -§.layout; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO8859-1/installation/sparc64/Makefile b/release/doc/en_US.ISO8859-1/installation/sparc64/Makefile deleted file mode 100644 index 706d297..0000000 --- a/release/doc/en_US.ISO8859-1/installation/sparc64/Makefile +++ /dev/null @@ -1,18 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= install.sgml -SRCS+= ../common/artheader.sgml -SRCS+= ../common/install.sgml -SRCS+= ../common/layout.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO8859-1/installation/sparc64/article.sgml b/release/doc/en_US.ISO8859-1/installation/sparc64/article.sgml deleted file mode 100644 index 16c0582..0000000 --- a/release/doc/en_US.ISO8859-1/installation/sparc64/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN"> -%articles.ent; - -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "sparc64"> -<!ENTITY arch.print "UltraSPARC"> -<!ENTITY release.url "ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/"> - -]> - -<article> -&artheader; -&abstract; -§.install; -§.layout; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml b/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml deleted file mode 100644 index 8fcb543..0000000 --- a/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml +++ /dev/null @@ -1,564 +0,0 @@ -<!-- - -$FreeBSD$ - -This file contains sparc64-specific installation instructions. - ---> - -<sect1 id="install"> - <title>Installing &os;</title> - - <para>This text describes how to install and boot the &arch; port. - Users of this port are encouraged to subscribe to the - &a.sparc;.</para> - - <warning> - <para>The kernel and userland binaries mentioned below are highly - experimental (for example, the kernel contains some ATA changes - and EEPROM handling code which could potentially be dangerous). - Unless you know what you are doing and are willing to cope with - any damage that might arise, you should probably not be trying - this.</para> - </warning> - - <para>Unlike &os;/i386 or &os;/alpha, there is no version of - &man.sysinstall.8; for &os;/&arch;. The installation procedure - consists of loading a kernel (either from CDROM or the network) - onto the &arch; machine, with a root filesystem on CDROM or - exported via NFS. The utilities on the root filesystem can then - be used to partition the local disk on the &arch; machine and - optionally to copy the &os; distribution to the local disk to make - a stand-alone machine.</para> - - <para>Currently, there are two ways to install &os;/&arch; on a new - machine. By far the easier of the two is to install from CDROM; - this method allows you to install &os; without any dependencies on - any other computers.</para> - - <para>If installing from CDROM is impossible or undesirable, the - alternative is to install over the network. This requires another - machine, suitably configured, to serve the boot loader, kernel, - and root filesystem to the new machine, via a combination of - RARP, TFTP, and either BOOTP or DHCP. This netboot server can be - another &os; machine, but is not required to be.</para> - - <para>You will need to decide which of these methods you want to use - for installation, as this will determine the set of files you need - to download (if any), as well as the steps required to do the - installation.</para> - -<!-- this should read "in this document" after the re-structure --> - - <important> - <para>The URLs in this section are provisional and subject to - change. Please see the archives of the &a.sparc; for the most - recent locations of files. This notice will be removed when - more permanent URLs have been determined.</para> - </important> - - <sect2 id="getting-to-prom-prompt"> - <title>Getting to the PROM Prompt</title> - - <para>Most &arch; systems are set up to boot automatically from - disk. To install &os;, you need to boot over the network or - from a CDROM, which requires you to break into the PROM - (OpenFirmware).</para> - - <para>To do this, reboot the system, and wait until the boot - message appears. It depends on the model, but should look about - like:</para> - - <screen>Sun Blade 100 (UltraSPARC-IIe), Keyboard Present -Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. -OpenBoot 4.2, 128 MB memory installed, Serial #51090132. -Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen> - - <para>If your system proceeds to boot from disk at this point, you - need to press <keycombo - action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo> - or <keycombo - action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo> - on the keyboard, or send a <command>BREAK</command> over the - serial console (using for example <command>~#</command> in - &man.tip.1; or &man.cu.1;) to get to the PROM prompt. It looks - like this:</para> - - <screenco> - <areaspec> - <area id="prompt-single" coords="1 5"> - <area id="prompt-smp" coords="2 5"> - </areaspec> - - <screen><prompt>ok </prompt> -<prompt>ok {0} </prompt></screen> - - <calloutlist> - <callout arearefs="prompt-single"> - <para>This is the prompt used on systems with just one - CPU.</para> - </callout> - - <callout arearefs="prompt-smp"> - <para>This is the prompt used on SMP systems, the digit - indicates the number of the active CPU.</para> - </callout> - </calloutlist> - </screenco> - </sect2> - - <sect2 id="prepare-cd"> - <title>Preparing for a CDROM Installation</title> - - <para>If you want to do a CDROM installation, an ISO image with a - snapshot of &os;/&arch; can be found at <ulink - url="&release.url;"></ulink>. This file can be used to create a - bootable CDROM which contains everything necessary to boot and - load at least a minimal &os; installation.</para> - -<!-- XXX ISO location?--> - <para>Place the CDROM into your drive, and break into the PROM as - described above. On the PROM prompt, type <command>boot - cdrom</command>. The system should boot into single-user mode - now, and you can create the disk label and install the base - system archive as described in <xref - linkend="creating-disk-label"> and <xref - linkend="creating-root-filesystem">.</para> - </sect2> - - <sect2 id="prepare-network"> - <title>Preparing for a Network Installation</title> - - <para>A &os;/&arch; kernel is booted by having the firmware - retrieve and execute a <application>loader</application>, which - in turn fetches and executes the actual kernel. For this boot - process, you need to set up &man.rarpd.8; and &man.tftpd.8; (for - the firmware) and &man.bootpd.8; (for the - <application>loader</application>) on another networked system. - The loader can fetch a kernel using TFTP or NFS. All of this is - covered in detail below.</para> - - <sect3 id="downloading"> - <title>Getting the Required Files</title> - - <para>For a network installation, you will need several files. - First, you will need to download a &os;/&arch; loader for - &man.tftpd.8; to serve to your &arch; client. The loader will - use either TFTP or NFS to retrieve the &os; kernel from the - netboot server. There is a separate loader for each of these - methods (i.e. a loader for TFTP and a loader for NFS). You - should download one of the following files, as - appropriate:</para> - - <itemizedlist> - <listitem> - <para><ulink - url="&release.url;loader-tftp.gz"></ulink></para> - </listitem> - - <listitem> - <para><ulink - url="&release.url;loader-nfs.gz"></ulink></para> - </listitem> - </itemizedlist> - - <para>A network installation also requires a kernel to be served - to the netboot client. A suitable kernel can be found at - <ulink url="&release.url;"></ulink>.</para> -<!-- XXX kernel filename?--> - - <para>Finally, you will need a &man.tar.1; archive which - contains the binaries and configuration files from the base - system. This file is available from <ulink - url="&release.url;distrib.tar.gz"></ulink>.</para> - </sect3> - -<!-- put the words "netboot server" in here --> - <sect3> - <title>rarpd</title> - - <para>You need to add the Ethernet address of your &os;/&arch; - system to <filename>/etc/ethers</filename> on the netboot - server. An entry looks like:</para> - - <programlisting>0:3:ba:b:92:d4 your.host.name</programlisting> - - <para>The Ethernet address is usually displayed in the boot - message.</para> - - <para>Make sure <hostid>your.host.name</hostid> is in - <filename>/etc/hosts</filename> or has a valid DNS entry (or - use an IP address). Then, start &man.rarpd.8; on a network - interface that is on the same subnet as the &os;/&arch; - system.</para> - </sect3> - -<!-- put the words "netboot server" in here --> - <sect3> - <title>tftpd</title> - - <para>Activate &man.tftpd.8; in your &man.inetd.8; - configuration by uncommenting the following line in - <filename>/etc/inetd.conf</filename>:</para> - - <programlisting>tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot</programlisting> - - <para>Copy the unpacked loader to your - <filename>/tftpboot</filename> directory, and name it with the - &os;/&arch; host's IP address in upper-case hexadecimal - notation without dots (or use appropriately-named symbolic - links). For example, your setup may look like this, for an IP - address of <hostid>192.168.0.16</hostid>:</para> - - <screen> lrwx------ 1 tmm users 9 Jul 24 17:05 /tftpboot/C0A80010 -> boot/loader - -rw-r--r-- 1 tmm users 1643021 Oct 20 18:04 /tftpboot/boot/loader</screen> - - <para>If you have trouble booting, it is very helpful to use - &man.tcpdump.1; to monitor the TFTP requests. This will allow - you to see the file name you need to use for the loader. - Error replies by the TFTP server are most often due to - incorrect file permissions.</para> - </sect3> - -<!-- put the words "netboot server" in here --> - <sect3> - <title>Setting up bootpd/dhcpd</title> - - <para>You can use either BOOTP or DHCP (both not both) to - provide some parameters to the boot loader, such as a - machine's IP address. If you are using another &os; machine - as a netboot server, the BOOTP functionality is provided by - &man.bootpd.8;, which is a part of the &os; base system. - Several DHCP servers are provided in the &os; Ports - Collection.</para> - - <para>If you are going to use &man.bootpd.8;, create entries for - your &os;/&arch; system in the server's - <filename>/etc/bootptab</filename> (see &man.bootptab.5; for - more details):</para> - - <programlisting>.default:\ - :bf="kernel":dn=local:ds=<replaceable>name-server-ip-address</replaceable>:\ - :gw=<replaceable>gateway-ip-address</replaceable>:ht=ether:hd="/tftpboot/boot/kernel":hn:\ - :sa="<replaceable>tftp-server-ip-address</replaceable>":\ - :rp="<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>":\ - :sm=<replaceable>ip-netmask</replaceable> - -<replaceable>name-of-the-entry</replaceable>:\ - ha=<replaceable>sparc64-ethernet-address</replaceable>:ip=<replaceable>sparc64-ip-address</replaceable>:tc=.default</programlisting> - - <para>The Ethernet address must be the same as the one in the - TFTP example above, but it is specified hexadecimal notation - without colons (for the example above, this would be - <literal>0003ba0b92d4</literal>). NFS/TFTP specific entries - can be omitted if the given method is not used. The strings - given in the <literal>hd</literal> and <literal>bf</literal> - properties are concatenated to give the boot file name. If - your kernel is named differently or you use another directory, - change these values as required. If you are booting using - NFS, remove the <literal>bf</literal> and - <literal>hd</literal> settings (or change them to specify the - directory and file inside the NFS root hierarchy in which the - kernel will reside). The name of the host entry is - conventionally the host name without the domain - appended.</para> - - <para>For a DHCP server, add an entry similar to the following - to your <filename>dhcpd.conf</filename> file. An example - entry for <application>ISC DHCP</application> version 2 - (available in the &os; Ports Collection as <filename - role="package">net/isc-dhcp2</filename>) is shown - below:</para> - - <programlisting>host <replaceable>name-of-entry</replaceable> { - hardware ethernet <replaceable>sparc64-ethernet-address</replaceable>; - option host-name "<replaceable>sparc64-fully-qualified-domain-name</replaceable>"; - fixed-address <replaceable>sparc64-ip-address</replaceable>; - always-reply-rfc1048 on; - filename "kernel"; - option root-path "<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>"; -}</programlisting> - - <para>The <literal>filename</literal> option corresponds to the - concatenation of <literal>hd</literal> and - <literal>bf</literal> in <filename>/etc/bootptab</filename>. - The Ethernet address is specified in hexadecimal with colons, - just like in the &man.rarpd.8; example above. - <literal>options root-path</literal> corresponds to - <literal>rp</literal> in <filename>/etc/bootptab</filename>. - If the name given in <literal>option host-name</literal> is - resolvable, i.e. has a DNS entry or is associated with an - address in <filename>/etc/hosts</filename>, the - <literal>fixed-address</literal> specification can be - omitted.</para> - </sect3> - - <sect3> - <title>Loading the Kernel</title> - - <para>With the daemons on the netboot server configured, the - next step is to copy the kernel (obtained during the steps of - <xref linkend="downloading">) to an appropriate directory. - There are two ways of retrieving a kernel over the network: - TFTP and NFS. (You specified one of these two alternatives by - picking a loader.)</para> - - <para>For both TFTP and NFS, the loader will use the parameters - that it obtained via BOOTP or DHCP to find the kernel.</para> - - <sect4> - <title>Loading the Kernel over TFTP</title> - - <para>Place the kernel in the directory you specified using - <literal>bf</literal> and <literal>hd</literal> in the - <filename>/etc/bootptab</filename> or the - <literal>filename</literal> parameter to - <filename>dhcpd.conf</filename>.</para> - </sect4> - - <sect4> - <title>Loading the Kernel over NFS</title> - - <para>Export the directory that was specified by the - <literal>rp</literal> property in - <filename>/etc/bootptab</filename> or the - <literal>root-path</literal> parameter in - <filename>dhcpd.conf</filename> (see &man.exports.5;). Copy - the kernel to the directory you specified using - <literal>bf</literal> and <literal>hd</literal> in the - <filename>/etc/bootptab</filename> or the - <literal>filename</literal> parameter to - <filename>dhcpd.conf</filename>.</para> - </sect4> - </sect3> - - <sect3> - <title>Loading the Base System to the Netboot Server</title> - - <para>You must extract the base system distribution image to the - NFS root directory specified either by the - <literal>rp</literal> option in - <filename>/etc/bootptab</filename> or the - <literal>root-path</literal> option in - <filename>dhcpd.conf</filename>. This directory tree will - become the &arch;'s root filesystem once the kernel is booted. - Besides providing a normal userland environment, it also - contains all of the necessary utilities for you to install the - distribution on the &arch; client's local disk.</para> - - <para>Using whatever editing tools you have on the netboot - server, you probably will want to edit the &arch;'s - <filename>/etc/fstab</filename> and - <filename>/etc/rc.conf</filename> and set a - <username>root</username> password.</para> - </sect3> - - <sect3> - <title>Booting</title> - - <para>If all goes well, you can now boot the &os; on your &arch; - machine by dropping into the PROM prompt as described in <xref - linkend="getting-to-prom-prompt">. Now, just type - <command>boot net</command> and the system should boot. - Specifically, the loader is retrieved via TFTP, it then does a - BOOTP request and will proceed to load the kernel (either - using TFTP or NFS, depending on your choice of loader). Then, - it should wait 10 seconds for user input and proceed to - execute the kernel.</para> - - <para>If something does not work in between, and you suspect - TFTP/NFS/BOOTP problems, <application>Ethereal</application> - (available in the &os; Ports Collection as <filename - role="package"> net/ethereal</filename>) is usually helpful. - The most common problems are related to bad file permissions. - Also note that &man.rarpd.8; will not answer to packets under - some circumstances, refer to the manual page for - details.</para> - </sect3> - </sect2> - - <sect2 id="creating-disk-label"> - <title>Creating a Disk Label</title> - - <para>The kernel supports the Sun disk label format, so you can - label the disks you want to use with &os; from Solaris.</para> - - <para>&os; disk labels must currently be created by hand, as - &man.sysinstall.8; is not yet available on &os;/&arch;. Please - refer to the <ulink - url="&url.books.handbook;/">&os; - Handbook</ulink> for more information about labels and special - partitions.</para> - - <para>On &os;/&arch;, a Sun compatibility label is embedded in the - &os; label; this is needed for the PROM to boot from disk. This - imposes an additional restriction on the disk label format: - partitions are required to start on a cylinder boundary.</para> - - <para>To create a disk label, the following procedure is the - easiest:</para> - - <procedure> - <step> - <para>Run <command>disklabel -w -r - <replaceable>device</replaceable> auto</command> to create a - basic disk label. The third argument you need specify here - is just the name of the device, not the complete path to the - device node (e.g. <devicename>ad0</devicename> for the first - ATA disk).</para> - </step> - - <step> - <para> Use <command>disklabel -e - <replaceable>device</replaceable></command> to open an - editor in which you can edit the disk label. The - information presented to you should look like:</para> - - <screen># /dev/ad6c: -type: unknown -disk: amnesiac -label: -flags: -bytes/sector: 512 -sectors/track: 63 -tracks/cylinder: 16 -sectors/cylinder: 1008 -cylinders: 79780 -sectors/unit: 80418240 -rpm: 3600 -interleave: 1 -trackskew: 0 -cylinderskew: 0 -headswitch: 0 # milliseconds -track-to-track seek: 0 # milliseconds -drivedata: 0 - -8 partitions: -# size offset fstype [fsize bsize bps/cpg] - c: 80418240 0 unused 0 0 # (Cyl. 0 - 79779)</screen> - - <para>You can now add new partitions in the same format as the - already present line. Using <literal>*</literal> in the - offset field makes the procedure easier; please refer to the - &man.disklabel.8; manual page for more information.</para> - - <para>To make sure the restriction mentioned above is met, the - size of each partition must be a multiple of the number of - sectors per cylinder as shown in the information that is - presented in the editor (1008 in the example above).</para> - - <para>When you are done, save your changes and quit the - editor.i This will cause the disk label to be - written.</para> - - <warning> - <para>This procedure will overwrite any disk label that may - be already present on the disk. Any existing filesystems - on this disk must have their respective partition entries - in the old and new label match - <emphasis>exactly</emphasis>, or they will be - lost.</para> - </warning> - - <para>If you want to double-check that your partitions end on - cylinder boundaries, run <command>disklabel -e - <replaceable>device</replaceable></command> again. The - editor will display the cylinders used by a particular - partition on the right hand side of the output. If any of - the partitions you defined (i.e. anything except partition - <literal>c</literal>) shows an <literal>*</literal> next to - it, the partition does <emphasis>NOT</emphasis> start or end - on a cylinder boundary. You <emphasis>MUST</emphasis> fix - these or your system will not work.</para> - </step> - - <step> - <para>Use <command>disklabel -B</command> if you want to make - the disk bootable for &os;/&arch;.</para> - - <warning> - <para>Using <command>disklabel -B</command> on a disk will - overwrite any preexisting boot block, so it will likely - render any other operating system installed on the same - disk unbootable.</para> - </warning> - - <para>If you do not want to overwrite the boot block, it is - possible to load the <application>loader</application> via - TFTP as described above, but have it boot the kernel from - disk. This requires a special loader binary, which is - available at <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz"></ulink></para> - </step> - </procedure> - </sect2> - - <sect2 id="creating-root-filesystem"> - <title>Creating the Root Fileystem</title> - - <para>If you want to boot from a local disk, you will need to - create a root filesystem to hold the base system binaries and - configuration files (and optionally other filesystems mounted - in places such as <filename>/usr</filename> and - <filename>/var</filename>).</para> - - <para>The kernel contains support for Sun disklabels, so you can - use Solaris disks, which may even be prepared using - <application>newfs</application> under Solaris. NetBSD disk - labels and filesystems are also usable from &os;.</para> - - <warning> - <para>Do <emphasis>not</emphasis> run Solaris - <application>fsck</application> on filesystems modified by - &os;. Doing so will damage the file permissions.</para> - </warning> - - <para>To create filesystems and to install the base system, boot - from CDROM or via NFS and create a disk label as described in - <xref linkend="creating-disk-label">.</para> - - <para>When booting the first time and you have not entered your - root partition into <filename>/etc/fstab</filename> yet, you may - need to specify your root partition on the mountroot prompt when - booting (use a format like - <command>ufs:<replaceable>disk</replaceable><replaceable>partition</replaceable></command>, - i.e. leave the slice specification out). If the kernel does - automatically attempt to boot from another filesystem, press a - key other than <keycap>Enter</keycap> on the - <application>loader</application> prompt:</para> - - <screen>Hit [Enter] to boot immediately, or any other key for command prompt.</screen> - - <para>Then, boot the kernel using <command>boot -a -s</command>, - which will cause the kernel to ask you for the root partition - and then boot into single-user mode. Once the root filesystem - has been entered into <filename>/etc/fstab</filename>, it should - be automatically mounted as <filename>/</filename> on the next - boot.</para> - - <para>If you are booting over the network (via NFS), the above - BOOTP entries should suffice to have the kernel find and mount - the root filesystem via NFS.</para> - </sect2> - - <sect2 id="installing-base-system"> - <title>Installing the Base System</title> - - <para>If you booted the kernel from the network, you downloaded a - &man.tar.1; archive with the base system and exported it from - the netboot server via NFS. You can unpack this same archive to - your local disk to create a stand-alone system (remember to copy - the kernel over as well).</para> - - <para>If you booted from CDROM, the same archive is available in - <filename>/root/</filename> on the CDROM.</para> - - <para>Before booting the system stand-alone, you will want to edit - <filename>/etc/fstab</filename> and - <filename>/etc/rc.conf</filename> and set a - <username>root</username> password.</para> - - <para>Note that some programs from the base system may not be - present in the archive, or may not work properly yet.</para> - </sect2> -</sect1> |
