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