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