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