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