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