Disklabel operations are no longer legal on the raw disk, use DIOCGPART to
[dragonfly.git] / UPDATING
CommitLineData
23e12d00 1$DragonFly: src/UPDATING,v 1.22 2006/10/24 17:09:45 swildner Exp $
984263bc 2
5e0ae0d4 3Updating Information for DragonFly users.
984263bc 4
5e0ae0d4
JR
5This file should warn you of any pitfalls which you might need to work around
6when trying to update your DragonFly system.
984263bc 7
5e0ae0d4
JR
8If you discover any problem, please contact the bugs@lists.dragonflybsd.org
9mailing list with the details.
984263bc 10
5e0ae0d4 11------------------------------------------------------------------------------
984263bc 12
58116288
JS
13> Updating from pre-1.2 systems or FreeBSD 4.x to DragonFly 1.3+ (either
14 PREVIEW or HEAD)
15---------------------
16
114580ac 17The compatibility shims for the build environment have been removed, you
58116288
JS
18have to update to DragonFly 1.2 release branch first.
19
1fcc7462
JS
20The default PAM configuration has moved from /etc/pam.conf to /etc/pam.d/.
21The existing configuration can be converted using /etc/pam.d/convert.sh.
22Entries in /etc/pam.d/ override entries in /etc/pam.conf. In addition
23the pam_skey.so module was retired, you have to remove it manually from
24your configuration, when you convert it.
58116288 25
a3107071
MD
26> Required user and group IDs when upgrading from either FreeBSD or DragonFly
27---------------------
28
29The following users may be missing from your password file. Use vipw and
30add any that are missing:
31
32smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
dcf85892
JS
33_pflogd:*:64:64::0:0:pflogd privsep user:/var/empty:/sbin/nologin
34_ntp:*:65:65::0:0:ntpd privsep user:/var/empty:/sbin/nologin
a3107071
MD
35
36The following groups may be missing from your group file. Use vi /etc/group
37and add any that are missing:
38
39smmsp:*:25:
40authpf:*:63:
dcf85892
JS
41_pflogd:*:64:
42_ntp:*:65:
a3107071
MD
43
44
f419daca 45> Upgrading to DragonFly from FreeBSD
5e0ae0d4 46---------------------
984263bc 47
f419daca
MD
48You can build the DragonFly world and DragonFly kernels on a FreeBSD-4.x or
49FreeBSD-5.x machine and then install DragonFly over FreeBSD, replacing
50FreeBSD. Note that the DragonFly buildworld target does not try to reuse
51make depend information, it starts from scratch, so no pre-cleaning of the
52object hierarchy is necessary.
53
466bbc10 54 # get the CVS repository (it is placed in /home/dcvs, 500MB).
f419daca
MD
55 # Please use the -h option and a mirror site to pull the
56 # initial repository, but feel free to use the main repository
57 # machine to pull updates.
5010eeb3 58 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
f419daca
MD
59 # install the source from the CVS hierarchy (remove preexisting
60 # FreeBSD src first) (500MB)
61 cd /usr
62 rm -rf src
50172b1c 63 cvs -R -d /home/dcvs checkout -P src
f419daca
MD
64
65 # build it (500MB used in /usr/obj)
66 #
67 cd /usr/src
68 make buildworld
69 make buildkernel KERNCONF=<KERNELNAME>
984263bc 70
f419daca
MD
71Once you have built DragonFly you have to install it over FreeBSD. Since
72DragonFly does not track changes made by FreeBSD to its include file
73hierarchy and include file pollution can cause all sorts of unexpected
74compilation issues to come up, it is best to wipe your include hierarchy
75prior to installing DragonFly. Note that you should not wipe any installed
76FreeBSD header files or binaries until after you have successfully completed
77the build steps above.
fb12f484 78
f419daca
MD
79 rm -rf /usr/include
80 mkdir /usr/include
81 make installkernel KERNCONF=<KERNELNAME>
82 make installworld
fb12f484 83
b8cbf045 84Then you need to upgrade your system. DragonFly's 'make upgrade' target
f419daca 85will unconditionally upgrade the /etc files that sysops do not usually
b8cbf045
SW
86mess around with, such as the files in /etc/rc.d. It will also remove any
87obsolete files such as utilities and manpages that have been removed from
88the system since the version you're coming from. If you are unsure we
89recommend that you make a backup of at least your /etc before applying
90this step. Note that DragonFly's RC system is basically RCNG from
91FreeBSD-5, but there are some differences in the contents of the RC files.
f419daca
MD
92
93 make upgrade
94
b8cbf045
SW
95NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
96Doing so might leave your system in an unusable state.
97
f419daca 98Finally we recommend that you do an 'ls -lta BLAH' for /bin, /sbin, /usr/bin,
b8cbf045
SW
99/usr/bin, and /usr/lib, and remove any stale files that you find. Please
100report these files to the DragonFly developers so that they can be added to
101the 'upgrade' target.
f419daca
MD
102
103------------------------------------------------------------------------------
104
105> Upgrading DragonFly on an existing DragonFly system.
106---------------------
107
108The best way to upgrade DragonFly is to maintain a copy of the DragonFly
f789eec2
SW
109CVS repository via cvsup and to checkout the source base via this repository.
110The repository is stored in /home/dcvs by default and requires about 800MB
111of disk space. The checked out source tree (/usr/src) requires about 400MB
112of disk space, and the build will eat around 800MB of space out of /usr/obj.
113To maintain the build you should reserve at least 2.5GB of disk space, and
1143.5GB if you have the space.
f419daca
MD
115
116Note: most people run cvsup via a root cron job to keep the repository up to
117date. Please limit such automatic updates to once a day and try to randomize
118the hour and minute in the cron job a bit to avoid pileups.
119
466bbc10 120 # get the CVS repository (it is placed in /home/dcvs)
5010eeb3 121 cvsup /usr/share/examples/cvsup/DragonFly-cvs-supfile
f419daca
MD
122 # install the source from the CVS hierarchy
123 cd /usr
3eb4a8b6 124 cvs -R -d /home/dcvs checkout -P src
f419daca
MD
125
126Once you have the repository and broken out sources you can decide whether to
127update your sources from the repository automatically or manually. Since
128you are tracking changes made to DragonFly, it is usually a good idea to
129update the sources manually:
fb12f484 130
fb12f484 131 cd /usr/src
3eb4a8b6 132 cvs update -dP
fb12f484 133
f419daca 134To upgrade a DragonFly system from sources you run the following sequence:
fb12f484 135
fb12f484 136 cd /usr/src
fb12f484 137 make buildworld
f419daca
MD
138 make buildkernel KERNCONF=<KERNELNAME>
139 make installkernel KERNCONF=<KERNELNAME>
fb12f484
MD
140 make installworld
141
b8cbf045
SW
142You will also want to run the 'upgrade' target to upgrade your /etc and the
143rest of your system. The upgrade target is aware of stale files created by
144older DragonFly installations and should delete them automatically.
f419daca
MD
145
146 make upgrade
147
b8cbf045
SW
148NOTE! Never do a 'make upgrade' before 'make installworld' has been run.
149Doing so might leave your system in an unusable state.
150
23e12d00 151If you are using 'config' manually from /usr/src/sys/config, note
9fbfae7b 152that the build will use the current DragonFly environment rather than
f419daca
MD
153the post-build environment from the last buildworld. For this reason manual
154configs are discouraged. The proper way to build a kernel is to use the
155'buildkernel' or 'quickkernel' target in /usr/src.
156
157Once you've done a full build of the world and kernel you can do incremental
158upgrades of either by using the 'quickworld' and 'quickkernel' targets
159instead of 'buildworld' and 'buildkernel'. If you have any problems with
160the quick targets, try doing a cvsup, cvs update, and then a full buildworld
161and buildkernel as shown above, before asking for help.
984263bc 162
5e0ae0d4
JR
163> Kerberos IV
164-------------
984263bc 165
5e0ae0d4
JR
166Kerberos IV (eBones) was removed from the tree, please consider moving to
167Kerberos 5 (Heimdal).
984263bc 168
a2023ec8
SW
169> Package Management System
170---------------------------
892096eb 171
a2023ec8
SW
172Starting with the 1.4 release, DragonFly uses NetBSD's pkgsrc package
173management system. The necessary tools to build and maintain packages
174are provided in /usr/pkg/bin and /usr/pkg/sbin. Make sure that these
175directories are in your PATH variable.
892096eb 176
a2023ec8
SW
177In order to obtain a reasonably current snapshot of the pkgsrc tree, use
178the tarball from NetBSD:
892096eb 179
a2023ec8
SW
180 fetch -o /tmp/pkgsrc.tar.gz ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz
181 cd /usr; tar -xzf /tmp/pkgsrc.tar.gz; chown -R root:wheel pkgsrc
892096eb 182
a2023ec8 183This tree can then be kept up to date with cvs update:
984263bc 184
a2023ec8
SW
185 cd /usr/pkgsrc; cvs up
186
187NOTE! If you upgraded from a pre-1.4 system to 1.4 or later, you need to
188build and install the pkgsrc bootstrap manually:
189
190 cd /usr/pkgsrc/bootstrap
191 ./bootstrap --pkgdbdir /var/db/pkg --prefix /usr/pkg