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 LOADER OPTIONS CHANGED
16 ----------------------
18 Right after the development branch started, the Fred art accompanying the
19 loader menu was improved. The line between Fred and the menu was removed
20 by default (but can optionally be returned) and the placement shifted as
21 a result. The drawing was improved, and the colored version was improved,
22 changing the eyes and wing color from white to red. A new color version
23 of Fred was added, one with a blue scheme.
25 The loader menu defaults have changed since release 4.0: The vertical
26 line was removed, the loader is displayed in color by default*, and the
29 The loader.conf changes are:
30 loader_color: option has been removed
31 loader_plain: option has been added, it changed menu to monochrome
32 fred_is_red: changes color scheme from blue to red
33 fred_is_blue: option existed only on 4.1, it has been removed
34 fred_separated: Adds line between Fred and menu (as seen previously)
36 * If loader.conf defines "console" as "comconsole" or "console" is defined
37 in the environment as "comconsole" then color will not be displayed,
38 even if loader_plain value is "NO".
40 SENDMAIL REMOVED FROM BASE
41 --------------------------
43 The only Mail Transfer Agent provided now is DragonFly Mail Agent (dma).
44 If the system being upgraded is still configured to use the sendmail
45 binaries from base, the "make upgrade" command will fail.
47 The administrator must change /etc/mail/mailer.conf to switch the
48 mailwrapper to dma or a DPorts-based MTA prior to running the upgrade
49 command that permanently removes sendmail executables and could
50 potentially break a running mail server.
52 Refer: http://www.dragonflybsd.com/docs/docs/newhandbook/mta/ for
53 detailed instructions on how to configure the MTA selection.
55 _KPOSIX_VERSION and P1003_1B OPTIONS REMOVED
56 --------------------------------------------
58 The _KPOSIX_VERSION and P1003_1B kernel options have been changed to
59 no-ops. They can be removed from custom kernel configurations.
61 SOUND SYSTEM UPDATED FROM FreeBSD 11-CURRENT
62 --------------------------------------------
64 Many more sound devices may be detected.
66 If the default device choosen isn't to your liking, setting the sysctl
67 hw.snd.default_unit to a different number will change it.
72 Support for the SCTP protocol has been removed.
74 OLD USB DRIVERS REMOVED
75 -----------------------
77 The old USB stack, along with the kernel config option "device oldusb"
78 and the make.conf variable "WANT_OLDUSB" have been removed. This means
79 that for custom kernel configuration files which were derived from a
80 GENERIC or X86_64_GENERIC file prior to making the usb4bsd stack default,
81 various (old USB stack specific) devices will now complain about being
85 * natausb (not yet ported to usb4bsd)
86 * rue (not yet ported to usb4bsd)
87 * ugen (no longer needed in usb4bsd)
88 * urio (not yet ported to usb4bsd)
89 * uscanner (no longer needed in usb4bsd)
91 They should be removed or commented out in such custom kernel configs.
96 The GCC 4.4 compiler has been retired. It has been replaced by a
97 [prerelease] version of GCC 5.0. The following make.conf variables no
98 longer work: NO_GCC44, NO_OBJC, and NO_CXX. The latter was never
99 documented and the latest versions of GCC are partially written in C++
100 so a C++ compiler is no longer optional. In practical terms it has not
101 been optional for many years as other base components are also written in
102 C++. The resource savings by avoiding building Objective-C compiler is
103 so small, the complexity added by NO_OBJC internally was deemed a bad
104 tradeoff so that is the reason for its removal. Also note that no "info"
105 pages are installed with GCC 5.0. This is intentional; they are available
106 via the internet if desired over the installed man pages.
108 Currently, GCC 4.7 is still designated as the primary compiler. After
109 GCC 5.0 is released, this may change and these update notes will be
110 revised accordingly. DPorts will use GCC 5.0 on this release regardless.
111 If GCC 5.0 is unwanted, the make.conf variable NO_GCC50 will block its
112 building and installation.
114 To use GCC 5.0 to build world and kernel, set WORLD_CCVER=gcc50 in
115 make.conf before building those targets.
117 +-----------------------------------------------------------------------+
118 + UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS +
119 +-----------------------------------------------------------------------+
121 SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
122 -------------------------------------------
124 DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
125 the default now (even on single-core systems), both for, like, 21 months.
126 We kept the options around as no-ops as a convenience, to allow people
127 using the same config for the then current release and the then current
128 master. That period is now over, so any configs still having those
129 options have to be adjusted.
131 SYSVIPC SYSCALLS MADE NON-OPTIONAL
132 ----------------------------------
134 The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
135 now compiled in by default. The options are no-ops for now.
137 DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
138 --------------------------------------------------------------------
140 The default driver for those controllers is now mrsas(4) due to reports
141 of file system corruption using the mfi(4) driver. The whole issue (and
142 how to deal with potential problems when switching) was explained here:
144 http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
146 A tunable is provided for letting those controllers still attach via
147 the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
149 OLDER NETWORK DRIVERS MOVED TO I386 ONLY
150 ----------------------------------------
152 The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
153 and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
154 removed in kernel configs derived from X86_64_GENERIC.
156 +-----------------------------------------------------------------------+
157 + UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS +
158 +-----------------------------------------------------------------------+
160 UPDATE FROM MOST RECENT 3.6
161 ---------------------------
163 Versions of 3.6 built before June 25th have a bug where installworld might
164 crash during installation of the new initrd. Upgrade to the latest version
165 of 3.6 before updating to 3.8 or later.
167 ATM, IPX, NCP AND NWFS SUPPORT DROPPED
168 --------------------------------------
170 Support for the IPX and NCP network protocols and for mouting NetWare
171 file systems has been dropped. Dito for ATM protocol support.
173 INITRD IMAGES NOW INSTALLED BY DEFAULT
174 --------------------------------------
176 An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
178 Older images installed under the file name of initrd.img will be removed
179 automatically by the make upgrade process.
181 USB4BSD IS NOW THE DEFAULT USB STACK
182 ------------------------------------
184 To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
185 replace "device usb" with "device oldusb" in the kernel configuration.
187 MORE ISA SUPPORT DROPPED
188 ------------------------
190 ISA support has been dropped from the following drivers: adv(4), an(4),
191 ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
192 si(4), sn(4), and stg(4).
194 +-----------------------------------------------------------------------+
195 + UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS +
196 +-----------------------------------------------------------------------+
201 Installed third-party software (dports) will have to be rebuilt after upgrade,
202 or reinstalled from binary packages.
204 UPDATING FROM 3.4 TO 3.6
205 ------------------------
207 This only applies for this specific upgrade due to locale changes; it is
208 not needed for upgrades after 3.6. Please update in this order:
217 See this mailing list post for details:
218 http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
220 CYRIX OPTIONS REMOVED
221 ---------------------
223 The following Cyrix related options have been removed: CPU_BTB_EN,
224 CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
225 CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
226 CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
228 ISA SUPPORT REMOVED FROM RP(4)
229 ------------------------------
231 ISA support has been removed from the rp(4) driver. It is now PCI only.
233 +-----------------------------------------------------------------------+
234 + UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS +
235 +-----------------------------------------------------------------------+
237 COMPAT_SUNOS OPTION REMOVED
238 ---------------------------
240 The COMPAT_SUNOS option has been removed. It was meant to provide binary
241 compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
243 ISA SOUND CARD SUPPORT REMOVED
244 ------------------------------
246 The following modules have been removed (all for ISA sound cards):
247 snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
252 DragonFly has switched base compilers. GCC 4.7 is now the default
253 compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make
254 variable ceases to work now.
256 Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
257 /etc/make.conf to prohibit GCC 4.4 from building. However, using it is
258 highly discouraged. There are a few packages in pkgsrc that do not build
259 with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At
260 this time, it is recommended to keep both compilers on the base system.
265 The SMP kernel option has been made a no-op. All kernels now feature SMP
266 support. If you have 'options SMP' in your kernel config, you can as well
269 DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
270 ---------------------------------------------------------------------------
272 The DEVICE_POLLING kernel option has been made a no-op and it has been
273 replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your
274 kernel config, you need to change it to IFPOLL_ENABLE.
276 Also, the KTR_POLLING kernel option has been removed, so it must be
277 removed from kernel configs that have it.
279 BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
280 ---------------------------------------------------
282 The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
283 cards will no longer be detected.
285 The same has been done for Stallion multiport serial controllers. stli(4)
286 has been completely removed (along with the stlload(8) and stlstty(8)
287 utilities) and stl(4) was changed to support only PCI cards. Similarly,
288 ISA support was removed from cy(4) too. All these drivers are i386 only.
290 COMPAT_OLDISA OPTION GONE
291 -------------------------
293 The i386 specific COMPAT_OLDISA kernel option has been removed, since
294 nothing needs it anymore.
296 +-----------------------------------------------------------------------+
297 + UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS +
298 +-----------------------------------------------------------------------+
300 APIC_IO OPTION REMOVED
301 ----------------------
303 The APIC_IO kernel option is no longer accepted after having been without
304 effect for a while. The hw.ioapic_enable tunable now serves its purpose.
305 If you have 'options APIC_IO' in your kernel config, you'll have to
308 WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
309 -----------------------------------------
311 The wdog framework is now compiled into our kernels by default, so the
312 options are no longer needed.
317 doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
318 NO_X make.conf option was removed too.
323 GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
324 default compiler in base (default is still GCC 4.4).
326 Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
327 NO_GCC47 in /etc/make.conf.
332 A new USB stack (from FreeBSD) has been brought in. The following
333 modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
334 usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
337 It is not yet the default. To activate it, WANT_USB4BSD=yes has to
338 be put in make.conf and device "usb4bsd" (quotes needed) has to
339 replace device usb in the kernel config. After that, a full
340 build/install/upgrade cycle is needed.
342 Note that this is experimental and incomplete, but we are interested
343 in hearing about issues with it, of course.
345 ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
346 ---------------------------------------------
348 ISA adapter support was dropped from the aic(4) driver.
350 +-----------------------------------------------------------------------+
351 + UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS +
352 +-----------------------------------------------------------------------+
354 SEVERAL ISA DRIVERS REMOVED
355 ---------------------------
357 The following ISA only drivers have been removed along with a couple of
358 associated userland tools:
374 tw(4) & xten(1) & xtend(8)
378 Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
379 config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
382 If buildkernel complains about any of these drivers, just remove them
383 from your kernel configuration.
387 Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
388 values of BINUTILSVERS are now binutils221 and binutils222 (default).
390 BUILDWORLD/-KERNEL PARALLELIZATION WORK
391 ---------------------------------------
392 Due to changes in the way we build with more than one make job, you
393 will have to update install(1) and mkdir(1) prior to buildworld if you
394 want to build with 'make -j':
396 cd /usr/src/usr.bin/xinstall; make; make install; make clean
397 cd /usr/src/bin/mkdir; make; make install; make clean
401 dma(8) has been upgraded to v0.7 which no longer supports the
402 /etc/dma/virtusertable. Some of its functionality has been replaced
403 with the MASQUERADE keyword and the EMAIL environment variable (see
404 the dma(8) manual page).
406 +-----------------------------------------------------------------------+
407 + UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS +
408 +-----------------------------------------------------------------------+
410 GCC 4.4 & BINUTILS 2.21
411 -----------------------
413 GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
414 been made DragonFly's default Binutils.
416 That means that any settings that set CCVER to 'gcc44' are not needed
417 anymore. Instead, CCVER can be set to 'gcc41' to go back to using
420 It also means that 'binutils221' as a value for BINUTILSVER has no
421 effect anymore. 2.17 has been removed and 'binutils220' is available
424 The NO_GCC44 option has been removed and will not affect the build
425 anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
426 building in a similar fashion.
428 Note that you must do a full buildworld/buildkernel for upgrading.
433 The config file for pkg_radd has moved from /etc/settings.conf to
434 /etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
435 if this is needed. This warning only applies if /etc/settings.conf
436 exists. pkg_radd will continue to work with defaults.
438 +-----------------------------------------------------------------------+
440 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
441 +-----------------------------------------------------------------------+
446 OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
447 This shouldn't break any 3rd-party software, but you'll need to recompile your
448 3rd-party software if you want it to link against the new version of OpenSSL.
453 A new loader (dloader) has been added which better handles booting from
454 multiple kernel/module versions.
456 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
462 make buildkernel KERNCONF=<KERNELNAME>
463 make installkernel KERNCONF=<KERNELNAME>
465 Note that you must installworld and run the 'upgrade' target before
466 installing the new kernel.
471 BIND has been removed from the base system. The ldns and drill tools have
472 been added for basic functionality. Use 'drill' where you would normally
473 use nslookup or dig, or install BIND from pkgsrc. It's available as
474 net/bind95, net/bind96, or net/bind97 as of this writing.
476 This only affects older systems upgrading to 2.8. New 2.8+ installs
477 include BIND as a pkgsrc package.
479 +-----------------------------------------------------------------------+
480 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
482 +-----------------------------------------------------------------------+
484 Instructions on how to obtain and maintain DragonFly source code using git
485 are in the development(7) manual page.
487 To upgrade a DragonFly system from sources you run the following sequence:
491 make buildkernel KERNCONF=<KERNELNAME>
492 make installkernel KERNCONF=<KERNELNAME>
495 You will also want to run the 'upgrade' target to upgrade your /etc and the
496 rest of your system. The upgrade target is aware of stale files created by
497 older DragonFly installations and should delete them automatically.
501 See the build(7) manual page for further information.
503 Once you've done a full build of the world and kernel you can do incremental
504 upgrades of either by using the 'quickworld' and 'quickkernel' targets
505 instead of 'buildworld' and 'buildkernel'. If you have any problems with
506 the quick targets, try updating your repo first, and then a full buildworld
507 and buildkernel as shown above, before asking for help.
509 +-----------------------------------------------------------------------+
510 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
511 +-----------------------------------------------------------------------+
513 In 2.1 kernel and modules has moved to boot directory. For most cases
514 this is handled automatically by 'make upgrade'. A few cases needs manual
517 * When installing a kernel without first doing a make buildworld,
518 installworld and upgrade to the same DESTDIR as kernel:
519 make DESTDIR/boot directory and move kernel and modules into this boot
520 directory; also move kernel.old and modules.old.
521 Typical example is vkernel(7), use (no modules used):
525 chflags noschg kernel
526 mv kernel kernel.old boot
527 chflags schg boot/kernel
529 * When using a boot-only partition, /boot/loader.rc needs to be edited:
530 delete occurrences of '/boot/'.
531 These occurences can normally be deleted in any case, see loader(8).
533 +-----------------------------------------------------------------------+
534 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
535 +-----------------------------------------------------------------------+
537 In 1.9 major changes to the disk management infrastructure have taken
538 place. make upgrade may not catch all of your disk devices in /dev,
539 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
540 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
541 and MAKEDEV no longer exists.
543 The biggest changes in 1.9 are:
545 (1) That whole-slice devices such as da0s1 no longer share the same device
546 id as partition c devices such as da0s1c.
548 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
549 with no snooping or reserved sectors. Consequently you cannot run
550 disklabel on this device. Instead you must run disklabel on a
553 (3) The 'compatibility' partitions now use slice 0 in the device name,
554 so instead of da0a you must specify da0s0a. Also, as per (1) above,
555 accessing the disklabel for the compatibility partitions must be
556 done via slice 0 (da0s0).
558 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
559 and CCD now run through the disk management layer and are assigned
560 real disk management devices. VN and CCD in particular do not usually
561 use a MBR and disklabels must be accessed through the compatibility
562 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
563 don't name it 'ccd0s0' in the config file.
565 Generally speaking, you have to get used to running fdisk and disklabel on
566 the correctly specified device names. A lot of the wiggle, such as running
567 disklabel on a partition, has been removed.
569 +-----------------------------------------------------------------------+
570 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
571 +-----------------------------------------------------------------------+
576 Kerberos IV (eBones) was removed from the tree, please consider moving to
577 Kerberos 5 (Heimdal).
579 > Package Management System
580 ---------------------------
582 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
583 management system. The necessary tools to build and maintain packages
584 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
585 directories are in your PATH variable.
587 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
588 the tarball from NetBSD:
590 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
591 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
593 This tree can then be kept up to date with cvs update:
595 cd /usr/pkgsrc; cvs up
597 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
598 build and install the pkgsrc bootstrap manually:
600 cd /usr/pkgsrc/bootstrap
601 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
603 +-----------------------------------------------------------------------+
604 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
605 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
606 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
607 +-----------------------------------------------------------------------+
609 The compatibility shims for the build environment have been removed, you
610 have to update to DragonFly 1.2 release branch first.
612 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
613 The existing configuration can be converted using /etc/pam.d/convert.sh.
614 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
615 the pam_skey.so module was retired, you have to remove it manually from
616 your configuration, when you convert it.
618 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
619 ---------------------
621 The following users may be missing from your password file. Use vipw and
622 add any that are missing:
624 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
625 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
627 The following groups may be missing from your group file. Use vi /etc/group
628 and add any that are missing:
635 > Upgrading to DragonFly from FreeBSD
636 ---------------------
638 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
639 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
640 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
641 make depend information, it starts from scratch, so no pre-cleaning of the
642 object hierarchy is necessary.
644 # get the CVS repository (it is placed in /home/dcvs, 500MB).
645 # Please use the -h option and a mirror site to pull the
646 # initial repository, but feel free to use the main repository
647 # machine to pull updates.
648 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
649 # install the source from the CVS hierarchy (remove preexisting
650 # FreeBSD src first) (500MB)
653 cvs -R -d /home/dcvs checkout -P src
655 # build it (500MB used in /usr/obj)
659 make buildkernel KERNCONF=<KERNELNAME>
661 Once you have built DragonFly you have to install it over FreeBSD. Since
662 DragonFly does not track changes made by FreeBSD to its include file
663 hierarchy and include file pollution can cause all sorts of unexpected
664 compilation issues to come up, it is best to wipe your include hierarchy
665 prior to installing DragonFly. Note that you should not wipe any installed
666 FreeBSD header files or binaries until after you have successfully completed
667 the build steps above.
671 make installkernel KERNCONF=<KERNELNAME>
674 Then you need to upgrade your system. DragonFly's 'make upgrade' target
675 will unconditionally upgrade the /etc files that sysops do not usually
676 mess around with, such as the files in /etc/rc.d. It will also remove any
677 obsolete files such as utilities and manpages that have been removed from
678 the system since the version you're coming from. If you are unsure we
679 recommend that you make a backup of at least your /etc before applying
680 this step. Note that DragonFly's RC system is basically RCNG from
681 FreeBSD-5, but there are some differences in the contents of the RC files.
685 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
686 Doing so might leave your system in an unusable state.
688 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
689 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
690 report these files to the DragonFly developers so that they can be added to
691 the 'upgrade' target.