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