2 The FreeBSD Documentation Project
3 The FreeBSD French Documentation Project
7 Original revision: 1.12
8 Ce fichier contient les instructions pour l'installation
9 specifique aux systemes sparc64.
14 <title>***Non traduit***Installing &os;</title>
16 <para>This text describes how to install and boot the &arch; port.
17 Users of this port are encouraged to subscribe to the
21 <para>The kernel and userland binaries mentioned below are highly
22 experimental (for example, the kernel contains some ATA changes
23 and EEPROM handling code which could potentially be dangerous).
24 Unless you know what you are doing and are willing to cope with
25 any damage that might arise, you should probably not be trying
29 <para>Unlike &os;/i386 or &os;/alpha, there is no version of
30 &man.sysinstall.8; for &os;/&arch;. The installation procedure
31 consists of loading a kernel (either from CDROM or the network)
32 onto the &arch; machine, with a root filesystem on CDROM or
33 exported via NFS. The utilities on the root filesystem can then
34 be used to partition the local disk on the &arch; machine and
35 optionally to copy the &os; distribution to the local disk to make
36 a stand-alone machine.</para>
38 <para>Currently, there are two ways to install &os;/&arch; on a new
39 machine. By far the easier of the two is to install from CDROM;
40 this method allows you to install &os; without any dependencies on
41 any other computers.</para>
43 <para>If installing from CDROM is impossible or undesirable, the
44 alternative is to install over the network. This requires another
45 machine, suitably configured, to serve the boot loader, kernel,
46 and root filesystem to the new machine, via a combination of
47 RARP, TFTP, and either BOOTP or DHCP. This netboot server can be
48 another &os; machine, but is not required to be.</para>
50 <para>You will need to decide which of these methods you want to use
51 for installation, as this will determine the set of files you need
52 to download (if any), as well as the steps required to do the
55 <!-- this should read "in this document" after the re-structure -->
58 <para>The URLs in this section are provisional and subject to
59 change. Please see the archives of the &a.sparc; for the most
60 recent locations of files. This notice will be removed when
61 more permanent URLs have been determined.</para>
64 <sect2 id="getting-to-prom-prompt">
65 <title>Getting to the PROM Prompt</title>
67 <para>Most &arch; systems are set up to boot automatically from
68 disk. To install &os;, you need to boot over the network or
69 from a CDROM, which requires you to break into the PROM
70 (OpenFirmware).</para>
72 <para>To do this, reboot the system, and wait until the boot
73 message appears. It depends on the model, but should look about
76 <screen>Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
77 Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved.
78 OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
79 Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
81 <para>If your system proceeds to boot from disk at this point, you
82 need to press <keycombo
83 action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo>
85 action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo>
86 on the keyboard, or send a <command>BREAK</command> over the
87 serial console (using for example <command>~#</command> in
88 &man.tip.1; or &man.cu.1;) to get to the PROM prompt. It looks
93 <area id="prompt-single" coords="1 5">
94 <area id="prompt-smp" coords="2 5">
97 <screen><prompt>ok </prompt>
98 <prompt>ok {0} </prompt></screen>
101 <callout arearefs="prompt-single">
102 <para>This is the prompt used on systems with just one
106 <callout arearefs="prompt-smp">
107 <para>This is the prompt used on SMP systems, the digit
108 indicates the number of the active CPU.</para>
114 <sect2 id="prepare-cd">
115 <title>Preparing for a CDROM Installation</title>
117 <para>If you want to do a CDROM installation, an ISO image with a
118 snapshot of &os;/&arch; can be found at <ulink
119 url="&release.url;"></ulink>. This file can be used to create a
120 bootable CDROM which contains everything necessary to boot and
121 load at least a minimal &os; installation.</para>
123 <!-- XXX ISO location?-->
124 <para>Place the CDROM into your drive, and break into the PROM as
125 described above. On the PROM prompt, type <command>boot
126 cdrom</command>. The system should boot into single-user mode
127 now, and you can create the disk label and install the base
128 system archive as described in <xref
129 linkend="creating-disk-label"> and <xref
130 linkend="creating-root-filesystem">.</para>
133 <sect2 id="prepare-network">
134 <title>Preparing for a Network Installation</title>
136 <para>A &os;/&arch; kernel is booted by having the firmware
137 retrieve and execute a <application>loader</application>, which
138 in turn fetches and executes the actual kernel. For this boot
139 process, you need to set up &man.rarpd.8; and &man.tftpd.8; (for
140 the firmware) and &man.bootpd.8; (for the
141 <application>loader</application>) on another networked system.
142 The loader can fetch a kernel using TFTP or NFS. All of this is
143 covered in detail below.</para>
145 <sect3 id="downloading">
146 <title>Getting the Required Files</title>
148 <para>For a network installation, you will need several files.
149 First, you will need to download a &os;/&arch; loader for
150 &man.tftpd.8; to serve to your &arch; client. The loader will
151 use either TFTP or NFS to retrieve the &os; kernel from the
152 netboot server. There is a separate loader for each of these
153 methods (i.e. a loader for TFTP and a loader for NFS). You
154 should download one of the following files, as
160 url="&release.url;loader-tftp.gz"></ulink></para>
165 url="&release.url;loader-nfs.gz"></ulink></para>
169 <para>A network installation also requires a kernel to be served
170 to the netboot client. A suitable kernel can be found at
171 <ulink url="&release.url;"></ulink>.</para>
172 <!-- XXX kernel filename?-->
174 <para>Finally, you will need a &man.tar.1; archive which
175 contains the binaries and configuration files from the base
176 system. This file is available from <ulink
177 url="&release.url;distrib.tar.gz"></ulink>.</para>
180 <!-- put the words "netboot server" in here -->
184 <para>You need to add the Ethernet address of your &os;/&arch;
185 system to <filename>/etc/ethers</filename> on the netboot
186 server. An entry looks like:</para>
188 <programlisting>0:3:ba:b:92:d4 your.host.name</programlisting>
190 <para>The Ethernet address is usually displayed in the boot
193 <para>Make sure <hostid>your.host.name</hostid> is in
194 <filename>/etc/hosts</filename> or has a valid DNS entry (or
195 use an IP address). Then, start &man.rarpd.8; on a network
196 interface that is on the same subnet as the &os;/&arch;
200 <!-- put the words "netboot server" in here -->
204 <para>Activate &man.tftpd.8; in your &man.inetd.8;
205 configuration by uncommenting the following line in
206 <filename>/etc/inetd.conf</filename>:</para>
208 <programlisting>tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot</programlisting>
210 <para>Copy the unpacked loader to your
211 <filename>/tftpboot</filename> directory, and name it with the
212 &os;/&arch; host's IP address in upper-case hexadecimal
213 notation without dots (or use appropriately-named symbolic
214 links). For example, your setup may look like this, for an IP
215 address of <hostid>192.168.0.16</hostid>:</para>
217 <screen> lrwx------ 1 tmm users 9 Jul 24 17:05 /tftpboot/C0A80010 -> boot/loader
218 -rw-r--r-- 1 tmm users 1643021 Oct 20 18:04 /tftpboot/boot/loader</screen>
220 <para>If you have trouble booting, it is very helpful to use
221 &man.tcpdump.1; to monitor the TFTP requests. This will allow
222 you to see the file name you need to use for the loader.
223 Error replies by the TFTP server are most often due to
224 incorrect file permissions.</para>
227 <!-- put the words "netboot server" in here -->
229 <title>Setting up bootpd/dhcpd</title>
231 <para>You can use either BOOTP or DHCP (both not both) to
232 provide some parameters to the boot loader, such as a
233 machine's IP address. If you are using another &os; machine
234 as a netboot server, the BOOTP functionality is provided by
235 &man.bootpd.8;, which is a part of the &os; base system.
236 Several DHCP servers are provided in the &os; Ports
239 <para>If you are going to use &man.bootpd.8;, create entries for
240 your &os;/&arch; system in the server's
241 <filename>/etc/bootptab</filename> (see &man.bootptab.5; for
242 more details):</para>
244 <programlisting>.default:\
245 :bf="kernel":dn=local:ds=<replaceable>name-server-ip-address</replaceable>:\
246 :gw=<replaceable>gateway-ip-address</replaceable>:ht=ether:hd="/tftpboot/boot/kernel":hn:\
247 :sa="<replaceable>tftp-server-ip-address</replaceable>":\
248 :rp="<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>":\
249 :sm=<replaceable>ip-netmask</replaceable>
251 <replaceable>name-of-the-entry</replaceable>:\
252 ha=<replaceable>sparc64-ethernet-address</replaceable>:ip=<replaceable>sparc64-ip-address</replaceable>:tc=.default</programlisting>
254 <para>The Ethernet address must be the same as the one in the
255 TFTP example above, but it is specified hexadecimal notation
256 without colons (for the example above, this would be
257 <literal>0003ba0b92d4</literal>). NFS/TFTP specific entries
258 can be omitted if the given method is not used. The strings
259 given in the <literal>hd</literal> and <literal>bf</literal>
260 properties are concatenated to give the boot file name. If
261 your kernel is named differently or you use another directory,
262 change these values as required. If you are booting using
263 NFS, remove the <literal>bf</literal> and
264 <literal>hd</literal> settings (or change them to specify the
265 directory and file inside the NFS root hierarchy in which the
266 kernel will reside). The name of the host entry is
267 conventionally the host name without the domain
270 <para>For a DHCP server, add an entry similar to the following
271 to your <filename>dhcpd.conf</filename> file. An example
272 entry for <application>ISC DHCP</application> version 2
273 (available in the &os; Ports Collection as <filename
274 role="package">net/isc-dhcp2</filename>) is shown
277 <programlisting>host <replaceable>name-of-entry</replaceable> {
278 hardware ethernet <replaceable>sparc64-ethernet-address</replaceable>;
279 option host-name "<replaceable>sparc64-fully-qualified-domain-name</replaceable>";
280 fixed-address <replaceable>sparc64-ip-address</replaceable>;
281 always-reply-rfc1048 on;
283 option root-path "<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>";
286 <para>The <literal>filename</literal> option corresponds to the
287 concatenation of <literal>hd</literal> and
288 <literal>bf</literal> in <filename>/etc/bootptab</filename>.
289 The Ethernet address is specified in hexadecimal with colons,
290 just like in the &man.rarpd.8; example above.
291 <literal>options root-path</literal> corresponds to
292 <literal>rp</literal> in <filename>/etc/bootptab</filename>.
293 If the name given in <literal>option host-name</literal> is
294 resolvable, i.e. has a DNS entry or is associated with an
295 address in <filename>/etc/hosts</filename>, the
296 <literal>fixed-address</literal> specification can be
301 <title>Loading the Kernel</title>
303 <para>With the daemons on the netboot server configured, the
304 next step is to copy the kernel (obtained during the steps of
305 <xref linkend="downloading">) to an appropriate directory.
306 There are two ways of retrieving a kernel over the network:
307 TFTP and NFS. (You specified one of these two alternatives by
308 picking a loader.)</para>
310 <para>For both TFTP and NFS, the loader will use the parameters
311 that it obtained via BOOTP or DHCP to find the kernel.</para>
314 <title>Loading the Kernel over TFTP</title>
316 <para>Place the kernel in the directory you specified using
317 <literal>bf</literal> and <literal>hd</literal> in the
318 <filename>/etc/bootptab</filename> or the
319 <literal>filename</literal> parameter to
320 <filename>dhcpd.conf</filename>.</para>
324 <title>Loading the Kernel over NFS</title>
326 <para>Export the directory that was specified by the
327 <literal>rp</literal> property in
328 <filename>/etc/bootptab</filename> or the
329 <literal>root-path</literal> parameter in
330 <filename>dhcpd.conf</filename> (see &man.exports.5;). Copy
331 the kernel to the directory you specified using
332 <literal>bf</literal> and <literal>hd</literal> in the
333 <filename>/etc/bootptab</filename> or the
334 <literal>filename</literal> parameter to
335 <filename>dhcpd.conf</filename>.</para>
340 <title>Loading the Base System to the Netboot Server</title>
342 <para>You must extract the base system distribution image to the
343 NFS root directory specified either by the
344 <literal>rp</literal> option in
345 <filename>/etc/bootptab</filename> or the
346 <literal>root-path</literal> option in
347 <filename>dhcpd.conf</filename>. This directory tree will
348 become the &arch;'s root filesystem once the kernel is booted.
349 Besides providing a normal userland environment, it also
350 contains all of the necessary utilities for you to install the
351 distribution on the &arch; client's local disk.</para>
353 <para>Using whatever editing tools you have on the netboot
354 server, you probably will want to edit the &arch;'s
355 <filename>/etc/fstab</filename> and
356 <filename>/etc/rc.conf</filename> and set a
357 <username>root</username> password.</para>
361 <title>Booting</title>
363 <para>If all goes well, you can now boot the &os; on your &arch;
364 machine by dropping into the PROM prompt as described in <xref
365 linkend="getting-to-prom-prompt">. Now, just type
366 <command>boot net</command> and the system should boot.
367 Specifically, the loader is retrieved via TFTP, it then does a
368 BOOTP request and will proceed to load the kernel (either
369 using TFTP or NFS, depending on your choice of loader). Then,
370 it should wait 10 seconds for user input and proceed to
371 execute the kernel.</para>
373 <para>If something does not work in between, and you suspect
374 TFTP/NFS/BOOTP problems, <application>Ethereal</application>
375 (available in the &os; Ports Collection as <filename
376 role="package"> net/ethereal</filename>) is usually helpful.
377 The most common problems are related to bad file permissions.
378 Also note that &man.rarpd.8; will not answer to packets under
379 some circumstances, refer to the manual page for
384 <sect2 id="creating-disk-label">
385 <title>Creating a Disk Label</title>
387 <para>The kernel supports the Sun disk label format, so you can
388 label the disks you want to use with &os; from Solaris.</para>
390 <para>&os; disk labels must currently be created by hand, as
391 &man.sysinstall.8; is not yet available on &os;/&arch;. Please
393 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
394 Handbook</ulink> for more information about labels and special
397 <para>On &os;/&arch;, a Sun compatibility label is embedded in the
398 &os; label; this is needed for the PROM to boot from disk. This
399 imposes an additional restriction on the disk label format:
400 partitions are required to start on a cylinder boundary.</para>
402 <para>To create a disk label, the following procedure is the
407 <para>Run <command>disklabel -w -r
408 <replaceable>device</replaceable> auto</command> to create a
409 basic disk label. The third argument you need specify here
410 is just the name of the device, not the complete path to the
411 device node (e.g. <devicename>ad0</devicename> for the first
416 <para> Use <command>disklabel -e
417 <replaceable>device</replaceable></command> to open an
418 editor in which you can edit the disk label. The
419 information presented to you should look like:</para>
429 sectors/cylinder: 1008
431 sectors/unit: 80418240
436 headswitch: 0 # milliseconds
437 track-to-track seek: 0 # milliseconds
441 # size offset fstype [fsize bsize bps/cpg]
442 c: 80418240 0 unused 0 0 # (Cyl. 0 - 79779)</screen>
444 <para>You can now add new partitions in the same format as the
445 already present line. Using <literal>*</literal> in the
446 offset field makes the procedure easier; please refer to the
447 &man.disklabel.8; manual page for more information.</para>
449 <para>To make sure the restriction mentioned above is met, the
450 size of each partition must be a multiple of the number of
451 sectors per cylinder as shown in the information that is
452 presented in the editor (1008 in the example above).</para>
454 <para>When you are done, save your changes and quit the
455 editor.i This will cause the disk label to be
459 <para>This procedure will overwrite any disk label that may
460 be already present on the disk. Any existing filesystems
461 on this disk must have their respective partition entries
462 in the old and new label match
463 <emphasis>exactly</emphasis>, or they will be
467 <para>If you want to double-check that your partitions end on
468 cylinder boundaries, run <command>disklabel -e
469 <replaceable>device</replaceable></command> again. The
470 editor will display the cylinders used by a particular
471 partition on the right hand side of the output. If any of
472 the partitions you defined (i.e. anything except partition
473 <literal>c</literal>) shows an <literal>*</literal> next to
474 it, the partition does <emphasis>NOT</emphasis> start or end
475 on a cylinder boundary. You <emphasis>MUST</emphasis> fix
476 these or your system will not work.</para>
480 <para>Use <command>disklabel -B</command> if you want to make
481 the disk bootable for &os;/&arch;.</para>
484 <para>Using <command>disklabel -B</command> on a disk will
485 overwrite any preexisting boot block, so it will likely
486 render any other operating system installed on the same
487 disk unbootable.</para>
490 <para>If you do not want to overwrite the boot block, it is
491 possible to load the <application>loader</application> via
492 TFTP as described above, but have it boot the kernel from
493 disk. This requires a special loader binary, which is
495 url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz"></ulink></para>
500 <sect2 id="creating-root-filesystem">
501 <title>Creating the Root Fileystem</title>
503 <para>If you want to boot from a local disk, you will need to
504 create a root filesystem to hold the base system binaries and
505 configuration files (and optionally other filesystems mounted
506 in places such as <filename>/usr</filename> and
507 <filename>/var</filename>).</para>
509 <para>The kernel contains support for Sun disklabels, so you can
510 use Solaris disks, which may even be prepared using
511 <application>newfs</application> under Solaris. NetBSD disk
512 labels and filesystems are also usable from &os;.</para>
515 <para>Do <emphasis>not</emphasis> run Solaris
516 <application>fsck</application> on filesystems modified by
517 &os;. Doing so will damage the file permissions.</para>
520 <para>To create filesystems and to install the base system, boot
521 from CDROM or via NFS and create a disk label as described in
522 <xref linkend="creating-disk-label">.</para>
524 <para>When booting the first time and you have not entered your
525 root partition into <filename>/etc/fstab</filename> yet, you may
526 need to specify your root partition on the mountroot prompt when
527 booting (use a format like
528 <command>ufs:<replaceable>disk</replaceable><replaceable>partition</replaceable></command>,
529 i.e. leave the slice specification out). If the kernel does
530 automatically attempt to boot from another filesystem, press a
531 key other than <keycap>Enter</keycap> on the
532 <application>loader</application> prompt:</para>
534 <screen>Hit [Enter] to boot immediately, or any other key for command prompt.</screen>
536 <para>Then, boot the kernel using <command>boot -a -s</command>,
537 which will cause the kernel to ask you for the root partition
538 and then boot into single-user mode. Once the root filesystem
539 has been entered into <filename>/etc/fstab</filename>, it should
540 be automatically mounted as <filename>/</filename> on the next
543 <para>If you are booting over the network (via NFS), the above
544 BOOTP entries should suffice to have the kernel find and mount
545 the root filesystem via NFS.</para>
548 <sect2 id="installing-base-system">
549 <title>Installing the Base System</title>
551 <para>If you booted the kernel from the network, you downloaded a
552 &man.tar.1; archive with the base system and exported it from
553 the netboot server via NFS. You can unpack this same archive to
554 your local disk to create a stand-alone system (remember to copy
555 the kernel over as well).</para>
557 <para>If you booted from CDROM, the same archive is available in
558 <filename>/root/</filename> on the CDROM.</para>
560 <para>Before booting the system stand-alone, you will want to edit
561 <filename>/etc/fstab</filename> and
562 <filename>/etc/rc.conf</filename> and set a
563 <username>root</username> password.</para>
565 <para>Note that some programs from the base system may not be
566 present in the archive, or may not work properly yet.</para>