ioapic: Add tunable hw.ioapic_use_old
[dragonfly.git] / UPDATING
... / ...
CommitLineData
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.
10
11+-----------------------------------------------------------------------+
12+ UPGRADING DRAGONFLY FROM 2.8 to later versions +
13+-----------------------------------------------------------------------+
14
15GCC 4.4
16-------
17
18GCC 4.4 has been made DragonFly's default compiler.
19
20That means that any settings that set CCVER to 'gcc44' are not needed
21anymore. Instead, CCVER can be set to 'gcc41' to go back to using
22GCC 4.1.
23
24The NO_GCC44 option has been removed and will not affect the build
25anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
26building in a similar fashion.
27
28Also, we recommend to do a full buildworld/buildkernel for upgrading.
29
30pkg_radd settings
31-----------------
32
33The config file for pkg_radd has moved from /etc/settings.conf to
34/etc/pkg_radd.conf. Save the contents of settings.conf before upgrading
35if this is needed. This warning only applies if /etc/settings.conf
36exists. pkg_radd will continue to work with defaults.
37
38+-----------------------------------------------------------------------+
39+ 20100927 +
40+ UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD +
41+-----------------------------------------------------------------------+
42
43OpenSSL
44--------
45
46OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
47This shouldn't break any 3rd-party software, but you'll need to recompile your
483rd-party software if you want it to link against the new version of OpenSSL.
49
50Loader
51-------
52
53A new loader (dloader) has been added which better handles booting from
54multiple kernel/module versions.
55
56To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
57
58 cd /usr/src
59 make buildworld
60 make installworld
61 make upgrade
62 make buildkernel KERNCONF=<KERNELNAME>
63 make installkernel KERNCONF=<KERNELNAME>
64
65Note that you must installworld and run the 'upgrade' target before
66installing the new kernel.
67
68BIND
69-----
70
71BIND has been removed from the base system. The ldns and drill tools have
72been added for basic functionality. Use 'drill' where you would normally
73use nslookup or dig, or install BIND from pkgsrc. It's available as
74net/bind95, net/bind96, or net/bind97 as of this writing.
75
76This only affects older systems upgrading to 2.8. New 2.8+ installs
77include BIND as a pkgsrc package.
78
79+-----------------------------------------------------------------------+
80+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
81+ GENERAL +
82+-----------------------------------------------------------------------+
83
84Instructions on how to obtain and maintain DragonFly source code using git
85are in the development(7) manual page.
86
87To upgrade a DragonFly system from sources you run the following sequence:
88
89 cd /usr/src
90 make buildworld
91 make buildkernel KERNCONF=<KERNELNAME>
92 make installkernel KERNCONF=<KERNELNAME>
93 make installworld
94
95You will also want to run the 'upgrade' target to upgrade your /etc and the
96rest of your system. The upgrade target is aware of stale files created by
97older DragonFly installations and should delete them automatically.
98
99 make upgrade
100
101See the build(7) manual page for further information.
102
103Once you've done a full build of the world and kernel you can do incremental
104upgrades of either by using the 'quickworld' and 'quickkernel' targets
105instead of 'buildworld' and 'buildkernel'. If you have any problems with
106the quick targets, try updating your repo first, and then a full buildworld
107and buildkernel as shown above, before asking for help.
108
109+-----------------------------------------------------------------------+
110+ UPGRADING FROM DRAGONFLY <= 2.0 TO DRAGONFLY >= 2.1 +
111+-----------------------------------------------------------------------+
112
113In 2.1 kernel and modules has moved to boot directory. For most cases
114this is handled automatically by 'make upgrade'. A few cases needs manual
115intervention:
116
117 * When installing a kernel without first doing a make buildworld,
118 installworld and upgrade to the same DESTDIR as kernel:
119 make DESTDIR/boot directory and move kernel and modules into this boot
120 directory; also move kernel.old and modules.old.
121 Typical example is vkernel(7), use (no modules used):
122
123 cd /var/vkernel
124 mkdir boot
125 chflags noschg kernel
126 mv kernel kernel.old boot
127 chflags schg boot/kernel
128
129 * When using a boot-only partition, /boot/loader.rc needs to be edited:
130 delete occurrences of '/boot/'.
131 These occurences can normally be deleted in any case, see loader(8).
132
133+-----------------------------------------------------------------------+
134+ UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
135+-----------------------------------------------------------------------+
136
137In 1.9 major changes to the disk management infrastructure have taken
138place. make upgrade may not catch all of your disk devices in /dev,
139so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
140are all of your disk devices. HOWEVER, from late 2.3 on we run devfs
141and MAKEDEV no longer exists.
142
143The biggest changes in 1.9 are:
144
145(1) That whole-slice devices such as da0s1 no longer share the same device
146 id as partition c devices such as da0s1c.
147
148(2) The whole-disk device (e.g. da0) is full raw access to the disk,
149 with no snooping or reserved sectors. Consequently you cannot run
150 disklabel on this device. Instead you must run disklabel on a
151 whole-slice device.
152
153(3) The 'compatibility' partitions now use slice 0 in the device name,
154 so instead of da0a you must specify da0s0a. Also, as per (1) above,
155 accessing the disklabel for the compatibility partitions must be
156 done via slice 0 (da0s0).
157
158(4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
159 and CCD now run through the disk management layer and are assigned
160 real disk management devices. VN and CCD in particular do not usually
161 use a MBR and disklabels must be accessed through the compatibility
162 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
163 don't name it 'ccd0s0' in the config file.
164
165Generally speaking, you have to get used to running fdisk and disklabel on
166the correctly specified device names. A lot of the wiggle, such as running
167disklabel on a partition, has been removed.
168
169+-----------------------------------------------------------------------+
170+ UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
171+-----------------------------------------------------------------------+
172
173> Kerberos IV
174-------------
175
176Kerberos IV (eBones) was removed from the tree, please consider moving to
177Kerberos 5 (Heimdal).
178
179> Package Management System
180---------------------------
181
182Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
183management system. The necessary tools to build and maintain packages
184are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
185directories are in your PATH variable.
186
187In order to obtain a reasonably current snapshot of the pkgsrc tree, use
188the tarball from NetBSD:
189
190 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
191 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
192
193This tree can then be kept up to date with cvs update:
194
195 cd /usr/pkgsrc; cvs up
196
197NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
198build and install the pkgsrc bootstrap manually:
199
200 cd /usr/pkgsrc/bootstrap
201 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
202
203+-----------------------------------------------------------------------+
204+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
205+ UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
206+ DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
207+-----------------------------------------------------------------------+
208
209The compatibility shims for the build environment have been removed, you
210have to update to DragonFly 1.2 release branch first.
211
212The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
213The existing configuration can be converted using /etc/pam.d/convert.sh.
214Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
215the pam_skey.so module was retired, you have to remove it manually from
216your configuration, when you convert it.
217
218> Required user and group IDs when upgrading from either FreeBSD or DragonFly
219---------------------
220
221The following users may be missing from your password file. Use vipw and
222add any that are missing:
223
224smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
225_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
226
227The following groups may be missing from your group file. Use vi /etc/group
228and add any that are missing:
229
230smmsp:*:25:
231authpf:*:63:
232_pflogd:*:64:
233
234
235> Upgrading to DragonFly from FreeBSD
236---------------------
237
238You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
239FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
240FreeBSD. Note that the DragonFly buildworld target does not try to reuse
241make depend information, it starts from scratch, so no pre-cleaning of the
242object hierarchy is necessary.
243
244 # get the CVS repository (it is placed in /home/dcvs, 500MB).
245 # Please use the -h option and a mirror site to pull the
246 # initial repository, but feel free to use the main repository
247 # machine to pull updates.
248 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
249 # install the source from the CVS hierarchy (remove preexisting
250 # FreeBSD src first) (500MB)
251 cd /usr
252 rm -rf src
253 cvs -R -d /home/dcvs checkout -P src
254
255 # build it (500MB used in /usr/obj)
256 #
257 cd /usr/src
258 make buildworld
259 make buildkernel KERNCONF=<KERNELNAME>
260
261Once you have built DragonFly you have to install it over FreeBSD. Since
262DragonFly does not track changes made by FreeBSD to its include file
263hierarchy and include file pollution can cause all sorts of unexpected
264compilation issues to come up, it is best to wipe your include hierarchy
265prior to installing DragonFly. Note that you should not wipe any installed
266FreeBSD header files or binaries until after you have successfully completed
267the build steps above.
268
269 rm -rf /usr/include
270 mkdir /usr/include
271 make installkernel KERNCONF=<KERNELNAME>
272 make installworld
273
274Then you need to upgrade your system. DragonFly's 'make upgrade' target
275will unconditionally upgrade the /etc files that sysops do not usually
276mess around with, such as the files in /etc/rc.d. It will also remove any
277obsolete files such as utilities and manpages that have been removed from
278the system since the version you're coming from. If you are unsure we
279recommend that you make a backup of at least your /etc before applying
280this step. Note that DragonFly's RC system is basically RCNG from
281FreeBSD-5, but there are some differences in the contents of the RC files.
282
283 make upgrade
284
285NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
286Doing so might leave your system in an unusable state.
287
288Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
289/usr/bin, and /usr/lib, and remove any stale files that you find. Please
290report these files to the DragonFly developers so that they can be added to
291the 'upgrade' target.
292