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