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