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
9 Mark Murray just committed the first parts of a cleanup of
10 /dev/zero, et al. This is also cleaning up /dev/random.
11 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
12 -CURRENT FROM THIS POINT FORWARD for cryptographic services
13 until Mark can merge in the fixes to this work in progress.
14 openssh and openssl should not be used to generate keys from this
15 date to the completion of the work.
18 The license on the softupdates is now a standard 2 clause
19 BSD license. You may need to remove your symbolic links
20 that used to be required when updating.
23 Scott Flatman <sf@aracnet.com> sent in a decent writeup on
24 the config file update procedure.
25 http://people.freebsd.org/~imp/config-upd.html
28 Binutils 2.10 have hit the tree, or will shortly. As soon
29 as they do, the problem noted in 20000522 will be resolved and
30 that workaround will no longer be required.
33 phk removed the compatibility creation of wd devices in the
34 ad driver. If you haven't done so already, you must update
35 your fstab, etc to use the ad devices instead of the wd
38 In addition, you'll need to update your boot blocks to a
39 more modern version, if you haven't already done so. Modern
40 here means 4.0 release or newer (although older releases
44 Peter took an axe to config(8). Besure that you read his mail
45 on the topic before even thinking about updating. You will
46 need to create a /boot/devices.hints or add a hints directive
47 to your config file to compile them in statically. The format
48 of the config file has changed as well. Please see LINT,
49 GENERIC or NEWCARD for examples of the new format.
52 A new set of binutils went into the tree today. Anybody
53 building a kernel after this point is advised that they need
54 to rebuild their binutils (or better yet do a
55 buildworld/installworld) before building a new kernel.
57 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
58 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
59 is recommended that you don't set this option until the problem
63 The ethernet drivers were all updated to clean up the BPF handling.
66 The problems with boot blocks on the alphas have been corrected.
67 This will require some care in updating alphas. A new libstand
68 is requires for the boot blocks to build properly.
71 Recompile all kld modules. Proper version dependency info
75 Modules have been disconnected from the buildworld tree and
76 connected to the kernel building instead.
79 You may need to build gperf
80 cd /usr/src/gnu/usr.bin/gperf && make depend all install
81 when upgrading from 4.0 -> current. The build system now uses
82 an option only in -current.
85 The method that we brand ELF binaries has changed to be more
86 acceptible to the binutils maintainers. You will need to
87 rebrand your ELF binaries that aren't native. One problem
88 binary is the Linux ldconfig. After your make world, but
89 before you reboot, you'll neeed to issue:
90 brandelf -t Linux /compat/linux/sbin/ldconfig
91 if you have Linux compatibility enabled on your machine.
94 If you have really bad/marginal IDE drives, you may find they
95 don't work well. Use pio mode instead. The easiest way to
96 cope if you have a problem combination is to add:
97 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
98 to the start of /etc/rc.conf.
101 The ISA and PCI compatability shims have been connected to the
102 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
103 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
104 include the appropriate option in your kernel config. Drivers
105 using the shims should be updated or they won't ship with
106 5.0-RELEASE, targeted for 2001.
109 We've entered the tradtional post release dumping party.
110 Large kernel changes are being committed and are in the
111 works. It is important to keep the systems' klds and kernel
112 in sync as kernel interfaces and structures are changing.
113 Before reporting kernel panics, make sure that all modules
114 that you are loading are up to date.
117 If you are upgrading from an older version of FreeBSD, you
118 need to update your boot blocks as well. 'disklabel -B ad0'
119 will do the trick. This isn't critical until you remove your
120 wd device entries in /dev, at which point your system will not
124 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
125 to upgrade to 4.0 from 3.x.
131 Update config, genassym and go:
132 config YOUR_KERNEL_HERE [1]
133 cd ../../compile/YOUR_KERNEL_HERE
136 [1] If upgrading, add -r won't hurt and sometimes helps.
138 To rebuild everything
139 ---------------------
142 To upgrade from 4.0-stable to current
143 -------------------------------------
145 make buildkernel KERNEL=YOUR_KERNEL_HERE
146 make installkernel KERNEL=YOUR_KERNEL_HERE
150 Make sure that you've read the UPDATING file to understand
151 the tweaks to various things you need. At this point in the
152 life cycloe of current, things change often and you are on
157 This file contains a list, in reverse chronologocal order, of major
158 breakages in tracking -current. Not all things will be listed here,
159 and it only starts on March 15, 2000. Updating files can found in
160 previous releases if your system is older than this.
162 Please filter your entries through Warner Losh (imp@village.org) so
163 that the style, formatting, etc of this file can be maintained.