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