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.
56 The GCC 4.4 compiler has been retired. It has been replaced by a
57 [prerelease] version of GCC 5.0. The following make.conf variables no
58 longer work: NO_GCC44, NO_OBJC, and NO_CXX. The latter was never
59 documented and the latest versions of GCC are partially written in C++
60 so a C++ compiler is no longer optional. In practical terms it has not
61 been optional for many years as other base components are also written in
62 C++. The resource savings by avoiding building Objective-C compiler is
63 so small, the complexity added by NO_OBJC internally was deemed a bad
64 tradeoff so that is the reason for its removal. Also note that no "info"
65 pages are installed with GCC 5.0. This is intentional; they are available
66 via the internet if desired over the installed man pages.
68 Currently, GCC 4.7 is still designated as the primary compiler. After
69 GCC 5.0 is released, this may change and these update notes will be
70 revised accordingly. DPorts will use GCC 5.0 on this release regardless.
71 If GCC 5.0 is unwanted, the make.conf variable NO_GCC50 will block its
72 building and installation.
74 To use GCC 5.0 to build world and kernel, set WORLD_CCVER=gcc50 in
75 make.conf before building those targets.
77 +-----------------------------------------------------------------------+
78 + UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS +
79 +-----------------------------------------------------------------------+
81 SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
82 -------------------------------------------
84 DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
85 the default now (even on single-core systems), both for, like, 21 months.
86 We kept the options around as no-ops as a convenience, to allow people
87 using the same config for the then current release and the then current
88 master. That period is now over, so any configs still having those
89 options have to be adjusted.
91 SYSVIPC SYSCALLS MADE NON-OPTIONAL
92 ----------------------------------
94 The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
95 now compiled in by default. The options are no-ops for now.
97 DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
98 --------------------------------------------------------------------
100 The default driver for those controllers is now mrsas(4) due to reports
101 of file system corruption using the mfi(4) driver. The whole issue (and
102 how to deal with potential problems when switching) was explained here:
104 http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
106 A tunable is provided for letting those controllers still attach via
107 the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
109 OLDER NETWORK DRIVERS MOVED TO I386 ONLY
110 ----------------------------------------
112 The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
113 and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
114 removed in kernel configs derived from X86_64_GENERIC.
116 +-----------------------------------------------------------------------+
117 + UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS +
118 +-----------------------------------------------------------------------+
120 UPDATE FROM MOST RECENT 3.6
121 ---------------------------
123 Versions of 3.6 built before June 25th have a bug where installworld might
124 crash during installation of the new initrd. Upgrade to the latest version
125 of 3.6 before updating to 3.8 or later.
127 ATM, IPX, NCP AND NWFS SUPPORT DROPPED
128 --------------------------------------
130 Support for the IPX and NCP network protocols and for mouting NetWare
131 file systems has been dropped. Dito for ATM protocol support.
133 INITRD IMAGES NOW INSTALLED BY DEFAULT
134 --------------------------------------
136 An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
138 Older images installed under the file name of initrd.img will be removed
139 automatically by the make upgrade process.
141 USB4BSD IS NOW THE DEFAULT USB STACK
142 ------------------------------------
144 To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
145 replace "device usb" with "device oldusb" in the kernel configuration.
147 MORE ISA SUPPORT DROPPED
148 ------------------------
150 ISA support has been dropped from the following drivers: adv(4), an(4),
151 ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
152 si(4), sn(4), and stg(4).
154 +-----------------------------------------------------------------------+
155 + UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS +
156 +-----------------------------------------------------------------------+
161 Installed third-party software (dports) will have to be rebuilt after upgrade,
162 or reinstalled from binary packages.
164 UPDATING FROM 3.4 TO 3.6
165 ------------------------
167 This only applies for this specific upgrade due to locale changes; it is
168 not needed for upgrades after 3.6. Please update in this order:
177 See this mailing list post for details:
178 http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
180 CYRIX OPTIONS REMOVED
181 ---------------------
183 The following Cyrix related options have been removed: CPU_BTB_EN,
184 CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
185 CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
186 CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
188 ISA SUPPORT REMOVED FROM RP(4)
189 ------------------------------
191 ISA support has been removed from the rp(4) driver. It is now PCI only.
193 +-----------------------------------------------------------------------+
194 + UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS +
195 +-----------------------------------------------------------------------+
197 COMPAT_SUNOS OPTION REMOVED
198 ---------------------------
200 The COMPAT_SUNOS option has been removed. It was meant to provide binary
201 compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
203 ISA SOUND CARD SUPPORT REMOVED
204 ------------------------------
206 The following modules have been removed (all for ISA sound cards):
207 snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
212 DragonFly has switched base compilers. GCC 4.7 is now the default
213 compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make
214 variable ceases to work now.
216 Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
217 /etc/make.conf to prohibit GCC 4.4 from building. However, using it is
218 highly discouraged. There are a few packages in pkgsrc that do not build
219 with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At
220 this time, it is recommended to keep both compilers on the base system.
225 The SMP kernel option has been made a no-op. All kernels now feature SMP
226 support. If you have 'options SMP' in your kernel config, you can as well
229 DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
230 ---------------------------------------------------------------------------
232 The DEVICE_POLLING kernel option has been made a no-op and it has been
233 replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your
234 kernel config, you need to change it to IFPOLL_ENABLE.
236 Also, the KTR_POLLING kernel option has been removed, so it must be
237 removed from kernel configs that have it.
239 BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
240 ---------------------------------------------------
242 The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
243 cards will no longer be detected.
245 The same has been done for Stallion multiport serial controllers. stli(4)
246 has been completely removed (along with the stlload(8) and stlstty(8)
247 utilities) and stl(4) was changed to support only PCI cards. Similarly,
248 ISA support was removed from cy(4) too. All these drivers are i386 only.
250 COMPAT_OLDISA OPTION GONE
251 -------------------------
253 The i386 specific COMPAT_OLDISA kernel option has been removed, since
254 nothing needs it anymore.
256 +-----------------------------------------------------------------------+
257 + UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS +
258 +-----------------------------------------------------------------------+
260 APIC_IO OPTION REMOVED
261 ----------------------
263 The APIC_IO kernel option is no longer accepted after having been without
264 effect for a while. The hw.ioapic_enable tunable now serves its purpose.
265 If you have 'options APIC_IO' in your kernel config, you'll have to
268 WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
269 -----------------------------------------
271 The wdog framework is now compiled into our kernels by default, so the
272 options are no longer needed.
277 doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
278 NO_X make.conf option was removed too.
283 GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
284 default compiler in base (default is still GCC 4.4).
286 Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
287 NO_GCC47 in /etc/make.conf.
292 A new USB stack (from FreeBSD) has been brought in. The following
293 modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
294 usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
297 It is not yet the default. To activate it, WANT_USB4BSD=yes has to
298 be put in make.conf and device "usb4bsd" (quotes needed) has to
299 replace device usb in the kernel config. After that, a full
300 build/install/upgrade cycle is needed.
302 Note that this is experimental and incomplete, but we are interested
303 in hearing about issues with it, of course.
305 ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
306 ---------------------------------------------
308 ISA adapter support was dropped from the aic(4) driver.
310 +-----------------------------------------------------------------------+
311 + UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS +
312 +-----------------------------------------------------------------------+
314 SEVERAL ISA DRIVERS REMOVED
315 ---------------------------
317 The following ISA only drivers have been removed along with a couple of
318 associated userland tools:
334 tw(4) & xten(1) & xtend(8)
338 Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
339 config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
342 If buildkernel complains about any of these drivers, just remove them
343 from your kernel configuration.
347 Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
348 values of BINUTILSVERS are now binutils221 and binutils222 (default).
350 BUILDWORLD/-KERNEL PARALLELIZATION WORK
351 ---------------------------------------
352 Due to changes in the way we build with more than one make job, you
353 will have to update install(1) and mkdir(1) prior to buildworld if you
354 want to build with 'make -j':
356 cd /usr/src/usr.bin/xinstall; make; make install; make clean
357 cd /usr/src/bin/mkdir; make; make install; make clean
361 dma(8) has been upgraded to v0.7 which no longer supports the
362 /etc/dma/virtusertable. Some of its functionality has been replaced
363 with the MASQUERADE keyword and the EMAIL environment variable (see
364 the dma(8) manual page).
366 +-----------------------------------------------------------------------+
367 + UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS +
368 +-----------------------------------------------------------------------+
370 GCC 4.4 & BINUTILS 2.21
371 -----------------------
373 GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
374 been made DragonFly's default Binutils.
376 That means that any settings that set CCVER to 'gcc44' are not needed
377 anymore. Instead, CCVER can be set to 'gcc41' to go back to using
380 It also means that 'binutils221' as a value for BINUTILSVER has no
381 effect anymore. 2.17 has been removed and 'binutils220' is available
384 The NO_GCC44 option has been removed and will not affect the build
385 anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
386 building in a similar fashion.
388 Note that you must do a full buildworld/buildkernel for upgrading.
393 The config file for pkg_radd has moved from /etc/settings.conf to
394 /etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
395 if this is needed. This warning only applies if /etc/settings.conf
396 exists. pkg_radd will continue to work with defaults.
398 +-----------------------------------------------------------------------+
400 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
401 +-----------------------------------------------------------------------+
406 OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
407 This shouldn't break any 3rd-party software, but you'll need to recompile your
408 3rd-party software if you want it to link against the new version of OpenSSL.
413 A new loader (dloader) has been added which better handles booting from
414 multiple kernel/module versions.
416 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
422 make buildkernel KERNCONF=<KERNELNAME>
423 make installkernel KERNCONF=<KERNELNAME>
425 Note that you must installworld and run the 'upgrade' target before
426 installing the new kernel.
431 BIND has been removed from the base system. The ldns and drill tools have
432 been added for basic functionality. Use 'drill' where you would normally
433 use nslookup or dig, or install BIND from pkgsrc. It's available as
434 net/bind95, net/bind96, or net/bind97 as of this writing.
436 This only affects older systems upgrading to 2.8. New 2.8+ installs
437 include BIND as a pkgsrc package.
439 +-----------------------------------------------------------------------+
440 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
442 +-----------------------------------------------------------------------+
444 Instructions on how to obtain and maintain DragonFly source code using git
445 are in the development(7) manual page.
447 To upgrade a DragonFly system from sources you run the following sequence:
451 make buildkernel KERNCONF=<KERNELNAME>
452 make installkernel KERNCONF=<KERNELNAME>
455 You will also want to run the 'upgrade' target to upgrade your /etc and the
456 rest of your system. The upgrade target is aware of stale files created by
457 older DragonFly installations and should delete them automatically.
461 See the build(7) manual page for further information.
463 Once you've done a full build of the world and kernel you can do incremental
464 upgrades of either by using the 'quickworld' and 'quickkernel' targets
465 instead of 'buildworld' and 'buildkernel'. If you have any problems with
466 the quick targets, try updating your repo first, and then a full buildworld
467 and buildkernel as shown above, before asking for help.
469 +-----------------------------------------------------------------------+
470 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
471 +-----------------------------------------------------------------------+
473 In 2.1 kernel and modules has moved to boot directory. For most cases
474 this is handled automatically by 'make upgrade'. A few cases needs manual
477 * When installing a kernel without first doing a make buildworld,
478 installworld and upgrade to the same DESTDIR as kernel:
479 make DESTDIR/boot directory and move kernel and modules into this boot
480 directory; also move kernel.old and modules.old.
481 Typical example is vkernel(7), use (no modules used):
485 chflags noschg kernel
486 mv kernel kernel.old boot
487 chflags schg boot/kernel
489 * When using a boot-only partition, /boot/loader.rc needs to be edited:
490 delete occurrences of '/boot/'.
491 These occurences can normally be deleted in any case, see loader(8).
493 +-----------------------------------------------------------------------+
494 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
495 +-----------------------------------------------------------------------+
497 In 1.9 major changes to the disk management infrastructure have taken
498 place. make upgrade may not catch all of your disk devices in /dev,
499 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
500 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
501 and MAKEDEV no longer exists.
503 The biggest changes in 1.9 are:
505 (1) That whole-slice devices such as da0s1 no longer share the same device
506 id as partition c devices such as da0s1c.
508 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
509 with no snooping or reserved sectors. Consequently you cannot run
510 disklabel on this device. Instead you must run disklabel on a
513 (3) The 'compatibility' partitions now use slice 0 in the device name,
514 so instead of da0a you must specify da0s0a. Also, as per (1) above,
515 accessing the disklabel for the compatibility partitions must be
516 done via slice 0 (da0s0).
518 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
519 and CCD now run through the disk management layer and are assigned
520 real disk management devices. VN and CCD in particular do not usually
521 use a MBR and disklabels must be accessed through the compatibility
522 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
523 don't name it 'ccd0s0' in the config file.
525 Generally speaking, you have to get used to running fdisk and disklabel on
526 the correctly specified device names. A lot of the wiggle, such as running
527 disklabel on a partition, has been removed.
529 +-----------------------------------------------------------------------+
530 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
531 +-----------------------------------------------------------------------+
536 Kerberos IV (eBones) was removed from the tree, please consider moving to
537 Kerberos 5 (Heimdal).
539 > Package Management System
540 ---------------------------
542 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
543 management system. The necessary tools to build and maintain packages
544 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
545 directories are in your PATH variable.
547 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
548 the tarball from NetBSD:
550 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
551 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
553 This tree can then be kept up to date with cvs update:
555 cd /usr/pkgsrc; cvs up
557 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
558 build and install the pkgsrc bootstrap manually:
560 cd /usr/pkgsrc/bootstrap
561 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
563 +-----------------------------------------------------------------------+
564 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
565 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
566 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
567 +-----------------------------------------------------------------------+
569 The compatibility shims for the build environment have been removed, you
570 have to update to DragonFly 1.2 release branch first.
572 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
573 The existing configuration can be converted using /etc/pam.d/convert.sh.
574 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
575 the pam_skey.so module was retired, you have to remove it manually from
576 your configuration, when you convert it.
578 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
579 ---------------------
581 The following users may be missing from your password file. Use vipw and
582 add any that are missing:
584 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
585 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
587 The following groups may be missing from your group file. Use vi /etc/group
588 and add any that are missing:
595 > Upgrading to DragonFly from FreeBSD
596 ---------------------
598 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
599 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
600 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
601 make depend information, it starts from scratch, so no pre-cleaning of the
602 object hierarchy is necessary.
604 # get the CVS repository (it is placed in /home/dcvs, 500MB).
605 # Please use the -h option and a mirror site to pull the
606 # initial repository, but feel free to use the main repository
607 # machine to pull updates.
608 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
609 # install the source from the CVS hierarchy (remove preexisting
610 # FreeBSD src first) (500MB)
613 cvs -R -d /home/dcvs checkout -P src
615 # build it (500MB used in /usr/obj)
619 make buildkernel KERNCONF=<KERNELNAME>
621 Once you have built DragonFly you have to install it over FreeBSD. Since
622 DragonFly does not track changes made by FreeBSD to its include file
623 hierarchy and include file pollution can cause all sorts of unexpected
624 compilation issues to come up, it is best to wipe your include hierarchy
625 prior to installing DragonFly. Note that you should not wipe any installed
626 FreeBSD header files or binaries until after you have successfully completed
627 the build steps above.
631 make installkernel KERNCONF=<KERNELNAME>
634 Then you need to upgrade your system. DragonFly's 'make upgrade' target
635 will unconditionally upgrade the /etc files that sysops do not usually
636 mess around with, such as the files in /etc/rc.d. It will also remove any
637 obsolete files such as utilities and manpages that have been removed from
638 the system since the version you're coming from. If you are unsure we
639 recommend that you make a backup of at least your /etc before applying
640 this step. Note that DragonFly's RC system is basically RCNG from
641 FreeBSD-5, but there are some differences in the contents of the RC files.
645 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
646 Doing so might leave your system in an unusable state.
648 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
649 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
650 report these files to the DragonFly developers so that they can be added to
651 the 'upgrade' target.