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