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