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