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 3.2 to later versions + 13+-----------------------------------------------------------------------+ 14 15GCC 4.7 16------- 17 18DragonFly has switched base compilers. GCC 4.7 is now the default 19compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make 20variable ceases to work now. 21 22Users who wish to build only GCC 4.7 have to use NO_GCC44 in the 23/etc/make.conf to prohibit GCC 4.4 from building. However, using it is 24highly discouraged. There are a few packages in pkgsrc that do not build 25with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At 26this time, it is recommended to keep both compilers on the base system. 27 28SMP OPTION REMOVED 29------------------ 30 31The SMP kernel option has been made a no-op. All kernels now feature SMP 32support. If you have 'options SMP' in your kernel config, you can as well 33remove it. 34 35DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED 36--------------------------------------------------------------------------- 37 38The DEVICE_POLLING kernel option has been made a no-op and it has been 39replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your 40kernel config, you need to change it to IFPOLL_ENABLE. 41 42Also, the KTR_POLLING kernel option has been removed, so it must be 43removed from kernel configs that have it. 44 45BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED 46--------------------------------------------------- 47 48The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA 49cards will no longer be detected. 50 51The same has been done for Stallion multiport serial controllers. stli(4) 52has been completely removed (along with the stlload(8) and stlstty(8) 53utilities) and stl(4) was changed to support only PCI cards. Similarly, 54ISA support was removed from cy(4) too. All these drivers are i386 only. 55 56COMPAT_OLDISA OPTION GONE 57------------------------- 58 59The i386 specific COMPAT_OLDISA kernel option has been removed, since 60nothing needs it anymore. 61 62+-----------------------------------------------------------------------+ 63+ UPGRADING DRAGONFLY FROM 3.0 to later versions + 64+-----------------------------------------------------------------------+ 65 66APIC_IO OPTION REMOVED 67---------------------- 68 69The APIC_IO kernel option is no longer accepted after having been without 70effect for a while. The hw.ioapic_enable tunable now serves its purpose. 71If you have 'options APIC_IO' in your kernel config, you'll have to 72remove it. 73 74WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED 75----------------------------------------- 76 77The wdog framework is now compiled into our kernels by default, so the 78options are no longer needed. 79 80DOSCMD(1) REMOVED 81----------------- 82 83doscmd(1) has been removed. It was i386 only. The doscmd(1) specific 84NO_X make.conf option was removed too. 85 86GCC 4.7 87------- 88 89GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non- 90default compiler in base (default is still GCC 4.4). 91 92Users who wish to build only GCC 4.4 have to replace NO_GCC41 with 93NO_GCC47 in /etc/make.conf. 94 95USB4BSD 96------- 97 98A new USB stack (from FreeBSD) has been brought in. The following 99modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass, 100usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk, 101and uaudio. 102 103It is not yet the default. To activate it, WANT_USB4BSD=yes has to 104be put in make.conf and device "usb4bsd" (quotes needed) has to 105replace device usb in the kernel config. After that, a full 106build/install/upgrade cycle is needed. 107 108Note that this is experimental and incomplete, but we are interested 109in hearing about issues with it, of course. 110 111ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER 112--------------------------------------------- 113 114ISA adapter support was dropped from the aic(4) driver. 115 116+-----------------------------------------------------------------------+ 117+ UPGRADING DRAGONFLY FROM 2.10 to later versions + 118+-----------------------------------------------------------------------+ 119 120SEVERAL ISA DRIVERS REMOVED 121--------------------------- 122 123The following ISA only drivers have been removed along with a couple of 124associated userland tools: 125 126aha(4) 127asc(4) & sasc(1) 128ctx 129dgb(4) 130el(4) 131gpib 132gsc(4) & sgsc(1) 133ie(4) 134labpc(4) 135le(4) 136mse(4) 137rc(4) 138rdp(4) 139spigot 140tw(4) & xten(1) & xtend(8) 141wl(4) & wlconfig(8) 142wt(4) 143 144Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC 145config and one (aha(4)) is in our X86_64_GENERIC kernel configuration 146file. 147 148If buildkernel complains about any of these drivers, just remove them 149from your kernel configuration. 150 151BINUTILS 2.20 152------------- 153Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted 154values of BINUTILSVERS are now binutils221 and binutils222 (default). 155 156BUILDWORLD/-KERNEL PARALLELIZATION WORK 157--------------------------------------- 158Due to changes in the way we build with more than one make job, you 159will have to update install(1) and mkdir(1) prior to buildworld if you 160want to build with 'make -j': 161 162cd /usr/src/usr.bin/xinstall; make; make install; make clean 163cd /usr/src/bin/mkdir; make; make install; make clean 164 165DMA(8) UPGRADE 166-------------- 167dma(8) has been upgraded to v0.7 which no longer supports the 168/etc/dma/virtusertable. Some of its functionality has been replaced 169with the MASQUERADE keyword and the EMAIL environment variable (see 170the dma(8) manual page). 171 172+-----------------------------------------------------------------------+ 173+ UPGRADING DRAGONFLY FROM 2.8 to later versions + 174+-----------------------------------------------------------------------+ 175 176GCC 4.4 & BINUTILS 2.21 177----------------------- 178 179GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has 180been made DragonFly's default Binutils. 181 182That means that any settings that set CCVER to 'gcc44' are not needed 183anymore. Instead, CCVER can be set to 'gcc41' to go back to using 184GCC 4.1. 185 186It also means that 'binutils221' as a value for BINUTILSVER has no 187effect anymore. 2.17 has been removed and 'binutils220' is available 188as an option. 189 190The NO_GCC44 option has been removed and will not affect the build 191anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from 192building in a similar fashion. 193 194Note that you must do a full buildworld/buildkernel for upgrading. 195 196pkg_radd settings 197----------------- 198 199The config file for pkg_radd has moved from /etc/settings.conf to 200/etc/pkg_radd.conf. Save the contents of settings.conf before upgrading 201if this is needed. This warning only applies if /etc/settings.conf 202exists. pkg_radd will continue to work with defaults. 203 204+-----------------------------------------------------------------------+ 205+ 20100927 + 206+ UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD + 207+-----------------------------------------------------------------------+ 208 209OpenSSL 210-------- 211 212OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto. 213This shouldn't break any 3rd-party software, but you'll need to recompile your 2143rd-party software if you want it to link against the new version of OpenSSL. 215 216Loader 217------- 218 219A new loader (dloader) has been added which better handles booting from 220multiple kernel/module versions. 221 222To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below) 223 224 cd /usr/src 225 make buildworld 226 make installworld 227 make upgrade 228 make buildkernel KERNCONF=<KERNELNAME> 229 make installkernel KERNCONF=<KERNELNAME> 230 231Note that you must installworld and run the 'upgrade' target before 232installing the new kernel. 233 234BIND 235----- 236 237BIND has been removed from the base system. The ldns and drill tools have 238been added for basic functionality. Use 'drill' where you would normally 239use nslookup or dig, or install BIND from pkgsrc. It's available as 240net/bind95, net/bind96, or net/bind97 as of this writing. 241 242This only affects older systems upgrading to 2.8. New 2.8+ installs 243include BIND as a pkgsrc package. 244 245+-----------------------------------------------------------------------+ 246+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM + 247+ GENERAL + 248+-----------------------------------------------------------------------+ 249 250Instructions on how to obtain and maintain DragonFly source code using git 251are in the development(7) manual page. 252 253To upgrade a DragonFly system from sources you run the following sequence: 254 255 cd /usr/src 256 make buildworld 257 make buildkernel KERNCONF=<KERNELNAME> 258 make installkernel KERNCONF=<KERNELNAME> 259 make installworld 260 261You will also want to run the 'upgrade' target to upgrade your /etc and the 262rest of your system. The upgrade target is aware of stale files created by 263older DragonFly installations and should delete them automatically. 264 265 make upgrade 266 267See the build(7) manual page for further information. 268 269Once you've done a full build of the world and kernel you can do incremental 270upgrades of either by using the 'quickworld' and 'quickkernel' targets 271instead of 'buildworld' and 'buildkernel'. If you have any problems with 272the quick targets, try updating your repo first, and then a full buildworld 273and buildkernel as shown above, before asking for help. 274 275+-----------------------------------------------------------------------+ 276+ UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 + 277+-----------------------------------------------------------------------+ 278 279In 2.1 kernel and modules has moved to boot directory. For most cases 280this is handled automatically by 'make upgrade'. A few cases needs manual 281intervention: 282 283 * When installing a kernel without first doing a make buildworld, 284 installworld and upgrade to the same DESTDIR as kernel: 285 make DESTDIR/boot directory and move kernel and modules into this boot 286 directory; also move kernel.old and modules.old. 287 Typical example is vkernel(7), use (no modules used): 288 289 cd /var/vkernel 290 mkdir boot 291 chflags noschg kernel 292 mv kernel kernel.old boot 293 chflags schg boot/kernel 294 295 * When using a boot-only partition, /boot/loader.rc needs to be edited: 296 delete occurrences of '/boot/'. 297 These occurences can normally be deleted in any case, see loader(8). 298 299+-----------------------------------------------------------------------+ 300+ UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 + 301+-----------------------------------------------------------------------+ 302 303In 1.9 major changes to the disk management infrastructure have taken 304place. make upgrade may not catch all of your disk devices in /dev, 305so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah> 306are all of your disk devices. HOWEVER, from late 2.3 on we run devfs 307and MAKEDEV no longer exists. 308 309The biggest changes in 1.9 are: 310 311(1) That whole-slice devices such as da0s1 no longer share the same device 312 id as partition c devices such as da0s1c. 313 314(2) The whole-disk device (e.g. da0) is full raw access to the disk, 315 with no snooping or reserved sectors. Consequently you cannot run 316 disklabel on this device. Instead you must run disklabel on a 317 whole-slice device. 318 319(3) The 'compatibility' partitions now use slice 0 in the device name, 320 so instead of da0a you must specify da0s0a. Also, as per (1) above, 321 accessing the disklabel for the compatibility partitions must be 322 done via slice 0 (da0s0). 323 324(4) Many device drivers that used to fake up labels, such as CD, ACD, VN, 325 and CCD now run through the disk management layer and are assigned 326 real disk management devices. VN and CCD in particular do not usually 327 use a MBR and disklabels must be accessed through the compatibility 328 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you 329 don't name it 'ccd0s0' in the config file. 330 331Generally speaking, you have to get used to running fdisk and disklabel on 332the correctly specified device names. A lot of the wiggle, such as running 333disklabel on a partition, has been removed. 334 335+-----------------------------------------------------------------------+ 336+ UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD + 337+-----------------------------------------------------------------------+ 338 339> Kerberos IV 340------------- 341 342Kerberos IV (eBones) was removed from the tree, please consider moving to 343Kerberos 5 (Heimdal). 344 345> Package Management System 346--------------------------- 347 348Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package 349management system. The necessary tools to build and maintain packages 350are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these 351directories are in your PATH variable. 352 353In order to obtain a reasonably current snapshot of the pkgsrc tree, use 354the tarball from NetBSD: 355 356 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz 357 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc 358 359This tree can then be kept up to date with cvs update: 360 361 cd /usr/pkgsrc; cvs up 362 363NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to 364build and install the pkgsrc bootstrap manually: 365 366 cd /usr/pkgsrc/bootstrap 367 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg 368 369+-----------------------------------------------------------------------+ 370+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM + 371+ UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO + 372+ DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) + 373+-----------------------------------------------------------------------+ 374 375The compatibility shims for the build environment have been removed, you 376have to update to DragonFly 1.2 release branch first. 377 378The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/. 379The existing configuration can be converted using /etc/pam.d/convert.sh. 380Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition 381the pam_skey.so module was retired, you have to remove it manually from 382your configuration, when you convert it. 383 384> Required user and group IDs when upgrading from either FreeBSD or DragonFly 385--------------------- 386 387The following users may be missing from your password file. Use vipw and 388add any that are missing: 389 390smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin 391_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin 392 393The following groups may be missing from your group file. Use vi /etc/group 394and add any that are missing: 395 396smmsp:*:25: 397authpf:*:63: 398_pflogd:*:64: 399 400 401> Upgrading to DragonFly from FreeBSD 402--------------------- 403 404You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or 405FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing 406FreeBSD. Note that the DragonFly buildworld target does not try to reuse 407make depend information, it starts from scratch, so no pre-cleaning of the 408object hierarchy is necessary. 409 410 # get the CVS repository (it is placed in /home/dcvs, 500MB). 411 # Please use the -h option and a mirror site to pull the 412 # initial repository, but feel free to use the main repository 413 # machine to pull updates. 414 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile 415 # install the source from the CVS hierarchy (remove preexisting 416 # FreeBSD src first) (500MB) 417 cd /usr 418 rm -rf src 419 cvs -R -d /home/dcvs checkout -P src 420 421 # build it (500MB used in /usr/obj) 422 # 423 cd /usr/src 424 make buildworld 425 make buildkernel KERNCONF=<KERNELNAME> 426 427Once you have built DragonFly you have to install it over FreeBSD. Since 428DragonFly does not track changes made by FreeBSD to its include file 429hierarchy and include file pollution can cause all sorts of unexpected 430compilation issues to come up, it is best to wipe your include hierarchy 431prior to installing DragonFly. Note that you should not wipe any installed 432FreeBSD header files or binaries until after you have successfully completed 433the build steps above. 434 435 rm -rf /usr/include 436 mkdir /usr/include 437 make installkernel KERNCONF=<KERNELNAME> 438 make installworld 439 440Then you need to upgrade your system. DragonFly's 'make upgrade' target 441will unconditionally upgrade the /etc files that sysops do not usually 442mess around with, such as the files in /etc/rc.d. It will also remove any 443obsolete files such as utilities and manpages that have been removed from 444the system since the version you're coming from. If you are unsure we 445recommend that you make a backup of at least your /etc before applying 446this step. Note that DragonFly's RC system is basically RCNG from 447FreeBSD-5, but there are some differences in the contents of the RC files. 448 449 make upgrade 450 451NOTE! Never do a 'make upgrade' before 'make installworld' has been run. 452Doing so might leave your system in an unusable state. 453 454Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin, 455/usr/bin, and /usr/lib, and remove any stale files that you find. Please 456report these files to the DragonFly developers so that they can be added to 457the 'upgrade' target. 458 459