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