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