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