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