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