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