1 .\" Copyright (c) 1988, 1993 The Regents of the University of California.
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)2.t 8.1 (Berkeley) 7/27/93
29 .\" $FreeBSD: src/share/doc/smm/01.setup/2.t,v 1.7 1999/08/28 00:18:35 peter Exp $
30 .\" $DragonFly: src/share/doc/smm/01.setup/2.t,v 1.2 2003/06/17 04:36:57 dillon Exp $
34 .ds LH "Installing/Operating \*(4B
37 .Sh 1 "Bootstrap procedure"
39 This section explains the bootstrap procedure that can be used
40 to get the kernel supplied with this distribution running on your machine.
41 If you are not currently running \*(Ps you will
42 have to do a full bootstrap.
43 Section 3 describes how to upgrade a \*(Ps system.
44 An understanding of the operations used in a full bootstrap
45 is helpful in doing an upgrade as well.
46 In either case, it is highly desirable to read and understand
47 the remainder of this document before proceeding.
49 The distribution supports a somewhat wider set of machines than
50 those for which we have built binaries.
51 The architectures that are supported only in source form include:
53 Intel 386/486-based machines (ISA/AT or EISA bus only)
55 Sony News MIPS-based workstations
57 Omron Luna 68000-based workstations
59 If you wish to run one of these architectures,
60 you will have to build a cross compilation environment.
61 Note that the distribution does
63 include the machine support for the Tahoe and VAX architectures
64 found in previous BSD distributions.
65 Our primary development environment is the HP9000/300 series machines.
66 The other architectures are developed and supported by
67 people outside the university.
68 Consequently, we are not able to directly test or maintain these
69 other architectures, so cannot comment on their robustness,
70 reliability, or completeness.
71 .Sh 2 "Bootstrapping from the tape"
73 The set of files on the distribution tape are as follows:
81 (SPARC) image of the root filesystem
104 except sys and contrib
111 (8mm Exabyte tape distributions only)
117 The tape bootstrap procedure used to create a
118 working system involves the following major steps:
120 Transfer a bootable root filesystem from the tape to a disk
121 and get it booted and running.
123 Build and restore the
127 filesystems from tape with
130 Extract the system and utility source files as desired.
132 The following sections describe the above steps in detail.
133 The details of the first step vary between architectures.
134 The specific steps for the HP300, SPARC, and DECstation are
135 given in the next three sections respectively.
136 You should follow the instructions for your particular architecture.
138 commands you are expected to type are shown in italics, while that
139 information printed by the system is shown emboldened.
140 .Sh 2 "Booting the HP300"
141 .Sh 3 "Supported hardware"
143 The hardware supported by \*(4B for the HP300/400 is as follows:
148 68020 based (318, 319, 320, 330 and 350),
149 68030 based (340, 345, 360, 370, 375, 400) and
150 68040 based (380, 425, 433).
154 HP-IB/CS80 (7912, 7914, 7933, 7936, 7945, 7957, 7958, 7959, 2200, 2203)
155 and SCSI-I (including magneto-optical).
159 Low-density CS80 cartridge (7914, 7946, 9144),
160 high-density CS80 cartridge (9145),
166 98644 built-in single-port, 98642 4-port and 98638 8-port interfaces.
170 98643 internal and external LAN cards.
174 Terminal emulation and raw frame buffer support for
175 98544 / 98545 / 98547 (Topcat color & monochrome),
176 98548 / 98549 / 98550 (Catseye color & monochrome),
177 98700 / 98710 (Gatorbox),
178 98720 / 98721 (Renaissance),
179 98730 / 98731 (DaVinci) and
180 A1096A (Hyperion monochrome).
184 General interface supporting all HIL devices.
185 (e.g. keyboard, 2 and 3 button mice, ID module, ...)
189 Battery-backed real time clock,
190 builtin and 98625A/B HP-IB interfaces,
191 builtin and 98658A SCSI interfaces,
192 serial printers and plotters on HP-IB,
193 and SCSI autochanger device.
197 Major items that are not supported
198 include the 310 and 332 CPU's, 400 series machines
199 configured for Domain/OS, EISA and VME bus adaptors, audio, the centronics
200 port, 1/2" tape drives (7980), CD-ROM, and the PVRX/TVRX 3D graphics displays.
201 .Sh 3 "Standalone device file naming"
203 The standalone system device name syntax on the HP300 is of the form:
208 \fIxx\fP is the device type,
209 \fIa\fP specifies the adaptor to use,
210 \fIc\fP the controller,
211 \fIu\fP the unit, and
213 The \fIdevice type\fP differentiates the various disks and tapes and is one of:
214 ``rd'' for HP-IB CS80 disks,
215 ``ct'' for HP-IB CS80 cartridge tapes, or
216 ``sd'' for SCSI-I disks
217 (SCSI-I tapes are currently not supported).
218 The \fIadaptor\fP field is a logical HP-IB or SCSI bus adaptor card number.
219 This will typically be
221 0 for devices on the ``slow'' HP-IB interface (usually tapes) and
222 1 for devices on the ``fast'' HP-IB interface (usually disks).
223 To get a complete mapping of physical (select-code) to logical card numbers
224 just type a ^C at the standalone prompt.
225 The \fIcontroller\fP field is the disk or tape's target number on the
227 For SCSI the range is 0 to 6 (7 is the adaptor address) and
228 for HP-IB the range is 0 to 7.
229 The \fIunit\fP field is unused and should be 0.
230 The \fIpartition\fP field is interpreted differently for tapes
231 and disks: for disks it is a disk partition (in the range 0-7),
232 and for tapes it is a file number offset on the tape.
233 Thus, partition 2 of a SCSI disk drive at target 3 on SCSI bus 1
234 would be ``sd(1,3,0,2)''.
235 If you have only one of any type bus adaptor, you may omit the adaptor
236 and controller numbers;
237 e.g. ``sd(0,2)'' could be used instead of ``sd(0,0,0,2)''.
238 The following examples always use the full syntax for clarity.
239 .Sh 3 "The procedure"
241 The basic steps involved in bringing up the HP300 are as follows:
243 Obtain a second disk and format it, if necessary.
245 Copy a root filesystem from the
246 tape onto the beginning of the disk.
248 Boot the UNIX system on the new disk.
250 (Optional) Build a root filesystem optimized for your disk.
252 Label the disks with the
255 .Sh 4 "Step 1: selecting and formatting a disk"
257 For your first system you will have to obtain a formatted disk
258 of a type given in the ``supported hardware'' list above.
259 If you want to load an entire binary system
260 (i.e., everything except
262 on the single disk you will need a minimum of 290MB,
263 ruling out anything smaller than a 7959B/S disk.
264 The disklabel included in the bootstrap root image is laid out
265 to accommodate this scenario.
266 Note that an HP SCSI magneto-optical disk will work fine for this case.
267 \*(4B will boot and run (albeit slowly) using one.
268 If you want to load source on a single disk system,
269 you will need at least 640MB (at least a 2213A SCSI or 2203A HP-IB disk).
270 A disk as small as the 7945A (54MB) can be used for the bootstrap
271 procedure but will hold only the root and primary swap partitions.
272 If you plan to use multiple disks,
273 refer to section 2.5 for suggestions on partitioning.
275 After selecting a disk, you may need to format it.
276 Since most HP disk drives come pre-formatted
277 (except optical media)
278 you probably will not, but if necessary,
279 you can format a disk under HP-UX using the
282 Once you have \*(4B up and running on one machine you can use the
284 program to format additional SCSI disks.
285 Any additional HP-IB disks will have to be formatted using HP-UX.
286 .Sh 4 "Step 2: copying the root filesystem from tape to disk"
288 Once you have a formatted second disk you can use the
290 command under HP-UX to copy the root filesystem image from
291 the tape to the beginning of the second disk.
292 For HP's, the root filesystem image is the first file on the tape.
293 It includes a disklabel and bootblock along with the root filesystem.
294 An example command to copy the image from tape to the beginning of a disk is:
297 dd if=/dev/rmt/0m of=/dev/rdsk/1s0 bs=\*(Bzb
299 The actual special file syntax may vary depending on unit numbers and
300 the version of HP-UX that is running.
305 man pages for details.
307 Note that if you have a SCSI disk, you don't necessarily have to use
308 HP-UX (or an HP) to create the boot disk.
309 Any machine and operating system that will allow you to copy the
310 raw disk image out to block 0 of the disk will do.
312 If you have only a single machine with a single disk,
313 you may still be able to install and boot \*(4B if you have an
314 HP-IB cartridge tape drive.
315 If so, you can use a more difficult approach of booting a
316 standalone copy program from the tape, and using that to copy the
317 root filesystem image from the tape to the disk.
318 To do this, you need to extract the first file of the distribution tape
319 (the root image), copy it over to a machine with a cartridge drive
320 and then copy the image onto tape.
324 dd if=/dev/rst0 of=bootimage bs=\*(Bzb
325 rcp bootimage foo:/tmp/bootimage
327 dd if=/tmp/bootimage of=/dev/rct/0m bs=\*(Bzb
329 Once this tape is created you can boot and run the standalone tape
330 copy program from it.
331 The copy program is loaded just as any other program would be loaded
332 by the bootrom in ``attended'' mode:
334 hold down the space bar until the word ``Keyboard'' appears in the
335 installed interface list, and
336 enter the menu selection for SYS_TCOPY.
337 Once loaded and running:
341 \fBFrom:\fP \fI^C\fP (control-C to see logical adaptor assignments)
344 \fBFrom:\fP \fIct(0,7,0,0)\fP (HP-IB tape, target 7, first tape file)
345 \fBTo:\fP \fIsd(0,0,0,2)\fP (SCSI disk, target 0, third partition)
346 \fBCopy completed: 1728 records copied\fP
350 This copy will likely take 30 minutes or more.
351 .Sh 4 "Step 3: booting the root filesystem"
353 You now have a bootable root filesystem on the disk.
354 If you were previously running with two disks,
355 it would be best if you shut down the machine and turn off power on
357 It will be less confusing and it will eliminate any chance of accidentally
358 destroying the HP-UX disk.
359 If you used a cartridge tape for booting you should also unload the tape
361 Whether you booted from tape or copied from disk you should now reboot
362 the machine and do another attended boot (see previous section),
363 this time with SYS_TBOOT.
364 Once loaded and running the boot program will display the CPU type and
365 prompt for a kernel file to boot:
371 \fB:\fP \fI/kernel\fP
374 After providing the kernel name, the machine will boot \*(4B with
375 output that looks about like this:
378 597480+34120+139288 start 0xfe8019ec
379 Copyright (c) 1982, 1986, 1989, 1991, 1993
380 The Regents of the University of California.
381 Copyright (c) 1992 Hewlett-Packard Company
382 Copyright (c) 1992 Motorola Inc.
385 4.4BSD UNIX #1: Tue Jul 20 11:40:36 PDT 1993
386 mckusick@vangogh.CS.Berkeley.EDU:/usr/obj/sys/compile/GENERIC.hp300
387 HP9000/433 (33MHz MC68040 CPU+MMU+FPU, 4k on-chip physical I/D caches)
390 using ### buffers containing ### bytes of memory
391 (... information about available devices ...)
396 The first three numbers are printed out by the bootstrap program and
397 are the sizes of different parts of the system (text, initialized and
398 uninitialized data). The system also allocates several system data
399 structures after it starts running. The sizes of these structures are
400 based on the amount of available memory and the maximum count of active
401 users expected, as declared in a system configuration description. This
402 will be discussed later.
404 UNIX itself then runs for the first time and begins by printing out a banner
405 identifying the release and
406 version of the system that is in use and the date that it was compiled.
411 amount of real (physical) memory and the
412 memory available to user programs
414 For example, if your machine has 16Mb bytes of memory, then
415 \fBxxx\fP will be 16777216.
417 The messages that come out next show what devices were found on
418 the current processor. These messages are described in
420 The distributed system may not have
421 found all the communications devices you have
422 or all the mass storage peripherals you have, especially
423 if you have more than
424 two of anything. You will correct this when you create
425 a description of your machine from which to configure a site-dependent
427 The messages printed at boot here contain much of the information
428 that will be used in creating the configuration.
429 In a correctly configured system most of the information
430 present in the configuration description
431 is printed out at boot time as the system verifies that each device
434 The \*(lqroot device?\*(rq prompt was printed by the system
435 to ask you for the name of the root filesystem to use.
436 This happens because the distribution system is a \fIgeneric\fP
437 system, i.e., it can be bootstrapped on a cpu with its root device
438 and paging area on any available disk drive.
439 You will most likely respond to the root device question with ``sd0''
440 if you are booting from a SCSI disk,
441 or with ``rd0'' if you are booting from an HP-IB disk.
442 This response shows that the disk it is running
443 on is drive 0 of type ``sd'' or ``rd'' respectively.
444 If you have other disks attached to the system,
445 it is possible that the drive you are using will not be configured
447 Check the autoconfiguration messages printed out by the kernel to
449 These messages will show the type of every logical drive
450 and their associated controller and slave addresses.
451 You will later build a system tailored to your configuration
452 that will not prompt you for a root device when it is bootstrapped.
454 \fBroot device?\fP \fI\*(Dk0\fP
455 \fBWARNING: preposterous time in filesystem \-\- CHECK AND RESET THE DATE!\fP
456 \fBerase ^?, kill ^U, intr ^C\fP
460 The \*(lqerase ...\*(rq message is part of the
462 that was executed by the root shell when it started. This message
463 tells you about the settings of the character erase,
464 line erase, and interrupt characters.
467 and the \fIUNIX Programmer's Manual\fP applies. The ``#'' is the prompt
468 from the Bourne shell, and lets you know that you are the super-user,
469 whose login name is \*(lqroot\*(rq.
471 At this point, the root filesystem is mounted read-only.
472 Before continuing the installation, the filesystem needs to be ``updated''
473 to allow writing and device special files for the following steps need
475 This is done as follows:
479 \fB#\fP \fImount_mfs -s 1000 -T type /dev/null /tmp\fP (create a writable filesystem)
480 (\fItype\fP is the disk type as determined from /etc/disktab)
481 \fB#\fP \fIcd /tmp\fP (connect to that directory)
482 \fB#\fP \fI../dev/MAKEDEV \*(Dk#\fP (create special files for root disk)
483 (\fI\*(Dk\fP is the disk type, \fI#\fP is the unit number)
484 (ignore warning from ``sh'')
485 \fB#\fP \fImount \-uw /tmp/\*(Dk#a /\fP (read-write mount root filesystem)
486 \fB#\fP \fIcd /dev\fP (go to device directory)
487 \fB#\fP \fI./MAKEDEV \*(Dk#\fP (create permanent special files for root disk)
488 (again, ignore warning from ``sh'')
491 .Sh 4 "Step 4: (optional) restoring the root filesystem"
493 The root filesystem that you are currently running on is complete,
494 however it probably is not optimally laid out for the disk on
495 which you are running.
496 If you will be cloning copies of the system onto multiple disks for
497 other machines, you are advised to connect one of these disks to
498 this machine, and build and restore a properly laid out root filesystem
500 If this is the only machine on which you will be running \*(4B
501 or peak performance is not an issue, you can skip this step and
502 proceed directly to step 5.
504 Connect a second disk to your machine.
505 If you bootstrapped using the two disk method, you can
506 overwrite your initial HP-UX disk, as it will no longer
507 be needed (assuming you have no plans to run HP-UX again).
509 To really create the root filesystem on drive 1
510 you should first label the disk as described in step 5 below.
511 Then run the following commands:
513 \fB#\fP \fIcd /dev\fP
514 \fB#\fP \fI./MAKEDEV \*(Dk1a\fP
515 \fB#\fP\|\fInewfs /dev/r\*(Dk1a\fP
516 \fB#\fP\|\fImount /dev/\*(Dk1a /mnt\fP
517 \fB#\fP\|\fIcd /mnt\fP
518 \fB#\fP\|\fIdump 0f \- /dev/r\*(Dk0a | restore xf \-\fP
519 (Note: restore will ask if you want to ``set owner/mode for '.'''
520 to which you should reply ``yes''.)
524 you should then shut down the system, and boot on the disk that
525 you just created following the procedure in step (3) above.
526 .Sh 4 "Step 5: placing labels on the disks"
528 For each disk on the HP300, \*(4B places information about the geometry
529 of the drive and the partition layout at byte offset 1024.
530 This information is written with
533 The root image just loaded includes a ``generic'' label intended to allow
534 easy installation of the root and
536 and may not be suitable for the actual
537 disk on which it was installed.
539 it may make your disk appear larger or smaller than its real size.
540 In the former case, you lose some capacity.
541 In the latter, some of the partitions may map non-existent sectors
542 leading to errors if those partitions are used.
543 It is also possible that the defined geometry will interact poorly with
544 the filesystem code resulting in reduced performance.
545 However, as long as you are willing to give up a little space,
546 not use certain partitions or suffer minor performance degradation,
547 you might want to avoid this step;
548 especially if you do not know how to use
551 If you choose to edit this label,
552 you can fill in correct geometry information from
554 You may also want to rework the ``e'' and ``f'' partitions used for loading
558 You should not attempt to, and
560 will not let you, modify the ``a'', ``b'' and ``d'' partitions.
563 \fB#\fP \fIEDITOR=ed\fP
564 \fB#\fP \fIexport EDITOR\fP
565 \fB#\fP \fIdisklabel -r -e /dev/r\fBXX#\fPd
567 where \fBXX\fP is the type and \fB#\fP is the logical drive number; e.g.
571 Note the explicit use of the ``d'' partition.
572 This partition includes the bootblock as does ``c''
573 and using it allows you to change the size of ``c''.
575 If you wish to label any additional disks, run the following command for each:
577 \fB#\|\fP\fIdisklabel -rw \fBXX# type\fP \fI"optional_pack_name"\fP
579 where \fBXX#\fP is the same as in the previous command
580 and \fBtype\fP is the HP300 disk device name as listed in
582 The optional information may contain any descriptive name for the
583 contents of a disk, and may be up to 16 characters long. This procedure
584 will place the label on the disk using the information found in
586 for the disk type named.
587 If you have changed the disk partition sizes,
588 you may wish to add entries for the modified configuration in
590 before labeling the affected disks.
592 You have now completed the HP300 specific part of the installation.
593 Now proceed to the generic part of the installation
594 described starting in section 2.5 below.
595 Note that where the disk name ``sd'' is used throughout section 2.5,
596 you should substitute the name ``rd'' if you are running on an HP-IB disk.
597 Also, if you are loading on a single disk with the default disklabel,
599 should be restored to the ``f'' partition and
601 to the ``e'' partition.
602 .Sh 2 "Booting the SPARC"
603 .Sh 3 "Supported hardware"
605 The hardware supported by \*(4B for the SPARC is as follows:
610 SPARCstation 1 series (1, 1+, SLC, IPC) and
611 SPARCstation 2 series (2, IPX).
623 SPARCstation Lance (le).
635 Battery-backed real time clock,
636 built-in serial devices,
637 Sbus SCSI controller,
642 Major items that are not supported include
644 the GX (cgsix) display,
645 the floppy disk, and SCSI tapes.
648 There are several important limitations on the \*(4B distribution
653 have SunOS 4.1.x or Solaris to bring up \*(4B.
654 There is no SPARCstation bootstrap code in this distribution. The
655 Sun-supplied boot loader will be used to boot \*(4B; you must copy
656 this from your SunOS distribution. This imposes several
657 restrictions on the system, as detailed below.
659 The \*(4B SPARC kernel does not remap SCSI IDs. A SCSI disk at
660 target 0 will become ``sd0'', where in SunOS the same disk will
661 normally be called ``sd3''. If your existing SunOS system is
662 diskful, it will be least painful to have SunOS running on the disk
663 on target 0 lun 0 and put \*(4B on the disk on target 3 lun 0. Both
664 systems will then think they are running on ``sd0'', and you can
665 boot either system as needed simply by changing the EEPROM's boot
668 There is no SCSI tape driver.
669 You must have another system for tape reading and backups.
671 Although the \*(4B SPARC kernel will handle existing SunOS shared
672 libraries, it does not use or create them itself, and therefore
673 requires much more disk space than SunOS does.
675 It is currently difficult (though not completely impossible) to
676 run \*(4B diskless. These instructions assume you will have a local
677 boot, swap, and root filesystem.
679 When using a serial port rather than a graphics display as the console,
685 will fail when the kernel tries
686 to print the boot up messages to the console.
687 .Sh 3 "The procedure"
689 You must have a spare disk on which to place \*(4B.
690 The steps involved in bootstrapping this tape are as follows:
692 Bring up SunOS (preferably SunOS 4.1.x or Solaris 1.x, although
693 Solaris 2 may work \(em this is untested).
695 Attach auxiliary SCSI disk(s). Format and label using the
696 SunOS formatting and labeling programs as needed.
697 Note that the root filesystem currently requires at least 10 MB; 16 MB
698 or more is recommended. The b partition will be used for swap;
699 this should be at least 32 MB.
703 to build the root filesystem. You may also
704 want to build other filesystems at the same time. (By default, the
707 builds a filesystem that SunOS will not handle; if you
708 plan to switch OSes back and forth you may want to sacrifice the
709 performance gain from the new filesystem format for compatibility.)
710 You can build an old-format filesystem on \*(4B by giving the \-O
714 can convert old format filesystems to new format
715 filesystems, but not vice versa,
716 so you may want to initially build old format filesystems so that they
717 can be mounted under SunOS,
718 and then later convert them to new format filesystems when you are
719 satisfied that \*(4B is running properly.
722 you must build an old-style root filesystem
724 so that the SunOS boot program will work.
726 Mount the new root, then copy the SunOS
728 into place and use the SunOS ``installboot'' program
729 to enable disk-based booting.
730 Note that the filesystem must be mounted when you do the ``installboot'':
733 # mount /dev/sd3a /mnt
736 # installboot /mnt/boot bootsd /dev/rsd3a
740 will load \*(4B kernels; there is no SPARCstation
741 bootstrap code on the distribution. Note that the SunOS
743 does not handle the new \*(4B filesystem format.
745 Restore the contents of the \*(4B root filesystem.
749 # rrestore xf tapehost:/dev/nrst0
752 Boot the supplied kernel:
756 ok boot sd(0,3)kernel -s [for old proms] OR
757 ok boot disk3 -s [for new proms]
758 \&... [\*(4B boot messages]
761 To install the remaining filesystems, use the procedure described
762 starting in section 2.5.
763 In these instructions,
765 should be loaded into the ``e'' partition and
767 in the ``f'' partition.
769 After completing the filesystem installation you may want
770 to set up \*(4B to reboot automatically:
774 ok setenv boot-from sd(0,3)kernel [for old proms] OR
775 ok setenv boot-device disk3 [for new proms]
777 If you build backwards-compatible filesystems, either with the SunOS
778 newfs or with the \*(4B ``\-O'' option, you can mount these under
779 SunOS. The SunOS fsck will, however, always think that these filesystems
780 are corrupted, as there are several new (previously unused)
781 superblock fields that are updated in \*(4B. Running ``fsck \-b32''
782 and letting it ``fix'' the superblock will take care of this.
784 If you wish to run SunOS binaries that use SunOS shared libraries, you
785 simply need to copy all the dynamic linker files from an existing
789 # rcp sunos-host:/etc/ld.so.cache /etc/
790 # rcp sunos-host:'/usr/lib/*.so*' /usr/lib/
792 The SunOS compiler and linker should be able to produce SunOS binaries
793 under \*(4B, but this has not been tested. If you plan to try it you
794 will need the appropriate .sa files as well.
795 .Sh 2 "Booting the DECstation"
796 .Sh 3 "Supported hardware"
798 The hardware supported by \*(4B for the DECstation is as follows:
803 R2000 based (3100) and
804 R3000 based (5000/200, 5000/20, 5000/25, 5000/1xx).
808 SCSI-I (tested RZ23, RZ55, RZ57, Maxtor 8760S).
812 SCSI-I (tested DEC TK50, Archive DAT, Emulex MT02).
816 Internal DEC dc7085 and AMD 8530 based interfaces.
820 TURBOchannel PMAD-AA and internal LANCE based interfaces.
824 Terminal emulation and raw frame buffer support for
825 3100 (color & monochrome),
826 TURBOchannel PMAG-AA, PMAG-BA, PMAG-DV.
830 Standard DEC keyboard (LK201) and mouse.
834 Battery-backed real time clock,
835 internal and TURBOchannel PMAZ-AA SCSI interfaces.
839 Major items that are not supported include the 5000/240
840 (there is code but not compiled in or tested),
841 R4000 based machines, FDDI and audio interfaces.
842 Diskless machines are not supported but booting kernels and bootstrapping
843 over the network is supported on the 5000 series.
844 .Sh 3 "The procedure"
846 The first file on the distribution tape is a tar file that contains
848 The first step requires a running UNIX (or ULTRIX) system that can
849 be used to extract the tar archive from the first file on the tape.
855 will extract the following four files:
857 A) root.image: \fIdd\fP image of the root filesystem
858 B) kernel.tape: \fIdd\fP image for creating boot tapes
859 C) kernel.net: file for booting over the network
860 D) root.dump: \fIdump\fP image of the root filesystem
862 There are three basic ways a system can be bootstrapped corresponding to the
864 You may want to read the section on bootstrapping the HP300
865 since many of the steps are similar.
866 A spare, formatted SCSI disk is also useful.
867 .Sh 4 "Procedure A: copy root filesystem to disk"
869 This procedure is similar to the HP300.
870 If you have an extra disk, the easiest approach is to use \fIdd\fP\|(1)
871 under ULTRIX to copy the root filesystem image to the beginning
873 The root filesystem image includes a disklabel and bootblock along with the
875 An example command to copy the image to the beginning of a disk is:
878 dd if=root.image of=/dev/rz1c bs=\*(Bzb
880 The actual special file syntax will vary depending on unit numbers and
881 the version of ULTRIX that is running.
882 This system is now ready to boot. You can boot the kernel with one of the
883 following PROM commands. If you are booting on a 3100, the disk must be SCSI
884 id zero because of a bug.
887 DEC 3100: boot \-f rz(0,0,0)kernel
888 DEC 5000: boot 5/rz0/kernel
890 You can then proceed to section 2.5
891 to create reasonable disk partitions for your machine
892 and then install the rest of the system.
893 .Sh 4 "Procedure B: bootstrap from tape"
895 If you have only a single machine with a single disk,
896 you need to use the more difficult approach of booting a
897 kernel and mini-root from tape or the network, and using it to restore
900 First, you will need to create a boot tape. This can be done using
901 \fIdd\fP as in the following example.
904 dd if=kernel.tape of=/dev/nrmt0 bs=1b
905 dd if=root.dump of=/dev/nrmt0 bs=\*(Bzb
907 The actual special file syntax for the tape drive will vary depending on
908 unit numbers, tape device and the version of ULTRIX that is running.
910 The first file on the boot tape contains a boot header, kernel, and
911 mini-root filesystem that the PROM can copy into memory.
912 Installing from tape has only been tested
913 on a 3100 and a 5000/200 using a TK50 tape drive. Here are two example
914 PROM commands to boot from tape.
917 DEC 3100: boot \-f tz(0,5,0) m # 5 is the SCSI id of the TK50
918 DEC 5000: boot 5/tz6 m # 6 is the SCSI id of the TK50
920 The `m' argument tells the kernel to look for a root filesystem in memory.
921 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
922 .Sh 4 "Procedure C: bootstrap over the network"
924 You will need a host machine that is running the \fIbootp\fP server
927 file installed in the default directory defined by the
928 configuration file for
930 Here are two example PROM commands to boot across the net:
933 DEC 3100: boot \-f tftp()kernel.net m
934 DEC 5000: boot 6/tftp/kernel.net m
936 This command should load the kernel and mini-root into memory and
937 run the same as the tape install (procedure B).
938 The rest of the steps are the same except
939 you will need to start the network
940 (if you are unsure how to fill in the <name> fields below,
941 see sections 4.4 and 5).
942 Execute the following to start the networking:
946 # echo 127.0.0.1 localhost >> /etc/hosts
947 # echo <your.host.inet.number> myname.my.domain myname >> /etc/hosts
948 # echo <friend.host.inet.number> myfriend.my.domain myfriend >> /etc/hosts
949 # ifconfig le0 inet myname
951 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
952 .Sh 3 "Label disk and create the root filesystem"
954 There are five steps to create a disk-based root filesystem.
959 # disklabel -W /dev/rrz?c # This enables writing the label
960 # disklabel -w -r -B /dev/rrz?c $DISKTYPE
966 Supported disk types are listed in
969 Restore the root filesystem.
977 If you are restoring locally (procedure B), run:
980 # mt \-f /dev/nrmt0 rew
981 # restore \-xsf 2 /dev/rmt0
984 If you are restoring across the net (procedure c), run:
987 # rrestore xf myfriend:/path/to/root.dump
990 When the restore finishes, clean up with:
999 Reset the system and initialize the PROM monitor to boot automatically.
1002 DEC 3100: setenv bootpath boot \-f rz(0,?,0)kernel
1003 DEC 5000: setenv bootpath 5/rz?/kernel -a
1006 After booting UNIX, you will need to create
1008 to run X Window System as in the following example.
1012 ln /dev/xx /dev/mouse
1014 The 'xx' should be one of the following:
1016 pm0 raw interface to PMAX graphics devices
1017 cfb0 raw interface to TURBOchannel PMAG-BA color frame buffer
1018 xcfb0 raw interface to maxine graphics devices
1019 mfb0 raw interface to mono graphics devices
1021 You can then proceed to section 2.5 to install the rest of the system.
1022 Note that where the disk name ``sd'' is used throughout section 2.5,
1023 you should substitute the name ``rz''.
1024 .Sh 2 "Disk configuration"
1026 All architectures now have a root filesystem up and running and
1027 proceed from this point to layout filesystems to make use
1028 of the available space and to balance disk load for better system
1030 .Sh 3 "Disk naming and divisions"
1032 Each physical disk drive can be divided into up to 8 partitions;
1033 UNIX typically uses only 3 or 4 partitions.
1034 For instance, the first partition, \*(Dk0a,
1035 is used for a root filesystem, a backup thereof,
1036 or a small filesystem like,
1038 the second partition, \*(Dk0b,
1039 is used for paging and swapping; and
1040 a third partition, typically \*(Dk0e,
1041 holds a user filesystem.
1043 The space available on a disk varies per device.
1044 Each disk typically has a paging area of 30 to 100 megabytes
1045 and a root filesystem of about 17 megabytes.
1047 The distributed system binaries occupy about 150 (180 with X11R5) megabytes
1049 while the major sources occupy another 250 (340 with X11R5) megabytes.
1052 filesystem as delivered on the tape is only 2Mb,
1053 however it should have at least 50Mb allocated to it just for
1054 normal system activity.
1055 Usually it is allocated the last partition on the disk
1056 so that it can provide as much space as possible to the
1059 See section 2.5.4 for further details on disk layouts.
1061 Be aware that the disks have their sizes
1062 measured in disk sectors (usually 512 bytes), while the UNIX filesystem
1063 blocks are variable sized.
1066 is set in the user's environment, all user programs report
1067 disk space in kilobytes, otherwise,
1068 disk sizes are always reported in units of 512-byte sectors\**.
1070 You can thank System V intransigence and POSIX duplicity for
1071 requiring that 512-byte blocks be the units that programs report.
1075 file used in labelling disks and making filesystems
1076 specifies disk partition sizes in sectors.
1077 .Sh 3 "Layout considerations"
1079 There are several considerations in deciding how
1080 to adjust the arrangement of things on your disks.
1081 The most important is making sure that there is adequate space
1082 for what is required; secondarily, throughput should be maximized.
1083 Paging space is an important parameter.
1084 The system, as distributed, sizes the configured
1085 paging areas each time the system is booted. Further,
1086 multiple paging areas of different sizes may be interleaved.
1088 Many common system programs (C, the editor, the assembler etc.)
1089 create intermediate files in the
1091 directory, so the filesystem where this is stored also should be made
1092 large enough to accommodate most high-water marks.
1095 is constructed from a memory-based filesystem (see
1097 Programs that want their temporary files to persist
1098 across system reboots (such as editors) should use
1100 If you plan to use a disk-based
1102 filesystem to avoid loss across system reboots, it makes
1103 sense to mount this in a ``root'' (i.e. first partition)
1104 filesystem on another disk.
1105 All the programs that create files in
1107 take care to delete them, but are not immune to rare events
1108 and can leave dregs.
1109 The directory should be examined every so often and the old
1112 The efficiency with which UNIX is able to use the CPU
1113 is often strongly affected by the configuration of disk controllers;
1114 it is critical for good performance to balance disk load.
1115 There are at least five components of the disk load that you can
1116 divide between the available disks:
1118 The root filesystem.
1130 The user filesystems.
1132 The paging activity.
1134 The following possibilities are ones we have used at times
1135 when we had 2, 3 and 4 disks:
1139 l | lw(5) | lw(5) | lw(5).
1146 paging 0+1 0+2 0+2+3
1151 The most important things to consider are to
1152 even out the disk load as much as possible, and to do this by
1153 decoupling filesystems (on separate arms) between which heavy copying occurs.
1154 Note that a long term average balanced load is not important; it is
1155 much more important to have an instantaneously balanced
1156 load when the system is busy.
1158 Intelligent experimentation with a few filesystem arrangements can
1159 pay off in much improved performance. It is particularly easy to
1164 filesystems and the paging areas. Place the
1167 directory as space needs dictate and experiment
1168 with the other, more easily moved filesystems.
1169 .Sh 3 "Filesystem parameters"
1171 Each filesystem is parameterized according to its block size,
1172 fragment size, and the disk geometry characteristics of the
1173 medium on which it resides. Inaccurate specification of the disk
1174 characteristics or haphazard choice of the filesystem parameters
1175 can result in substantial throughput degradation or significant
1176 waste of disk space. As distributed,
1177 filesystems are configured according to the following table.
1182 Filesystem Block size Fragment size
1184 root 8 kbytes 1 kbytes
1185 usr 8 kbytes 1 kbytes
1186 users 4 kbytes 512 bytes
1190 The root filesystem block size is
1191 made large to optimize bandwidth to the associated disk.
1192 The large block size is important as many of the most
1193 heavily used programs are demand paged out of the
1196 The fragment size of 1 kbyte is a ``nominal'' value to use
1197 with a filesystem. With a 1 kbyte fragment size
1198 disk space utilization is about the same
1199 as with the earlier versions of the filesystem.
1201 The filesystems for users have a 4 kbyte block
1202 size with 512 byte fragment size. These parameters
1203 have been selected based on observations of the
1204 performance of our user filesystems. The 4 kbyte
1205 block size provides adequate bandwidth while the
1206 512 byte fragment size provides acceptable space compaction
1207 and disk fragmentation.
1209 Other parameters may be chosen in constructing filesystems,
1210 but the factors involved in choosing a block
1211 size and fragment size are many and interact in complex
1212 ways. Larger block sizes result in better
1213 throughput to large files in the filesystem as
1214 larger I/O requests will then be done by the
1216 consideration must be given to the average file sizes
1217 found in the filesystem and the performance of the
1218 internal system buffer cache. The system
1219 currently provides space in the inode for
1220 12 direct block pointers, 1 single indirect block
1221 pointer, 1 double indirect block pointer,
1222 and 1 triple indirect block pointer.
1223 If a file uses only direct blocks, access time to
1224 it will be optimized by maximizing the block size.
1225 If a file spills over into an indirect block,
1226 increasing the block size of the filesystem may
1227 decrease the amount of space used
1228 by eliminating the need to allocate an indirect block.
1229 However, if the block size is increased and an indirect
1230 block is still required, then more disk space will be
1231 used by the file because indirect blocks are allocated
1232 according to the block size of the filesystem.
1234 In selecting a fragment size for a filesystem, at least
1235 two considerations should be given. The major performance
1236 tradeoffs observed are between an 8 kbyte block filesystem
1237 and a 4 kbyte block filesystem. Because of implementation
1238 constraints, the block size versus fragment size ratio can not
1239 be greater than 8. This means that an 8 kbyte filesystem
1240 will always have a fragment size of at least 1 kbytes. If
1241 a filesystem is created with a 4 kbyte block size and a
1242 1 kbyte fragment size, then upgraded to an 8 kbyte block size
1243 and 1 kbyte fragment size, identical space compaction will be
1244 observed. However, if a filesystem has a 4 kbyte block size
1245 and 512 byte fragment size, converting it to an 8K/1K
1246 filesystem will result in 4-8% more space being
1247 used. This implies that 4 kbyte block filesystems that
1248 might be upgraded to 8 kbyte blocks for higher performance should
1249 use fragment sizes of at least 1 kbytes to minimize the amount
1250 of work required in conversion.
1252 A second, more important, consideration when selecting the
1253 fragment size for a filesystem is the level of fragmentation
1254 on the disk. With an 8:1 fragment to block ratio, storage fragmentation
1255 occurs much sooner, particularly with a busy filesystem running
1256 near full capacity. By comparison, the level of fragmentation in a
1257 4:1 fragment to block ratio filesystem is one tenth as severe. This
1258 means that on filesystems where many files are created and
1259 deleted, the 512 byte fragment size is more likely to result in apparent
1260 space exhaustion because of fragmentation. That is, when the filesystem
1261 is nearly full, file expansion that requires locating a
1262 contiguous area of disk space is more likely to fail on a 512
1263 byte filesystem than on a 1 kbyte filesystem. To minimize
1264 fragmentation problems of this sort, a parameter in the super
1265 block specifies a minimum acceptable free space threshold. When
1266 normal users (i.e. anyone but the super-user) attempt to allocate
1267 disk space and the free space threshold is exceeded, the user is
1268 returned an error as if the filesystem were really full. This
1269 parameter is nominally set to 5%; it may be changed by supplying
1272 or by updating the super block of an existing filesystem using
1275 Finally, a third, less common consideration is the attributes of
1276 the disk itself. The fragment size should not be smaller than the
1277 physical sector size of the disk. As an example, the HP magneto-optical
1278 disks have 1024 byte physical sectors. Using a 512 byte fragment size
1279 on such disks will work but is extremely inefficient.
1281 Note that the above discussion considers block sizes of up to only 8k.
1282 As of the 4.4 release, the maximum block size has been increased to 64k.
1283 This allows an entirely new set of block/fragment combinations for which
1284 there is little experience to date.
1285 In general though, unless a filesystem is to be used
1286 for a special purpose application (for example, storing
1287 image processing data), we recommend using the
1288 values supplied above.
1289 Remember that the current
1290 implementation limits the block size to at most 64 kbytes
1291 and the ratio of block size versus fragment size must be 1, 2, 4, or 8.
1293 The disk geometry information used by the filesystem
1294 affects the block layout policies employed. The file
1296 as supplied, contains the data for most
1297 all drives supported by the system. Before constructing
1300 you should label the disk (if it has not yet been labeled,
1301 and the driver supports labels).
1302 If labels cannot be used, you must instead
1303 specify the type of disk on which the filesystem resides;
1307 instead of the pack label.
1308 This file also contains the default
1309 filesystem partition
1310 sizes, and default block and fragment sizes. To
1311 override any of the default values you can modify the file,
1312 edit the disk label,
1315 .Sh 3 "Implementing a layout"
1317 To put a chosen disk layout into effect, you should use the
1319 command to create each new filesystem.
1320 Each filesystem must also be added to the file
1322 so that it will be checked and mounted when the system is bootstrapped.
1324 First we will consider a system with a single disk.
1325 There is little real choice on how to do the layout;
1326 the root filesystem goes in the ``a'' partition,
1328 goes in the ``e'' partition, and
1330 fills out the remainder of the disk in the ``f'' partition.
1331 This is the organization used if you loaded the disk-image root filesystem.
1332 With the addition of a memory-based
1334 filesystem, its fstab entry would be as follows:
1338 /dev/\*(Dk0a / ufs rw 1 1
1339 /dev/\*(Dk0b none swap sw 0 0
1340 /dev/\*(Dk0b /tmp mfs rw,-s=14000,-b=8192,-f=1024,-T=sd660 0 0
1341 /dev/\*(Dk0e /usr ufs ro 1 2
1342 /dev/\*(Dk0f /var ufs rw 1 2
1345 If we had a second disk, we would split the load between the drives.
1346 On the second disk, we place the
1350 filesystems in their usual \*(Dk1e and \*(Dk1f
1351 partitions respectively.
1352 The \*(Dk1b partition would be used as a second paging area,
1353 and the \*(Dk1a partition left as a spare root filesystem
1354 (alternatively \*(Dk1a could be used for
1356 The first disk still holds the
1357 the root filesystem in \*(Dk0a, and the primary swap area in \*(Dk0b.
1358 The \*(Dk0e partition is used to hold home directories in
1360 The \*(Dk0f partition can be used for
1362 or alternately the \*(Dk0e partition can be extended to cover
1363 the rest of the disk with
1367 directory is a memory-based filesystem.
1368 Note that to interleave the paging between the two disks
1369 you must build a system configuration that specifies:
1371 config kernel root on \*(Dk0 swap on \*(Dk0 and \*(Dk1
1375 file would then contain
1379 /dev/\*(Dk0a / ufs rw 1 1
1380 /dev/\*(Dk0b none swap sw 0 0
1381 /dev/\*(Dk1b none swap sw 0 0
1382 /dev/\*(Dk0b /tmp mfs rw,-s=14000,-b=8192,-f=1024,-T=sd660 0 0
1383 /dev/\*(Dk1e /usr ufs ro 1 2
1384 /dev/\*(Dk0f /usr/src ufs rw 1 2
1385 /dev/\*(Dk1f /var ufs rw 1 2
1386 /dev/\*(Dk0e /var/users ufs rw 1 2
1391 filesystem we would do:
1393 \fB#\fP \fIcd /dev\fP
1394 \fB#\fP \fIMAKEDEV \*(Dk1\fP
1395 \fB#\fP \fIdisklabel -wr \*(Dk1 "disk type" "disk name"\fP
1396 \fB#\fP \fInewfs \*(Dk1f\fP
1397 (information about filesystem prints out)
1398 \fB#\fP \fImkdir /var\fP
1399 \fB#\fP \fImount /dev/\*(Dk1f /var\fP
1401 .Sh 2 "Installing the rest of the system"
1403 At this point you should have your disks partitioned.
1404 The next step is to extract the rest of the data from the tape.
1405 At a minimum you need to set up the
1410 You may also want to extract some or all the program sources.
1411 Since not all architectures support tape drives or don't support the
1412 correct ones, you may need to extract the files indirectly using
1414 For example, for a directly connected tape drive you might do:
1416 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP
1417 \fB#\fP \fItar xbpf \*(Bz /dev/nr\*(Mt0\fP
1419 The equivalent indirect procedure (where the tape drive is on machine ``foo'')
1422 \fB#\fP \fIrsh foo mt -f /dev/nr\*(Mt0 fsf\fP
1423 \fB#\fP \fIrsh foo dd if=/dev/nr\*(Mt0 bs=\*(Bzb | tar xbpf \*(Bz -\fP
1425 Obviously, the target machine must be connected to the local network
1429 \fB#\fP \fIecho 127.0.0.1 localhost >> /etc/hosts\fP
1430 \fB#\fP \fIecho \fPyour.host.inet.number myname.my.domain myname\fI >> /etc/hosts\fP
1431 \fB#\fP \fIecho \fPfriend.host.inet.number myfriend.my.domain myfriend\fI >> /etc/hosts\fP
1432 \fB#\fP \fIifconfig le0 inet \fPmyname
1434 where the ``host.inet.number'' fields are the IP addresses for your host and
1435 the host with the tape drive
1436 and the ``my.domain'' fields are the names of your machine and the tape-hosting
1438 See sections 4.4 and 5 for more information on setting up the network.
1440 Assuming a directly connected tape drive, here is how to extract and
1449 \fB#\fP \fImount \-uw /dev/\*(Dk#a /\fP (read-write mount root filesystem)
1450 \fB#\fP \fIdate yymmddhhmm\fP (set date, see \fIdate\fP\|(1))
1452 \fB#\fP \fIpasswd -l root\fP (set password for super-user)
1453 \fBNew password:\fP (password will not echo)
1454 \fBRetype new password:\fP
1455 \fB#\fP \fIpasswd -l toor\fP (set password for super-user)
1456 \fBNew password:\fP (password will not echo)
1457 \fBRetype new password:\fP
1458 \fB#\fP \fIhostname mysitename\fP (set your hostname)
1459 \fB#\fP \fInewfs r\*(Dk#p\fP (create empty user filesystem)
1460 (\fI\*(Dk\fP is the disk type, \fI#\fP is the unit number,
1461 \fIp\fP is the partition; this takes a few minutes)
1462 \fB#\fP \fImount /dev/\*(Dk#p /var\fP (mount the var filesystem)
1463 \fB#\fP \fIcd /var\fP (make /var the current directory)
1464 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1465 \fB#\fP \fItar xbpf \*(Bz /dev/nr\*(Mt0\fP (extract all of var)
1466 (this takes a few minutes)
1467 \fB#\fP \fInewfs r\*(Dk#p\fP (create empty user filesystem)
1468 (as before \fI\*(Dk\fP is the disk type, \fI#\fP is the unit number,
1469 \fIp\fP is the partition)
1470 \fB#\fP \fImount /dev/\*(Dk#p /mnt\fP (mount the new /usr in temporary location)
1471 \fB#\fP \fIcd /mnt\fP (make /mnt the current directory)
1472 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1473 \fB#\fP \fItar xbpf \*(Bz /dev/nr\*(Mt0\fP (extract all of usr except usr/src)
1474 (this takes about 15-20 minutes)
1475 \fB#\fP \fIcd /\fP (make / the current directory)
1476 \fB#\fP \fIumount /mnt\fP (unmount from temporary mount point)
1477 \fB#\fP \fIrm -r /usr/*\fP (remove excess bootstrap binaries)
1478 \fB#\fP \fImount /dev/\*(Dk#p /usr\fP (remount /usr)
1480 If no disk label has been installed on the disk, the
1482 command will require a third argument to specify the disk type,
1483 using one of the names in
1485 If the tape had been rewound or positioned incorrectly before the
1489 it may be repositioned by the following commands.
1491 \fB#\fP \fImt -f /dev/nr\*(Mt0 rew\fP
1492 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf 1\fP
1494 The data on the second and third tape files has now been extracted.
1495 If you are using 6250bpi tapes, the first reel of the
1496 distribution is no longer needed; you should now mount the second
1497 reel instead. The installation procedure continues from this
1498 point on the 8mm tape.
1499 The next step is to extract the sources.
1500 As previously noted,
1503 requires about 250-340Mb of space.
1504 Ideally sources should be in a separate filesystem;
1505 if you plan to put them into your
1507 filesystem, it will need at least 500Mb of space.
1508 Assuming that you will be using a separate filesystem on \*(Dk0f for
1510 you will start by creating and mounting it:
1512 \fB#\fP \fInewfs \*(Dk0f\fP
1513 (information about filesystem prints out)
1514 \fB#\fP \fImkdir /usr/src\fP
1515 \fB#\fP \fImount /dev/\*(Dk0f /usr/src\fP
1518 First you will extract the kernel source:
1522 \fB#\fP \fIcd /usr/src\fP
1523 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1524 (this should only be done on Exabyte distributions)
1525 \fB#\fP \fItar xpbf \*(Bz /dev/nr\*(Mt0\fP (extract the kernel sources)
1526 (this takes about 15-30 minutes)
1530 The next tar file contains the sources for the utilities.
1531 It is extracted as follows:
1535 \fB#\fP \fIcd /usr/src\fP
1536 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1537 \fB#\fP \fItar xpbf \*(Bz /dev/rmt12\fP (extract the utility source)
1538 (this takes about 30-60 minutes)
1542 If you are using 6250bpi tapes, the second reel of the
1543 distribution is no longer needed; you should now mount the third
1544 reel instead. The installation procedure continues from this
1545 point on the 8mm tape.
1547 The next tar file contains the sources for the contributed software.
1548 It is extracted as follows:
1552 \fB#\fP \fIcd /usr/src\fP
1553 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1554 (this should only be done on Exabyte distributions)
1555 \fB#\fP \fItar xpbf \*(Bz /dev/rmt12\fP (extract the contributed software source)
1556 (this takes about 30-60 minutes)
1560 If you received a distribution on 8mm Exabyte tape,
1561 there is one additional tape file on the distribution tape
1562 that has not been installed to this point; it contains the
1563 sources for X11R5 in
1565 format. As distributed, X11R5 should be placed in
1566 .Pn /usr/src/X11R5 .
1570 \fB#\fP \fIcd /usr/src\fP
1571 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1572 \fB#\fP \fItar xpbf \*(Bz /dev/nr\*(Mt0\fP (extract the X11R5 source)
1573 (this takes about 30-60 minutes)
1576 Many of the X11 utilities search using the path
1578 so be sure that you have a symbolic link that points at
1579 the location of your X11 binaries (here, X11R5).
1581 Having now completed the extraction of the sources,
1582 you may want to verify that your
1584 filesystem is consistent.
1585 To do so, you must unmount it, and run
1587 assuming that you used \*(Dk0f you would proceed as follows:
1591 \fB#\fP \fIcd /\fP (change directory, back to the root)
1592 \fB#\fP \fIumount /usr/src\fP (unmount /usr/src)
1593 \fB#\fP \fIfsck /dev/r\*(Dk0f\fP
1598 should look something like:
1602 ** Last Mounted on /usr/src
1603 ** Phase 1 - Check Blocks and Sizes
1604 ** Phase 2 - Check Pathnames
1605 ** Phase 3 - Check Connectivity
1606 ** Phase 4 - Check Reference Counts
1607 ** Phase 5 - Check Cyl groups
1608 23000 files, 261000 used, 39000 free (2200 frags, 4600 blocks)
1612 If there are inconsistencies in the filesystem, you may be prompted
1613 to apply corrective action; see the
1615 or \fIFsck \(en The UNIX File System Check Program\fP (SMM:3) for more details.
1619 filesystem, you should now remount it with:
1621 \fB#\fP \fImount /dev/\*(Dk0f /usr/src\fP
1623 or if you have made an entry for it in
1625 you can remount it with:
1627 \fB#\fP \fImount /usr/src\fP
1629 .Sh 2 "Additional conversion information"
1631 After setting up the new \*(4B filesystems, you may restore the user
1632 files that were saved on tape before beginning the conversion.
1635 program does its work on a mounted filesystem using normal system operations.
1636 This means that filesystem dumps may be restored even
1637 if the characteristics of the filesystem changed.
1638 To restore a dump tape for, say, the
1640 filesystem something like the following would be used:
1642 \fB#\fP \fImkdir /a\fP
1643 \fB#\fP \fInewfs \*(Dk#p\fI
1644 \fB#\fP \fImount /dev/\*(Dk#p /a\fP
1646 \fB#\fP \fIrestore x\fP
1651 images were written instead of doing a dump, you should
1652 be sure to use its `\-p' option when reading the files back. No matter
1653 how you restore a filesystem, be sure to unmount it and check its
1656 when the job is complete.