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