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