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