xfer revision 1.1 1 1.1 oki Installation is supported from several media types, including:
2 1.1 oki
3 1.1 oki Magneto-Optical disk (MO)
4 1.1 oki Tape
5 1.1 oki Remote NFS partition
6 1.1 oki FTP
7 1.1 oki
8 1.1 oki No matter which installation medium you choose, you'll need to have
9 1.1 oki a floppy disk. On the first, you'll put the install or upgrade floppy
10 1.1 oki image, depending on whether you're installing NetBSD for the first time,
11 1.1 oki or upgrading a previous installation.
12 1.1 oki
13 1.1 oki If you are using a UN*X-like system to write the floppy images to
14 1.1 oki disks, you should use the "dd" command to copy the file system images
15 1.1 oki (.fs files) directly to the raw floppy disks. It is suggested that
16 1.1 oki you read the dd(1) manual page or ask your system administrator to
17 1.1 oki determine the correct set of arguments to use; it will be slightly
18 1.1 oki different from system to system, and a comprehensive list of the
19 1.1 oki possibilities is beyond the scope of this document.
20 1.1 oki
21 1.1 oki If you are using Human68k to write the floppy images to disks, you should
22 1.1 oki use the "rawrite" utility, provided in the "x68k/utils" directory
23 1.1 oki of the NetBSD distribution. It will write the file system images (.fs
24 1.1 oki files) to disks.
25 1.1 oki
26 1.1 oki Note that, when installing, the install floppy MUST not be write-protected.
27 1.1 oki The install program needs to write some temporary files, and if the
28 1.1 oki disk is write-protected, it can't. If you're upgrading your system,
29 1.1 oki the upgrade floppy may be write-protected.
30 1.1 oki
31 1.1 oki Obviously, the steps necessary to prepare the distribution sets for
32 1.1 oki installation or upgrade depend on which installation medium you
33 1.1 oki choose. The steps for the various media are outlined below.
34 1.1 oki
35 1.1 oki To install or upgrade NetBSD using MO, the MO media MUST be of the
36 1.1 oki IBM `Super-floppy' format. The Human68k format is not recognized by this
37 1.1 oki release of the NetBSD/x68k. If you have a MS-DOS (or MS-Windows) machine
38 1.1 oki with an MO drive connected, use it. If you don't, and if you have
39 1.1 oki a program to handle IBM format MO for Human68k, copy all the files in
40 1.1 oki the subdirectory "x68k/binaries" and RENAME THEIR NAME IN UPPER CASE.
41 1.1 oki
42 1.1 oki To install or upgrade NetBSD using a tape, you need to do the
43 1.1 oki following:
44 1.1 oki
45 1.1 oki To install NetBSD from a tape, you need to make a tape that
46 1.1 oki contains the distribution set files, in "tar" format. If
47 1.1 oki you're making the tape on a UN*X-like system, the easiest way
48 1.1 oki to do so is probably something like:
49 1.1 oki
50 1.1 oki tar cf <tape_device> <dist_directories>
51 1.1 oki
52 1.1 oki where "<tape_device>" is the name of the tape device that
53 1.1 oki describes the tape drive you're using (possibly /dev/rst0, or
54 1.1 oki something similar, but it will vary from system to system.
55 1.1 oki (If you can't figure it out, ask your system administrator.)
56 1.1 oki In the above example, "<dist_directories>" are the
57 1.1 oki distribution sets' directories, for the distribution sets you
58 1.1 oki wish to place on the tape. For instance, to put the "base12"
59 1.1 oki and "etc12" distributions on tape (in order to do the absolute
60 1.1 oki minimum installation to a new disk), you would do the
61 1.1 oki following:
62 1.1 oki
63 1.1 oki cd .../NetBSD-1.2 # the top of the tree
64 1.1 oki cd x68k/binary
65 1.1 oki tar cf <tape_device> base12 etc12
66 1.1 oki
67 1.1 oki (Note that you still need to fill in "<tape_device>" in the
68 1.1 oki example.)
69 1.1 oki
70 1.1 oki Once you have the files on the tape, you can proceed to the
71 1.1 oki next step in the installation or upgrade process. If you're
72 1.1 oki installing NetBSD from scratch, go to the section on preparing
73 1.1 oki your hard disk, below. If you're upgrading an existing
74 1.1 oki installation, go directly to the section on upgrading.
75 1.1 oki
76 1.1 oki To install or upgrade NetBSD using a remote partition, mounted via
77 1.1 oki NFS, you must do the following:
78 1.1 oki
79 1.1 oki NOTE: This method of installation is recommended only for
80 1.1 oki those already familiar with using BSD network
81 1.1 oki configuration and management commands. If you aren't,
82 1.1 oki this documentation should help, but is not intended to
83 1.1 oki be all-encompassing.
84 1.1 oki
85 1.1 oki Place the NetBSD distribution sets you wish to install into a
86 1.1 oki directory on an NFS server, and make that directory mountable
87 1.1 oki by the machine on which you are installing or upgrading NetBSD.
88 1.1 oki This will probably require modifying the /etc/exports file on
89 1.1 oki of the NFS server and resetting its mount daemon (mountd).
90 1.1 oki (Both of these actions will probably require superuser
91 1.1 oki privileges on the server.)
92 1.1 oki
93 1.1 oki You need to know the the numeric IP address of the NFS server,
94 1.1 oki and, if the server is not on a network directly connected to
95 1.1 oki the machine on which you're installing or upgrading NetBSD,
96 1.1 oki you need to know the numeric IP address of the router closest
97 1.1 oki to the NetBSD machine. Finally, you need to know the numeric
98 1.1 oki IP address of the NetBSD machine itself.
99 1.1 oki
100 1.1 oki Once the NFS server is set up properly and you have the
101 1.1 oki information mentioned above, you can proceed to the next step
102 1.1 oki in the installation or upgrade process. If you're installing
103 1.1 oki NetBSD from scratch, go to the section on preparing your hard
104 1.1 oki disk, below. If you're upgrading an existing installation, go
105 1.1 oki directly to the section on upgrading.
106 1.1 oki
107 1.1 oki To install or upgrade NetBSD by using FTP to get the installation
108 1.1 oki sets, you must do the following:
109 1.1 oki
110 1.1 oki NOTE: This method of installation is recommended only for
111 1.1 oki those already familiar with using BSD network
112 1.1 oki configuration and management commands. If you aren't,
113 1.1 oki this documentation should help, but is not intended to
114 1.1 oki be all-encompassing.
115 1.1 oki
116 1.1 oki The preparations for this installation/upgrade method are
117 1.1 oki easy; all you make sure that there's some FTP site from which
118 1.1 oki you can retrieve the NetBSD distribution when you're about to
119 1.1 oki install or upgrade. You need to know the numeric IP address
120 1.1 oki of that site, and, if it's not on a network directly connected
121 1.1 oki to the machine on which you're installing or upgrading NetBSD,
122 1.1 oki you need to know the numeric IP address of the router closest
123 1.1 oki to the NetBSD machine. Finally, you need to know the numeric
124 1.1 oki IP address of the NetBSD machine itself.
125 1.1 oki
126 1.1 oki Once you have this information, you can proceed to the next
127 1.1 oki step in the installation or upgrade process. If you're
128 1.1 oki installing NetBSD from scratch, go to the section on
129 1.1 oki preparing your hard disk, below. If you're upgrading an
130 1.1 oki existing installation, go directly to the section on
131 1.1 oki upgrading.
132 1.1 oki
133 1.1 oki If you are upgrading NetBSD, you also have the option of installing
134 1.1 oki NetBSD by putting the new distribution sets somewhere in your existing
135 1.1 oki file system, and using them from there. To do that, you must do the
136 1.1 oki following:
137 1.1 oki
138 1.1 oki Place the distribution sets you wish to upgrade somewhere in
139 1.1 oki your current file system tree. At a bare minimum, you must
140 1.1 oki upgrade the "base" binary distribution, and so must put the
141 1.1 oki "base12" set somewhere in your file system. If you wish,
142 1.1 oki you can do the other sets, as well, but you should NOT upgrade
143 1.1 oki the "etc" distribution; the "etc" distribution contains system
144 1.1 oki configuration files that you should review and update by hand.
145 1.1 oki
146 1.1 oki Once you have done this, you can proceed to the next step in
147 1.1 oki the upgrade process, actually upgrading your system.
148