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