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