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.6 TO LATER VERSIONS +
13 +-----------------------------------------------------------------------+
18 The cs(4) driver has been removed. It's old and seems to be i386
19 specific, but it was in X86_64_GENERIC, so custom configurations
20 derived from it have to be adjusted.
22 +-----------------------------------------------------------------------+
23 + UPGRADING DRAGONFLY FROM 4.4 TO LATER VERSIONS +
24 +-----------------------------------------------------------------------+
29 The am-utils automounter suite has been removed. It stopped working
30 at some point and was never fixed. autofs(5) and the associated
31 userland has been brought in from FreeBSD and replaces it.
36 The an(4) driver has been removed. It was in the X86_64_GENERIC kernel
37 config file, so any configurations derived from it have to be adjusted.
39 /DEV/DRI GROUP CHANGED
40 ----------------------
42 The default group assigned to /dev/dri entries has been changed
43 from 'wheel' to 'video' with the id of '44'. If you want to have
44 access to the dri devices please add yourself to the video group
47 # pw groupmod video -m $USER
49 +-----------------------------------------------------------------------+
50 + UPGRADING DRAGONFLY FROM 4.2 TO LATER VERSIONS +
51 +-----------------------------------------------------------------------+
56 dsched(4) has been removed and one of its kernel options, DSCHED_FQ, was
57 in our default kernel config file. So the DSCHED_FQ option has been turned
58 into a no-op for now and can be removed from custom configurations.
60 EST DRIVER REMOVED, COMPILE_ET AND LIBCOM_ERR TOO
61 -------------------------------------------------
63 The est(4) driver has been removed. All CPUs it supported (except one)
64 were 32 bits only. Those who are still using the Core 2 Duo T7500 should
65 report back if there are any issues with this CPU and our regular ACPI
68 Also, compile_et(1) and com_err(3) have been removed as well. They
69 should have been removed along with kerberos support, back in 2009.
71 SEVERAL LOCALES RENAMED
72 -----------------------
74 Several locales were using obsolete and misleading names, and thus have
75 been adjusted to current standards. Any users of the following locales
76 need to select alternates:
78 DFLY 4.2 locale DFLY 4.4 alterative locale
79 --------------- ------------------------------------
80 mn_MN.UTF-8 mn_Cyrl_MN.UTF-8
81 no_NO.UTF-8 nb_NO.UTF-8 or nn_NO.UTF-8
82 no_NO.ISO8859-1 nb_NO.ISO8869-1 or nn_NO.ISO8859-1
83 no_NO.ISO8859-15 nb_NO.ISO8859-15 or nn_NO.ISO8859-15
84 sr_YU.UTF-8 sr_Cyrl_RS.UTF-8 or sr_Latn_RS.UTF-8
85 sr_YU.ISO8859-5 sr_Cyrl_RS.ISO8859-5
86 sr_YU.ISO8859-2 sr_Latn_RS.ISO8859-2
87 zh_CN.GBK zh_Hans_CN.GBK
88 zh_CN.UTF-8 zh_Hans_CN.UTF-8
89 zh_CN.eucCN zh_Hans_CN.eucCN
90 zh_CN.GB2312 zh_Hans_CH.GB2312
91 zh_CN.GB18030 zh_Hans_CH.GB18030
92 zh_HK.Big5HKSCS zh_Hant_HK.Big5HKSCS
93 zh_HK.UTF_8 zh_Hant_HK.UTF-8
94 zh_TW.Big5 zh_Hant_TW.Big5
95 zh_TW.UTF-8 zh_Hant_TW.UTF-8
97 +-----------------------------------------------------------------------+
98 + UPGRADING DRAGONFLY FROM 4.0 TO LATER VERSIONS +
99 +-----------------------------------------------------------------------+
101 BINUTILS 2.25 REPLACES 2.22, PRIMARY
102 ------------------------------------
104 The oldest of the two versions of Binutils, version 2.22, was removed
105 and replaced with Binutils 2.25. It becomes the primary version version
106 of binutils and version 2.24 becomes the alternate. There are 8 current
107 CVE written against 2.24, so for security reasons version 2.25 should
110 The accepted values of BINUTILSVER are now "binutils225" (default) and
111 "binutils224". The building of Binutils 2.24 can be prevented by setting
112 NO_ALTBINUTILS=yes in make.conf.
114 LOADER OPTIONS CHANGED
115 ----------------------
117 Right after the development branch started, the Fred art accompanying the
118 loader menu was improved. The line between Fred and the menu was removed
119 by default (but can optionally be returned) and the placement shifted as
120 a result. The drawing was improved, and the colored version was improved,
121 changing the eyes and wing color from white to red. A new color version
122 of Fred was added, one with a blue scheme.
124 The loader menu defaults have changed since release 4.0: The vertical
125 line was removed, the loader is displayed in color by default*, and the
128 The loader.conf changes are:
129 loader_color: option has been removed
130 loader_plain: option has been added, it changed menu to monochrome
131 fred_is_red: changes color scheme from blue to red
132 fred_is_blue: option existed only on 4.1, it has been removed
133 fred_separated: Adds line between Fred and menu (as seen previously)
135 * If loader.conf defines "console" as "comconsole" or "console" is defined
136 in the environment as "comconsole" then color will not be displayed,
137 even if loader_plain value is "NO".
139 SENDMAIL REMOVED FROM BASE
140 --------------------------
142 The only Mail Transfer Agent provided now is DragonFly Mail Agent (dma).
143 If the system being upgraded is still configured to use the sendmail
144 binaries from base, the "make upgrade" command will fail.
146 The administrator must change /etc/mail/mailer.conf to switch the
147 mailwrapper to dma or a DPorts-based MTA prior to running the upgrade
148 command that permanently removes sendmail executables and could
149 potentially break a running mail server.
151 Refer: http://www.dragonflybsd.com/docs/docs/newhandbook/mta/ for
152 detailed instructions on how to configure the MTA selection.
154 _KPOSIX_VERSION and P1003_1B OPTIONS REMOVED
155 --------------------------------------------
157 The _KPOSIX_VERSION and P1003_1B kernel options have been changed to
158 no-ops. They can be removed from custom kernel configurations.
160 SOUND SYSTEM UPDATED FROM FreeBSD 11-CURRENT
161 --------------------------------------------
163 Many more sound devices may be detected.
165 If the default device choosen isn't to your liking, setting the sysctl
166 hw.snd.default_unit to a different number will change it.
171 Support for the SCTP protocol has been removed.
173 OLD USB DRIVERS REMOVED
174 -----------------------
176 The old USB stack, along with the kernel config option "device oldusb"
177 and the make.conf variable "WANT_OLDUSB" have been removed. This means
178 that for custom kernel configuration files which were derived from a
179 GENERIC or X86_64_GENERIC file prior to making the usb4bsd stack default,
180 various (old USB stack specific) devices will now complain about being
184 * natausb (not yet ported to usb4bsd)
185 * rue (not yet ported to usb4bsd)
186 * ugen (no longer needed in usb4bsd)
187 * urio (not yet ported to usb4bsd)
188 * uscanner (no longer needed in usb4bsd)
190 They should be removed or commented out in such custom kernel configs.
195 The GCC 4.4 compiler has been retired. It has been replaced by a GCC 5.1.
196 The following make.conf variables no longer work: NO_GCC44, NO_OBJC, and
197 NO_CXX. The latter was never documented and the latest versions of GCC are
198 partially written in C++ so a C++ compiler is no longer optional. In
199 practical terms it has not been optional for many years as other base
200 components are also written in C++. The resource savings by avoiding
201 building Objective-C compiler is so small, the complexity added by NO_OBJC
202 internally was deemed a bad tradeoff so that is the reason for its removal.
203 Also note that no "info" pages are installed with GCC 5. After this entry
204 was originally written, all info pages were removed from DragonFly.
206 GCC 5.1 has been designated as the primary compiler. As such, there is a
207 new make.conf variable, NO_ALTCOMPILER. It will block the rebuilding of
208 the designated secondary compiler, GCC 4.7. However, while DPorts
209 primarily uses GCC 5 to build ports now, it still uses GCC 4.7 as well, so
210 if building ports from source is desired, don't block building of the
213 +-----------------------------------------------------------------------+
214 + UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS +
215 +-----------------------------------------------------------------------+
217 SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
218 -------------------------------------------
220 DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
221 the default now (even on single-core systems), both for, like, 21 months.
222 We kept the options around as no-ops as a convenience, to allow people
223 using the same config for the then current release and the then current
224 master. That period is now over, so any configs still having those
225 options have to be adjusted.
227 SYSVIPC SYSCALLS MADE NON-OPTIONAL
228 ----------------------------------
230 The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
231 now compiled in by default. The options are no-ops for now.
233 DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
234 --------------------------------------------------------------------
236 The default driver for those controllers is now mrsas(4) due to reports
237 of file system corruption using the mfi(4) driver. The whole issue (and
238 how to deal with potential problems when switching) was explained here:
240 http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
242 A tunable is provided for letting those controllers still attach via
243 the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
245 OLDER NETWORK DRIVERS MOVED TO I386 ONLY
246 ----------------------------------------
248 The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
249 and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
250 removed in kernel configs derived from X86_64_GENERIC.
252 +-----------------------------------------------------------------------+
253 + UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS +
254 +-----------------------------------------------------------------------+
256 UPDATE FROM MOST RECENT 3.6
257 ---------------------------
259 Versions of 3.6 built before June 25th have a bug where installworld might
260 crash during installation of the new initrd. Upgrade to the latest version
261 of 3.6 before updating to 3.8 or later.
263 ATM, IPX, NCP AND NWFS SUPPORT DROPPED
264 --------------------------------------
266 Support for the IPX and NCP network protocols and for mouting NetWare
267 file systems has been dropped. Dito for ATM protocol support.
269 INITRD IMAGES NOW INSTALLED BY DEFAULT
270 --------------------------------------
272 An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
274 Older images installed under the file name of initrd.img will be removed
275 automatically by the make upgrade process.
277 USB4BSD IS NOW THE DEFAULT USB STACK
278 ------------------------------------
280 To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
281 replace "device usb" with "device oldusb" in the kernel configuration.
283 MORE ISA SUPPORT DROPPED
284 ------------------------
286 ISA support has been dropped from the following drivers: adv(4), an(4),
287 ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
288 si(4), sn(4), and stg(4).
290 +-----------------------------------------------------------------------+
291 + UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS +
292 +-----------------------------------------------------------------------+
297 Installed third-party software (dports) will have to be rebuilt after upgrade,
298 or reinstalled from binary packages.
300 UPDATING FROM 3.4 TO 3.6
301 ------------------------
303 This only applies for this specific upgrade due to locale changes; it is
304 not needed for upgrades after 3.6. Please update in this order:
313 See this mailing list post for details:
314 http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
316 CYRIX OPTIONS REMOVED
317 ---------------------
319 The following Cyrix related options have been removed: CPU_BTB_EN,
320 CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
321 CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
322 CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
324 ISA SUPPORT REMOVED FROM RP(4)
325 ------------------------------
327 ISA support has been removed from the rp(4) driver. It is now PCI only.
329 +-----------------------------------------------------------------------+
330 + UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS +
331 +-----------------------------------------------------------------------+
333 COMPAT_SUNOS OPTION REMOVED
334 ---------------------------
336 The COMPAT_SUNOS option has been removed. It was meant to provide binary
337 compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
339 ISA SOUND CARD SUPPORT REMOVED
340 ------------------------------
342 The following modules have been removed (all for ISA sound cards):
343 snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
348 DragonFly has switched base compilers. GCC 4.7 is now the default
349 compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make
350 variable ceases to work now.
352 Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
353 /etc/make.conf to prohibit GCC 4.4 from building. However, using it is
354 highly discouraged. There are a few packages in pkgsrc that do not build
355 with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At
356 this time, it is recommended to keep both compilers on the base system.
361 The SMP kernel option has been made a no-op. All kernels now feature SMP
362 support. If you have 'options SMP' in your kernel config, you can as well
365 DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
366 ---------------------------------------------------------------------------
368 The DEVICE_POLLING kernel option has been made a no-op and it has been
369 replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your
370 kernel config, you need to change it to IFPOLL_ENABLE.
372 Also, the KTR_POLLING kernel option has been removed, so it must be
373 removed from kernel configs that have it.
375 BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
376 ---------------------------------------------------
378 The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
379 cards will no longer be detected.
381 The same has been done for Stallion multiport serial controllers. stli(4)
382 has been completely removed (along with the stlload(8) and stlstty(8)
383 utilities) and stl(4) was changed to support only PCI cards. Similarly,
384 ISA support was removed from cy(4) too. All these drivers are i386 only.
386 COMPAT_OLDISA OPTION GONE
387 -------------------------
389 The i386 specific COMPAT_OLDISA kernel option has been removed, since
390 nothing needs it anymore.
392 +-----------------------------------------------------------------------+
393 + UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS +
394 +-----------------------------------------------------------------------+
396 APIC_IO OPTION REMOVED
397 ----------------------
399 The APIC_IO kernel option is no longer accepted after having been without
400 effect for a while. The hw.ioapic_enable tunable now serves its purpose.
401 If you have 'options APIC_IO' in your kernel config, you'll have to
404 WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
405 -----------------------------------------
407 The wdog framework is now compiled into our kernels by default, so the
408 options are no longer needed.
413 doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
414 NO_X make.conf option was removed too.
419 GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
420 default compiler in base (default is still GCC 4.4).
422 Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
423 NO_GCC47 in /etc/make.conf.
428 A new USB stack (from FreeBSD) has been brought in. The following
429 modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
430 usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
433 It is not yet the default. To activate it, WANT_USB4BSD=yes has to
434 be put in make.conf and device "usb4bsd" (quotes needed) has to
435 replace device usb in the kernel config. After that, a full
436 build/install/upgrade cycle is needed.
438 Note that this is experimental and incomplete, but we are interested
439 in hearing about issues with it, of course.
441 ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
442 ---------------------------------------------
444 ISA adapter support was dropped from the aic(4) driver.
446 +-----------------------------------------------------------------------+
447 + UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS +
448 +-----------------------------------------------------------------------+
450 SEVERAL ISA DRIVERS REMOVED
451 ---------------------------
453 The following ISA only drivers have been removed along with a couple of
454 associated userland tools:
470 tw(4) & xten(1) & xtend(8)
474 Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
475 config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
478 If buildkernel complains about any of these drivers, just remove them
479 from your kernel configuration.
483 Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
484 values of BINUTILSVERS are now binutils221 and binutils222 (default).
486 BUILDWORLD/-KERNEL PARALLELIZATION WORK
487 ---------------------------------------
488 Due to changes in the way we build with more than one make job, you
489 will have to update install(1) and mkdir(1) prior to buildworld if you
490 want to build with 'make -j':
492 cd /usr/src/usr.bin/xinstall; make; make install; make clean
493 cd /usr/src/bin/mkdir; make; make install; make clean
497 dma(8) has been upgraded to v0.7 which no longer supports the
498 /etc/dma/virtusertable. Some of its functionality has been replaced
499 with the MASQUERADE keyword and the EMAIL environment variable (see
500 the dma(8) manual page).
502 +-----------------------------------------------------------------------+
503 + UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS +
504 +-----------------------------------------------------------------------+
506 GCC 4.4 & BINUTILS 2.21
507 -----------------------
509 GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
510 been made DragonFly's default Binutils.
512 That means that any settings that set CCVER to 'gcc44' are not needed
513 anymore. Instead, CCVER can be set to 'gcc41' to go back to using
516 It also means that 'binutils221' as a value for BINUTILSVER has no
517 effect anymore. 2.17 has been removed and 'binutils220' is available
520 The NO_GCC44 option has been removed and will not affect the build
521 anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
522 building in a similar fashion.
524 Note that you must do a full buildworld/buildkernel for upgrading.
529 The config file for pkg_radd has moved from /etc/settings.conf to
530 /etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
531 if this is needed. This warning only applies if /etc/settings.conf
532 exists. pkg_radd will continue to work with defaults.
534 +-----------------------------------------------------------------------+
536 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
537 +-----------------------------------------------------------------------+
542 OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
543 This shouldn't break any 3rd-party software, but you'll need to recompile your
544 3rd-party software if you want it to link against the new version of OpenSSL.
549 A new loader (dloader) has been added which better handles booting from
550 multiple kernel/module versions.
552 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
558 make buildkernel KERNCONF=<KERNELNAME>
559 make installkernel KERNCONF=<KERNELNAME>
561 Note that you must installworld and run the 'upgrade' target before
562 installing the new kernel.
567 BIND has been removed from the base system. The ldns and drill tools have
568 been added for basic functionality. Use 'drill' where you would normally
569 use nslookup or dig, or install BIND from pkgsrc. It's available as
570 net/bind95, net/bind96, or net/bind97 as of this writing.
572 This only affects older systems upgrading to 2.8. New 2.8+ installs
573 include BIND as a pkgsrc package.
575 +-----------------------------------------------------------------------+
576 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
578 +-----------------------------------------------------------------------+
580 Instructions on how to obtain and maintain DragonFly source code using git
581 are in the development(7) manual page.
583 To upgrade a DragonFly system from sources you run the following sequence:
587 make buildkernel KERNCONF=<KERNELNAME>
588 make installkernel KERNCONF=<KERNELNAME>
591 You will also want to run the 'upgrade' target to upgrade your /etc and the
592 rest of your system. The upgrade target is aware of stale files created by
593 older DragonFly installations and should delete them automatically.
597 See the build(7) manual page for further information.
599 Once you've done a full build of the world and kernel you can do incremental
600 upgrades of either by using the 'quickworld' and 'quickkernel' targets
601 instead of 'buildworld' and 'buildkernel'. If you have any problems with
602 the quick targets, try updating your repo first, and then a full buildworld
603 and buildkernel as shown above, before asking for help.
605 +-----------------------------------------------------------------------+
606 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
607 +-----------------------------------------------------------------------+
609 In 2.1 kernel and modules has moved to boot directory. For most cases
610 this is handled automatically by 'make upgrade'. A few cases needs manual
613 * When installing a kernel without first doing a make buildworld,
614 installworld and upgrade to the same DESTDIR as kernel:
615 make DESTDIR/boot directory and move kernel and modules into this boot
616 directory; also move kernel.old and modules.old.
617 Typical example is vkernel(7), use (no modules used):
621 chflags noschg kernel
622 mv kernel kernel.old boot
623 chflags schg boot/kernel
625 * When using a boot-only partition, /boot/loader.rc needs to be edited:
626 delete occurrences of '/boot/'.
627 These occurences can normally be deleted in any case, see loader(8).
629 +-----------------------------------------------------------------------+
630 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
631 +-----------------------------------------------------------------------+
633 In 1.9 major changes to the disk management infrastructure have taken
634 place. make upgrade may not catch all of your disk devices in /dev,
635 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
636 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
637 and MAKEDEV no longer exists.
639 The biggest changes in 1.9 are:
641 (1) That whole-slice devices such as da0s1 no longer share the same device
642 id as partition c devices such as da0s1c.
644 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
645 with no snooping or reserved sectors. Consequently you cannot run
646 disklabel on this device. Instead you must run disklabel on a
649 (3) The 'compatibility' partitions now use slice 0 in the device name,
650 so instead of da0a you must specify da0s0a. Also, as per (1) above,
651 accessing the disklabel for the compatibility partitions must be
652 done via slice 0 (da0s0).
654 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
655 and CCD now run through the disk management layer and are assigned
656 real disk management devices. VN and CCD in particular do not usually
657 use a MBR and disklabels must be accessed through the compatibility
658 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
659 don't name it 'ccd0s0' in the config file.
661 Generally speaking, you have to get used to running fdisk and disklabel on
662 the correctly specified device names. A lot of the wiggle, such as running
663 disklabel on a partition, has been removed.
665 +-----------------------------------------------------------------------+
666 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
667 +-----------------------------------------------------------------------+
672 Kerberos IV (eBones) was removed from the tree, please consider moving to
673 Kerberos 5 (Heimdal).
675 > Package Management System
676 ---------------------------
678 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
679 management system. The necessary tools to build and maintain packages
680 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
681 directories are in your PATH variable.
683 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
684 the tarball from NetBSD:
686 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
687 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
689 This tree can then be kept up to date with cvs update:
691 cd /usr/pkgsrc; cvs up
693 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
694 build and install the pkgsrc bootstrap manually:
696 cd /usr/pkgsrc/bootstrap
697 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
699 +-----------------------------------------------------------------------+
700 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
701 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
702 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
703 +-----------------------------------------------------------------------+
705 The compatibility shims for the build environment have been removed, you
706 have to update to DragonFly 1.2 release branch first.
708 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
709 The existing configuration can be converted using /etc/pam.d/convert.sh.
710 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
711 the pam_skey.so module was retired, you have to remove it manually from
712 your configuration, when you convert it.
714 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
715 ---------------------
717 The following users may be missing from your password file. Use vipw and
718 add any that are missing:
720 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
721 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
723 The following groups may be missing from your group file. Use vi /etc/group
724 and add any that are missing:
731 > Upgrading to DragonFly from FreeBSD
732 ---------------------
734 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
735 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
736 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
737 make depend information, it starts from scratch, so no pre-cleaning of the
738 object hierarchy is necessary.
740 # get the CVS repository (it is placed in /home/dcvs, 500MB).
741 # Please use the -h option and a mirror site to pull the
742 # initial repository, but feel free to use the main repository
743 # machine to pull updates.
744 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
745 # install the source from the CVS hierarchy (remove preexisting
746 # FreeBSD src first) (500MB)
749 cvs -R -d /home/dcvs checkout -P src
751 # build it (500MB used in /usr/obj)
755 make buildkernel KERNCONF=<KERNELNAME>
757 Once you have built DragonFly you have to install it over FreeBSD. Since
758 DragonFly does not track changes made by FreeBSD to its include file
759 hierarchy and include file pollution can cause all sorts of unexpected
760 compilation issues to come up, it is best to wipe your include hierarchy
761 prior to installing DragonFly. Note that you should not wipe any installed
762 FreeBSD header files or binaries until after you have successfully completed
763 the build steps above.
767 make installkernel KERNCONF=<KERNELNAME>
770 Then you need to upgrade your system. DragonFly's 'make upgrade' target
771 will unconditionally upgrade the /etc files that sysops do not usually
772 mess around with, such as the files in /etc/rc.d. It will also remove any
773 obsolete files such as utilities and manpages that have been removed from
774 the system since the version you're coming from. If you are unsure we
775 recommend that you make a backup of at least your /etc before applying
776 this step. Note that DragonFly's RC system is basically RCNG from
777 FreeBSD-5, but there are some differences in the contents of the RC files.
781 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
782 Doing so might leave your system in an unusable state.
784 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
785 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
786 report these files to the DragonFly developers so that they can be added to
787 the 'upgrade' target.