1 # Updating Information for DragonFly users.
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.
8 # If you discover any problem, please contact the bugs@lists.dragonflybsd.org
9 # mailing list with the details.
11 +-----------------------------------------------------------------------+
12 + UPGRADING DRAGONFLY FROM 4.0 TO LATER VERSIONS +
13 +-----------------------------------------------------------------------+
15 _KPOSIX_VERSION and P1003_1B OPTIONS REMOVED
16 --------------------------------------------
18 The _KPOSIX_VERSION and P1003_1B kernel options have been changed to
19 no-ops. They can be removed from custom kernel configurations.
21 SOUND SYSTEM UPDATED FROM FreeBSD 11-CURRENT
22 --------------------------------------------
24 Many more sound devices may be detected.
26 If the default device choosen isn't to your liking, setting the sysctl
27 hw.snd.default_unit to a different number will change it.
32 Support for the SCTP protocol has been removed.
34 OLD USB DRIVERS REMOVED
35 -----------------------
37 The old USB stack, along with the kernel config option "device oldusb"
38 and the make.conf variable "WANT_OLDUSB" have been removed. This means
39 that for custom kernel configuration files which were derived from a
40 GENERIC or X86_64_GENERIC file prior to making the usb4bsd stack default,
41 various (old USB stack specific) devices will now complain about being
45 * natausb (not yet ported to usb4bsd)
46 * rue (not yet ported to usb4bsd)
47 * ugen (no longer needed in usb4bsd)
48 * urio (not yet ported to usb4bsd)
49 * uscanner (no longer needed in usb4bsd)
51 They should be removed or commented out in such custom kernel configs.
53 +-----------------------------------------------------------------------+
54 + UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS +
55 +-----------------------------------------------------------------------+
57 SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
58 -------------------------------------------
60 DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
61 the default now (even on single-core systems), both for, like, 21 months.
62 We kept the options around as no-ops as a convenience, to allow people
63 using the same config for the then current release and the then current
64 master. That period is now over, so any configs still having those
65 options have to be adjusted.
67 SYSVIPC SYSCALLS MADE NON-OPTIONAL
68 ----------------------------------
70 The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
71 now compiled in by default. The options are no-ops for now.
73 DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
74 --------------------------------------------------------------------
76 The default driver for those controllers is now mrsas(4) due to reports
77 of file system corruption using the mfi(4) driver. The whole issue (and
78 how to deal with potential problems when switching) was explained here:
80 http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
82 A tunable is provided for letting those controllers still attach via
83 the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
85 OLDER NETWORK DRIVERS MOVED TO I386 ONLY
86 ----------------------------------------
88 The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
89 and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
90 removed in kernel configs derived from X86_64_GENERIC.
92 +-----------------------------------------------------------------------+
93 + UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS +
94 +-----------------------------------------------------------------------+
96 UPDATE FROM MOST RECENT 3.6
97 ---------------------------
99 Versions of 3.6 built before June 25th have a bug where installworld might
100 crash during installation of the new initrd. Upgrade to the latest version
101 of 3.6 before updating to 3.8 or later.
103 ATM, IPX, NCP AND NWFS SUPPORT DROPPED
104 --------------------------------------
106 Support for the IPX and NCP network protocols and for mouting NetWare
107 file systems has been dropped. Dito for ATM protocol support.
109 INITRD IMAGES NOW INSTALLED BY DEFAULT
110 --------------------------------------
112 An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
114 Older images installed under the file name of initrd.img will be removed
115 automatically by the make upgrade process.
117 USB4BSD IS NOW THE DEFAULT USB STACK
118 ------------------------------------
120 To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
121 replace "device usb" with "device oldusb" in the kernel configuration.
123 MORE ISA SUPPORT DROPPED
124 ------------------------
126 ISA support has been dropped from the following drivers: adv(4), an(4),
127 ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
128 si(4), sn(4), and stg(4).
130 +-----------------------------------------------------------------------+
131 + UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS +
132 +-----------------------------------------------------------------------+
137 Installed third-party software (dports) will have to be rebuilt after upgrade,
138 or reinstalled from binary packages.
140 UPDATING FROM 3.4 TO 3.6
141 ------------------------
143 This only applies for this specific upgrade due to locale changes; it is
144 not needed for upgrades after 3.6. Please update in this order:
153 See this mailing list post for details:
154 http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
156 CYRIX OPTIONS REMOVED
157 ---------------------
159 The following Cyrix related options have been removed: CPU_BTB_EN,
160 CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
161 CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
162 CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
164 ISA SUPPORT REMOVED FROM RP(4)
165 ------------------------------
167 ISA support has been removed from the rp(4) driver. It is now PCI only.
169 +-----------------------------------------------------------------------+
170 + UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS +
171 +-----------------------------------------------------------------------+
173 COMPAT_SUNOS OPTION REMOVED
174 ---------------------------
176 The COMPAT_SUNOS option has been removed. It was meant to provide binary
177 compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
179 ISA SOUND CARD SUPPORT REMOVED
180 ------------------------------
182 The following modules have been removed (all for ISA sound cards):
183 snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
188 DragonFly has switched base compilers. GCC 4.7 is now the default
189 compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make
190 variable ceases to work now.
192 Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
193 /etc/make.conf to prohibit GCC 4.4 from building. However, using it is
194 highly discouraged. There are a few packages in pkgsrc that do not build
195 with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At
196 this time, it is recommended to keep both compilers on the base system.
201 The SMP kernel option has been made a no-op. All kernels now feature SMP
202 support. If you have 'options SMP' in your kernel config, you can as well
205 DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
206 ---------------------------------------------------------------------------
208 The DEVICE_POLLING kernel option has been made a no-op and it has been
209 replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your
210 kernel config, you need to change it to IFPOLL_ENABLE.
212 Also, the KTR_POLLING kernel option has been removed, so it must be
213 removed from kernel configs that have it.
215 BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
216 ---------------------------------------------------
218 The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
219 cards will no longer be detected.
221 The same has been done for Stallion multiport serial controllers. stli(4)
222 has been completely removed (along with the stlload(8) and stlstty(8)
223 utilities) and stl(4) was changed to support only PCI cards. Similarly,
224 ISA support was removed from cy(4) too. All these drivers are i386 only.
226 COMPAT_OLDISA OPTION GONE
227 -------------------------
229 The i386 specific COMPAT_OLDISA kernel option has been removed, since
230 nothing needs it anymore.
232 +-----------------------------------------------------------------------+
233 + UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS +
234 +-----------------------------------------------------------------------+
236 APIC_IO OPTION REMOVED
237 ----------------------
239 The APIC_IO kernel option is no longer accepted after having been without
240 effect for a while. The hw.ioapic_enable tunable now serves its purpose.
241 If you have 'options APIC_IO' in your kernel config, you'll have to
244 WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
245 -----------------------------------------
247 The wdog framework is now compiled into our kernels by default, so the
248 options are no longer needed.
253 doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
254 NO_X make.conf option was removed too.
259 GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
260 default compiler in base (default is still GCC 4.4).
262 Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
263 NO_GCC47 in /etc/make.conf.
268 A new USB stack (from FreeBSD) has been brought in. The following
269 modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
270 usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
273 It is not yet the default. To activate it, WANT_USB4BSD=yes has to
274 be put in make.conf and device "usb4bsd" (quotes needed) has to
275 replace device usb in the kernel config. After that, a full
276 build/install/upgrade cycle is needed.
278 Note that this is experimental and incomplete, but we are interested
279 in hearing about issues with it, of course.
281 ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
282 ---------------------------------------------
284 ISA adapter support was dropped from the aic(4) driver.
286 +-----------------------------------------------------------------------+
287 + UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS +
288 +-----------------------------------------------------------------------+
290 SEVERAL ISA DRIVERS REMOVED
291 ---------------------------
293 The following ISA only drivers have been removed along with a couple of
294 associated userland tools:
310 tw(4) & xten(1) & xtend(8)
314 Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
315 config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
318 If buildkernel complains about any of these drivers, just remove them
319 from your kernel configuration.
323 Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
324 values of BINUTILSVERS are now binutils221 and binutils222 (default).
326 BUILDWORLD/-KERNEL PARALLELIZATION WORK
327 ---------------------------------------
328 Due to changes in the way we build with more than one make job, you
329 will have to update install(1) and mkdir(1) prior to buildworld if you
330 want to build with 'make -j':
332 cd /usr/src/usr.bin/xinstall; make; make install; make clean
333 cd /usr/src/bin/mkdir; make; make install; make clean
337 dma(8) has been upgraded to v0.7 which no longer supports the
338 /etc/dma/virtusertable. Some of its functionality has been replaced
339 with the MASQUERADE keyword and the EMAIL environment variable (see
340 the dma(8) manual page).
342 +-----------------------------------------------------------------------+
343 + UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS +
344 +-----------------------------------------------------------------------+
346 GCC 4.4 & BINUTILS 2.21
347 -----------------------
349 GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
350 been made DragonFly's default Binutils.
352 That means that any settings that set CCVER to 'gcc44' are not needed
353 anymore. Instead, CCVER can be set to 'gcc41' to go back to using
356 It also means that 'binutils221' as a value for BINUTILSVER has no
357 effect anymore. 2.17 has been removed and 'binutils220' is available
360 The NO_GCC44 option has been removed and will not affect the build
361 anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
362 building in a similar fashion.
364 Note that you must do a full buildworld/buildkernel for upgrading.
369 The config file for pkg_radd has moved from /etc/settings.conf to
370 /etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
371 if this is needed. This warning only applies if /etc/settings.conf
372 exists. pkg_radd will continue to work with defaults.
374 +-----------------------------------------------------------------------+
376 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
377 +-----------------------------------------------------------------------+
382 OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
383 This shouldn't break any 3rd-party software, but you'll need to recompile your
384 3rd-party software if you want it to link against the new version of OpenSSL.
389 A new loader (dloader) has been added which better handles booting from
390 multiple kernel/module versions.
392 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
398 make buildkernel KERNCONF=<KERNELNAME>
399 make installkernel KERNCONF=<KERNELNAME>
401 Note that you must installworld and run the 'upgrade' target before
402 installing the new kernel.
407 BIND has been removed from the base system. The ldns and drill tools have
408 been added for basic functionality. Use 'drill' where you would normally
409 use nslookup or dig, or install BIND from pkgsrc. It's available as
410 net/bind95, net/bind96, or net/bind97 as of this writing.
412 This only affects older systems upgrading to 2.8. New 2.8+ installs
413 include BIND as a pkgsrc package.
415 +-----------------------------------------------------------------------+
416 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
418 +-----------------------------------------------------------------------+
420 Instructions on how to obtain and maintain DragonFly source code using git
421 are in the development(7) manual page.
423 To upgrade a DragonFly system from sources you run the following sequence:
427 make buildkernel KERNCONF=<KERNELNAME>
428 make installkernel KERNCONF=<KERNELNAME>
431 You will also want to run the 'upgrade' target to upgrade your /etc and the
432 rest of your system. The upgrade target is aware of stale files created by
433 older DragonFly installations and should delete them automatically.
437 See the build(7) manual page for further information.
439 Once you've done a full build of the world and kernel you can do incremental
440 upgrades of either by using the 'quickworld' and 'quickkernel' targets
441 instead of 'buildworld' and 'buildkernel'. If you have any problems with
442 the quick targets, try updating your repo first, and then a full buildworld
443 and buildkernel as shown above, before asking for help.
445 +-----------------------------------------------------------------------+
446 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
447 +-----------------------------------------------------------------------+
449 In 2.1 kernel and modules has moved to boot directory. For most cases
450 this is handled automatically by 'make upgrade'. A few cases needs manual
453 * When installing a kernel without first doing a make buildworld,
454 installworld and upgrade to the same DESTDIR as kernel:
455 make DESTDIR/boot directory and move kernel and modules into this boot
456 directory; also move kernel.old and modules.old.
457 Typical example is vkernel(7), use (no modules used):
461 chflags noschg kernel
462 mv kernel kernel.old boot
463 chflags schg boot/kernel
465 * When using a boot-only partition, /boot/loader.rc needs to be edited:
466 delete occurrences of '/boot/'.
467 These occurences can normally be deleted in any case, see loader(8).
469 +-----------------------------------------------------------------------+
470 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
471 +-----------------------------------------------------------------------+
473 In 1.9 major changes to the disk management infrastructure have taken
474 place. make upgrade may not catch all of your disk devices in /dev,
475 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
476 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
477 and MAKEDEV no longer exists.
479 The biggest changes in 1.9 are:
481 (1) That whole-slice devices such as da0s1 no longer share the same device
482 id as partition c devices such as da0s1c.
484 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
485 with no snooping or reserved sectors. Consequently you cannot run
486 disklabel on this device. Instead you must run disklabel on a
489 (3) The 'compatibility' partitions now use slice 0 in the device name,
490 so instead of da0a you must specify da0s0a. Also, as per (1) above,
491 accessing the disklabel for the compatibility partitions must be
492 done via slice 0 (da0s0).
494 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
495 and CCD now run through the disk management layer and are assigned
496 real disk management devices. VN and CCD in particular do not usually
497 use a MBR and disklabels must be accessed through the compatibility
498 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
499 don't name it 'ccd0s0' in the config file.
501 Generally speaking, you have to get used to running fdisk and disklabel on
502 the correctly specified device names. A lot of the wiggle, such as running
503 disklabel on a partition, has been removed.
505 +-----------------------------------------------------------------------+
506 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
507 +-----------------------------------------------------------------------+
512 Kerberos IV (eBones) was removed from the tree, please consider moving to
513 Kerberos 5 (Heimdal).
515 > Package Management System
516 ---------------------------
518 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
519 management system. The necessary tools to build and maintain packages
520 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
521 directories are in your PATH variable.
523 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
524 the tarball from NetBSD:
526 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
527 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
529 This tree can then be kept up to date with cvs update:
531 cd /usr/pkgsrc; cvs up
533 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
534 build and install the pkgsrc bootstrap manually:
536 cd /usr/pkgsrc/bootstrap
537 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
539 +-----------------------------------------------------------------------+
540 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
541 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
542 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
543 +-----------------------------------------------------------------------+
545 The compatibility shims for the build environment have been removed, you
546 have to update to DragonFly 1.2 release branch first.
548 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
549 The existing configuration can be converted using /etc/pam.d/convert.sh.
550 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
551 the pam_skey.so module was retired, you have to remove it manually from
552 your configuration, when you convert it.
554 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
555 ---------------------
557 The following users may be missing from your password file. Use vipw and
558 add any that are missing:
560 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
561 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
563 The following groups may be missing from your group file. Use vi /etc/group
564 and add any that are missing:
571 > Upgrading to DragonFly from FreeBSD
572 ---------------------
574 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
575 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
576 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
577 make depend information, it starts from scratch, so no pre-cleaning of the
578 object hierarchy is necessary.
580 # get the CVS repository (it is placed in /home/dcvs, 500MB).
581 # Please use the -h option and a mirror site to pull the
582 # initial repository, but feel free to use the main repository
583 # machine to pull updates.
584 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
585 # install the source from the CVS hierarchy (remove preexisting
586 # FreeBSD src first) (500MB)
589 cvs -R -d /home/dcvs checkout -P src
591 # build it (500MB used in /usr/obj)
595 make buildkernel KERNCONF=<KERNELNAME>
597 Once you have built DragonFly you have to install it over FreeBSD. Since
598 DragonFly does not track changes made by FreeBSD to its include file
599 hierarchy and include file pollution can cause all sorts of unexpected
600 compilation issues to come up, it is best to wipe your include hierarchy
601 prior to installing DragonFly. Note that you should not wipe any installed
602 FreeBSD header files or binaries until after you have successfully completed
603 the build steps above.
607 make installkernel KERNCONF=<KERNELNAME>
610 Then you need to upgrade your system. DragonFly's 'make upgrade' target
611 will unconditionally upgrade the /etc files that sysops do not usually
612 mess around with, such as the files in /etc/rc.d. It will also remove any
613 obsolete files such as utilities and manpages that have been removed from
614 the system since the version you're coming from. If you are unsure we
615 recommend that you make a backup of at least your /etc before applying
616 this step. Note that DragonFly's RC system is basically RCNG from
617 FreeBSD-5, but there are some differences in the contents of the RC files.
621 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
622 Doing so might leave your system in an unusable state.
624 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
625 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
626 report these files to the DragonFly developers so that they can be added to
627 the 'upgrade' target.