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 3.8 TO LATER VERSIONS + 13+-----------------------------------------------------------------------+ 14 15SMP and DEVICE_POLLING OPTIONS MADE UNKNOWN 16------------------------------------------- 17 18DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is 19the default now (even on single-core systems), both for, like, 21 months. 20We kept the options around as no-ops as a convenience, to allow people 21using the same config for the then current release and the then current 22master. That period is now over, so any configs still having those 23options have to be adjusted. 24 25SYSVIPC SYSCALLS MADE NON-OPTIONAL 26---------------------------------- 27 28The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is 29now compiled in by default. The options are no-ops for now. 30 31DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS 32-------------------------------------------------------------------- 33 34The default driver for those controllers is now mrsas(4) due to reports 35of file system corruption using the mfi(4) driver. The whole issue (and 36how to deal with potential problems when switching) was explained here: 37 38http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html 39 40A tunable is provided for letting those controllers still attach via 41the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page). 42 43OLDER NETWORK DRIVERS MOVED TO I386 ONLY 44---------------------------------------- 45 46The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar 47and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be 48removed in kernel configs derived from X86_64_GENERIC. 49 50+-----------------------------------------------------------------------+ 51+ UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS + 52+-----------------------------------------------------------------------+ 53 54UPDATE FROM MOST RECENT 3.6 55--------------------------- 56 57Versions of 3.6 built before June 25th have a bug where installworld might 58crash during installation of the new initrd. Upgrade to the latest version 59of 3.6 before updating to 3.8 or later. 60 61ATM, IPX, NCP AND NWFS SUPPORT DROPPED 62-------------------------------------- 63 64Support for the IPX and NCP network protocols and for mouting NetWare 65file systems has been dropped. Dito for ATM protocol support. 66 67INITRD IMAGES NOW INSTALLED BY DEFAULT 68-------------------------------------- 69 70An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz 71 72Older images installed under the file name of initrd.img will be removed 73automatically by the make upgrade process. 74 75USB4BSD IS NOW THE DEFAULT USB STACK 76------------------------------------ 77 78To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and 79replace "device usb" with "device oldusb" in the kernel configuration. 80 81MORE ISA SUPPORT DROPPED 82------------------------ 83 84ISA support has been dropped from the following drivers: adv(4), an(4), 85ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4), 86si(4), sn(4), and stg(4). 87 88+-----------------------------------------------------------------------+ 89+ UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS + 90+-----------------------------------------------------------------------+ 91 92ABI CHANGE 93---------- 94 95Installed third-party software (dports) will have to be rebuilt after upgrade, 96or reinstalled from binary packages. 97 98UPDATING FROM 3.4 TO 3.6 99------------------------ 100 101This only applies for this specific upgrade due to locale changes; it is 102not needed for upgrades after 3.6. Please update in this order: 103 104make buildworld 105make buildkernel 106make installworld 107make installkernel 108*reboot* 109make upgrade 110 111See this mailing list post for details: 112http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html 113 114CYRIX OPTIONS REMOVED 115--------------------- 116 117The following Cyrix related options have been removed: CPU_BTB_EN, 118CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER, 119CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT, 120CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS 121 122ISA SUPPORT REMOVED FROM RP(4) 123------------------------------ 124 125ISA support has been removed from the rp(4) driver. It is now PCI only. 126 127+-----------------------------------------------------------------------+ 128+ UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS + 129+-----------------------------------------------------------------------+ 130 131COMPAT_SUNOS OPTION REMOVED 132--------------------------- 133 134The COMPAT_SUNOS option has been removed. It was meant to provide binary 135compatibility with SunOS 4.x for the sparc32 port of 4.4BSD. 136 137ISA SOUND CARD SUPPORT REMOVED 138------------------------------ 139 140The following modules have been removed (all for ISA sound cards): 141snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko 142 143GCC 4.7 144------- 145 146DragonFly has switched base compilers. GCC 4.7 is now the default 147compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make 148variable ceases to work now. 149 150Users who wish to build only GCC 4.7 have to use NO_GCC44 in the 151/etc/make.conf to prohibit GCC 4.4 from building. However, using it is 152highly discouraged. There are a few packages in pkgsrc that do not build 153with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At 154this time, it is recommended to keep both compilers on the base system. 155 156SMP OPTION REMOVED 157------------------ 158 159The SMP kernel option has been made a no-op. All kernels now feature SMP 160support. If you have 'options SMP' in your kernel config, you can as well 161remove it. 162 163DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED 164--------------------------------------------------------------------------- 165 166The DEVICE_POLLING kernel option has been made a no-op and it has been 167replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your 168kernel config, you need to change it to IFPOLL_ENABLE. 169 170Also, the KTR_POLLING kernel option has been removed, so it must be 171removed from kernel configs that have it. 172 173BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED 174--------------------------------------------------- 175 176The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA 177cards will no longer be detected. 178 179The same has been done for Stallion multiport serial controllers. stli(4) 180has been completely removed (along with the stlload(8) and stlstty(8) 181utilities) and stl(4) was changed to support only PCI cards. Similarly, 182ISA support was removed from cy(4) too. All these drivers are i386 only. 183 184COMPAT_OLDISA OPTION GONE 185------------------------- 186 187The i386 specific COMPAT_OLDISA kernel option has been removed, since 188nothing needs it anymore. 189 190+-----------------------------------------------------------------------+ 191+ UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS + 192+-----------------------------------------------------------------------+ 193 194APIC_IO OPTION REMOVED 195---------------------- 196 197The APIC_IO kernel option is no longer accepted after having been without 198effect for a while. The hw.ioapic_enable tunable now serves its purpose. 199If you have 'options APIC_IO' in your kernel config, you'll have to 200remove it. 201 202WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED 203----------------------------------------- 204 205The wdog framework is now compiled into our kernels by default, so the 206options are no longer needed. 207 208DOSCMD(1) REMOVED 209----------------- 210 211doscmd(1) has been removed. It was i386 only. The doscmd(1) specific 212NO_X make.conf option was removed too. 213 214GCC 4.7 215------- 216 217GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non- 218default compiler in base (default is still GCC 4.4). 219 220Users who wish to build only GCC 4.4 have to replace NO_GCC41 with 221NO_GCC47 in /etc/make.conf. 222 223USB4BSD 224------- 225 226A new USB stack (from FreeBSD) has been brought in. The following 227modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass, 228usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk, 229and uaudio. 230 231It is not yet the default. To activate it, WANT_USB4BSD=yes has to 232be put in make.conf and device "usb4bsd" (quotes needed) has to 233replace device usb in the kernel config. After that, a full 234build/install/upgrade cycle is needed. 235 236Note that this is experimental and incomplete, but we are interested 237in hearing about issues with it, of course. 238 239ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER 240--------------------------------------------- 241 242ISA adapter support was dropped from the aic(4) driver. 243 244+-----------------------------------------------------------------------+ 245+ UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS + 246+-----------------------------------------------------------------------+ 247 248SEVERAL ISA DRIVERS REMOVED 249--------------------------- 250 251The following ISA only drivers have been removed along with a couple of 252associated userland tools: 253 254aha(4) 255asc(4) & sasc(1) 256ctx 257dgb(4) 258el(4) 259gpib 260gsc(4) & sgsc(1) 261ie(4) 262labpc(4) 263le(4) 264mse(4) 265rc(4) 266rdp(4) 267spigot 268tw(4) & xten(1) & xtend(8) 269wl(4) & wlconfig(8) 270wt(4) 271 272Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC 273config and one (aha(4)) is in our X86_64_GENERIC kernel configuration 274file. 275 276If buildkernel complains about any of these drivers, just remove them 277from your kernel configuration. 278 279BINUTILS 2.20 280------------- 281Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted 282values of BINUTILSVERS are now binutils221 and binutils222 (default). 283 284BUILDWORLD/-KERNEL PARALLELIZATION WORK 285--------------------------------------- 286Due to changes in the way we build with more than one make job, you 287will have to update install(1) and mkdir(1) prior to buildworld if you 288want to build with 'make -j': 289 290cd /usr/src/usr.bin/xinstall; make; make install; make clean 291cd /usr/src/bin/mkdir; make; make install; make clean 292 293DMA(8) UPGRADE 294-------------- 295dma(8) has been upgraded to v0.7 which no longer supports the 296/etc/dma/virtusertable. Some of its functionality has been replaced 297with the MASQUERADE keyword and the EMAIL environment variable (see 298the dma(8) manual page). 299 300+-----------------------------------------------------------------------+ 301+ UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS + 302+-----------------------------------------------------------------------+ 303 304GCC 4.4 & BINUTILS 2.21 305----------------------- 306 307GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has 308been made DragonFly's default Binutils. 309 310That means that any settings that set CCVER to 'gcc44' are not needed 311anymore. Instead, CCVER can be set to 'gcc41' to go back to using 312GCC 4.1. 313 314It also means that 'binutils221' as a value for BINUTILSVER has no 315effect anymore. 2.17 has been removed and 'binutils220' is available 316as an option. 317 318The NO_GCC44 option has been removed and will not affect the build 319anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from 320building in a similar fashion. 321 322Note that you must do a full buildworld/buildkernel for upgrading. 323 324pkg_radd settings 325----------------- 326 327The config file for pkg_radd has moved from /etc/settings.conf to 328/etc/pkg_radd.conf. Save the contents of settings.conf before upgrading 329if this is needed. This warning only applies if /etc/settings.conf 330exists. pkg_radd will continue to work with defaults. 331 332+-----------------------------------------------------------------------+ 333+ 20100927 + 334+ UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD + 335+-----------------------------------------------------------------------+ 336 337OpenSSL 338-------- 339 340OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto. 341This shouldn't break any 3rd-party software, but you'll need to recompile your 3423rd-party software if you want it to link against the new version of OpenSSL. 343 344Loader 345------- 346 347A new loader (dloader) has been added which better handles booting from 348multiple kernel/module versions. 349 350To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below) 351 352 cd /usr/src 353 make buildworld 354 make installworld 355 make upgrade 356 make buildkernel KERNCONF=<KERNELNAME> 357 make installkernel KERNCONF=<KERNELNAME> 358 359Note that you must installworld and run the 'upgrade' target before 360installing the new kernel. 361 362BIND 363----- 364 365BIND has been removed from the base system. The ldns and drill tools have 366been added for basic functionality. Use 'drill' where you would normally 367use nslookup or dig, or install BIND from pkgsrc. It's available as 368net/bind95, net/bind96, or net/bind97 as of this writing. 369 370This only affects older systems upgrading to 2.8. New 2.8+ installs 371include BIND as a pkgsrc package. 372 373+-----------------------------------------------------------------------+ 374+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM + 375+ GENERAL + 376+-----------------------------------------------------------------------+ 377 378Instructions on how to obtain and maintain DragonFly source code using git 379are in the development(7) manual page. 380 381To upgrade a DragonFly system from sources you run the following sequence: 382 383 cd /usr/src 384 make buildworld 385 make buildkernel KERNCONF=<KERNELNAME> 386 make installkernel KERNCONF=<KERNELNAME> 387 make installworld 388 389You will also want to run the 'upgrade' target to upgrade your /etc and the 390rest of your system. The upgrade target is aware of stale files created by 391older DragonFly installations and should delete them automatically. 392 393 make upgrade 394 395See the build(7) manual page for further information. 396 397Once you've done a full build of the world and kernel you can do incremental 398upgrades of either by using the 'quickworld' and 'quickkernel' targets 399instead of 'buildworld' and 'buildkernel'. If you have any problems with 400the quick targets, try updating your repo first, and then a full buildworld 401and buildkernel as shown above, before asking for help. 402 403+-----------------------------------------------------------------------+ 404+ UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 + 405+-----------------------------------------------------------------------+ 406 407In 2.1 kernel and modules has moved to boot directory. For most cases 408this is handled automatically by 'make upgrade'. A few cases needs manual 409intervention: 410 411 * When installing a kernel without first doing a make buildworld, 412 installworld and upgrade to the same DESTDIR as kernel: 413 make DESTDIR/boot directory and move kernel and modules into this boot 414 directory; also move kernel.old and modules.old. 415 Typical example is vkernel(7), use (no modules used): 416 417 cd /var/vkernel 418 mkdir boot 419 chflags noschg kernel 420 mv kernel kernel.old boot 421 chflags schg boot/kernel 422 423 * When using a boot-only partition, /boot/loader.rc needs to be edited: 424 delete occurrences of '/boot/'. 425 These occurences can normally be deleted in any case, see loader(8). 426 427+-----------------------------------------------------------------------+ 428+ UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 + 429+-----------------------------------------------------------------------+ 430 431In 1.9 major changes to the disk management infrastructure have taken 432place. make upgrade may not catch all of your disk devices in /dev, 433so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah> 434are all of your disk devices. HOWEVER, from late 2.3 on we run devfs 435and MAKEDEV no longer exists. 436 437The biggest changes in 1.9 are: 438 439(1) That whole-slice devices such as da0s1 no longer share the same device 440 id as partition c devices such as da0s1c. 441 442(2) The whole-disk device (e.g. da0) is full raw access to the disk, 443 with no snooping or reserved sectors. Consequently you cannot run 444 disklabel on this device. Instead you must run disklabel on a 445 whole-slice device. 446 447(3) The 'compatibility' partitions now use slice 0 in the device name, 448 so instead of da0a you must specify da0s0a. Also, as per (1) above, 449 accessing the disklabel for the compatibility partitions must be 450 done via slice 0 (da0s0). 451 452(4) Many device drivers that used to fake up labels, such as CD, ACD, VN, 453 and CCD now run through the disk management layer and are assigned 454 real disk management devices. VN and CCD in particular do not usually 455 use a MBR and disklabels must be accessed through the compatibility 456 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you 457 don't name it 'ccd0s0' in the config file. 458 459Generally speaking, you have to get used to running fdisk and disklabel on 460the correctly specified device names. A lot of the wiggle, such as running 461disklabel on a partition, has been removed. 462 463+-----------------------------------------------------------------------+ 464+ UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD + 465+-----------------------------------------------------------------------+ 466 467> Kerberos IV 468------------- 469 470Kerberos IV (eBones) was removed from the tree, please consider moving to 471Kerberos 5 (Heimdal). 472 473> Package Management System 474--------------------------- 475 476Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package 477management system. The necessary tools to build and maintain packages 478are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these 479directories are in your PATH variable. 480 481In order to obtain a reasonably current snapshot of the pkgsrc tree, use 482the tarball from NetBSD: 483 484 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz 485 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc 486 487This tree can then be kept up to date with cvs update: 488 489 cd /usr/pkgsrc; cvs up 490 491NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to 492build and install the pkgsrc bootstrap manually: 493 494 cd /usr/pkgsrc/bootstrap 495 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg 496 497+-----------------------------------------------------------------------+ 498+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM + 499+ UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO + 500+ DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) + 501+-----------------------------------------------------------------------+ 502 503The compatibility shims for the build environment have been removed, you 504have to update to DragonFly 1.2 release branch first. 505 506The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/. 507The existing configuration can be converted using /etc/pam.d/convert.sh. 508Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition 509the pam_skey.so module was retired, you have to remove it manually from 510your configuration, when you convert it. 511 512> Required user and group IDs when upgrading from either FreeBSD or DragonFly 513--------------------- 514 515The following users may be missing from your password file. Use vipw and 516add any that are missing: 517 518smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin 519_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin 520 521The following groups may be missing from your group file. Use vi /etc/group 522and add any that are missing: 523 524smmsp:*:25: 525authpf:*:63: 526_pflogd:*:64: 527 528 529> Upgrading to DragonFly from FreeBSD 530--------------------- 531 532You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or 533FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing 534FreeBSD. Note that the DragonFly buildworld target does not try to reuse 535make depend information, it starts from scratch, so no pre-cleaning of the 536object hierarchy is necessary. 537 538 # get the CVS repository (it is placed in /home/dcvs, 500MB). 539 # Please use the -h option and a mirror site to pull the 540 # initial repository, but feel free to use the main repository 541 # machine to pull updates. 542 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile 543 # install the source from the CVS hierarchy (remove preexisting 544 # FreeBSD src first) (500MB) 545 cd /usr 546 rm -rf src 547 cvs -R -d /home/dcvs checkout -P src 548 549 # build it (500MB used in /usr/obj) 550 # 551 cd /usr/src 552 make buildworld 553 make buildkernel KERNCONF=<KERNELNAME> 554 555Once you have built DragonFly you have to install it over FreeBSD. Since 556DragonFly does not track changes made by FreeBSD to its include file 557hierarchy and include file pollution can cause all sorts of unexpected 558compilation issues to come up, it is best to wipe your include hierarchy 559prior to installing DragonFly. Note that you should not wipe any installed 560FreeBSD header files or binaries until after you have successfully completed 561the build steps above. 562 563 rm -rf /usr/include 564 mkdir /usr/include 565 make installkernel KERNCONF=<KERNELNAME> 566 make installworld 567 568Then you need to upgrade your system. DragonFly's 'make upgrade' target 569will unconditionally upgrade the /etc files that sysops do not usually 570mess around with, such as the files in /etc/rc.d. It will also remove any 571obsolete files such as utilities and manpages that have been removed from 572the system since the version you're coming from. If you are unsure we 573recommend that you make a backup of at least your /etc before applying 574this step. Note that DragonFly's RC system is basically RCNG from 575FreeBSD-5, but there are some differences in the contents of the RC files. 576 577 make upgrade 578 579NOTE! Never do a 'make upgrade' before 'make installworld' has been run. 580Doing so might leave your system in an unusable state. 581 582Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin, 583/usr/bin, and /usr/lib, and remove any stale files that you find. Please 584report these files to the DragonFly developers so that they can be added to 585the 'upgrade' target. 586 587