xref: /dragonfly/UPDATING (revision c07d5880)
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 5.0 TO LATER VERSIONS                +
13+-----------------------------------------------------------------------+
14
15VIRTIO_PCI REMOVED FROM KERNEL CONFIG
16-------------------------------------
17
18The "device virtio_pci" line in X86_64_GENERIC has been removed. People
19with configuration files derived from it have to remove it manually.
20
21VARIOUS 'R' COMMANDS AND DAEMONS REMOVED
22----------------------------------------
23
24rcp(1), rlogin(1), rlogind(8), rsh(1) and rshd(8) have been removed.
25For those that still need them, there is the net/bsdrcmds port.
26
27VARIOUS FORMER OPTIONS REMOVED
28------------------------------
29
30Various former kernel configuration options which had been no-ops for
31some time were completely removed: SYSVMSG, SYSVSEM, SYSVSHM, P1003_1B,
32_KPOSIX_VERSION and DSCHED_FQ. Users that have any of these still in
33their kernel configuration files have to remove them.
34
35BOOTSTRAPPING LIMITED FROM PRE 4.4
36----------------------------------
37
38Upgrading to 5.1 and later versions now require at least 4.4 in
39preparations for upcoming base compilers updates.
40
41IF_PPP, PPPD, IF_FAITH, AND FAITHD REMOVED
42------------------------------------------
43
44if_ppp has been replaced by "user ppp", i.e. ppp(8) and tun(4). It had
45already been removed from our default kernel configuration before 5.0,
46so only people with custom configurations based on earlier X86_64_GENERIC
47will have to remove it manually.
48
49The faith(4) interface has been completely removed after it had also
50been removed from our default kernel configuration.
51
52+-----------------------------------------------------------------------+
53+         UPGRADING DRAGONFLY FROM 4.8 TO LATER VERSIONS                +
54+-----------------------------------------------------------------------+
55
56FFS_ROOT OPTION DISABLED
57------------------------
58
59The FFS_ROOT option has been made a no-op and will be completely removed
60at some point in the future. Users with a custom kernel configuration
61can remove this option from it now.
62
63+-----------------------------------------------------------------------+
64+         UPGRADING DRAGONFLY FROM 4.6 TO LATER VERSIONS                +
65+-----------------------------------------------------------------------+
66
67AHC, AHD, AIC, NCV, NSP AND STG DRIVERS REMOVED
68-----------------------------------------------
69
70They were all in our X86_64_GENERIC kernel configuration file, along with
71the AHC_REG_PRETTY_PRINT and AHD_REG_PRETTY_PRINT options, so any custom
72configuration files derived from it need adjustment.
73
74PORTAL FILE SYSTEM REMOVED
75--------------------------
76
77It has been broken for a long time now.
78
79BINUTILS 2.27 REPLACES 2.24, PRIMARY
80------------------------------------
81
82The oldest of the two versions of Binutils, version 2.24, was removed
83and replaced with Binutils 2.27.  It becomes the primary version version
84of binutils and version 2.25 becomes the alternate.
85
86The accepted values of BINUTILSVER are now "binutils227" (default) and
87"binutils225".  The building of Binutils 2.25 can be prevented by setting
88NO_ALTBINUTILS=yes in make.conf.
89
90COMPAT_43 KERNEL OPTION REMOVED
91-------------------------------
92
93It was commented out in our default configs for several years now, but
94might still be present in custom configs created before Nov. 2011.
95
96OPENSSL REMOVED
97---------------
98
99OpenSSL has been removed from base and replaced with a private version of
100LibreSSL.  The previously installed OpenSSL libraries, headers, and man
101pages will remain on the system unless the "make upgrade" command is
102specifically instructed to remove them.  To do this, define
103REMOVE_OPENSSL_FILES for the upgrade command, e.g.
104"make upgrade REMOVE_OPENSSL_FILES=yes"
105
10628-Oct-2016: openssl has been replaced by ressl.  It is recommended that any
107stale OpenSSL files be removed to avoid configuration scripts from using
108the stale and potentially vulnerable version, but all binaries that are
109dynamically linked to the OpenSSL libraries should be rebuilt first to
110avoid breakage.
111
112OPENSSH HPN REMOVED
113-------------------
114
115It has become too cumbersome to maintain HPN patches in OpenSSH in base.
116To use OpenSSH in base remove HPN config, if you have added it.
117Check files below for HPN config, see a few lines below.
118  /etc/ssh/ssh_config, /etc/ssh/sshd_config, ~/.ssh/config
119sshd(8) will fail to start if HPN config is used.
120
121NOTE: HPN config in sshd_config will prohibit remote access to host using ssh.
122
123HPN config:
124HPNDisabled
125HPNBufferSize
126TcpRcvBuf
127TcpRcvBufPoll
128NoneEnabled
129NoneSwitch
130cipher MTR-AES-CTR
131cipher NONE
132
133OpenSSH HPN is a patch set to OpenSSH providing higher performance under some
134circumstances, especially for networking.
135If HPN functionality is needed, install security/openssh from dports.
136
137CS, EX AND VX DRIVERS REMOVED
138-----------------------------
139
140The cs(4), ex(4) and vx(4) drivers have been removed. They were very
141old and its doubtful they ever worked properly in x86_64 but they were
142in X86_64_GENERIC, so custom configurations derived from it have to be
143adjusted.
144
145+-----------------------------------------------------------------------+
146+         UPGRADING DRAGONFLY FROM 4.4 TO LATER VERSIONS                +
147+-----------------------------------------------------------------------+
148
149AMD REMOVED
150-----------
151
152The am-utils automounter suite has been removed. It stopped working
153at some point and was never fixed. autofs(5) and the associated
154userland has been brought in from FreeBSD and replaces it.
155
156AN DRIVER REMOVED
157-----------------
158
159The an(4) driver has been removed. It was in the X86_64_GENERIC kernel
160config file, so any configurations derived from it have to be adjusted.
161
162/DEV/DRI GROUP CHANGED
163----------------------
164
165The default group assigned to /dev/dri entries has been changed
166from 'wheel' to 'video' with the id of '44'. If you want to have
167access to the dri devices please add yourself to the video group
168with:
169
170# pw groupmod video -m $USER
171
172+-----------------------------------------------------------------------+
173+         UPGRADING DRAGONFLY FROM 4.2 TO LATER VERSIONS                +
174+-----------------------------------------------------------------------+
175
176DSCHED REMOVED
177--------------
178
179dsched(4) has been removed and one of its kernel options, DSCHED_FQ, was
180in our default kernel config file. So the DSCHED_FQ option has been turned
181into a no-op for now and can be removed from custom configurations.
182
183EST DRIVER REMOVED, COMPILE_ET AND LIBCOM_ERR TOO
184-------------------------------------------------
185
186The est(4) driver has been removed. All CPUs it supported (except one)
187were 32 bits only. Those who are still using the Core 2 Duo T7500 should
188report back if there are any issues with this CPU and our regular ACPI
189P-state support.
190
191Also, compile_et(1) and com_err(3) have been removed as well. They
192should have been removed along with kerberos support, back in 2009.
193
194SEVERAL LOCALES RENAMED
195-----------------------
196
197Several locales were using obsolete and misleading names, and thus have
198been adjusted to current standards. Any users of the following locales
199need to select alternates:
200
201DFLY 4.2 locale            DFLY 4.4 alterative locale
202---------------            ------------------------------------
203mn_MN.UTF-8                mn_Cyrl_MN.UTF-8
204no_NO.UTF-8                nb_NO.UTF-8      or nn_NO.UTF-8
205no_NO.ISO8859-1            nb_NO.ISO8869-1  or nn_NO.ISO8859-1
206no_NO.ISO8859-15           nb_NO.ISO8859-15 or nn_NO.ISO8859-15
207sr_YU.UTF-8                sr_Cyrl_RS.UTF-8 or sr_Latn_RS.UTF-8
208sr_YU.ISO8859-5            sr_Cyrl_RS.ISO8859-5
209sr_YU.ISO8859-2            sr_Latn_RS.ISO8859-2
210zh_CN.GBK                  zh_Hans_CN.GBK
211zh_CN.UTF-8                zh_Hans_CN.UTF-8
212zh_CN.eucCN                zh_Hans_CN.eucCN
213zh_CN.GB2312               zh_Hans_CH.GB2312
214zh_CN.GB18030              zh_Hans_CH.GB18030
215zh_HK.Big5HKSCS            zh_Hant_HK.Big5HKSCS
216zh_HK.UTF_8                zh_Hant_HK.UTF-8
217zh_TW.Big5                 zh_Hant_TW.Big5
218zh_TW.UTF-8                zh_Hant_TW.UTF-8
219
220+-----------------------------------------------------------------------+
221+         UPGRADING DRAGONFLY FROM 4.0 TO LATER VERSIONS                +
222+-----------------------------------------------------------------------+
223
224BINUTILS 2.25 REPLACES 2.22, PRIMARY
225------------------------------------
226
227The oldest of the two versions of Binutils, version 2.22, was removed
228and replaced with Binutils 2.25.  It becomes the primary version version
229of binutils and version 2.24 becomes the alternate.  There are 8 current
230CVE written against 2.24, so for security reasons version 2.25 should
231always be used.
232
233The accepted values of BINUTILSVER are now "binutils225" (default) and
234"binutils224".  The building of Binutils 2.24 can be prevented by setting
235NO_ALTBINUTILS=yes in make.conf.
236
237LOADER OPTIONS CHANGED
238----------------------
239
240Right after the development branch started, the Fred art accompanying the
241loader menu was improved.  The line between Fred and the menu was removed
242by default (but can optionally be returned) and the placement shifted as
243a result.  The drawing was improved, and the colored version was improved,
244changing the eyes and wing color from white to red.  A new color version
245of Fred was added, one with a blue scheme.
246
247The loader menu defaults have changed since release 4.0:  The vertical
248line was removed, the loader is displayed in color by default*, and the
249blue scheme is used.
250
251The loader.conf changes are:
252loader_color:   option has been removed
253loader_plain:   option has been added, it changed menu to monochrome
254fred_is_red:    changes color scheme from blue to red
255fred_is_blue:   option existed only on 4.1, it has been removed
256fred_separated: Adds line between Fred and menu (as seen previously)
257
258* If loader.conf defines "console" as "comconsole" or "console" is defined
259  in the environment as "comconsole" then color will not be displayed,
260  even if loader_plain value is "NO".
261
262SENDMAIL REMOVED FROM BASE
263--------------------------
264
265The only Mail Transfer Agent provided now is DragonFly Mail Agent (dma).
266If the system being upgraded is still configured to use the sendmail
267binaries from base, the "make upgrade" command will fail.
268
269The administrator must change /etc/mail/mailer.conf to switch the
270mailwrapper to dma or a DPorts-based MTA prior to running the upgrade
271command that permanently removes sendmail executables and could
272potentially break a running mail server.
273
274Refer: http://www.dragonflybsd.com/docs/docs/newhandbook/mta/ for
275detailed instructions on how to configure the MTA selection.
276
277_KPOSIX_VERSION and P1003_1B OPTIONS REMOVED
278--------------------------------------------
279
280The _KPOSIX_VERSION and P1003_1B kernel options have been changed to
281no-ops. They can be removed from custom kernel configurations.
282
283SOUND SYSTEM UPDATED FROM FreeBSD 11-CURRENT
284--------------------------------------------
285
286Many more sound devices may be detected.
287
288If the default device choosen isn't to your liking, setting the sysctl
289hw.snd.default_unit to a different number will change it.
290
291SCTP SUPPORT DROPPED
292--------------------
293
294Support for the SCTP protocol has been removed.
295
296OLD USB DRIVERS REMOVED
297-----------------------
298
299The old USB stack, along with the kernel config option "device oldusb"
300and the make.conf variable "WANT_OLDUSB" have been removed. This means
301that for custom kernel configuration files which were derived from a
302GENERIC or X86_64_GENERIC file prior to making the usb4bsd stack default,
303various (old USB stack specific) devices will now complain about being
304unknown:
305
306  * oldusb	(obviously)
307  * natausb	(not yet ported to usb4bsd)
308  * rue		(not yet ported to usb4bsd)
309  * ugen	(no longer needed in usb4bsd)
310  * urio	(not yet ported to usb4bsd)
311  * uscanner	(no longer needed in usb4bsd)
312
313They should be removed or commented out in such custom kernel configs.
314
315GCC 5
316-----
317
318The GCC 4.4 compiler has been retired.  It has been replaced by a GCC 5.1.
319The following make.conf variables no longer work: NO_GCC44, NO_OBJC, and
320NO_CXX.  The latter was never documented and the latest versions of GCC are
321partially written in C++ so a C++ compiler is no longer optional.  In
322practical terms it has not been optional for many years as other base
323components are also written in C++.  The resource savings by avoiding
324building Objective-C compiler is so small, the complexity added by NO_OBJC
325internally was deemed a bad tradeoff so that is the reason for its removal.
326Also note that no "info" pages are installed with GCC 5.  After this entry
327was originally written, all info pages were removed from DragonFly.
328
329GCC 5.1 has been designated as the primary compiler.  As such, there is a
330new make.conf variable, NO_ALTCOMPILER.  It will block the rebuilding of
331the designated secondary compiler, GCC 4.7.  However, while DPorts
332primarily uses GCC 5 to build ports now, it still uses GCC 4.7 as well, so
333if building ports from source is desired, don't block building of the
334secondary compiler.
335
336+-----------------------------------------------------------------------+
337+         UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS                +
338+-----------------------------------------------------------------------+
339
340SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
341-------------------------------------------
342
343DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
344the default now (even on single-core systems), both for, like, 21 months.
345We kept the options around as no-ops as a convenience, to allow people
346using the same config for the then current release and the then current
347master. That period is now over, so any configs still having those
348options have to be adjusted.
349
350SYSVIPC SYSCALLS MADE NON-OPTIONAL
351----------------------------------
352
353The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
354now compiled in by default. The options are no-ops for now.
355
356DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
357--------------------------------------------------------------------
358
359The default driver for those controllers is now mrsas(4) due to reports
360of file system corruption using the mfi(4) driver. The whole issue (and
361how to deal with potential problems when switching) was explained here:
362
363http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
364
365A tunable is provided for letting those controllers still attach via
366the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
367
368OLDER NETWORK DRIVERS MOVED TO I386 ONLY
369----------------------------------------
370
371The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
372and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
373removed in kernel configs derived from X86_64_GENERIC.
374
375+-----------------------------------------------------------------------+
376+         UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS                +
377+-----------------------------------------------------------------------+
378
379UPDATE FROM MOST RECENT 3.6
380---------------------------
381
382Versions of 3.6 built before June 25th have a bug where installworld might
383crash during installation of the new initrd.  Upgrade to the latest version
384of 3.6 before updating to 3.8 or later.
385
386ATM, IPX, NCP AND NWFS SUPPORT DROPPED
387--------------------------------------
388
389Support for the IPX and NCP network protocols and for mouting NetWare
390file systems has been dropped. Dito for ATM protocol support.
391
392INITRD IMAGES NOW INSTALLED BY DEFAULT
393--------------------------------------
394
395An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
396
397Older images installed under the file name of initrd.img will be removed
398automatically by the make upgrade process.
399
400USB4BSD IS NOW THE DEFAULT USB STACK
401------------------------------------
402
403To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
404replace "device usb" with "device oldusb" in the kernel configuration.
405
406MORE ISA SUPPORT DROPPED
407------------------------
408
409ISA support has been dropped from the following drivers: adv(4), an(4),
410ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
411si(4), sn(4), and stg(4).
412
413+-----------------------------------------------------------------------+
414+         UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS                +
415+-----------------------------------------------------------------------+
416
417ABI CHANGE
418----------
419
420Installed third-party software (dports) will have to be rebuilt after upgrade,
421or reinstalled from binary packages.
422
423UPDATING FROM 3.4 TO 3.6
424------------------------
425
426This only applies for this specific upgrade due to locale changes; it is
427not needed for upgrades after 3.6.  Please update in this order:
428
429make buildworld
430make buildkernel
431make installworld
432make installkernel
433*reboot*
434make upgrade
435
436See this mailing list post for details:
437http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
438
439CYRIX OPTIONS REMOVED
440---------------------
441
442The following Cyrix related options have been removed: CPU_BTB_EN,
443CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
444CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
445CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
446
447ISA SUPPORT REMOVED FROM RP(4)
448------------------------------
449
450ISA support has been removed from the rp(4) driver. It is now PCI only.
451
452+-----------------------------------------------------------------------+
453+         UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS                +
454+-----------------------------------------------------------------------+
455
456COMPAT_SUNOS OPTION REMOVED
457---------------------------
458
459The COMPAT_SUNOS option has been removed. It was meant to provide binary
460compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
461
462ISA SOUND CARD SUPPORT REMOVED
463------------------------------
464
465The following modules have been removed (all for ISA sound cards):
466snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
467
468GCC 4.7
469-------
470
471DragonFly has switched base compilers.  GCC 4.7 is now the default
472compiler and GCC 4.4 is the alternative compiler.  The "NO_GCC47" make
473variable ceases to work now.
474
475Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
476/etc/make.conf to prohibit GCC 4.4 from building.  However, using it is
477highly discouraged.  There are a few packages in pkgsrc that do not build
478with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default.  At
479this time, it is recommended to keep both compilers on the base system.
480
481SMP OPTION REMOVED
482------------------
483
484The SMP kernel option has been made a no-op. All kernels now feature SMP
485support. If you have 'options SMP' in your kernel config, you can as well
486remove it.
487
488DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
489---------------------------------------------------------------------------
490
491The DEVICE_POLLING kernel option has been made a no-op and it has been
492replaced by IFPOLL_ENABLE.  If you have 'options DEVICE_POLLING' in your
493kernel config, you need to change it to IFPOLL_ENABLE.
494
495Also, the KTR_POLLING kernel option has been removed, so it must be
496removed from kernel configs that have it.
497
498BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
499---------------------------------------------------
500
501The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
502cards will no longer be detected.
503
504The same has been done for Stallion multiport serial controllers. stli(4)
505has been completely removed (along with the stlload(8) and stlstty(8)
506utilities) and stl(4) was changed to support only PCI cards. Similarly,
507ISA support was removed from cy(4) too. All these drivers are i386 only.
508
509COMPAT_OLDISA OPTION GONE
510-------------------------
511
512The i386 specific COMPAT_OLDISA kernel option has been removed, since
513nothing needs it anymore.
514
515+-----------------------------------------------------------------------+
516+         UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS                +
517+-----------------------------------------------------------------------+
518
519APIC_IO OPTION REMOVED
520----------------------
521
522The APIC_IO kernel option is no longer accepted after having been without
523effect for a while. The hw.ioapic_enable tunable now serves its purpose.
524If you have 'options APIC_IO' in your kernel config, you'll have to
525remove it.
526
527WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
528-----------------------------------------
529
530The wdog framework is now compiled into our kernels by default, so the
531options are no longer needed.
532
533DOSCMD(1) REMOVED
534-----------------
535
536doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
537NO_X make.conf option was removed too.
538
539GCC 4.7
540-------
541
542GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
543default compiler in base (default is still GCC 4.4).
544
545Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
546NO_GCC47 in /etc/make.conf.
547
548USB4BSD
549-------
550
551A new USB stack (from FreeBSD) has been brought in. The following
552modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
553usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
554and uaudio.
555
556It is not yet the default. To activate it, WANT_USB4BSD=yes has to
557be put in make.conf and device "usb4bsd" (quotes needed) has to
558replace device usb in the kernel config. After that, a full
559build/install/upgrade cycle is needed.
560
561Note that this is experimental and incomplete, but we are interested
562in hearing about issues with it, of course.
563
564ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
565---------------------------------------------
566
567ISA adapter support was dropped from the aic(4) driver.
568
569+-----------------------------------------------------------------------+
570+         UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS               +
571+-----------------------------------------------------------------------+
572
573SEVERAL ISA DRIVERS REMOVED
574---------------------------
575
576The following ISA only drivers have been removed along with a couple of
577associated userland tools:
578
579aha(4)
580asc(4) & sasc(1)
581ctx
582dgb(4)
583el(4)
584gpib
585gsc(4) & sgsc(1)
586ie(4)
587labpc(4)
588le(4)
589mse(4)
590rc(4)
591rdp(4)
592spigot
593tw(4) & xten(1) & xtend(8)
594wl(4) & wlconfig(8)
595wt(4)
596
597Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
598config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
599file.
600
601If buildkernel complains about any of these drivers, just remove them
602from your kernel configuration.
603
604BINUTILS 2.20
605-------------
606Binutils 2.20 has been removed in favor of Binutils 2.22.  The accepted
607values of BINUTILSVERS are now binutils221 and binutils222 (default).
608
609BUILDWORLD/-KERNEL PARALLELIZATION WORK
610---------------------------------------
611Due to changes in the way we build with more than one make job, you
612will have to update install(1) and mkdir(1) prior to buildworld if you
613want to build with 'make -j':
614
615cd /usr/src/usr.bin/xinstall; make; make install; make clean
616cd /usr/src/bin/mkdir; make; make install; make clean
617
618DMA(8) UPGRADE
619--------------
620dma(8) has been upgraded to v0.7 which no longer supports the
621/etc/dma/virtusertable. Some of its functionality has been replaced
622with the MASQUERADE keyword and the EMAIL environment variable (see
623the dma(8) manual page).
624
625+-----------------------------------------------------------------------+
626+         UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS                +
627+-----------------------------------------------------------------------+
628
629GCC 4.4 & BINUTILS 2.21
630-----------------------
631
632GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
633been made DragonFly's default Binutils.
634
635That means that any settings that set CCVER to 'gcc44' are not needed
636anymore. Instead, CCVER can be set to 'gcc41' to go back to using
637GCC 4.1.
638
639It also means that 'binutils221' as a value for BINUTILSVER has no
640effect anymore. 2.17 has been removed and 'binutils220' is available
641as an option.
642
643The NO_GCC44 option has been removed and will not affect the build
644anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
645building in a similar fashion.
646
647Note that you must do a full buildworld/buildkernel for upgrading.
648
649pkg_radd settings
650-----------------
651
652The config file for pkg_radd has moved from /etc/settings.conf to
653/etc/pkg_radd.conf.  Save the contents of settings.conf before upgrading
654if this is needed.  This warning only applies if /etc/settings.conf
655exists.  pkg_radd will continue to work with defaults.
656
657+-----------------------------------------------------------------------+
658+         20100927							+
659+         UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD			+
660+-----------------------------------------------------------------------+
661
662OpenSSL
663--------
664
665OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
666This shouldn't break any 3rd-party software, but you'll need to recompile your
6673rd-party software if you want it to link against the new version of OpenSSL.
668
669Loader
670-------
671
672A new loader (dloader) has been added which better handles booting from
673multiple kernel/module versions.
674
675To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
676
677	cd /usr/src
678	make buildworld
679	make installworld
680	make upgrade
681	make buildkernel KERNCONF=<KERNELNAME>
682	make installkernel KERNCONF=<KERNELNAME>
683
684Note that you must installworld and run the 'upgrade' target before
685installing the new kernel.
686
687BIND
688-----
689
690BIND has been removed from the base system.  The ldns and drill tools have
691been added for basic functionality.  Use 'drill' where you would normally
692use nslookup or dig, or install BIND from pkgsrc.  It's available as
693net/bind95, net/bind96, or net/bind97 as of this writing.
694
695This only affects older systems upgrading to 2.8.  New 2.8+ installs
696include BIND as a pkgsrc package.
697
698+-----------------------------------------------------------------------+
699+         UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM		+
700+				GENERAL					+
701+-----------------------------------------------------------------------+
702
703Instructions on how to obtain and maintain DragonFly source code using git
704are in the development(7) manual page.
705
706To upgrade a DragonFly system from sources you run the following sequence:
707
708	cd /usr/src
709	make buildworld
710	make buildkernel KERNCONF=<KERNELNAME>
711	make installkernel KERNCONF=<KERNELNAME>
712	make installworld
713
714You will also want to run the 'upgrade' target to upgrade your /etc and the
715rest of your system.  The upgrade target is aware of stale files created by
716older DragonFly installations and should delete them automatically.
717
718	make upgrade
719
720See the build(7) manual page for further information.
721
722Once you've done a full build of the world and kernel you can do incremental
723upgrades of either by using the 'quickworld' and 'quickkernel' targets
724instead of 'buildworld' and 'buildkernel'.  If you have any problems with
725the quick targets, try updating your repo first, and then a full buildworld
726and buildkernel as shown above, before asking for help.
727
728+-----------------------------------------------------------------------+
729+         UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1		+
730+-----------------------------------------------------------------------+
731
732In 2.1 kernel and modules has moved to boot directory.  For most cases
733this is handled automatically by 'make upgrade'.  A few cases needs manual
734intervention:
735
736 * When installing a kernel without first doing a make buildworld,
737   installworld and upgrade to the same DESTDIR as kernel:
738   make DESTDIR/boot directory and move kernel and modules into this boot
739   directory; also move kernel.old and modules.old.
740   Typical example is vkernel(7), use (no modules used):
741
742	cd /var/vkernel
743	mkdir boot
744	chflags noschg kernel
745	mv kernel kernel.old boot
746	chflags schg boot/kernel
747
748 * When using a boot-only partition, /boot/loader.rc needs to be edited:
749   delete occurrences of '/boot/'.
750   These occurences can normally be deleted in any case, see loader(8).
751
752+-----------------------------------------------------------------------+
753+         UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9		+
754+-----------------------------------------------------------------------+
755
756In 1.9 major changes to the disk management infrastructure have taken
757place.  make upgrade may not catch all of your disk devices in /dev,
758so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
759are all of your disk devices.  HOWEVER, from late 2.3 on we run devfs
760and MAKEDEV no longer exists.
761
762The biggest changes in 1.9 are:
763
764(1) That whole-slice devices such as da0s1 no longer share the same device
765    id as partition c devices such as da0s1c.
766
767(2) The whole-disk device (e.g. da0) is full raw access to the disk,
768    with no snooping or reserved sectors.  Consequently you cannot run
769    disklabel on this device.  Instead you must run disklabel on a
770    whole-slice device.
771
772(3) The 'compatibility' partitions now use slice 0 in the device name,
773    so instead of da0a you must specify da0s0a.  Also, as per (1) above,
774    accessing the disklabel for the compatibility partitions must be
775    done via slice 0 (da0s0).
776
777(4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
778    and CCD now run through the disk management layer and are assigned
779    real disk management devices.   VN and CCD in particular do not usually
780    use a MBR and disklabels must be accessed through the compatibility
781    slice 0.  Your /etc/ccd.conf file still specifies 'ccd0', though, you
782    don't name it 'ccd0s0' in the config file.
783
784Generally speaking, you have to get used to running fdisk and disklabel on
785the correctly specified device names.  A lot of the wiggle, such as running
786disklabel on a partition, has been removed.
787
788+-----------------------------------------------------------------------+
789+         UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD		+
790+-----------------------------------------------------------------------+
791
792> Kerberos IV
793-------------
794
795Kerberos IV (eBones) was removed from the tree, please consider moving to
796Kerberos 5 (Heimdal).
797
798> Package Management System
799---------------------------
800
801Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
802management system.  The necessary tools to build and maintain packages
803are provided in /usr/pkg/bin and /usr/pkg/sbin.  Make sure that these
804directories are in your PATH variable.
805
806In order to obtain a reasonably current snapshot of the pkgsrc tree, use
807the tarball from NetBSD:
808
809	fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
810	cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
811
812This tree can then be kept up to date with cvs update:
813
814	cd /usr/pkgsrc; cvs up
815
816NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
817build and install the pkgsrc bootstrap manually:
818
819	cd /usr/pkgsrc/bootstrap
820	./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
821
822+-----------------------------------------------------------------------+
823+         UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM		+
824+         UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO               +
825+         DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD)                       +
826+-----------------------------------------------------------------------+
827
828The compatibility shims for the build environment have been removed, you
829have to update to DragonFly 1.2 release branch first.
830
831The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
832The existing configuration can be converted using /etc/pam.d/convert.sh.
833Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
834the pam_skey.so module was retired, you have to remove it manually from
835your configuration, when you convert it.
836
837> Required user and group IDs when upgrading from either FreeBSD or DragonFly
838---------------------
839
840The following users may be missing from your password file.  Use vipw and
841add any that are missing:
842
843smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
844_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
845
846The following groups may be missing from your group file.  Use vi /etc/group
847and add any that are missing:
848
849smmsp:*:25:
850authpf:*:63:
851_pflogd:*:64:
852
853
854> Upgrading to DragonFly from FreeBSD
855---------------------
856
857You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
858FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
859FreeBSD.  Note that the DragonFly buildworld target does not try to reuse
860make depend information, it starts from scratch, so no pre-cleaning of the
861object hierarchy is necessary.
862
863	# get the CVS repository (it is placed in /home/dcvs, 500MB).
864	# Please use the -h option and a mirror site to pull the
865	# initial repository, but feel free to use the main repository
866	# machine to pull updates.
867	cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
868	# install the source from the CVS hierarchy (remove preexisting
869	# FreeBSD src first) (500MB)
870	cd /usr
871	rm -rf src
872	cvs -R -d /home/dcvs checkout -P src
873
874	# build it (500MB used in /usr/obj)
875	#
876	cd /usr/src
877	make buildworld
878	make buildkernel KERNCONF=<KERNELNAME>
879
880Once you have built DragonFly you have to install it over FreeBSD.  Since
881DragonFly does not track changes made by FreeBSD to its include file
882hierarchy and include file pollution can cause all sorts of unexpected
883compilation issues to come up, it is best to wipe your include hierarchy
884prior to installing DragonFly.  Note that you should not wipe any installed
885FreeBSD header files or binaries until after you have successfully completed
886the build steps above.
887
888	rm -rf /usr/include
889	mkdir /usr/include
890	make installkernel KERNCONF=<KERNELNAME>
891	make installworld
892
893Then you need to upgrade your system.  DragonFly's 'make upgrade' target
894will unconditionally upgrade the /etc files that sysops do not usually
895mess around with, such as the files in /etc/rc.d.  It will also remove any
896obsolete files such as utilities and manpages that have been removed from
897the system since the version you're coming from.  If you are unsure we
898recommend that you make a backup of at least your /etc before applying
899this step.  Note that DragonFly's RC system is basically RCNG from
900FreeBSD-5, but there are some differences in the contents of the RC files.
901
902	make upgrade
903
904NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
905Doing so might leave your system in an unusable state.
906
907Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
908/usr/bin, and /usr/lib, and remove any stale files that you find.  Please
909report these files to the DragonFly developers so that they can be added to
910the 'upgrade' target.
911
912