Adjust some comments with reality.
[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#
11# $DragonFly: src/UPDATING,v 1.23 2007/05/20 01:07:30 dillon Exp $
12
13+-----------------------------------------------------------------------+
14+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
15+ GENERAL +
16+-----------------------------------------------------------------------+
984263bc 17
d2a0decc
MD
18The best way to upgrade DragonFly is to maintain a copy of the DragonFly
19CVS repository via cvsup and to checkout the source base via this repository.
20The repository is stored in /home/dcvs by default and requires about 800MB
21of disk space. The checked out source tree (/usr/src) requires about 400MB
22of disk space, and the build will eat around 800MB of space out of /usr/obj.
23To maintain the build you should reserve at least 2.5GB of disk space, and
243.5GB if you have the space.
984263bc 25
d2a0decc
MD
26Note: most people run cvsup via a root cron job to keep the repository up to
27date. Please limit such automatic updates to once a day and try to randomize
28the hour and minute in the cron job a bit to avoid pileups.
984263bc 29
d2a0decc
MD
30 # get the CVS repository (it is placed in /home/dcvs)
31 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
32 # install the source from the CVS hierarchy
33 cd /usr
34 cvs -R -d /home/dcvs checkout -P src
984263bc 35
d2a0decc
MD
36Once you have the repository and broken out sources you can decide whether to
37update your sources from the repository automatically or manually. Since
38you are tracking changes made to DragonFly, it is usually a good idea to
39update the sources manually:
984263bc 40
d2a0decc
MD
41 cd /usr/src
42 cvs update -dP
43
44To upgrade a DragonFly system from sources you run the following sequence:
45
46 cd /usr/src
47 make buildworld
48 make buildkernel KERNCONF=<KERNELNAME>
49 make installkernel KERNCONF=<KERNELNAME>
50 make installworld
51
52You will also want to run the 'upgrade' target to upgrade your /etc and the
53rest of your system. The upgrade target is aware of stale files created by
54older DragonFly installations and should delete them automatically.
55
56 make upgrade
57
58NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
59Doing so might leave your system in an unusable state.
60
61Once you've done a full build of the world and kernel you can do incremental
62upgrades of either by using the 'quickworld' and 'quickkernel' targets
63instead of 'buildworld' and 'buildkernel'. If you have any problems with
64the quick targets, try doing a cvsup, cvs update, and then a full buildworld
65and buildkernel as shown above, before asking for help.
66
67+-----------------------------------------------------------------------+
68+ UPGRADING FROM DRAGONFLY <= 1.8 TO DRAGONFLY >= 1.9 +
69+-----------------------------------------------------------------------+
70
71In 1.9 major changes to the disk management infrastructure have taken
72place. make upgrade may not catch all of your disk devices in /dev,
73so after upgrading be sure to cd /dev; ./MAKEDEV <blah> where <blah>
74are all of your disk devices.
75
76The biggest changes in 1.9 are:
77
78(1) That whole-slice devices such as da0s1 no longer share the same device
79 id as partition c devices such as da0s1c.
80
81(2) The whole-disk device (e.g. da0) is full raw access to the disk,
82 with no snooping or reserved sectors. Consequently you cannot run
83 disklabel on this device. Instead you must run disklabel on a
84 whole-slice device.
85
86(3) The 'compatibility' partitions now use slice 0 in the device name,
87 so instead of da0a you must specify da0s0a. Also, as per (1) above,
88 accessing the disklabel for the compatibility partitions must be
89 done via slice 0 (da0s0).
90
91(4) Many device drivers that used to fake up labels, such as CD, ACD, VN,
92 and CCD now run through the disk management layer and are assigned
93 real disk management devices. VN and CCD in particular do not usually
94 use a MBR and disklabels must be accessed through the compatibility
95 slice 0. Your /etc/ccd.conf file still specifies 'ccd0', though, you
96 don't name it 'ccd0s0' in the config file.
97
98Generally speaking, you have to get used to running fdisk and disklabel on
99the correctly specified device names. A lot of the wiggle, such as running
100disklabel on a partition, has been removed.
101
102+-----------------------------------------------------------------------+
103+ UPGRADING FROM OLDER VERSIONS OF DRAGONFLY OR FREEBSD +
104+-----------------------------------------------------------------------+
105
106> Kerberos IV
107-------------
108
109Kerberos IV (eBones) was removed from the tree, please consider moving to
110Kerberos 5 (Heimdal).
111
112> Package Management System
113---------------------------
114
115Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
116management system. The necessary tools to build and maintain packages
117are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
118directories are in your PATH variable.
119
120In order to obtain a reasonably current snapshot of the pkgsrc tree, use
121the tarball from NetBSD:
122
123 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
124 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
125
126This tree can then be kept up to date with cvs update:
127
128 cd /usr/pkgsrc; cvs up
129
130NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
131build and install the pkgsrc bootstrap manually:
132
133 cd /usr/pkgsrc/bootstrap
134 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg
135
136+-----------------------------------------------------------------------+
137+ UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM +
138+ UPDATING FROM PRE-1.2 SYSTEMS OR FreeBSD 4.x TO +
139+ DRAGONFLY 1.3+ (EITHER PREVIEW or HEAD) +
140+-----------------------------------------------------------------------+
58116288 141
114580ac 142The compatibility shims for the build environment have been removed, you
58116288
JS
143have to update to DragonFly 1.2 release branch first.
144
1fcc7462
JS
145The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
146The existing configuration can be converted using /etc/pam.d/convert.sh.
147Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
148the pam_skey.so module was retired, you have to remove it manually from
149your configuration, when you convert it.
58116288 150
a3107071
MD
151> Required user and group IDs when upgrading from either FreeBSD or DragonFly
152---------------------
153
154The following users may be missing from your password file. Use vipw and
155add any that are missing:
156
157smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
dcf85892
JS
158_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
159_ntp:*:65:65::0:0:ntpd privsep user:/var/empty:/sbin/nologin
a3107071
MD
160
161The following groups may be missing from your group file. Use vi /etc/group
162and add any that are missing:
163
164smmsp:*:25:
165authpf:*:63:
dcf85892
JS
166_pflogd:*:64:
167_ntp:*:65:
a3107071
MD
168
169
f419daca 170> Upgrading to DragonFly from FreeBSD
5e0ae0d4 171---------------------
984263bc 172
f419daca
MD
173You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
174FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
175FreeBSD. Note that the DragonFly buildworld target does not try to reuse
176make depend information, it starts from scratch, so no pre-cleaning of the
177object hierarchy is necessary.
178
466bbc10 179 # get the CVS repository (it is placed in /home/dcvs, 500MB).
f419daca
MD
180 # Please use the -h option and a mirror site to pull the
181 # initial repository, but feel free to use the main repository
182 # machine to pull updates.
5010eeb3 183 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
f419daca
MD
184 # install the source from the CVS hierarchy (remove preexisting
185 # FreeBSD src first) (500MB)
186 cd /usr
187 rm -rf src
50172b1c 188 cvs -R -d /home/dcvs checkout -P src
f419daca
MD
189
190 # build it (500MB used in /usr/obj)
191 #
192 cd /usr/src
193 make buildworld
194 make buildkernel KERNCONF=<KERNELNAME>
984263bc 195
f419daca
MD
196Once you have built DragonFly you have to install it over FreeBSD. Since
197DragonFly does not track changes made by FreeBSD to its include file
198hierarchy and include file pollution can cause all sorts of unexpected
199compilation issues to come up, it is best to wipe your include hierarchy
200prior to installing DragonFly. Note that you should not wipe any installed
201FreeBSD header files or binaries until after you have successfully completed
202the build steps above.
fb12f484 203
f419daca
MD
204 rm -rf /usr/include
205 mkdir /usr/include
206 make installkernel KERNCONF=<KERNELNAME>
207 make installworld
fb12f484 208
b8cbf045 209Then you need to upgrade your system. DragonFly's 'make upgrade' target
f419daca 210will unconditionally upgrade the /etc files that sysops do not usually
b8cbf045
SW
211mess around with, such as the files in /etc/rc.d. It will also remove any
212obsolete files such as utilities and manpages that have been removed from
213the system since the version you're coming from. If you are unsure we
214recommend that you make a backup of at least your /etc before applying
215this step. Note that DragonFly's RC system is basically RCNG from
216FreeBSD-5, but there are some differences in the contents of the RC files.
f419daca
MD
217
218 make upgrade
219
b8cbf045
SW
220NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
221Doing so might leave your system in an unusable state.
222
f419daca 223Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
b8cbf045
SW
224/usr/bin, and /usr/lib, and remove any stale files that you find. Please
225report these files to the DragonFly developers so that they can be added to
226the 'upgrade' target.
f419daca 227