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