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