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