| blob | 26df15d91c582080069b380cce2680f7153c17e6 |
1 .\" $NetBSD: 1.t,v 1.2 1998/01/09 06:55:19 perry Exp $
2 .\"
3 .\" Copyright (c) 1988, 1993 The Regents of the University of California.
4 .\" All rights reserved.
5 .\"
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
17 .\"
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" SUCH DAMAGE.
29 .\"
30 .\" @(#)1.t 8.1 (Berkeley) 7/27/93
31 .\"
32 .ds lq ``
33 .ds rq ''
34 .ds LH "Installing/Operating \*(4B
35 .ds RH Introduction
36 .ds CF \*(Dy
37 .LP
38 .bp
39 .Sh 1 "Introduction"
40 .PP
41 This document explains how to install the \*(4B Berkeley
42 version of UNIX on your system.
43 The filesystem format is compatible with \*(Ps
44 and it will only be necessary for you to do a full bootstrap
45 procedure if you are installing the release on a new machine.
46 The object file formats are completely different from the System
47 V release, so the most straightforward procedure for upgrading
48 a System V system is to do a full bootstrap.
49 .PP
50 The full bootstrap procedure
51 is outlined in section 2; the process starts with copying a filesystem
52 image onto a new disk.
53 This filesystem is then booted and used to extract the remainder of the
54 system binaries and sources from the archives on the tape(s).
55 .PP
56 The technique for upgrading a \*(Ps system is described
57 in section 3 of this document.
58 The upgrade procedure involves extracting system binaries
59 onto new root and
60 .Pn /usr
61 filesystems and merging local
62 configuration files into the new system.
63 User filesystems may be upgraded in place.
64 Most \*(Ps binaries may be used with \*(4B in the course
65 of the conversion.
66 It is desirable to recompile local sources after the conversion,
67 as the new compiler (GCC) provides superior code optimization.
68 Consult section 3.5 for a description of some of the differences
69 between \*(Ps and \*(4B.
70 .Sh 2 "Distribution format"
71 .PP
72 The distribution comes in two formats:
73 .DS
74 (3)\0\0 6250bpi 2400' 9-track magnetic tapes, or
75 (1)\0\0 8mm Exabyte tape
76 .DE
77 .PP
78 If you have the facilities, we \fBstrongly\fP recommend copying the
79 magnetic tape(s) in the distribution kit to guard against disaster.
80 The tapes contain \*(Bb-byte records.
81 There are interspersed tape marks;
82 end-of-tape is signaled by a double end-of-file.
83 The first file on the tape is architecture dependent.
84 Additional files on the tape(s)
85 contain tape archive images of the system binaries and sources (see
86 .Xr tar (1)\**).
87 .FS
88 References of the form \fIX\fP(Y) mean the entry named
89 \fIX\fP in section Y of the ``UNIX Programmer's Manual''.
90 .FE
91 See the tape label for a description of the contents
92 and format of each individual tape.
93 .Sh 2 "UNIX device naming"
94 .PP
95 Device names have a different syntax depending on whether you are talking
96 to the standalone system or a running UNIX kernel.
97 The standalone system syntax is currently architecture dependent and is
98 described in the various architecture specific sections as applicable.
99 When not running standalone, devices are available via files in the
100 .Pn /dev/
101 directory.
102 The file name typically encodes the device type, its logical unit and
103 a partition within that unit.
104 For example,
105 .Pn /dev/sd2b
106 refers to the second partition (``b'') of
107 SCSI (``sd'') drive number ``2'', while
108 .Pn /dev/rmt0
109 refers to the raw (``r'') interface of 9-track tape (``mt'') unit ``0''.
110 .PP
111 The mapping of physical addressing information (e.g. controller, target)
112 to a logical unit number is dependent on the system configuration.
113 In all simple cases, where only a single controller is present, a drive
114 with physical unit number 0 (e.g., as determined by its unit
115 specification, either unit plug or other selection mechanism)
116 will be called unit 0 in its UNIX file name.
117 This is not, however, strictly
118 necessary, since the system has a level of indirection in this naming.
119 If there are multiple controllers, the disk unit numbers will normally
120 be counted sequentially across controllers. This can be taken
121 advantage of to make the system less dependent on the interconnect
122 topology, and to make reconfiguration after hardware failure easier.
123 .PP
124 Each UNIX physical disk is divided into at most 8 logical disk partitions,
125 each of which may occupy any consecutive cylinder range on the physical
126 device. The cylinders occupied by the 8 partitions for each drive type
127 are specified initially in the disk description file
128 .Pn /etc/disktab
129 (c.f.
130 .Xr disktab (5)).
131 The partition information and description of the
132 drive geometry are written in one of the first sectors of each disk with the
133 .Xr disklabel (8)
134 program. Each partition may be used for either a
135 raw data area such as a paging area or to store a UNIX filesystem.
136 It is conventional for the first partition on a disk to be used
137 to store a root filesystem, from which UNIX may be bootstrapped.
138 The second partition is traditionally used as a paging area, and the
139 rest of the disk is divided into spaces for additional ``mounted
140 filesystems'' by use of one or more additional partitions.
141 .Sh 2 "UNIX devices: block and raw"
142 .PP
143 UNIX makes a distinction between ``block'' and ``raw'' (character)
144 devices. Each disk has a block device interface where
145 the system makes the device byte addressable and you can write
146 a single byte in the middle of the disk. The system will read
147 out the data from the disk sector, insert the byte you gave it
148 and put the modified data back. The disks with the names
149 .Pn /dev/xx0[a-h] ,
150 etc., are block devices.
151 There are also raw devices available.
152 These have names like
153 .Pn /dev/rxx0[a-h] ,
154 the ``r'' here standing for ``raw''.
155 Raw devices bypass the buffer cache and use DMA directly to/from
156 the program's I/O buffers;
157 they are normally restricted to full-sector transfers.
158 In the bootstrap procedures we
159 will often suggest using the raw devices, because these tend
160 to work faster.
161 Raw devices are used when making new filesystems,
162 when checking unmounted filesystems,
163 or for copying quiescent filesystems.
164 The block devices are used to mount filesystems.
165 .PP
166 You should be aware that it is sometimes important whether to use
167 the character device (for efficiency) or not (because it would not
168 work, e.g. to write a single byte in the middle of a sector).
169 Do not change the instructions by using the wrong type of device
170 indiscriminately.