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 +-----------------------------------------------------------------------+
13 + UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
14 +-----------------------------------------------------------------------+
19 A new loader (dloader) has been added which better handles booting from
20 multiple kernel/module versions.
22 To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
28 make buildkernel KERNCONF=<KERNELNAME>
29 make installkernel KERNCONF=<KERNELNAME>
31 Note that you must installworld and run the 'upgrade' target before
32 installing the new kernel.
37 BIND has been removed from the base system. The ldns and drill tools have
38 been added for basic functionality. Use 'drill' where you would normally
39 use nslookup or dig, or install BIND from pkgsrc. It's available as
40 net/bind95, net/bind96, or net/bind97 as of this writing.
42 This only affects older systems upgrading to 2.8. New 2.8+ installs
43 include BIND as a pkgsrc package.
45 +-----------------------------------------------------------------------+
46 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
48 +-----------------------------------------------------------------------+
50 Instructions on how to obtain and maintain DragonFly source code using git
51 are in the development(7) manual page.
53 To upgrade a DragonFly system from sources you run the following sequence:
57 make buildkernel KERNCONF=<KERNELNAME>
58 make installkernel KERNCONF=<KERNELNAME>
61 You will also want to run the 'upgrade' target to upgrade your /etc and the
62 rest of your system. The upgrade target is aware of stale files created by
63 older DragonFly installations and should delete them automatically.
67 See the build(7) manual page for further information.
69 Once you've done a full build of the world and kernel you can do incremental
70 upgrades of either by using the 'quickworld' and 'quickkernel' targets
71 instead of 'buildworld' and 'buildkernel'. If you have any problems with
72 the quick targets, try updating your repo first, and then a full buildworld
73 and buildkernel as shown above, before asking for help.
75 +-----------------------------------------------------------------------+
76 + UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
77 +-----------------------------------------------------------------------+
79 In 2.1 kernel and modules has moved to boot directory. For most cases
80 this is handled automatically by 'make upgrade'. A few cases needs manual
83 * When installing a kernel without first doing a make buildworld,
84 installworld and upgrade to the same DESTDIR as kernel:
85 make DESTDIR/boot directory and move kernel and modules into this boot
86 directory; also move kernel.old and modules.old.
87 Typical example is vkernel(7), use (no modules used):
92 mv kernel kernel.old boot
93 chflags schg boot/kernel
95 * When using a boot-only partition, /boot/loader.rc needs to be edited:
96 delete occurrences of '/boot/'.
97 These occurences can normally be deleted in any case, see loader(8).
99 +-----------------------------------------------------------------------+
100 + UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
101 +-----------------------------------------------------------------------+
103 In 1.9 major changes to the disk management infrastructure have taken
104 place. make upgrade may not catch all of your disk devices in /dev,
105 so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
106 are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
107 and MAKEDEV no longer exists.
109 The biggest changes in 1.9 are:
111 (1) That whole-slice devices such as da0s1 no longer share the same device
112 id as partition c devices such as da0s1c.
114 (2) The whole-disk device (e.g. da0) is full raw access to the disk,
115 with no snooping or reserved sectors. Consequently you cannot run
116 disklabel on this device. Instead you must run disklabel on a
119 (3) The 'compatibility' partitions now use slice 0 in the device name,
120 so instead of da0a you must specify da0s0a. Also, as per (1) above,
121 accessing the disklabel for the compatibility partitions must be
122 done via slice 0 (da0s0).
124 (4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
125 and CCD now run through the disk management layer and are assigned
126 real disk management devices. VN and CCD in particular do not usually
127 use a MBR and disklabels must be accessed through the compatibility
128 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
129 don't name it 'ccd0s0' in the config file.
131 Generally speaking, you have to get used to running fdisk and disklabel on
132 the correctly specified device names. A lot of the wiggle, such as running
133 disklabel on a partition, has been removed.
135 +-----------------------------------------------------------------------+
136 + UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
137 +-----------------------------------------------------------------------+
142 Kerberos IV (eBones) was removed from the tree, please consider moving to
143 Kerberos 5 (Heimdal).
145 > Package Management System
146 ---------------------------
148 Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
149 management system. The necessary tools to build and maintain packages
150 are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
151 directories are in your PATH variable.
153 In order to obtain a reasonably current snapshot of the pkgsrc tree, use
154 the tarball from NetBSD:
156 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
157 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
159 This tree can then be kept up to date with cvs update:
161 cd /usr/pkgsrc; cvs up
163 NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
164 build and install the pkgsrc bootstrap manually:
166 cd /usr/pkgsrc/bootstrap
167 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
169 +-----------------------------------------------------------------------+
170 + UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
171 + UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
172 + DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
173 +-----------------------------------------------------------------------+
175 The compatibility shims for the build environment have been removed, you
176 have to update to DragonFly 1.2 release branch first.
178 The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
179 The existing configuration can be converted using /etc/pam.d/convert.sh.
180 Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
181 the pam_skey.so module was retired, you have to remove it manually from
182 your configuration, when you convert it.
184 > Required user and group IDs when upgrading from either FreeBSD or DragonFly
185 ---------------------
187 The following users may be missing from your password file. Use vipw and
188 add any that are missing:
190 smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
191 _pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
193 The following groups may be missing from your group file. Use vi /etc/group
194 and add any that are missing:
201 > Upgrading to DragonFly from FreeBSD
202 ---------------------
204 You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
205 FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
206 FreeBSD. Note that the DragonFly buildworld target does not try to reuse
207 make depend information, it starts from scratch, so no pre-cleaning of the
208 object hierarchy is necessary.
210 # get the CVS repository (it is placed in /home/dcvs, 500MB).
211 # Please use the -h option and a mirror site to pull the
212 # initial repository, but feel free to use the main repository
213 # machine to pull updates.
214 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
215 # install the source from the CVS hierarchy (remove preexisting
216 # FreeBSD src first) (500MB)
219 cvs -R -d /home/dcvs checkout -P src
221 # build it (500MB used in /usr/obj)
225 make buildkernel KERNCONF=<KERNELNAME>
227 Once you have built DragonFly you have to install it over FreeBSD. Since
228 DragonFly does not track changes made by FreeBSD to its include file
229 hierarchy and include file pollution can cause all sorts of unexpected
230 compilation issues to come up, it is best to wipe your include hierarchy
231 prior to installing DragonFly. Note that you should not wipe any installed
232 FreeBSD header files or binaries until after you have successfully completed
233 the build steps above.
237 make installkernel KERNCONF=<KERNELNAME>
240 Then you need to upgrade your system. DragonFly's 'make upgrade' target
241 will unconditionally upgrade the /etc files that sysops do not usually
242 mess around with, such as the files in /etc/rc.d. It will also remove any
243 obsolete files such as utilities and manpages that have been removed from
244 the system since the version you're coming from. If you are unsure we
245 recommend that you make a backup of at least your /etc before applying
246 this step. Note that DragonFly's RC system is basically RCNG from
247 FreeBSD-5, but there are some differences in the contents of the RC files.
251 NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
252 Doing so might leave your system in an unusable state.
254 Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
255 /usr/bin, and /usr/lib, and remove any stale files that you find. Please
256 report these files to the DragonFly developers so that they can be added to
257 the 'upgrade' target.