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