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