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