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