gcc50: Update to release version 5.1.0 => 5.1.1
[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
2a617999
SW
11+-----------------------------------------------------------------------+
12+ UPGRADING DRAGONFLY FROM 4.0 TO LATER VERSIONS +
13+-----------------------------------------------------------------------+
14
65c3b857
JM
15BINUTILS 2.25 REPLACES 2.22, PRIMARY
16------------------------------------
17
18The oldest of the two versions of Binutils, version 2.22, was removed
19and replaced with Binutils 2.25. It becomes the primary version version
20of binutils and version 2.24 becomes the alternate. There are 8 current
21CVE written against 2.24, so for security reasons version 2.25 should
22always be used.
23
24The accepted values of BINUTILSVER are now "binutils225" (default) and
25"binutils224". The building of Binutils 2.24 can be prevented by setting
26NO_ALTBINUTILS=yes in make.conf.
27
72b78560
JM
28LOADER OPTIONS CHANGED
29----------------------
30
31Right after the development branch started, the Fred art accompanying the
32loader menu was improved. The line between Fred and the menu was removed
33by default (but can optionally be returned) and the placement shifted as
34a result. The drawing was improved, and the colored version was improved,
35changing the eyes and wing color from white to red. A new color version
36of Fred was added, one with a blue scheme.
37
38The loader menu defaults have changed since release 4.0: The vertical
39line was removed, the loader is displayed in color by default*, and the
40blue scheme is used.
41
42The loader.conf changes are:
43loader_color: option has been removed
44loader_plain: option has been added, it changed menu to monochrome
45fred_is_red: changes color scheme from blue to red
46fred_is_blue: option existed only on 4.1, it has been removed
47fred_separated: Adds line between Fred and menu (as seen previously)
48
49* If loader.conf defines "console" as "comconsole" or "console" is defined
50 in the environment as "comconsole" then color will not be displayed,
51 even if loader_plain value is "NO".
52
cbab4ab1
JM
53SENDMAIL REMOVED FROM BASE
54--------------------------
55
56The only Mail Transfer Agent provided now is DragonFly Mail Agent (dma).
57If the system being upgraded is still configured to use the sendmail
58binaries from base, the "make upgrade" command will fail.
59
60The administrator must change /etc/mail/mailer.conf to switch the
61mailwrapper to dma or a DPorts-based MTA prior to running the upgrade
62command that permanently removes sendmail executables and could
63potentially break a running mail server.
64
65Refer: http://www.dragonflybsd.com/docs/docs/newhandbook/mta/ for
66detailed instructions on how to configure the MTA selection.
67
a7ac1ee9
SW
68_KPOSIX_VERSION and P1003_1B OPTIONS REMOVED
69--------------------------------------------
70
71The _KPOSIX_VERSION and P1003_1B kernel options have been changed to
72no-ops. They can be removed from custom kernel configurations.
73
aa7c3d6b
FT
74SOUND SYSTEM UPDATED FROM FreeBSD 11-CURRENT
75--------------------------------------------
76
77Many more sound devices may be detected.
78
79If the default device choosen isn't to your liking, setting the sysctl
80hw.snd.default_unit to a different number will change it.
81
60a260ad
SW
82SCTP SUPPORT DROPPED
83--------------------
84
85Support for the SCTP protocol has been removed.
86
2a617999
SW
87OLD USB DRIVERS REMOVED
88-----------------------
89
90The old USB stack, along with the kernel config option "device oldusb"
91and the make.conf variable "WANT_OLDUSB" have been removed. This means
92that for custom kernel configuration files which were derived from a
93GENERIC or X86_64_GENERIC file prior to making the usb4bsd stack default,
94various (old USB stack specific) devices will now complain about being
95unknown:
96
97 * oldusb (obviously)
98 * natausb (not yet ported to usb4bsd)
99 * rue (not yet ported to usb4bsd)
100 * ugen (no longer needed in usb4bsd)
101 * urio (not yet ported to usb4bsd)
102 * uscanner (no longer needed in usb4bsd)
103
104They should be removed or commented out in such custom kernel configs.
105
e9b676f1
JM
106GCC 5.0
107-------
108
109The GCC 4.4 compiler has been retired. It has been replaced by a
110[prerelease] version of GCC 5.0. The following make.conf variables no
111longer work: NO_GCC44, NO_OBJC, and NO_CXX. The latter was never
112documented and the latest versions of GCC are partially written in C++
113so a C++ compiler is no longer optional. In practical terms it has not
114been optional for many years as other base components are also written in
115C++. The resource savings by avoiding building Objective-C compiler is
116so small, the complexity added by NO_OBJC internally was deemed a bad
117tradeoff so that is the reason for its removal. Also note that no "info"
118pages are installed with GCC 5.0. This is intentional; they are available
119via the internet if desired over the installed man pages.
120
121Currently, GCC 4.7 is still designated as the primary compiler. After
122GCC 5.0 is released, this may change and these update notes will be
123revised accordingly. DPorts will use GCC 5.0 on this release regardless.
124If GCC 5.0 is unwanted, the make.conf variable NO_GCC50 will block its
125building and installation.
126
127To use GCC 5.0 to build world and kernel, set WORLD_CCVER=gcc50 in
128make.conf before building those targets.
129
0055c35b
SW
130+-----------------------------------------------------------------------+
131+ UPGRADING DRAGONFLY FROM 3.8 TO LATER VERSIONS +
132+-----------------------------------------------------------------------+
133
2a617999 134SMP AND DEVICE_POLLING OPTIONS MADE UNKNOWN
39b3e0a1
SW
135-------------------------------------------
136
137DEVICE_POLLING was replaced by IFPOLL_ENABLE and the former SMP code is
138the default now (even on single-core systems), both for, like, 21 months.
139We kept the options around as no-ops as a convenience, to allow people
140using the same config for the then current release and the then current
141master. That period is now over, so any configs still having those
142options have to be adjusted.
143
10ceb702
SW
144SYSVIPC SYSCALLS MADE NON-OPTIONAL
145----------------------------------
146
147The code related to the SYSVMSG, SYSVSEM and SYSVSHM kernel options is
148now compiled in by default. The options are no-ops for now.
149
79a3e83f
SW
150DEFAULT DRIVER CHANGED FOR LSI "THUNDERBOLT" SERIES RAID CONTROLLERS
151--------------------------------------------------------------------
152
153The default driver for those controllers is now mrsas(4) due to reports
154of file system corruption using the mfi(4) driver. The whole issue (and
155how to deal with potential problems when switching) was explained here:
156
157http://lists.dragonflybsd.org/pipermail/users/2014-July/128703.html
158
159A tunable is provided for letting those controllers still attach via
160the mfi(4) driver, hw.mrsas.mfi_enable (see mrsas(4) manual page).
161
0055c35b
SW
162OLDER NETWORK DRIVERS MOVED TO I386 ONLY
163----------------------------------------
164
165The following drivers have been made i386 only: ed(4), sr(4), ng_sync_ar
166and ng_sync_sr. ed(4) used to be in X86_64_GENERIC, so it has to be
167removed in kernel configs derived from X86_64_GENERIC.
168
e19e3c77 169+-----------------------------------------------------------------------+
62d4130d 170+ UPGRADING DRAGONFLY FROM 3.6 TO LATER VERSIONS +
e19e3c77
SW
171+-----------------------------------------------------------------------+
172
a6a7c140
JS
173UPDATE FROM MOST RECENT 3.6
174---------------------------
175
176Versions of 3.6 built before June 25th have a bug where installworld might
177crash during installation of the new initrd. Upgrade to the latest version
178of 3.6 before updating to 3.8 or later.
179
7c87aae6
SW
180ATM, IPX, NCP AND NWFS SUPPORT DROPPED
181--------------------------------------
6f25d555
SW
182
183Support for the IPX and NCP network protocols and for mouting NetWare
7c87aae6 184file systems has been dropped. Dito for ATM protocol support.
6f25d555
SW
185
186INITRD IMAGES NOW INSTALLED BY DEFAULT
187--------------------------------------
188
189An initial ramdisk image is now installed in /boot/kernel/initrd.img.gz
190
191Older images installed under the file name of initrd.img will be removed
192automatically by the make upgrade process.
193
f0478b8b
SW
194USB4BSD IS NOW THE DEFAULT USB STACK
195------------------------------------
196
197To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
198replace "device usb" with "device oldusb" in the kernel configuration.
199
e19e3c77
SW
200MORE ISA SUPPORT DROPPED
201------------------------
202
203ISA support has been dropped from the following drivers: adv(4), an(4),
204ar(4), cs(4), digi(4), ed(4), ep(4), ex(4), fe(4), lnc(4), sbni(4),
205si(4), sn(4), and stg(4).
206
9332798a 207+-----------------------------------------------------------------------+
62d4130d 208+ UPGRADING DRAGONFLY FROM 3.4 TO LATER VERSIONS +
9332798a
SW
209+-----------------------------------------------------------------------+
210
c04df145
JS
211ABI CHANGE
212----------
213
214Installed third-party software (dports) will have to be rebuilt after upgrade,
215or reinstalled from binary packages.
216
2b455b95
JS
217UPDATING FROM 3.4 TO 3.6
218------------------------
219
220This only applies for this specific upgrade due to locale changes; it is
221not needed for upgrades after 3.6. Please update in this order:
222
223make buildworld
224make buildkernel
225make installworld
226make installkernel
227*reboot*
228make upgrade
229
230See this mailing list post for details:
231http://lists.dragonflybsd.org/pipermail/users/2013-September/090163.html
232
9332798a
SW
233CYRIX OPTIONS REMOVED
234---------------------
235
236The following Cyrix related options have been removed: CPU_BTB_EN,
237CPU_CYRIX_NO_LOCK, CPU_DIRECT_MAPPED_CACHE, CPU_DISABLE_5X86_LSSER,
238CPU_FASTER_5X86_FPU, CPU_IORT, CPU_LOOP_EN, CPU_RSTK_EN, CPU_SUSP_HLT,
239CYRIX_CACHE_WORKS, and CYRIX_CACHE_REALLY_WORKS
240
241ISA SUPPORT REMOVED FROM RP(4)
242------------------------------
243
244ISA support has been removed from the rp(4) driver. It is now PCI only.
245
64aeb497 246+-----------------------------------------------------------------------+
62d4130d 247+ UPGRADING DRAGONFLY FROM 3.2 TO LATER VERSIONS +
64aeb497
SW
248+-----------------------------------------------------------------------+
249
d88b9605
SW
250COMPAT_SUNOS OPTION REMOVED
251---------------------------
252
253The COMPAT_SUNOS option has been removed. It was meant to provide binary
254compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
255
43f215d7
SW
256ISA SOUND CARD SUPPORT REMOVED
257------------------------------
258
259The following modules have been removed (all for ISA sound cards):
260snd_ad1816.ko, snd_ess.ko, snd_mss.ko, snd_sb8.ko, snd_sb16.ko, snd_sbc.ko
261
6100d1de
JM
262GCC 4.7
263-------
264
265DragonFly has switched base compilers. GCC 4.7 is now the default
266compiler and GCC 4.4 is the alternative compiler. The "NO_GCC47" make
267variable ceases to work now.
268
269Users who wish to build only GCC 4.7 have to use NO_GCC44 in the
270/etc/make.conf to prohibit GCC 4.4 from building. However, using it is
271highly discouraged. There are a few packages in pkgsrc that do not build
272with GCC 4.7 and the new "DPorts" system uses GCC 4.4 by default. At
273this time, it is recommended to keep both compilers on the base system.
274
2089bb7c
SW
275SMP OPTION REMOVED
276------------------
277
278The SMP kernel option has been made a no-op. All kernels now feature SMP
279support. If you have 'options SMP' in your kernel config, you can as well
280remove it.
281
1c297ed0
SW
282DEVICE_POLLING OPTION REPLACED BY IFPOLL_ENABLE OPTION, KTR_POLLING REMOVED
283---------------------------------------------------------------------------
640dc18f
SZ
284
285The DEVICE_POLLING kernel option has been made a no-op and it has been
286replaced by IFPOLL_ENABLE. If you have 'options DEVICE_POLLING' in your
287kernel config, you need to change it to IFPOLL_ENABLE.
288
1c297ed0
SW
289Also, the KTR_POLLING kernel option has been removed, so it must be
290removed from kernel configs that have it.
291
558b0a0b
SW
292BUSLOGIC, CYCLADES AND STALLION ISA SUPPORT REMOVED
293---------------------------------------------------
850c4634
SW
294
295The bt(4) driver for Buslogic SCSI adapters has been made PCI only. ISA
296cards will no longer be detected.
297
e6f626a1
SW
298The same has been done for Stallion multiport serial controllers. stli(4)
299has been completely removed (along with the stlload(8) and stlstty(8)
558b0a0b
SW
300utilities) and stl(4) was changed to support only PCI cards. Similarly,
301ISA support was removed from cy(4) too. All these drivers are i386 only.
e6f626a1 302
e98bcb27
SW
303COMPAT_OLDISA OPTION GONE
304-------------------------
305
306The i386 specific COMPAT_OLDISA kernel option has been removed, since
307nothing needs it anymore.
308
c691bb43 309+-----------------------------------------------------------------------+
62d4130d 310+ UPGRADING DRAGONFLY FROM 3.0 TO LATER VERSIONS +
c691bb43
SW
311+-----------------------------------------------------------------------+
312
313APIC_IO OPTION REMOVED
314----------------------
315
316The APIC_IO kernel option is no longer accepted after having been without
317effect for a while. The hw.ioapic_enable tunable now serves its purpose.
318If you have 'options APIC_IO' in your kernel config, you'll have to
319remove it.
320
6d488cc3
SW
321WATCHDOG_ENABLE & HW_WDOG OPTIONS REMOVED
322-----------------------------------------
cf03d6cd
SW
323
324The wdog framework is now compiled into our kernels by default, so the
6d488cc3 325options are no longer needed.
cf03d6cd 326
397ffc5c
SW
327DOSCMD(1) REMOVED
328-----------------
329
330doscmd(1) has been removed. It was i386 only. The doscmd(1) specific
331NO_X make.conf option was removed too.
332
a1404d4f
SW
333GCC 4.7
334-------
335
336GCC 4.7 has been brought in and replaces GCC 4.1 as DragonFly's non-
337default compiler in base (default is still GCC 4.4).
338
339Users who wish to build only GCC 4.4 have to replace NO_GCC41 with
340NO_GCC47 in /etc/make.conf.
341
2508820f
SW
342USB4BSD
343-------
344
345A new USB stack (from FreeBSD) has been brought in. The following
346modules have been ported so far: usb, uhci, ohci, ehci, xhci, umass,
347usfs, uether, if_axe, if_udav, ukbd, ums, uep, uhid, usb_quirk,
348and uaudio.
349
350It is not yet the default. To activate it, WANT_USB4BSD=yes has to
c7200221
SW
351be put in make.conf and device "usb4bsd" (quotes needed) has to
352replace device usb in the kernel config. After that, a full
353build/install/upgrade cycle is needed.
2508820f
SW
354
355Note that this is experimental and incomplete, but we are interested
356in hearing about issues with it, of course.
357
ae0870a3
SW
358ISA SUPPORT REMOVED FROM AIC-6260/6360 DRIVER
359---------------------------------------------
360
361ISA adapter support was dropped from the aic(4) driver.
362
96386d4b 363+-----------------------------------------------------------------------+
62d4130d 364+ UPGRADING DRAGONFLY FROM 2.10 TO LATER VERSIONS +
96386d4b
SW
365+-----------------------------------------------------------------------+
366
367SEVERAL ISA DRIVERS REMOVED
368---------------------------
369
370The following ISA only drivers have been removed along with a couple of
371associated userland tools:
372
373aha(4)
374asc(4) & sasc(1)
375ctx
376dgb(4)
377el(4)
378gpib
379gsc(4) & sgsc(1)
380ie(4)
381labpc(4)
382le(4)
383mse(4)
384rc(4)
385rdp(4)
386spigot
387tw(4) & xten(1) & xtend(8)
388wl(4) & wlconfig(8)
389wt(4)
390
391Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
392config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
393file.
394
395If buildkernel complains about any of these drivers, just remove them
396from your kernel configuration.
397
919eb219
JM
398BINUTILS 2.20
399-------------
37c5a0db 400Binutils 2.20 has been removed in favor of Binutils 2.22. The accepted
e685772e 401values of BINUTILSVERS are now binutils221 and binutils222 (default).
919eb219 402
83bc1e2a
SW
403BUILDWORLD/-KERNEL PARALLELIZATION WORK
404---------------------------------------
405Due to changes in the way we build with more than one make job, you
406will have to update install(1) and mkdir(1) prior to buildworld if you
407want to build with 'make -j':
408
409cd /usr/src/usr.bin/xinstall; make; make install; make clean
410cd /usr/src/bin/mkdir; make; make install; make clean
411
eca86bd9
SW
412DMA(8) UPGRADE
413--------------
414dma(8) has been upgraded to v0.7 which no longer supports the
415/etc/dma/virtusertable. Some of its functionality has been replaced
416with the MASQUERADE keyword and the EMAIL environment variable (see
417the dma(8) manual page).
418
a4a39c94 419+-----------------------------------------------------------------------+
62d4130d 420+ UPGRADING DRAGONFLY FROM 2.8 TO LATER VERSIONS +
a4a39c94
JS
421+-----------------------------------------------------------------------+
422
b1242318
SW
423GCC 4.4 & BINUTILS 2.21
424-----------------------
30c91f0c 425
b1242318
SW
426GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
427been made DragonFly's default Binutils.
30c91f0c
SW
428
429That means that any settings that set CCVER to 'gcc44' are not needed
430anymore. Instead, CCVER can be set to 'gcc41' to go back to using
431GCC 4.1.
432
b1242318
SW
433It also means that 'binutils221' as a value for BINUTILSVER has no
434effect anymore. 2.17 has been removed and 'binutils220' is available
435as an option.
436
5738210d 437The NO_GCC44 option has been removed and will not affect the build
30c91f0c
SW
438anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
439building in a similar fashion.
440
80abb3be 441Note that you must do a full buildworld/buildkernel for upgrading.
30c91f0c 442
a4a39c94 443pkg_radd settings
c983d16e 444-----------------
a4a39c94
JS
445
446The config file for pkg_radd has moved from /etc/settings.conf to
447/etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
448if this is needed. This warning only applies if /etc/settings.conf
449exists. pkg_radd will continue to work with defaults.
450
b79f66dd 451+-----------------------------------------------------------------------+
72fe41d3 452+ 20100927 +
1bb1cc14 453+ UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
b79f66dd
JT
454+-----------------------------------------------------------------------+
455
72fe41d3 456OpenSSL
c983d16e 457--------
72fe41d3
PA
458
459OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
460This shouldn't break any 3rd-party software, but you'll need to recompile your
4613rd-party software if you want it to link against the new version of OpenSSL.
462
8eb0b612 463Loader
c983d16e 464-------
8eb0b612 465
b79f66dd
JT
466A new loader (dloader) has been added which better handles booting from
467multiple kernel/module versions.
468
469To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
470
471 cd /usr/src
472 make buildworld
473 make installworld
474 make upgrade
475 make buildkernel KERNCONF=<KERNELNAME>
476 make installkernel KERNCONF=<KERNELNAME>
477
478Note that you must installworld and run the 'upgrade' target before
479installing the new kernel.
480
8eb0b612 481BIND
c983d16e 482-----
8eb0b612
JS
483
484BIND has been removed from the base system. The ldns and drill tools have
485been added for basic functionality. Use 'drill' where you would normally
486use nslookup or dig, or install BIND from pkgsrc. It's available as
487net/bind95, net/bind96, or net/bind97 as of this writing.
488
489This only affects older systems upgrading to 2.8. New 2.8+ installs
490include BIND as a pkgsrc package.
491
d2a0decc
MD
492+-----------------------------------------------------------------------+
493+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
494+ GENERAL +
495+-----------------------------------------------------------------------+
984263bc 496
a700883c
SW
497Instructions on how to obtain and maintain DragonFly source code using git
498are in the development(7) manual page.
d2a0decc
MD
499
500To upgrade a DragonFly system from sources you run the following sequence:
501
502 cd /usr/src
503 make buildworld
504 make buildkernel KERNCONF=<KERNELNAME>
505 make installkernel KERNCONF=<KERNELNAME>
506 make installworld
507
508You will also want to run the 'upgrade' target to upgrade your /etc and the
509rest of your system. The upgrade target is aware of stale files created by
510older DragonFly installations and should delete them automatically.
511
512 make upgrade
513
a700883c
SW
514See the build(7) manual page for further information.
515
d2a0decc
MD
516Once you've done a full build of the world and kernel you can do incremental
517upgrades of either by using the 'quickworld' and 'quickkernel' targets
518instead of 'buildworld' and 'buildkernel'. If you have any problems with
a700883c 519the quick targets, try updating your repo first, and then a full buildworld
d2a0decc 520and buildkernel as shown above, before asking for help.
4523a2c0
TN
521
522+-----------------------------------------------------------------------+
523+ UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
524+-----------------------------------------------------------------------+
525
526In 2.1 kernel and modules has moved to boot directory. For most cases
527this is handled automatically by 'make upgrade'. A few cases needs manual
528intervention:
529
530 * When installing a kernel without first doing a make buildworld,
531 installworld and upgrade to the same DESTDIR as kernel:
532 make DESTDIR/boot directory and move kernel and modules into this boot
533 directory; also move kernel.old and modules.old.
534 Typical example is vkernel(7), use (no modules used):
535
536 cd /var/vkernel
537 mkdir boot
538 chflags noschg kernel
539 mv kernel kernel.old boot
540 chflags schg boot/kernel
541
542 * When using a boot-only partition, /boot/loader.rc needs to be edited:
543 delete occurrences of '/boot/'.
544 These occurences can normally be deleted in any case, see loader(8).
d2a0decc
MD
545
546+-----------------------------------------------------------------------+
547+ UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
548+-----------------------------------------------------------------------+
549
550In 1.9 major changes to the disk management infrastructure have taken
551place. make upgrade may not catch all of your disk devices in /dev,
552so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
45e80934
MD
553are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
554and MAKEDEV no longer exists.
d2a0decc
MD
555
556The biggest changes in 1.9 are:
557
558(1) That whole-slice devices such as da0s1 no longer share the same device
559 id as partition c devices such as da0s1c.
560
561(2) The whole-disk device (e.g. da0) is full raw access to the disk,
562 with no snooping or reserved sectors. Consequently you cannot run
563 disklabel on this device. Instead you must run disklabel on a
564 whole-slice device.
565
566(3) The 'compatibility' partitions now use slice 0 in the device name,
567 so instead of da0a you must specify da0s0a. Also, as per (1) above,
568 accessing the disklabel for the compatibility partitions must be
569 done via slice 0 (da0s0).
570
571(4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
572 and CCD now run through the disk management layer and are assigned
573 real disk management devices. VN and CCD in particular do not usually
574 use a MBR and disklabels must be accessed through the compatibility
575 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
576 don't name it 'ccd0s0' in the config file.
577
578Generally speaking, you have to get used to running fdisk and disklabel on
579the correctly specified device names. A lot of the wiggle, such as running
580disklabel on a partition, has been removed.
581
582+-----------------------------------------------------------------------+
583+ UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
584+-----------------------------------------------------------------------+
585
586> Kerberos IV
587-------------
588
589Kerberos IV (eBones) was removed from the tree, please consider moving to
590Kerberos 5 (Heimdal).
591
592> Package Management System
593---------------------------
594
595Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
596management system. The necessary tools to build and maintain packages
597are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
598directories are in your PATH variable.
599
600In order to obtain a reasonably current snapshot of the pkgsrc tree, use
601the tarball from NetBSD:
602
603 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
604 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
605
606This tree can then be kept up to date with cvs update:
607
608 cd /usr/pkgsrc; cvs up
609
610NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
611build and install the pkgsrc bootstrap manually:
612
613 cd /usr/pkgsrc/bootstrap
614 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
615
616+-----------------------------------------------------------------------+
617+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
618+ UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
619+ DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
620+-----------------------------------------------------------------------+
58116288 621
114580ac 622The compatibility shims for the build environment have been removed, you
58116288
JS
623have to update to DragonFly 1.2 release branch first.
624
1fcc7462
JS
625The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
626The existing configuration can be converted using /etc/pam.d/convert.sh.
627Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
628the pam_skey.so module was retired, you have to remove it manually from
629your configuration, when you convert it.
58116288 630
a3107071
MD
631> Required user and group IDs when upgrading from either FreeBSD or DragonFly
632---------------------
633
634The following users may be missing from your password file. Use vipw and
635add any that are missing:
636
637smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
dcf85892 638_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
a3107071
MD
639
640The following groups may be missing from your group file. Use vi /etc/group
641and add any that are missing:
642
643smmsp:*:25:
644authpf:*:63:
dcf85892 645_pflogd:*:64:
a3107071
MD
646
647
f419daca 648> Upgrading to DragonFly from FreeBSD
5e0ae0d4 649---------------------
984263bc 650
f419daca
MD
651You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
652FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
653FreeBSD. Note that the DragonFly buildworld target does not try to reuse
654make depend information, it starts from scratch, so no pre-cleaning of the
655object hierarchy is necessary.
656
466bbc10 657 # get the CVS repository (it is placed in /home/dcvs, 500MB).
f419daca
MD
658 # Please use the -h option and a mirror site to pull the
659 # initial repository, but feel free to use the main repository
660 # machine to pull updates.
5010eeb3 661 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
f419daca
MD
662 # install the source from the CVS hierarchy (remove preexisting
663 # FreeBSD src first) (500MB)
664 cd /usr
665 rm -rf src
50172b1c 666 cvs -R -d /home/dcvs checkout -P src
f419daca
MD
667
668 # build it (500MB used in /usr/obj)
669 #
670 cd /usr/src
671 make buildworld
672 make buildkernel KERNCONF=<KERNELNAME>
984263bc 673
f419daca
MD
674Once you have built DragonFly you have to install it over FreeBSD. Since
675DragonFly does not track changes made by FreeBSD to its include file
676hierarchy and include file pollution can cause all sorts of unexpected
677compilation issues to come up, it is best to wipe your include hierarchy
678prior to installing DragonFly. Note that you should not wipe any installed
679FreeBSD header files or binaries until after you have successfully completed
680the build steps above.
fb12f484 681
f419daca
MD
682 rm -rf /usr/include
683 mkdir /usr/include
684 make installkernel KERNCONF=<KERNELNAME>
685 make installworld
fb12f484 686
b8cbf045 687Then you need to upgrade your system. DragonFly's 'make upgrade' target
f419daca 688will unconditionally upgrade the /etc files that sysops do not usually
b8cbf045
SW
689mess around with, such as the files in /etc/rc.d. It will also remove any
690obsolete files such as utilities and manpages that have been removed from
691the system since the version you're coming from. If you are unsure we
692recommend that you make a backup of at least your /etc before applying
693this step. Note that DragonFly's RC system is basically RCNG from
694FreeBSD-5, but there are some differences in the contents of the RC files.
f419daca
MD
695
696 make upgrade
697
b8cbf045
SW
698NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
699Doing so might leave your system in an unusable state.
700
f419daca 701Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
b8cbf045
SW
702/usr/bin, and /usr/lib, and remove any stale files that you find. Please
703report these files to the DragonFly developers so that they can be added to
704the 'upgrade' target.
f419daca 705