install revision 1.5 1 Installing NetBSD is a relatively complex process, but if you have
2 this document in hand it shouldn't be too much trouble.
3
4 There are several ways to install NetBSD onto a disk. If your Sparcstation
5 is hooked up in a network you can find find a server and arrange for a
6 diskless setup which is a convenient way to install on a machine with
7 a single disk attached. Alternatively, you could use SunOS (booted from
8 a local disk) and install NetBSD onto a second disk. For the latter method,
9 skip to the section "Installing from SunOS" below.
10
11
12 Installing using a diskless setup.
13
14 First, you must setup a diskless client configuration on a server. Consult
15 your server installation documents on how to proceed with this.
16 Put all the *.tar.gz files you want to install into the root directory
17 for your client on the server.
18
19 Next, unpack base.tar.gz on the server in the root directory for your machine.
20 If you elect to you a separately NFS-mounted filesystem for `/usr' on your
21 diskless setup, make sure the "./usr" base files in base.tar.gz end up
22 in the correct location. One way to do this is to temporarily use a loopback
23 mount on the server, re-routing <root>/usr to your server's exported
24 NetBSD "/usr" directory.
25
26 A few configuration files need to be edited:
27
28 <root>/etc/hosts
29 Add the IP addresses of both server and client.
30
31 <root>/etc/myname
32 This files contains the client's hostname; use the same
33 name as in <root>/etc/hosts.
34
35 <root>/etc/fstab
36 Enter the entries for remotely mounted `root', `swap' and
37 possibly `/usr' filesystems.
38
39 Now you must populate the the `/dev' directory for your client. If you server
40 runs SunOS 4.x, you can simply change your working directory to `<root>/dev'
41 and run the MAKEDEV script: `sh MAKEDEV all'.
42
43 On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error
44 messages about unknown user and groups. These errors are inconsequential
45 for the purpose of installing NetBSD. However, you may want to correct them
46 if you plan to the diskless setup regularly. In that case, you may re-run
47 MAKEDEV on your NetBSD machine once it has booted.
48
49 Boot your workstation from the server by entering the appropriate `boot'
50 command at the monitor prompt. Depending on the PROM version in your machine,
51 this command takes one of the following forms:
52
53 > b le()netbsd -s # for sun4 monitors
54 ok boot le()netbsd -s # for version 1 OpenBOOT ROMs
55 ok boot net netbsd -s # for version 2 OpenBOOT ROMs
56
57 This will boot the NetBSD kernel in single-user mode.
58
59 [[
60 NOTE: the latter two examples assume you operate the OpenBOOT ROM in
61 "new command mode". If your machine comes up and gives you a `>' prompt
62 instead of `ok', type:
63
64 >n # enter native OpenBOOT mode
65 ok setenv sunmon-compat? false # make it permanent
66 ok
67 ]]
68
69 If you use a diskless setup with a separately NFS-mounted /usr filesystem,
70 mount /usr by hand now:
71
72 netbsd# mount /usr
73
74
75 Start the installation procedure:
76
77 netbsd# ./install.sh
78
79
80 This script will do most of the work of transferring the system from the
81 tar files onto your disk. You will frequently be asked for confirmation
82 before the script proceeds with each phase of the installation process.
83 Occasionally, you'll have to provide a piece of information such as the
84 name of the disk you want to install on or IP addresses and domain names
85 you want to assign.
86
87 The installation script goes through the following phases:
88
89 - determination of the disk to install NetBSD on
90 - checking of the partition information on the disk
91 - creating and mounting the NetBSD filesystems
92 - setup of IP configuration
93 - extraction of the distribution tar files
94 - installation of boot programs
95
96
97 Now try a reboot. (If needed, swap your scsi id's first). Initially
98 I'd suggest you "boot sd()netbsd -bs", then try multiuser after that.
99 if you boot single-user the NetBSD incantation to make the root
100 filesystem writable is
101
102 netbsd# mount -u /dev/sd0a /
103
104 The Sun monitor normally tries to load a file called "vmunix". On
105 OpenBOOT ROM systems you can change it to load NetBSD instead using
106 the following commands:
107
108 On version 1 OpenBOOT ROMs:
109 >n
110 ok setenv boot-from sd(0,0,0)netbsd
111 ok
112
113 On version 2 OpenBOOT ROMs:
114 ok setenv boot-file netbsd
115 ok setenv boot-device /sbus/esp/sd@0,0
116
117
118 Congratulations, you have successfully installed NetBSD 1.0. When you
119 reboot into NetBSD, you should log in as "root" at the login prompt.
120 There is no initial password, but if you're using the machine in a
121 networked environment, you should create yourself an account and
122 protect it and the "root" account with good passwords.
123
124 Some of the files in the NetBSD 1.0 distribution might need to be
125 tailored for your site. In particular, the /etc/sendmail.cf file will
126 almost definitely need to be adjusted, and other files in /etc will
127 probably need to be modified. If you are unfamiliar with UN*X-like
128 system administration, it's recommended that you buy a book that
129 discusses it.
130
131
132
133 Installing from SunOS.
134
135 You need a SunOS machine to install NetBSD. You also need at
136 least the following pieces:
137
138 the *.tar.gz files you want to install (as a minimum, base.tar.gz)
139 gzip (GNU gzip) SunOS binary
140 gtar (GNU tar) SunOS binary
141 the "install.sh" script
142 a "/boot" file from a SunOS sun4c machine
143 a kernel, most likely "/netbsd"
144
145 All these pieces, except "/boot", are supplied in the NetBSD/sparc
146 distribution.
147
148 You need to format and partition the disk using SunOS (since
149 NetBSD/sparc uses SunOS disk labels.) Give yourself adequate
150 partition sizes. Here is an example layout:
151
152 partition size offset will be..
153 sd2a 28140 0 /
154 sd2b 16170 28140 swap
155 sd2c 204540 0 `whole disk'
156 sd2g 160230 44310 /usr
157
158 BTW, These are not recommended sizes. They simply match the first
159 (tiny) disk that NetBSD/sparc ran on.
160
161 Use SunOS to newfs the partitions which will have filesystems on them.
162 (NetBSD's filesystem format is identical to SunOS).
163
164 sunos# newfs /dev/rsd2a
165 [... lots of output]
166 sunos# newfs /dev/rsd2g
167 [... lots of output]
168
169 NOTE: If you are able to, there is a performance benefit from
170 newfs'ing using NetBSD. If you newfs using the NetBSD newfs command,
171 be sure to use the -O flag for your / partition, so that newfs will
172 use the 4.3BSD filesystem format, rather than the new 4.4BSD filesystem
173 format. If you forget, you will not be able to boot -- the SunOS boot
174 blocks do not understand the extended 4.4BSD filesystem format.
175
176 Mount those partitions in a tree formation, under /mnt; ie:
177
178 sunos# df
179 Filesystem kbytes used avail capacity Mounted on
180 [...]
181 /dev/sd2a 11501 0 11501 0% /mnt
182 /dev/sd2g 179529 0 179529 0% /mnt/usr
183
184 Place a standard SunOS "/boot" program in /mnt (your new root
185 partition), and use the SunOS command "installboot" to make it work.
186 The installboot man page says to do something like this:
187
188 sunos# cp /boot /mnt/boot
189 sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a
190
191 You can now extract the provided "*.tar.gz files onto your disk. The
192 provided script, "install.sh" will help you:
193
194 sunos# ls -FC
195 base.tar.gz etc.tar.gz man.tar.gz secr.tar.gz
196 comp.tar.gz games.tar.gz misc.tar.gz text.tar.gz
197 install.sh netbsd.id3_scsi
198 sunos# ./install.sh
199 [...]
200
201 This script NEEDS gzip and gtar (GNU gzip and GNU tar) on your
202 execution path! The tar files are in a "new format" that includes
203 directory information, and SunOS tar will not read them. Statically
204 linked versions of these programs for SunOS are supplied in the
205 distribution.
206
207 After the files have been extracted, repair /mnt/etc/fstab to match
208 your actual disk layout. (Minus the "/mnt" component of each path, of
209 course :-)
210
211 Now proceed to reboot the machine as described above in "Installing
212 using a diskless setup".
213