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