1 Updating Information for FreeBSD current users
3 This file is maintained by imp@village.org. Please send new entries
4 directly to him. See end of file for further details. For commonly
5 done items, please see the end of the file. Search for 'COMMON
12 The random device needs more entropy, so you need to make sure
13 that you've run mergemaster to get a /etc/rc which will seed
14 /dev/random. If you don't and the system hangs after ldconfig,
15 then banging on the keyboard randomly until it unhangs is one
19 ****************************** WARNING ******************************
20 Sendmail has been updated.
21 ****************************** WARNING ******************************
22 o mail.local(8) is no longer installed as a set-user-id binary.
23 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
25 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
27 o Now using sendmail's version of vacation(1).
28 o The sendmail cf building tools (contrib/sendmail/cf) are installed
29 in /usr/share/sendmail/cf.
30 o sendmail.cw changed to local-host-names
32 More details can be found at
33 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
36 The ports tree's new layout is in place. Be sure to update
37 your entire ports tree, or you will have problems.
40 The perl build proceedure no longer installs miniperl, nor uses
41 the installed miniperl. It is recommended that you delete
45 This weekend the ports tree will be updated to a new layout.
46 It will be in an inconsistant state until noted in the UPDATING
47 file, or with asami-san's message to the relevant mailing
48 lists. With this new layout, you'll need to update the whole
49 tree for anything to work.
52 There was a change in the passwd format. Need more information.
55 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
56 place. Please update boot loader (not the boot blocks) at the
57 same time as your kernel.
60 The new pmtimer device is necessary for laptops. Failure to
61 include the device will cause suspended laptops losing time
62 when they resume. Include
64 in your config file and
65 hint.pmtimer.0.at="isa"
66 to your /boot/device.hints file.
69 The random device has been turned into a (pseudo-)device,
70 rather than an option. The supplied kernel config files have
71 been updated. You will need to do something similar in your
72 own kernel config file.
77 If you prefer to load the loadable module, you need to do
81 The random device module has been renamed from randomdev.ko to
82 random.ko. You will need to edit your /boot/loader.conf to
83 reflect this if you load this module at boot time.
88 The SMPNG commit has happened. It should work, but if it
89 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
90 to be a variety of minor issues. Please see 20000905 to make
91 sure you don't have model loading problems which might at
92 first blush appear related to SMP.
95 nsswitch has been imported from NetBSD. Among other things,
96 this means that /etc/host.conf is no longer used. See
97 nsswitch.conf(5) instead. Note that at boot time rc.network
98 will attempt to produce a new nsswitch.conf file for you if you
99 don't have one, and you have host.conf.
102 The ucred structure changed size. This breaks the interface
103 that mountd uses. Trying to use an older mountd with a newer
104 kernel guarantees a panic. This means that you need to use
105 kernels newer than today only with matching mountd, but you
106 needed to do that anyway with the boot loader changes.
109 The boot loader has been updated. The new default kernel is
110 now /boot/kernel/kernel.ko. The new default module location
113 You *MUST* upgrade your boot loader and kernel at the same time.
114 The easiest way to do this is to do the buildworld/buildkernel/
115 installkernel/installworld dance.
117 Furthermore, you are urged to delete your old /modules directory
118 before booting the new kernel, since kldload will find stale
119 modules in that directory instead of finding them in the correct
120 path, /boot/kernel. The most common complaint that this cures
121 is that the linux module crashes your machine after the update.
123 if [ ! -d /boot/kernel.old ]; then
124 mv /modules.old /boot/kernel.old
125 chflags noschg /kernel.old
126 mv /kernel.old /boot/kernel.old/kernel.ko
127 chflags schg /boot/kernel.old/kernel.ko
131 A new issue with the sendmail upgrade has come to light.
132 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
133 incorrectly install the default aliases in /etc/mail rather than
134 move the old one from /etc. So you'll need to manually move the
135 file, create a symbolic link, remove the old /etc/aliases.db and
136 run newaliases. For safety sake, you should stop sendmail
137 while doing this and run the upgrade when locally sourced email
138 is not likely to be generated.
141 /boot/device.hints is now required for installkernel to
142 succeed. You should copy GENERIC.hints for your architecture
143 into /boot/device.hints. If and only if you compile hints
144 into your kernel, then this file may be empty. Please note,
145 if you have an empty or missing /boot/device.hints file and
146 you neglected to compile hints into your kernel, no boot
147 messages will appear after the boot loader tries to start the
151 If you do NOT have ``options RANDOMDEV'' in your kernel and
152 you DO want the random device then add randomdev_load="YES" to
156 suidperl is now always built and installed on the system, but
157 with permissions of 511. If you have applications that use
158 this program, you are now required to add ENABLE_SUIDPERL=true
159 to /etc/make.conf. If you forget to do this,
160 chmod 4511 /usr/bin/suidperl
161 will fix this until the next build.
164 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
165 visible changes that may immediately affect your configuration
167 - New default file locations from src/contrib/sendmail/cf/README
168 - newaliases limited to root and trusted users
169 - MSA port (587) turned on by default
170 - New queue file naming system so can't go from 8.11 -> 8.9
171 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
172 - FEATURE(`nullclient') is more full featured
173 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
174 - mail.local FreeBSD-only -b option changed to -B
175 - See src/contrib/sendmail/RELEASE_NOTES for more info
178 suidperl (aka sperl) is no longer build by default. You must
179 specifically define BUILD_SUIDPERL to "true" for it to be build.
180 Furthermore, we recommend that you remove /usr/bin/sperl* and
181 /usr/bin/suidperl files from your system unless you have a
185 Networking defaults have been tightened. Anybody upgrading
186 /etc/defaults/rc.conf needs to add the following lines to
187 /etc/rc.conf if they want to have the same setup
188 afterwards (unless the variables already are set, of course):
189 # Enable network daemons for user convenience.
192 sendmail_enable="YES"
195 If you have null_load="YES" in your /boot/loader.conf, you
196 will need to change that to nullfs_load="YES".
199 The "installkernel" target has changed slightly. Now even if
200 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
201 it will install the MYKERNEL file (built with the buildkernel
202 target) as /kernel rather than /MYKERNEL. Those who have
203 updated their /boot/loader.conf files to point to /MYKERNEL
204 should remove that entry or perform manual rename of /kernel
208 If you use CVSUP or CTM to get CVS trees, AND you used to get
209 the old crypto files from internat.freebsd.org AND you check
210 out files from the CVS tree with the cvs command, please read
211 http://people.freebsd.org/~imp/internat.txt
212 for details on potential problems that you might have and how
215 If you are merely a mirror, or don't answer yes to each of the
216 clauses above, you needn't worry.
219 /etc/security has been updated to print the inode number of
220 setuid programs that have changed. You will see a large spike
221 in the number of changed programs the first time when you run
222 mergemaster to get a new /etc/security.
225 /dev/random now has good entropy collection (from the keyboard
226 and sysmouse drivers). Please ensure that either `options
227 RANDOMDEV' is present in your kernel config file or that
228 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
229 not have the /dev/random driver, OpenSSL (and consequently
230 lots of crypto tools (like SSH)) will fail with strange
231 errors. (see below, 20000624).
233 FreeBSD-current is safe again to run Crypto.
236 phk made the malloc default options AJ. This may slow things
237 down and uncover other latent bugs in the code. If you need to
238 run at full speed, you can disable this by doing the following:
239 ln -s aj /etc/malloc.conf
242 libftpio's version was accidentally bumped a few days ago. This
243 has been corrected. You may need to remove /usr/lib/libftpio.so.6
244 before doing your next buildworld/installworld pair. It certainly
245 won't hurt to remove it before the update procedure. It will
246 break fetch until a new one is built, but ftp can be used in the
250 The crypto packages have changed for the cvsup. This has been done
251 in a backward compatible way, but the old packages will go away at
252 some point in the future. Look at /usr/share/examples/cvsup for
256 With the new sys/modules/sound/drivers/*, you will need to
257 set SYSDIR until you do an installworld after July 7th.
260 rc.shutdown and rc will now call the rc.d scripts with start
261 or stop. This may cause some harmless warnings from older
262 rc.d scripts that haven't been updated.
265 The libfetch based version of fetch has gone into the tree.
266 Minor problems may result on some of the less popular sites,
267 which should be reported to des@freebsd.org.
270 From approximately this date forward, one must have the crypto
271 system installed in order to build the system and kernel.
272 While not technically strictly true, one should treat it as
273 required and grab the crypto bits. If you are grabbing CVS
274 trees, src-all and cvs-crypto should be treated as if they
275 were required. You should check with the latest collections
276 to make sure that these haven't changed.
279 Mark Murray just committed the first parts of a cleanup of
280 /dev/zero, et al. This is also cleaning up /dev/random.
281 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
282 -CURRENT FROM THIS POINT FORWARD for cryptographic services
283 until Mark can merge in the fixes to this work in progress.
284 openssh and openssl should not be used to generate keys from this
285 date to the completion of the work.
287 If you must operate at this reduced level of security, add '
288 options RANDOMDEV' to your kernel or modload the randomdev
289 module. You may also need to copy a new MAKEDEV to /dev and
290 recreate the random and urandom devices.
293 The license on the softupdates is now a standard 2 clause
294 BSD license. You may need to remove your symbolic links
295 that used to be required when updating.
298 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
299 the config file update procedure.
300 http://people.freebsd.org/~imp/config-upd.html
301 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
302 isn't buildable. However, you can generate a LINT file.
305 Binutils 2.10 have hit the tree, or will shortly. As soon
306 as they do, the problem noted in 20000522 will be resolved and
307 that workaround will no longer be required.
310 phk removed the compatibility creation of wd devices in the
311 ad driver. If you haven't done so already, you must update
312 your fstab, etc to use the ad devices instead of the wd
315 In addition, you'll need to update your boot blocks to a
316 more modern version, if you haven't already done so. Modern
317 here means 4.0 release or newer (although older releases
321 Peter took an axe to config(8). Be sure that you read his mail
322 on the topic before even thinking about updating. You will
323 need to create a /boot/device.hints or add a hints directive
324 to your config file to compile them in statically. The format
325 of the config file has changed as well. Please see GENERIC or
326 NEWCARD for examples of the new format.
329 A new set of binutils went into the tree today. Anybody
330 building a kernel after this point is advised that they need
331 to rebuild their binutils (or better yet do a
332 buildworld/installworld) before building a new kernel.
334 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
335 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
336 is recommended that you don't set this option until the problem
340 The ethernet drivers were all updated to clean up the BPF handling.
343 The problems with boot blocks on the alphas have been corrected.
344 This will require some care in updating alphas. A new libstand
345 is requires for the boot blocks to build properly.
348 Recompile all kld modules. Proper version dependency info
352 Modules have been disconnected from the buildworld tree and
353 connected to the kernel building instead.
356 You may need to build gperf
357 cd /usr/src/gnu/usr.bin/gperf && make depend all install
358 when upgrading from 4.0 -> current. The build system now uses
359 an option only in -current.
362 The method that we brand ELF binaries has changed to be more
363 acceptable to the binutils maintainers. You will need to
364 rebrand your ELF binaries that aren't native. One problem
365 binary is the Linux ldconfig. After your make world, but
366 before you reboot, you'll need to issue:
367 brandelf -t Linux /compat/linux/sbin/ldconfig
368 if you have Linux compatibility enabled on your machine.
371 If you have really bad/marginal IDE drives, you may find they
372 don't work well. Use pio mode instead. The easiest way to
373 cope if you have a problem combination is to add:
374 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
375 to the start of /etc/rc.conf.
378 The ISA and PCI compatibility shims have been connected to the
379 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
380 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
381 include the appropriate option in your kernel config. Drivers
382 using the shims should be updated or they won't ship with
383 5.0-RELEASE, targeted for 2001.
386 We've entered the traditional post release dumping party.
387 Large kernel changes are being committed and are in the
388 works. It is important to keep the systems' klds and kernel
389 in sync as kernel interfaces and structures are changing.
390 Before reporting kernel panics, make sure that all modules
391 that you are loading are up to date.
394 If you are upgrading from an older version of FreeBSD, you
395 need to update your boot blocks as well. 'disklabel -B ad0'
396 will do the trick. This isn't critical until you remove your
397 wd device entries in /dev, at which point your system will not
401 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
402 to upgrade to 4.0 from 3.x.
408 Avoid using make -j when upgrading. From time to time in the
409 past there have been problems using -j with buildworld and/or
410 installworld. This is especially true when upgrading between
411 "distant" versions (eg one that cross a major release boundary
412 or several minor releases, or when several months have passed
413 on the -current branch).
417 If you are updating from a prior version of FreeBSD (even one just
418 a few days old), you should follow this procedure. With a
419 /usr/obj tree with a fresh buildworld,
420 make buildkernel KERNEL=YOUR_KERNEL_HERE
421 make installkernel KERNEL=YOUR_KERNEL_HERE
423 To just build a kernel when you know that it won't mess you up
424 --------------------------------------------------------------
425 cd src/sys/{i386,alpha}/conf
426 config KERNEL_NAME_HERE [1]
427 cd ../../compile/KERNEL_NAME_HERE
432 [1] If in doubt, -r might help here.
434 If this fails, go to the "To build a kernel" section.
436 To rebuild everything and install it on the current system.
437 -----------------------------------------------------------
439 Build a new kernel, see above.
441 To upgrade from 4.x-stable to current
442 -------------------------------------
444 make buildkernel KERNEL=YOUR_KERNEL_HERE
445 cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
446 make installkernel KERNEL=YOUR_KERNEL_HERE
451 Make sure that you've read the UPDATING file to understand the
452 tweaks to various things you need. At this point in the life
453 cycle of current, things change often and you are on your own
454 to cope. The defaults can also change, so please read ALL of
455 the UPDATING entries.
457 Also, if you are tracking -current, you must be subscribed to
458 freebsd-current@freebsd.org. Make sure that before you update
459 your sources that you have read and understood all the recent
460 messages there. If in doubt, please track -stable which has
463 [1] If you have third party modules, such as vmware, you
464 should disable them at this point so they don't crash your
467 [2] If you have legacy ISA devices, you may need to create
468 your own device.hints to reflect your unique hardware
473 This file contains a list, in reverse chronological order, of major
474 breakages in tracking -current. Not all things will be listed here,
475 and it only starts on March 15, 2000. Updating files can found in
476 previous releases if your system is older than this.
478 Please filter your entries through Warner Losh (imp@village.org) so
479 that the style, formatting, etc of this file can be maintained.