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