1 # Updating Information for DragonFly users.
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.
8 # If you discover any problem, please contact the bugs@lists.dragonflybsd.org
9 # mailing list with the details.
11 +-----------------------------------------------------------------------+
12 + UPGRADING DRAGONFLY FROM 2.8 to later versions +
13 +-----------------------------------------------------------------------+
18 GCC 4.4 has been made DragonFly's default compiler.
20 That means that any settings that set CCVER to 'gcc44' are not needed
21 anymore. Instead, CCVER can be set to 'gcc41' to go back to using
24 The NO_GCC44 option has been removed and will not affect the build
25 anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
26 building in a similar fashion.
28 Also, we recommend to do a full buildworld/buildkernel for upgrading.
33 The config file for pkg_radd has moved from /etc/settings.conf to
34 /etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
35 if this is needed. This warning only applies if /etc/settings.conf
36 exists. pkg_radd will continue to work with defaults.
38 +-----------------------------------------------------------------------+
40 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
41 +-----------------------------------------------------------------------+
46 OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
47 This shouldn't break any 3rd-party software, but you'll need to recompile your
48 3rd-party software if you want it to link against the new version of OpenSSL.
53 A new loader (dloader) has been added which better handles booting from
54 multiple kernel/module versions.
56 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
62 make buildkernel KERNCONF=<KERNELNAME>
63 make installkernel KERNCONF=<KERNELNAME>
65 Note that you must installworld and run the 'upgrade' target before
66 installing the new kernel.
71 BIND has been removed from the base system. The ldns and drill tools have
72 been added for basic functionality. Use 'drill' where you would normally
73 use nslookup or dig, or install BIND from pkgsrc. It's available as
74 net/bind95, net/bind96, or net/bind97 as of this writing.
76 This only affects older systems upgrading to 2.8. New 2.8+ installs
77 include BIND as a pkgsrc package.
79 +-----------------------------------------------------------------------+
80 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
82 +-----------------------------------------------------------------------+
84 Instructions on how to obtain and maintain DragonFly source code using git
85 are in the development(7) manual page.
87 To upgrade a DragonFly system from sources you run the following sequence:
91 make buildkernel KERNCONF=<KERNELNAME>
92 make installkernel KERNCONF=<KERNELNAME>
95 You will also want to run the 'upgrade' target to upgrade your /etc and the
96 rest of your system. The upgrade target is aware of stale files created by
97 older DragonFly installations and should delete them automatically.
101 See the build(7) manual page for further information.
103 Once you've done a full build of the world and kernel you can do incremental
104 upgrades of either by using the 'quickworld' and 'quickkernel' targets
105 instead of 'buildworld' and 'buildkernel'. If you have any problems with
106 the quick targets, try updating your repo first, and then a full buildworld
107 and buildkernel as shown above, before asking for help.
109 +-----------------------------------------------------------------------+
110 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
111 +-----------------------------------------------------------------------+
113 In 2.1 kernel and modules has moved to boot directory. For most cases
114 this is handled automatically by 'make upgrade'. A few cases needs manual
117 * When installing a kernel without first doing a make buildworld,
118 installworld and upgrade to the same DESTDIR as kernel:
119 make DESTDIR/boot directory and move kernel and modules into this boot
120 directory; also move kernel.old and modules.old.
121 Typical example is vkernel(7), use (no modules used):
125 chflags noschg kernel
126 mv kernel kernel.old boot
127 chflags schg boot/kernel
129 * When using a boot-only partition, /boot/loader.rc needs to be edited:
130 delete occurrences of '/boot/'.
131 These occurences can normally be deleted in any case, see loader(8).
133 +-----------------------------------------------------------------------+
134 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
135 +-----------------------------------------------------------------------+
137 In 1.9 major changes to the disk management infrastructure have taken
138 place. make upgrade may not catch all of your disk devices in /dev,
139 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
140 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
141 and MAKEDEV no longer exists.
143 The biggest changes in 1.9 are:
145 (1) That whole-slice devices such as da0s1 no longer share the same device
146 id as partition c devices such as da0s1c.
148 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
149 with no snooping or reserved sectors. Consequently you cannot run
150 disklabel on this device. Instead you must run disklabel on a
153 (3) The 'compatibility' partitions now use slice 0 in the device name,
154 so instead of da0a you must specify da0s0a. Also, as per (1) above,
155 accessing the disklabel for the compatibility partitions must be
156 done via slice 0 (da0s0).
158 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
159 and CCD now run through the disk management layer and are assigned
160 real disk management devices. VN and CCD in particular do not usually
161 use a MBR and disklabels must be accessed through the compatibility
162 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
163 don't name it 'ccd0s0' in the config file.
165 Generally speaking, you have to get used to running fdisk and disklabel on
166 the correctly specified device names. A lot of the wiggle, such as running
167 disklabel on a partition, has been removed.
169 +-----------------------------------------------------------------------+
170 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
171 +-----------------------------------------------------------------------+
176 Kerberos IV (eBones) was removed from the tree, please consider moving to
177 Kerberos 5 (Heimdal).
179 > Package Management System
180 ---------------------------
182 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
183 management system. The necessary tools to build and maintain packages
184 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
185 directories are in your PATH variable.
187 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
188 the tarball from NetBSD:
190 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
191 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
193 This tree can then be kept up to date with cvs update:
195 cd /usr/pkgsrc; cvs up
197 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
198 build and install the pkgsrc bootstrap manually:
200 cd /usr/pkgsrc/bootstrap
201 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
203 +-----------------------------------------------------------------------+
204 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
205 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
206 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
207 +-----------------------------------------------------------------------+
209 The compatibility shims for the build environment have been removed, you
210 have to update to DragonFly 1.2 release branch first.
212 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
213 The existing configuration can be converted using /etc/pam.d/convert.sh.
214 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
215 the pam_skey.so module was retired, you have to remove it manually from
216 your configuration, when you convert it.
218 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
219 ---------------------
221 The following users may be missing from your password file. Use vipw and
222 add any that are missing:
224 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
225 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
227 The following groups may be missing from your group file. Use vi /etc/group
228 and add any that are missing:
235 > Upgrading to DragonFly from FreeBSD
236 ---------------------
238 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
239 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
240 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
241 make depend information, it starts from scratch, so no pre-cleaning of the
242 object hierarchy is necessary.
244 # get the CVS repository (it is placed in /home/dcvs, 500MB).
245 # Please use the -h option and a mirror site to pull the
246 # initial repository, but feel free to use the main repository
247 # machine to pull updates.
248 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
249 # install the source from the CVS hierarchy (remove preexisting
250 # FreeBSD src first) (500MB)
253 cvs -R -d /home/dcvs checkout -P src
255 # build it (500MB used in /usr/obj)
259 make buildkernel KERNCONF=<KERNELNAME>
261 Once you have built DragonFly you have to install it over FreeBSD. Since
262 DragonFly does not track changes made by FreeBSD to its include file
263 hierarchy and include file pollution can cause all sorts of unexpected
264 compilation issues to come up, it is best to wipe your include hierarchy
265 prior to installing DragonFly. Note that you should not wipe any installed
266 FreeBSD header files or binaries until after you have successfully completed
267 the build steps above.
271 make installkernel KERNCONF=<KERNELNAME>
274 Then you need to upgrade your system. DragonFly's 'make upgrade' target
275 will unconditionally upgrade the /etc files that sysops do not usually
276 mess around with, such as the files in /etc/rc.d. It will also remove any
277 obsolete files such as utilities and manpages that have been removed from
278 the system since the version you're coming from. If you are unsure we
279 recommend that you make a backup of at least your /etc before applying
280 this step. Note that DragonFly's RC system is basically RCNG from
281 FreeBSD-5, but there are some differences in the contents of the RC files.
285 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
286 Doing so might leave your system in an unusable state.
288 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
289 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
290 report these files to the DragonFly developers so that they can be added to
291 the 'upgrade' target.