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