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