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