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