kernel: Add mps(4) to our GENERIC kernels.
[dragonfly.git] / UPDATING
CommitLineData
d2a0decc
MD
1# Updating Information for DragonFly users.
2#
3#
4# This file should warn you of any pitfalls which you might need to work around
5# when trying to update your DragonFly system. The information below is
6# in reverse-time order, with the latest information at the top.
7#
8# If you discover any problem, please contact the bugs@lists.dragonflybsd.org
9# mailing list with the details.
d2a0decc 10
c691bb43
SW
11+-----------------------------------------------------------------------+
12+ UPGRADING DRAGONFLY FROM 3.0 to later versions +
13+-----------------------------------------------------------------------+
14
15APIC_IO OPTION REMOVED
16----------------------
17
18The APIC_IO kernel option is no longer accepted after having been without
19effect for a while. The hw.ioapic_enable tunable now serves its purpose.
20If you have 'options APIC_IO' in your kernel config, you'll have to
21remove it.
22
96386d4b
SW
23+-----------------------------------------------------------------------+
24+ UPGRADING DRAGONFLY FROM 2.10 to later versions +
25+-----------------------------------------------------------------------+
26
27SEVERAL ISA DRIVERS REMOVED
28---------------------------
29
30The following ISA only drivers have been removed along with a couple of
31associated userland tools:
32
33aha(4)
34asc(4) & sasc(1)
35ctx
36dgb(4)
37el(4)
38gpib
39gsc(4) & sgsc(1)
40ie(4)
41labpc(4)
42le(4)
43mse(4)
44rc(4)
45rdp(4)
46spigot
47tw(4) & xten(1) & xtend(8)
48wl(4) & wlconfig(8)
49wt(4)
50
51Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
52config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
53file.
54
55If buildkernel complains about any of these drivers, just remove them
56from your kernel configuration.
57
919eb219
JM
58BINUTILS 2.20
59-------------
37c5a0db 60Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
e685772e 61values of BINUTILSVERS are now binutils221 and binutils222 (default).
919eb219 62
83bc1e2a
SW
63BUILDWORLD/-KERNEL PARALLELIZATION WORK
64---------------------------------------
65Due to changes in the way we build with more than one make job, you
66will have to update install(1) and mkdir(1) prior to buildworld if you
67want to build with 'make -j':
68
69cd /usr/src/usr.bin/xinstall; make; make install; make clean
70cd /usr/src/bin/mkdir; make; make install; make clean
71
eca86bd9
SW
72DMA(8) UPGRADE
73--------------
74dma(8) has been upgraded to v0.7 which no longer supports the
75/etc/dma/virtusertable. Some of its functionality has been replaced
76with the MASQUERADE keyword and the EMAIL environment variable (see
77the dma(8) manual page).
78
a4a39c94 79+-----------------------------------------------------------------------+
2443e96e 80+ UPGRADING DRAGONFLY FROM 2.8 to later versions +
a4a39c94
JS
81+-----------------------------------------------------------------------+
82
b1242318
SW
83GCC 4.4 & BINUTILS 2.21
84-----------------------
30c91f0c 85
b1242318
SW
86GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
87been made DragonFly's default Binutils.
30c91f0c
SW
88
89That means that any settings that set CCVER to 'gcc44' are not needed
90anymore. Instead, CCVER can be set to 'gcc41' to go back to using
91GCC 4.1.
92
b1242318
SW
93It also means that 'binutils221' as a value for BINUTILSVER has no
94effect anymore. 2.17 has been removed and 'binutils220' is available
95as an option.
96
5738210d 97The NO_GCC44 option has been removed and will not affect the build
30c91f0c
SW
98anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
99building in a similar fashion.
100
80abb3be 101Note that you must do a full buildworld/buildkernel for upgrading.
30c91f0c 102
a4a39c94 103pkg_radd settings
c983d16e 104-----------------
a4a39c94
JS
105
106The config file for pkg_radd has moved from /etc/settings.conf to
107/etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
108if this is needed. This warning only applies if /etc/settings.conf
109exists. pkg_radd will continue to work with defaults.
110
b79f66dd 111+-----------------------------------------------------------------------+
72fe41d3 112+ 20100927 +
1bb1cc14 113+ UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
b79f66dd
JT
114+-----------------------------------------------------------------------+
115
72fe41d3 116OpenSSL
c983d16e 117--------
72fe41d3
PA
118
119OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
120This shouldn't break any 3rd-party software, but you'll need to recompile your
1213rd-party software if you want it to link against the new version of OpenSSL.
122
8eb0b612 123Loader
c983d16e 124-------
8eb0b612 125
b79f66dd
JT
126A new loader (dloader) has been added which better handles booting from
127multiple kernel/module versions.
128
129To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
130
131 cd /usr/src
132 make buildworld
133 make installworld
134 make upgrade
135 make buildkernel KERNCONF=<KERNELNAME>
136 make installkernel KERNCONF=<KERNELNAME>
137
138Note that you must installworld and run the 'upgrade' target before
139installing the new kernel.
140
8eb0b612 141BIND
c983d16e 142-----
8eb0b612
JS
143
144BIND has been removed from the base system. The ldns and drill tools have
145been added for basic functionality. Use 'drill' where you would normally
146use nslookup or dig, or install BIND from pkgsrc. It's available as
147net/bind95, net/bind96, or net/bind97 as of this writing.
148
149This only affects older systems upgrading to 2.8. New 2.8+ installs
150include BIND as a pkgsrc package.
151
d2a0decc
MD
152+-----------------------------------------------------------------------+
153+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
154+ GENERAL +
155+-----------------------------------------------------------------------+
984263bc 156
a700883c
SW
157Instructions on how to obtain and maintain DragonFly source code using git
158are in the development(7) manual page.
d2a0decc
MD
159
160To upgrade a DragonFly system from sources you run the following sequence:
161
162 cd /usr/src
163 make buildworld
164 make buildkernel KERNCONF=<KERNELNAME>
165 make installkernel KERNCONF=<KERNELNAME>
166 make installworld
167
168You will also want to run the 'upgrade' target to upgrade your /etc and the
169rest of your system. The upgrade target is aware of stale files created by
170older DragonFly installations and should delete them automatically.
171
172 make upgrade
173
a700883c
SW
174See the build(7) manual page for further information.
175
d2a0decc
MD
176Once you've done a full build of the world and kernel you can do incremental
177upgrades of either by using the 'quickworld' and 'quickkernel' targets
178instead of 'buildworld' and 'buildkernel'. If you have any problems with
a700883c 179the quick targets, try updating your repo first, and then a full buildworld
d2a0decc 180and buildkernel as shown above, before asking for help.
4523a2c0
TN
181
182+-----------------------------------------------------------------------+
183+ UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
184+-----------------------------------------------------------------------+
185
186In 2.1 kernel and modules has moved to boot directory. For most cases
187this is handled automatically by 'make upgrade'. A few cases needs manual
188intervention:
189
190 * When installing a kernel without first doing a make buildworld,
191 installworld and upgrade to the same DESTDIR as kernel:
192 make DESTDIR/boot directory and move kernel and modules into this boot
193 directory; also move kernel.old and modules.old.
194 Typical example is vkernel(7), use (no modules used):
195
196 cd /var/vkernel
197 mkdir boot
198 chflags noschg kernel
199 mv kernel kernel.old boot
200 chflags schg boot/kernel
201
202 * When using a boot-only partition, /boot/loader.rc needs to be edited:
203 delete occurrences of '/boot/'.
204 These occurences can normally be deleted in any case, see loader(8).
d2a0decc
MD
205
206+-----------------------------------------------------------------------+
207+ UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
208+-----------------------------------------------------------------------+
209
210In 1.9 major changes to the disk management infrastructure have taken
211place. make upgrade may not catch all of your disk devices in /dev,
212so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
45e80934
MD
213are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
214and MAKEDEV no longer exists.
d2a0decc
MD
215
216The biggest changes in 1.9 are:
217
218(1) That whole-slice devices such as da0s1 no longer share the same device
219 id as partition c devices such as da0s1c.
220
221(2) The whole-disk device (e.g. da0) is full raw access to the disk,
222 with no snooping or reserved sectors. Consequently you cannot run
223 disklabel on this device. Instead you must run disklabel on a
224 whole-slice device.
225
226(3) The 'compatibility' partitions now use slice 0 in the device name,
227 so instead of da0a you must specify da0s0a. Also, as per (1) above,
228 accessing the disklabel for the compatibility partitions must be
229 done via slice 0 (da0s0).
230
231(4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
232 and CCD now run through the disk management layer and are assigned
233 real disk management devices. VN and CCD in particular do not usually
234 use a MBR and disklabels must be accessed through the compatibility
235 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
236 don't name it 'ccd0s0' in the config file.
237
238Generally speaking, you have to get used to running fdisk and disklabel on
239the correctly specified device names. A lot of the wiggle, such as running
240disklabel on a partition, has been removed.
241
242+-----------------------------------------------------------------------+
243+ UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
244+-----------------------------------------------------------------------+
245
246> Kerberos IV
247-------------
248
249Kerberos IV (eBones) was removed from the tree, please consider moving to
250Kerberos 5 (Heimdal).
251
252> Package Management System
253---------------------------
254
255Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
256management system. The necessary tools to build and maintain packages
257are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
258directories are in your PATH variable.
259
260In order to obtain a reasonably current snapshot of the pkgsrc tree, use
261the tarball from NetBSD:
262
263 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
264 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
265
266This tree can then be kept up to date with cvs update:
267
268 cd /usr/pkgsrc; cvs up
269
270NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
271build and install the pkgsrc bootstrap manually:
272
273 cd /usr/pkgsrc/bootstrap
274 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
275
276+-----------------------------------------------------------------------+
277+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
278+ UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
279+ DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
280+-----------------------------------------------------------------------+
58116288 281
114580ac 282The compatibility shims for the build environment have been removed, you
58116288
JS
283have to update to DragonFly 1.2 release branch first.
284
1fcc7462
JS
285The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
286The existing configuration can be converted using /etc/pam.d/convert.sh.
287Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
288the pam_skey.so module was retired, you have to remove it manually from
289your configuration, when you convert it.
58116288 290
a3107071
MD
291> Required user and group IDs when upgrading from either FreeBSD or DragonFly
292---------------------
293
294The following users may be missing from your password file. Use vipw and
295add any that are missing:
296
297smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
dcf85892 298_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
a3107071
MD
299
300The following groups may be missing from your group file. Use vi /etc/group
301and add any that are missing:
302
303smmsp:*:25:
304authpf:*:63:
dcf85892 305_pflogd:*:64:
a3107071
MD
306
307
f419daca 308> Upgrading to DragonFly from FreeBSD
5e0ae0d4 309---------------------
984263bc 310
f419daca
MD
311You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
312FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
313FreeBSD. Note that the DragonFly buildworld target does not try to reuse
314make depend information, it starts from scratch, so no pre-cleaning of the
315object hierarchy is necessary.
316
466bbc10 317 # get the CVS repository (it is placed in /home/dcvs, 500MB).
f419daca
MD
318 # Please use the -h option and a mirror site to pull the
319 # initial repository, but feel free to use the main repository
320 # machine to pull updates.
5010eeb3 321 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
f419daca
MD
322 # install the source from the CVS hierarchy (remove preexisting
323 # FreeBSD src first) (500MB)
324 cd /usr
325 rm -rf src
50172b1c 326 cvs -R -d /home/dcvs checkout -P src
f419daca
MD
327
328 # build it (500MB used in /usr/obj)
329 #
330 cd /usr/src
331 make buildworld
332 make buildkernel KERNCONF=<KERNELNAME>
984263bc 333
f419daca
MD
334Once you have built DragonFly you have to install it over FreeBSD. Since
335DragonFly does not track changes made by FreeBSD to its include file
336hierarchy and include file pollution can cause all sorts of unexpected
337compilation issues to come up, it is best to wipe your include hierarchy
338prior to installing DragonFly. Note that you should not wipe any installed
339FreeBSD header files or binaries until after you have successfully completed
340the build steps above.
fb12f484 341
f419daca
MD
342 rm -rf /usr/include
343 mkdir /usr/include
344 make installkernel KERNCONF=<KERNELNAME>
345 make installworld
fb12f484 346
b8cbf045 347Then you need to upgrade your system. DragonFly's 'make upgrade' target
f419daca 348will unconditionally upgrade the /etc files that sysops do not usually
b8cbf045
SW
349mess around with, such as the files in /etc/rc.d. It will also remove any
350obsolete files such as utilities and manpages that have been removed from
351the system since the version you're coming from. If you are unsure we
352recommend that you make a backup of at least your /etc before applying
353this step. Note that DragonFly's RC system is basically RCNG from
354FreeBSD-5, but there are some differences in the contents of the RC files.
f419daca
MD
355
356 make upgrade
357
b8cbf045
SW
358NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
359Doing so might leave your system in an unusable state.
360
f419daca 361Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
b8cbf045
SW
362/usr/bin, and /usr/lib, and remove any stale files that you find. Please
363report these files to the DragonFly developers so that they can be added to
364the 'upgrade' target.
f419daca 365