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