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 5.2 TO LATER VERSIONS +
13 +-----------------------------------------------------------------------+
15 MKINITRD COMMAND REMOVED
16 ------------------------
18 The mkinitrd(8) command is removed and its functionality is replaced by
19 the new "initrd" make target. After rebooting into the new world and
20 verifying everything works, execute "make initrd" to upgrade the rescue
21 tools and initrd image.
23 IPSEC, IPSEC_ESP AND IPSEC_DEBUG REMOVED FROM VKERNEL64 CONFIG
24 --------------------------------------------------------------
26 IPsec has been removed from the system. Of our standard kernel
27 configurations, only the virtual kernel one had it. People running
28 vkernels with configuration files derived from our VKERNEL64 will
29 have to remove these options manually.
31 +-----------------------------------------------------------------------+
32 + UPGRADING DRAGONFLY FROM 5.0 TO LATER VERSIONS +
33 +-----------------------------------------------------------------------+
35 VIRTIO_PCI REMOVED FROM KERNEL CONFIG
36 -------------------------------------
38 The "device virtio_pci" line in X86_64_GENERIC has been removed. People
39 with configuration files derived from it have to remove it manually.
41 VARIOUS 'R' COMMANDS AND DAEMONS REMOVED
42 ----------------------------------------
44 rcp(1), rlogin(1), rlogind(8), rsh(1) and rshd(8) have been removed.
45 For those that still need them, there is the net/bsdrcmds port.
47 VARIOUS FORMER OPTIONS REMOVED
48 ------------------------------
50 Various former kernel configuration options which had been no-ops for
51 some time were completely removed: SYSVMSG, SYSVSEM, SYSVSHM, P1003_1B,
52 _KPOSIX_VERSION and DSCHED_FQ. Users that have any of these still in
53 their kernel configuration files have to remove them.
55 BOOTSTRAPPING LIMITED FROM PRE 4.4
56 ----------------------------------
58 Upgrading to 5.1 and later versions now require at least 4.4 in
59 preparations for upcoming base compilers updates.
61 IF_PPP, PPPD, IF_FAITH, AND FAITHD REMOVED
62 ------------------------------------------
64 if_ppp has been replaced by "user ppp", i.e. ppp(8) and tun(4). It had
65 already been removed from our default kernel configuration before 5.0,
66 so only people with custom configurations based on earlier X86_64_GENERIC
67 will have to remove it manually.
69 The faith(4) interface has been completely removed after it had also
70 been removed from our default kernel configuration.
72 +-----------------------------------------------------------------------+
73 + UPGRADING DRAGONFLY FROM 4.8 TO LATER VERSIONS +
74 +-----------------------------------------------------------------------+
76 FFS_ROOT OPTION DISABLED
77 ------------------------
79 The FFS_ROOT option has been made a no-op and will be completely removed
80 at some point in the future. Users with a custom kernel configuration
81 can remove this option from it now.
83 +-----------------------------------------------------------------------+
84 + UPGRADING DRAGONFLY FROM 4.6 TO LATER VERSIONS +
85 +-----------------------------------------------------------------------+
87 AHC, AHD, AIC, NCV, NSP AND STG DRIVERS REMOVED
88 -----------------------------------------------
90 They were all in our X86_64_GENERIC kernel configuration file, along with
91 the AHC_REG_PRETTY_PRINT and AHD_REG_PRETTY_PRINT options, so any custom
92 configuration files derived from it need adjustment.
94 PORTAL FILE SYSTEM REMOVED
95 --------------------------
97 It has been broken for a long time now.
99 BINUTILS 2.27 REPLACES 2.24, PRIMARY
100 ------------------------------------
102 The oldest of the two versions of Binutils, version 2.24, was removed
103 and replaced with Binutils 2.27. It becomes the primary version version
104 of binutils and version 2.25 becomes the alternate.
106 The accepted values of BINUTILSVER are now "binutils227" (default) and
107 "binutils225". The building of Binutils 2.25 can be prevented by setting
108 NO_ALTBINUTILS=yes in make.conf.
110 COMPAT_43 KERNEL OPTION REMOVED
111 -------------------------------
113 It was commented out in our default configs for several years now, but
114 might still be present in custom configs created before Nov. 2011.
119 OpenSSL has been removed from base and replaced with a private version of
120 LibreSSL. The previously installed OpenSSL libraries, headers, and man
121 pages will remain on the system unless the "make upgrade" command is
122 specifically instructed to remove them. To do this, define
123 REMOVE_OPENSSL_FILES for the upgrade command, e.g.
124 "make upgrade REMOVE_OPENSSL_FILES=yes"
126 28-Oct-2016: openssl has been replaced by ressl. It is recommended that any
127 stale OpenSSL files be removed to avoid configuration scripts from using
128 the stale and potentially vulnerable version, but all binaries that are
129 dynamically linked to the OpenSSL libraries should be rebuilt first to
135 It has become too cumbersome to maintain HPN patches in OpenSSH in base.
136 To use OpenSSH in base remove HPN config, if you have added it.
137 Check files below for HPN config, see a few lines below.
138 /etc/ssh/ssh_config, /etc/ssh/sshd_config, ~/.ssh/config
139 sshd(8) will fail to start if HPN config is used.
141 NOTE: HPN config in sshd_config will prohibit remote access to host using ssh.
153 OpenSSH HPN is a patch set to OpenSSH providing higher performance under some
154 circumstances, especially for networking.
155 If HPN functionality is needed, install security/openssh from dports.
157 CS, EX AND VX DRIVERS REMOVED
158 -----------------------------
160 The cs(4), ex(4) and vx(4) drivers have been removed. They were very
161 old and its doubtful they ever worked properly in x86_64 but they were
162 in X86_64_GENERIC, so custom configurations derived from it have to be
165 +-----------------------------------------------------------------------+
166 + UPGRADING DRAGONFLY FROM 4.4 TO LATER VERSIONS +
167 +-----------------------------------------------------------------------+
172 The am-utils automounter suite has been removed. It stopped working
173 at some point and was never fixed. autofs(5) and the associated
174 userland has been brought in from FreeBSD and replaces it.
179 The an(4) driver has been removed. It was in the X86_64_GENERIC kernel
180 config file, so any configurations derived from it have to be adjusted.
182 /DEV/DRI GROUP CHANGED
183 ----------------------
185 The default group assigned to /dev/dri entries has been changed
186 from 'wheel' to 'video' with the id of '44'. If you want to have
187 access to the dri devices please add yourself to the video group
190 # pw groupmod video -m $USER
192 +-----------------------------------------------------------------------+
193 + UPGRADING DRAGONFLY FROM 4.2 TO LATER VERSIONS +
194 +-----------------------------------------------------------------------+
199 dsched(4) has been removed and one of its kernel options, DSCHED_FQ, was
200 in our default kernel config file. So the DSCHED_FQ option has been turned
201 into a no-op for now and can be removed from custom configurations.
203 EST DRIVER REMOVED, COMPILE_ET AND LIBCOM_ERR TOO
204 -------------------------------------------------
206 The est(4) driver has been removed. All CPUs it supported (except one)
207 were 32 bits only. Those who are still using the Core 2 Duo T7500 should
208 report back if there are any issues with this CPU and our regular ACPI
211 Also, compile_et(1) and com_err(3) have been removed as well. They
212 should have been removed along with kerberos support, back in 2009.
214 SEVERAL LOCALES RENAMED
215 -----------------------
217 Several locales were using obsolete and misleading names, and thus have
218 been adjusted to current standards. Any users of the following locales
219 need to select alternates:
221 DFLY 4.2 locale DFLY 4.4 alterative locale
222 --------------- ------------------------------------
223 mn_MN.UTF-8 mn_Cyrl_MN.UTF-8
224 no_NO.UTF-8 nb_NO.UTF-8 or nn_NO.UTF-8
225 no_NO.ISO8859-1 nb_NO.ISO8869-1 or nn_NO.ISO8859-1
226 no_NO.ISO8859-15 nb_NO.ISO8859-15 or nn_NO.ISO8859-15
227 sr_YU.UTF-8 sr_Cyrl_RS.UTF-8 or sr_Latn_RS.UTF-8
228 sr_YU.ISO8859-5 sr_Cyrl_RS.ISO8859-5
229 sr_YU.ISO8859-2 sr_Latn_RS.ISO8859-2
230 zh_CN.GBK zh_Hans_CN.GBK
231 zh_CN.UTF-8 zh_Hans_CN.UTF-8
232 zh_CN.eucCN zh_Hans_CN.eucCN
233 zh_CN.GB2312 zh_Hans_CH.GB2312
234 zh_CN.GB18030 zh_Hans_CH.GB18030
235 zh_HK.Big5HKSCS zh_Hant_HK.Big5HKSCS
236 zh_HK.UTF_8 zh_Hant_HK.UTF-8
237 zh_TW.Big5 zh_Hant_TW.Big5
238 zh_TW.UTF-8 zh_Hant_TW.UTF-8
240 +-----------------------------------------------------------------------+
241 + UPGRADING DRAGONFLY FROM 4.0 TO LATER VERSIONS +
242 +-----------------------------------------------------------------------+
244 BINUTILS 2.25 REPLACES 2.22, PRIMARY
245 ------------------------------------
247 The oldest of the two versions of Binutils, version 2.22, was removed
248 and replaced with Binutils 2.25. It becomes the primary version version
249 of binutils and version 2.24 becomes the alternate. There are 8 current
250 CVE written against 2.24, so for security reasons version 2.25 should
253 The accepted values of BINUTILSVER are now "binutils225" (default) and
254 "binutils224". The building of Binutils 2.24 can be prevented by setting
255 NO_ALTBINUTILS=yes in make.conf.
257 LOADER OPTIONS CHANGED
258 ----------------------
260 Right after the development branch started, the Fred art accompanying the
261 loader menu was improved. The line between Fred and the menu was removed
262 by default (but can optionally be returned) and the placement shifted as
263 a result. The drawing was improved, and the colored version was improved,
264 changing the eyes and wing color from white to red. A new color version
265 of Fred was added, one with a blue scheme.
267 The loader menu defaults have changed since release 4.0: The vertical
268 line was removed, the loader is displayed in color by default*, and the
271 The loader.conf changes are:
272 loader_color: option has been removed
273 loader_plain: option has been added, it changed menu to monochrome
274 fred_is_red: changes color scheme from blue to red
275 fred_is_blue: option existed only on 4.1, it has been removed
276 fred_separated: Adds line between Fred and menu (as seen previously)
278 * If loader.conf defines "console" as "comconsole" or "console" is defined
279 in the environment as "comconsole" then color will not be displayed,
280 even if loader_plain value is "NO".
282 SENDMAIL REMOVED FROM BASE
283 --------------------------
285 The only Mail Transfer Agent provided now is DragonFly Mail Agent (dma).
286 If the system being upgraded is still configured to use the sendmail
287 binaries from base, the "make upgrade" command will fail.
289 The administrator must change /etc/mail/mailer.conf to switch the
290 mailwrapper to dma or a DPorts-based MTA prior to running the upgrade
291 command that permanently removes sendmail executables and could
292 potentially break a running mail server.
294 Refer: http://www.dragonflybsd.com/docs/docs/newhandbook/mta/ for
295 detailed instructions on how to configure the MTA selection.
297 _KPOSIX_VERSION and P1003_1B OPTIONS REMOVED
298 --------------------------------------------
300 The _KPOSIX_VERSION and P1003_1B kernel options have been changed to
301 no-ops. They can be removed from custom kernel configurations.
303 SOUND SYSTEM UPDATED FROM FreeBSD 11-CURRENT
304 --------------------------------------------
306 Many more sound devices may be detected.
308 If the default device choosen isn't to your liking, setting the sysctl
309 hw.snd.default_unit to a different number will change it.
314 Support for the SCTP protocol has been removed.
316 OLD USB DRIVERS REMOVED
317 -----------------------
319 The old USB stack, along with the kernel config option "device oldusb"
320 and the make.conf variable "WANT_OLDUSB" have been removed. This means
321 that for custom kernel configuration files which were derived from a
322 GENERIC or X86_64_GENERIC file prior to making the usb4bsd stack default,
323 various (old USB stack specific) devices will now complain about being
327 * natausb (not yet ported to usb4bsd)
328 * rue (not yet ported to usb4bsd)
329 * ugen (no longer needed in usb4bsd)
330 * urio (not yet ported to usb4bsd)
331 * uscanner (no longer needed in usb4bsd)
333 They should be removed or commented out in such custom kernel configs.
338 The GCC 4.4 compiler has been retired. It has been replaced by a GCC 5.1.
339 The following make.conf variables no longer work: NO_GCC44, NO_OBJC, and
340 NO_CXX. The latter was never documented and the latest versions of GCC are
341 partially written in C++ so a C++ compiler is no longer optional. In
342 practical terms it has not been optional for many years as other base
343 components are also written in C++. The resource savings by avoiding
344 building Objective-C compiler is so small, the complexity added by NO_OBJC
345 internally was deemed a bad tradeoff so that is the reason for its removal.
346 Also note that no "info" pages are installed with GCC 5. After this entry
347 was originally written, all info pages were removed from DragonFly.
349 GCC 5.1 has been designated as the primary compiler. As such, there is a
350 new make.conf variable, NO_ALTCOMPILER. It will block the rebuilding of
351 the designated secondary compiler, GCC 4.7. However, while DPorts
352 primarily uses GCC 5 to build ports now, it still uses GCC 4.7 as well, so
353 if building ports from source is desired, don't block building of the
356 +-----------------------------------------------------------------------+
357 + UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS +
358 +-----------------------------------------------------------------------+
360 SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
361 -------------------------------------------
363 DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
364 the default now (even on single-core systems), both for, like, 21 months.
365 We kept the options around as no-ops as a convenience, to allow people
366 using the same config for the then current release and the then current
367 master. That period is now over, so any configs still having those
368 options have to be adjusted.
370 SYSVIPC SYSCALLS MADE NON-OPTIONAL
371 ----------------------------------
373 The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
374 now compiled in by default. The options are no-ops for now.
376 DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
377 --------------------------------------------------------------------
379 The default driver for those controllers is now mrsas(4) due to reports
380 of file system corruption using the mfi(4) driver. The whole issue (and
381 how to deal with potential problems when switching) was explained here:
383 http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
385 A tunable is provided for letting those controllers still attach via
386 the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
388 OLDER NETWORK DRIVERS MOVED TO I386 ONLY
389 ----------------------------------------
391 The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
392 and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
393 removed in kernel configs derived from X86_64_GENERIC.
395 +-----------------------------------------------------------------------+
396 + UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS +
397 +-----------------------------------------------------------------------+
399 UPDATE FROM MOST RECENT 3.6
400 ---------------------------
402 Versions of 3.6 built before June 25th have a bug where installworld might
403 crash during installation of the new initrd. Upgrade to the latest version
404 of 3.6 before updating to 3.8 or later.
406 ATM, IPX, NCP AND NWFS SUPPORT DROPPED
407 --------------------------------------
409 Support for the IPX and NCP network protocols and for mouting NetWare
410 file systems has been dropped. Dito for ATM protocol support.
412 INITRD IMAGES NOW INSTALLED BY DEFAULT
413 --------------------------------------
415 An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
417 Older images installed under the file name of initrd.img will be removed
418 automatically by the make upgrade process.
420 USB4BSD IS NOW THE DEFAULT USB STACK
421 ------------------------------------
423 To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
424 replace "device usb" with "device oldusb" in the kernel configuration.
426 MORE ISA SUPPORT DROPPED
427 ------------------------
429 ISA support has been dropped from the following drivers: adv(4), an(4),
430 ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
431 si(4), sn(4), and stg(4).
433 +-----------------------------------------------------------------------+
434 + UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS +
435 +-----------------------------------------------------------------------+
440 Installed third-party software (dports) will have to be rebuilt after upgrade,
441 or reinstalled from binary packages.
443 UPDATING FROM 3.4 TO 3.6
444 ------------------------
446 This only applies for this specific upgrade due to locale changes; it is
447 not needed for upgrades after 3.6. Please update in this order:
456 See this mailing list post for details:
457 http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
459 CYRIX OPTIONS REMOVED
460 ---------------------
462 The following Cyrix related options have been removed: CPU_BTB_EN,
463 CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
464 CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
465 CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
467 ISA SUPPORT REMOVED FROM RP(4)
468 ------------------------------
470 ISA support has been removed from the rp(4) driver. It is now PCI only.
472 +-----------------------------------------------------------------------+
473 + UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS +
474 +-----------------------------------------------------------------------+
476 COMPAT_SUNOS OPTION REMOVED
477 ---------------------------
479 The COMPAT_SUNOS option has been removed. It was meant to provide binary
480 compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
482 ISA SOUND CARD SUPPORT REMOVED
483 ------------------------------
485 The following modules have been removed (all for ISA sound cards):
486 snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
491 DragonFly has switched base compilers. GCC 4.7 is now the default
492 compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make
493 variable ceases to work now.
495 Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
496 /etc/make.conf to prohibit GCC 4.4 from building. However, using it is
497 highly discouraged. There are a few packages in pkgsrc that do not build
498 with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At
499 this time, it is recommended to keep both compilers on the base system.
504 The SMP kernel option has been made a no-op. All kernels now feature SMP
505 support. If you have 'options SMP' in your kernel config, you can as well
508 DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
509 ---------------------------------------------------------------------------
511 The DEVICE_POLLING kernel option has been made a no-op and it has been
512 replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your
513 kernel config, you need to change it to IFPOLL_ENABLE.
515 Also, the KTR_POLLING kernel option has been removed, so it must be
516 removed from kernel configs that have it.
518 BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
519 ---------------------------------------------------
521 The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
522 cards will no longer be detected.
524 The same has been done for Stallion multiport serial controllers. stli(4)
525 has been completely removed (along with the stlload(8) and stlstty(8)
526 utilities) and stl(4) was changed to support only PCI cards. Similarly,
527 ISA support was removed from cy(4) too. All these drivers are i386 only.
529 COMPAT_OLDISA OPTION GONE
530 -------------------------
532 The i386 specific COMPAT_OLDISA kernel option has been removed, since
533 nothing needs it anymore.
535 +-----------------------------------------------------------------------+
536 + UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS +
537 +-----------------------------------------------------------------------+
539 APIC_IO OPTION REMOVED
540 ----------------------
542 The APIC_IO kernel option is no longer accepted after having been without
543 effect for a while. The hw.ioapic_enable tunable now serves its purpose.
544 If you have 'options APIC_IO' in your kernel config, you'll have to
547 WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
548 -----------------------------------------
550 The wdog framework is now compiled into our kernels by default, so the
551 options are no longer needed.
556 doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
557 NO_X make.conf option was removed too.
562 GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
563 default compiler in base (default is still GCC 4.4).
565 Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
566 NO_GCC47 in /etc/make.conf.
571 A new USB stack (from FreeBSD) has been brought in. The following
572 modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
573 usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
576 It is not yet the default. To activate it, WANT_USB4BSD=yes has to
577 be put in make.conf and device "usb4bsd" (quotes needed) has to
578 replace device usb in the kernel config. After that, a full
579 build/install/upgrade cycle is needed.
581 Note that this is experimental and incomplete, but we are interested
582 in hearing about issues with it, of course.
584 ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
585 ---------------------------------------------
587 ISA adapter support was dropped from the aic(4) driver.
589 +-----------------------------------------------------------------------+
590 + UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS +
591 +-----------------------------------------------------------------------+
593 SEVERAL ISA DRIVERS REMOVED
594 ---------------------------
596 The following ISA only drivers have been removed along with a couple of
597 associated userland tools:
613 tw(4) & xten(1) & xtend(8)
617 Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
618 config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
621 If buildkernel complains about any of these drivers, just remove them
622 from your kernel configuration.
626 Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
627 values of BINUTILSVERS are now binutils221 and binutils222 (default).
629 BUILDWORLD/-KERNEL PARALLELIZATION WORK
630 ---------------------------------------
631 Due to changes in the way we build with more than one make job, you
632 will have to update install(1) and mkdir(1) prior to buildworld if you
633 want to build with 'make -j':
635 cd /usr/src/usr.bin/xinstall; make; make install; make clean
636 cd /usr/src/bin/mkdir; make; make install; make clean
640 dma(8) has been upgraded to v0.7 which no longer supports the
641 /etc/dma/virtusertable. Some of its functionality has been replaced
642 with the MASQUERADE keyword and the EMAIL environment variable (see
643 the dma(8) manual page).
645 +-----------------------------------------------------------------------+
646 + UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS +
647 +-----------------------------------------------------------------------+
649 GCC 4.4 & BINUTILS 2.21
650 -----------------------
652 GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
653 been made DragonFly's default Binutils.
655 That means that any settings that set CCVER to 'gcc44' are not needed
656 anymore. Instead, CCVER can be set to 'gcc41' to go back to using
659 It also means that 'binutils221' as a value for BINUTILSVER has no
660 effect anymore. 2.17 has been removed and 'binutils220' is available
663 The NO_GCC44 option has been removed and will not affect the build
664 anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
665 building in a similar fashion.
667 Note that you must do a full buildworld/buildkernel for upgrading.
672 The config file for pkg_radd has moved from /etc/settings.conf to
673 /etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
674 if this is needed. This warning only applies if /etc/settings.conf
675 exists. pkg_radd will continue to work with defaults.
677 +-----------------------------------------------------------------------+
679 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
680 +-----------------------------------------------------------------------+
685 OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
686 This shouldn't break any 3rd-party software, but you'll need to recompile your
687 3rd-party software if you want it to link against the new version of OpenSSL.
692 A new loader (dloader) has been added which better handles booting from
693 multiple kernel/module versions.
695 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
701 make buildkernel KERNCONF=<KERNELNAME>
702 make installkernel KERNCONF=<KERNELNAME>
704 Note that you must installworld and run the 'upgrade' target before
705 installing the new kernel.
710 BIND has been removed from the base system. The ldns and drill tools have
711 been added for basic functionality. Use 'drill' where you would normally
712 use nslookup or dig, or install BIND from pkgsrc. It's available as
713 net/bind95, net/bind96, or net/bind97 as of this writing.
715 This only affects older systems upgrading to 2.8. New 2.8+ installs
716 include BIND as a pkgsrc package.
718 +-----------------------------------------------------------------------+
719 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
721 +-----------------------------------------------------------------------+
723 Instructions on how to obtain and maintain DragonFly source code using git
724 are in the development(7) manual page.
726 To upgrade a DragonFly system from sources you run the following sequence:
730 make buildkernel KERNCONF=<KERNELNAME>
731 make installkernel KERNCONF=<KERNELNAME>
734 You will also want to run the 'upgrade' target to upgrade your /etc and the
735 rest of your system. The upgrade target is aware of stale files created by
736 older DragonFly installations and should delete them automatically.
740 See the build(7) manual page for further information.
742 Once you've done a full build of the world and kernel you can do incremental
743 upgrades of either by using the 'quickworld' and 'quickkernel' targets
744 instead of 'buildworld' and 'buildkernel'. If you have any problems with
745 the quick targets, try updating your repo first, and then a full buildworld
746 and buildkernel as shown above, before asking for help.
748 +-----------------------------------------------------------------------+
749 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
750 +-----------------------------------------------------------------------+
752 In 2.1 kernel and modules has moved to boot directory. For most cases
753 this is handled automatically by 'make upgrade'. A few cases needs manual
756 * When installing a kernel without first doing a make buildworld,
757 installworld and upgrade to the same DESTDIR as kernel:
758 make DESTDIR/boot directory and move kernel and modules into this boot
759 directory; also move kernel.old and modules.old.
760 Typical example is vkernel(7), use (no modules used):
764 chflags noschg kernel
765 mv kernel kernel.old boot
766 chflags schg boot/kernel
768 * When using a boot-only partition, /boot/loader.rc needs to be edited:
769 delete occurrences of '/boot/'.
770 These occurences can normally be deleted in any case, see loader(8).
772 +-----------------------------------------------------------------------+
773 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
774 +-----------------------------------------------------------------------+
776 In 1.9 major changes to the disk management infrastructure have taken
777 place. make upgrade may not catch all of your disk devices in /dev,
778 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
779 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
780 and MAKEDEV no longer exists.
782 The biggest changes in 1.9 are:
784 (1) That whole-slice devices such as da0s1 no longer share the same device
785 id as partition c devices such as da0s1c.
787 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
788 with no snooping or reserved sectors. Consequently you cannot run
789 disklabel on this device. Instead you must run disklabel on a
792 (3) The 'compatibility' partitions now use slice 0 in the device name,
793 so instead of da0a you must specify da0s0a. Also, as per (1) above,
794 accessing the disklabel for the compatibility partitions must be
795 done via slice 0 (da0s0).
797 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
798 and CCD now run through the disk management layer and are assigned
799 real disk management devices. VN and CCD in particular do not usually
800 use a MBR and disklabels must be accessed through the compatibility
801 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
802 don't name it 'ccd0s0' in the config file.
804 Generally speaking, you have to get used to running fdisk and disklabel on
805 the correctly specified device names. A lot of the wiggle, such as running
806 disklabel on a partition, has been removed.
808 +-----------------------------------------------------------------------+
809 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
810 +-----------------------------------------------------------------------+
815 Kerberos IV (eBones) was removed from the tree, please consider moving to
816 Kerberos 5 (Heimdal).
818 > Package Management System
819 ---------------------------
821 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
822 management system. The necessary tools to build and maintain packages
823 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
824 directories are in your PATH variable.
826 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
827 the tarball from NetBSD:
829 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
830 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
832 This tree can then be kept up to date with cvs update:
834 cd /usr/pkgsrc; cvs up
836 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
837 build and install the pkgsrc bootstrap manually:
839 cd /usr/pkgsrc/bootstrap
840 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
842 +-----------------------------------------------------------------------+
843 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
844 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
845 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
846 +-----------------------------------------------------------------------+
848 The compatibility shims for the build environment have been removed, you
849 have to update to DragonFly 1.2 release branch first.
851 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
852 The existing configuration can be converted using /etc/pam.d/convert.sh.
853 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
854 the pam_skey.so module was retired, you have to remove it manually from
855 your configuration, when you convert it.
857 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
858 ---------------------
860 The following users may be missing from your password file. Use vipw and
861 add any that are missing:
863 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
864 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
866 The following groups may be missing from your group file. Use vi /etc/group
867 and add any that are missing:
874 > Upgrading to DragonFly from FreeBSD
875 ---------------------
877 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
878 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
879 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
880 make depend information, it starts from scratch, so no pre-cleaning of the
881 object hierarchy is necessary.
883 # get the CVS repository (it is placed in /home/dcvs, 500MB).
884 # Please use the -h option and a mirror site to pull the
885 # initial repository, but feel free to use the main repository
886 # machine to pull updates.
887 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
888 # install the source from the CVS hierarchy (remove preexisting
889 # FreeBSD src first) (500MB)
892 cvs -R -d /home/dcvs checkout -P src
894 # build it (500MB used in /usr/obj)
898 make buildkernel KERNCONF=<KERNELNAME>
900 Once you have built DragonFly you have to install it over FreeBSD. Since
901 DragonFly does not track changes made by FreeBSD to its include file
902 hierarchy and include file pollution can cause all sorts of unexpected
903 compilation issues to come up, it is best to wipe your include hierarchy
904 prior to installing DragonFly. Note that you should not wipe any installed
905 FreeBSD header files or binaries until after you have successfully completed
906 the build steps above.
910 make installkernel KERNCONF=<KERNELNAME>
913 Then you need to upgrade your system. DragonFly's 'make upgrade' target
914 will unconditionally upgrade the /etc files that sysops do not usually
915 mess around with, such as the files in /etc/rc.d. It will also remove any
916 obsolete files such as utilities and manpages that have been removed from
917 the system since the version you're coming from. If you are unsure we
918 recommend that you make a backup of at least your /etc before applying
919 this step. Note that DragonFly's RC system is basically RCNG from
920 FreeBSD-5, but there are some differences in the contents of the RC files.
924 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
925 Doing so might leave your system in an unusable state.
927 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
928 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
929 report these files to the DragonFly developers so that they can be added to
930 the 'upgrade' target.