157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh 49698f2c0SWarner Losh<imp@village.org>. See end of file for further details. For commonly 59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file. 6e72fd46aSWarner Losh 72c724730SWarner LoshItems affecting the ports and packages system can be found in 82c724730SWarner Losh/usr/ports/UPDATING. Please read that file before running 92c724730SWarner Loshportupgrade. Important recent entries: 20040724 (default X changes). 102c724730SWarner Losh 11f692e7ecSWarner Losh[[ The UPDATING file will be trimmed to 20040814 on or about Oct 1, 2004 ]] 12f692e7ecSWarner Losh 13f692e7ecSWarner LoshNOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW: 14f692e7ecSWarner Losh FreeBSD 6.x has many debugging features turned on, in 1569f7bcf3SWarner Losh both the kernel and userland. These features attempt to detect 1669f7bcf3SWarner Losh incorrect use of system primitives, and encourage loud failure 1769f7bcf3SWarner Losh through extra sanity checking and fail stop semantics. They 1869f7bcf3SWarner Losh also substantially impact system performance. If you want to 1969f7bcf3SWarner Losh do performance measurement, benchmarking, and optimization, 2069f7bcf3SWarner Losh you'll want to turn them off. This includes various WITNESS- 2169f7bcf3SWarner Losh related kernel options, INVARIANTS, malloc debugging flags 2269f7bcf3SWarner Losh in userland, and various verbose features in the kernel. Many 2369f7bcf3SWarner Losh developers choose to disable these features on build machines 24a19f8ddaSDavid E. O'Brien to maximize performance. 25c1f61aa9SDavid E. O'Brien 2687c9e370SSam Leffler20041219: 2787c9e370SSam Leffler Auto-loading of ancillary wlan modules such as wlan_wep has 2887c9e370SSam Leffler been temporarily disabled; you need to statically configure 2987c9e370SSam Leffler the modules you need into your kernel or explicitly load them 3087c9e370SSam Leffler prior to use. Specifically, if you intend to use WEP encryption 3187c9e370SSam Leffler with an 802.11 device load/configure wlan_wep; if you want to 3287c9e370SSam Leffler use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp, 3387c9e370SSam Leffler and wlan_xauth as required. 3487c9e370SSam Leffler 3571c1c49aSBrian Somers20041213: 3671c1c49aSBrian Somers The behaviour of ppp(8) has changed slightly. If lqr is enabled 3771c1c49aSBrian Somers (``enable lqr''), older versions would revert to LCP ECHO mode on 3871c1c49aSBrian Somers negotiation failure. Now, ``enable echo'' is required for this 3971c1c49aSBrian Somers behaviour. The ppp version number has been bumped to 3.4.2 to 4071c1c49aSBrian Somers reflect the change. 4171c1c49aSBrian Somers 4288046524SSam Leffler20041201: 4388046524SSam Leffler The wlan support has been updated to split the crypto support 4488046524SSam Leffler into separate modules. For static WEP you must configure the 4588046524SSam Leffler wlan_wep module in your system or build and install the module 4688046524SSam Leffler in place where it can be loaded (the kernel will auto-load 4788046524SSam Leffler the module when a wep key is configured). 4888046524SSam Leffler 4988046524SSam Leffler20041201: 5088046524SSam Leffler The ath driver has been updated to split the tx rate control 5188046524SSam Leffler algorithm into a separate module. You need to include either 5288046524SSam Leffler ath_rate_onoe or ath_rate_amrr when configuring the kernel. 5388046524SSam Leffler 5481adddf3SJohn Baldwin20041116: 5581adddf3SJohn Baldwin Support for systems with an 80386 CPU has been removed. Please 5681adddf3SJohn Baldwin use FreeBSD 5.x or earlier on systems with an 80386. 5781adddf3SJohn Baldwin 5842ba1c57SPoul-Henning Kamp20041110: 5942ba1c57SPoul-Henning Kamp We have had a hack which would mount the root filesystem 6042ba1c57SPoul-Henning Kamp R/W if the device were named 'md*'. As part of the vnode 6142ba1c57SPoul-Henning Kamp work I'm doing I have had to remove this hack. People 6242ba1c57SPoul-Henning Kamp building systems which use preloaded MD root filesystems 6342ba1c57SPoul-Henning Kamp may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in 6442ba1c57SPoul-Henning Kamp their /etc/rc scripts. 6542ba1c57SPoul-Henning Kamp 66c94c54e4SAndre Oppermann20041102: 67c94c54e4SAndre Oppermann The size of struct tcpcb has changed again due to the removal 68c94c54e4SAndre Oppermann of RFC1644 T/TCP. You have to recompile userland programs that 69c94c54e4SAndre Oppermann read kmem for tcp sockets directly (netstat, sockstat, etc.) 70c94c54e4SAndre Oppermann 71cd109b0dSAndre Oppermann20041022: 72cd109b0dSAndre Oppermann The size of struct tcpcb has changed. You have to recompile 73cd109b0dSAndre Oppermann userland programs that read kmem for tcp sockets directly 74cd109b0dSAndre Oppermann (netstat, sockstat, etc.) 75cd109b0dSAndre Oppermann 76cf0684aeSMike Makonnen20041007: 77028a5b92SMike Makonnen The FreeBSD keyword is no longer a requirement for a valid 78028a5b92SMike Makonnen rc.d script. The rc(8) and rc.shutdown(8) scripts no longer check 79028a5b92SMike Makonnen for the existence of this keyword when ordering rc.d scripts. 8000bd8f10SMike Makonnen This change touches most of the file in /etc/rc.d; therefore, 8100bd8f10SMike Makonnen if you have not modified any files in that directory it may 8200bd8f10SMike Makonnen be easier to rm -rf /etc/rc.d and then use the -i switch with 8300bd8f10SMike Makonnen mergemaster(8). 84028a5b92SMike Makonnen 85028a5b92SMike Makonnen20041007: 86cf0684aeSMike Makonnen One of the syscalls the 1:1 threading library libthr uses has 87cf0684aeSMike Makonnen changed, thus breaking ABI compatibility. Make sure you rebuild 88cf0684aeSMike Makonnen this library with the kernel. 89cf0684aeSMike Makonnen 90773322d5SDavid E. O'Brien20041004: 91773322d5SDavid E. O'Brien A major sweep over the tty drivers to elimnate approx 3100 92773322d5SDavid E. O'Brien lines of copy&pasted code have been performed. As a part of 93773322d5SDavid E. O'Brien this change some tty devices have changed names: 94773322d5SDavid E. O'Brien sio devices are now named: {tty,cua}d%d[.init,.lock] 95773322d5SDavid E. O'Brien ucom devices are now named: {tty,cua}U%d[.init,.lock] 96773322d5SDavid E. O'Brien For other drivers see the commit logs. 97773322d5SDavid E. O'Brien 9885a8b887SKen Smith20041001: 9985a8b887SKen Smith The following libraries had their version number bumped up: 10085a8b887SKen Smith /lib/libm.so.2 -> libm.so.3 10185a8b887SKen Smith /lib/libreadline.so.4 -> libreadline.so.5 10285a8b887SKen Smith /usr/lib/libhistory.so.4 -> libhistory.so.5 10385a8b887SKen Smith /usr/lib/libopie.so.2 -> libopie.so.3 10485a8b887SKen Smith /usr/lib/libpcap.so.2 -> libpcap.so.3 10585a8b887SKen Smith FreeBSD 4.10 versions of these libraries will be added to the 10685a8b887SKen Smith compat4x collection. If you expect to be able to run old 4.X 10785a8b887SKen Smith executables you will need to remove the old versions of these 10885a8b887SKen Smith libraries. However note that any 5.X executables you have built 10985a8b887SKen Smith will stop working once you remove those old libraries. You should 11085a8b887SKen Smith have all your ports/packages rebuilt before removing the old 11185a8b887SKen Smith libraries. 11285a8b887SKen Smith 113d6a8d588SMax Laier20040929: 114d6a8d588SMax Laier The pfil API has gained an additional argument to pass an inpcb. 115d6a8d588SMax Laier You should rebuild all pfil consuming modules: ipfw, ipfilter 116d6a8d588SMax Laier and pf. 117d6a8d588SMax Laier 1188f1bb389SDoug Barton20040928: 119cfeb1f52SDoug Barton If named is enabled, the default is now to run it in a chroot 1208f1bb389SDoug Barton "sandbox." For users with existing configurations in 1218f1bb389SDoug Barton /etc/namedb the migration should be simple. Upgrade your 1228f1bb389SDoug Barton world as usual, then after installworld but before 1238f1bb389SDoug Barton mergemaster do the following: 1248f1bb389SDoug Barton 1258f1bb389SDoug Barton If named is running: /etc/rc.d/named stop 1268f1bb389SDoug Barton cd /etc 1278f1bb389SDoug Barton mv namedb namedb.bak 1288f1bb389SDoug Barton mkdir -p /var/named/etc/namedb 1298f1bb389SDoug Barton cp -Rp namedb.bak/* /var/named/etc/namedb/ 1308f1bb389SDoug Barton mergemaster (with your usual options) 1318f1bb389SDoug Barton If using the generated localhost* files: 1328f1bb389SDoug Barton cd /var/named/etc/namedb 1338f1bb389SDoug Barton /bin/sh make-localhost 1348f1bb389SDoug Barton rm -f localhost-v6.rev localhost.rev 135cfeb1f52SDoug Barton /etc/rc.d/syslogd restart 1368f1bb389SDoug Barton /etc/rc.d/named start 1378f1bb389SDoug Barton 1388f1bb389SDoug Barton If you are using a custom configuration, or if you have 1398f1bb389SDoug Barton customised the named_* variables in /etc/rc.conf[.local] 1408f1bb389SDoug Barton then you may have to adjust the instructions accordingly. 1418f1bb389SDoug Barton It is suggested that you carefully examine the new named 1428f1bb389SDoug Barton variables in /etc/defaults/rc.conf and the options in 1438f1bb389SDoug Barton /var/named/etc/namedb/named.conf to see if they might 1448f1bb389SDoug Barton now be more suitable. 1458f1bb389SDoug Barton 1465d36721aSDoug Barton20040925: 1475d36721aSDoug Barton BIND 9 has been imported into the base, and is now fully 1485d36721aSDoug Barton functional. BIND 8 has now been removed. There are numerous 1495d36721aSDoug Barton differences between BIND 8 and 9, and users with critical 1505d36721aSDoug Barton named installations should read the migration documentation 1515d36721aSDoug Barton in /usr/share/doc/bind9/misc/migration. There is also a 1525d36721aSDoug Barton new instruction manual in /usr/share/doc/bind9/arm. 1535d36721aSDoug Barton 1545d36721aSDoug Barton The key differences that most users will experience are in 1555d36721aSDoug Barton how picky BIND 9 is about zone file format. If you are using 1565d36721aSDoug Barton named as a resolving (caching) name server, you will likely 1575d36721aSDoug Barton not have trouble. 1585d36721aSDoug Barton 159f50b1bdbSDoug Barton The following files are part of the old BIND 8 installation 160f50b1bdbSDoug Barton and should be removed: 161f50b1bdbSDoug Barton /usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer 162f50b1bdbSDoug Barton /usr/sbin/named.restart /usr/sbin/ndc 163f50b1bdbSDoug Barton 164f50b1bdbSDoug Barton The following files have moved to /usr/bin, and should be 165f50b1bdbSDoug Barton removed from their old locations: 166f50b1bdbSDoug Barton /usr/sbin/nslookup /usr/sbin/nsupdate 167f50b1bdbSDoug Barton 168f5ee5a8bSMax Laier20040914: 169f5ee5a8bSMax Laier The format of the pflogd(8) logfile "/var/log/pflog" has changed for 170f5ee5a8bSMax Laier architectures that have a 64 bit long type to make it compatible to 171f5ee5a8bSMax Laier the standard pcap format. In order to prevent corruption move away 172f5ee5a8bSMax Laier any old logfile before using a new pflogd(8). 173f5ee5a8bSMax Laier 174d698cdb3SJohn-Mark Gurney20040906: 175d698cdb3SJohn-Mark Gurney debug.witness_* has been renamed to debug.witness.*. There are 176d698cdb3SJohn-Mark Gurney compatibility tunables left in for a few days. Update loader.conf 177d698cdb3SJohn-Mark Gurney as necessary. 178d698cdb3SJohn-Mark Gurney 1794ff62bd9SBrooks Davis20040902: 1804ff62bd9SBrooks Davis The ifi_epoch change has been reverted because the ABI breakage 1814ff62bd9SBrooks Davis was too extensive. If you are running with a kernel/userland 1824ff62bd9SBrooks Davis containing the initial change (20040830), you should heed the 1834ff62bd9SBrooks Davis warning about ifconfig incompatibility when upgrading again. 1844ff62bd9SBrooks Davis With this change, 5.3 and 6.0 ifconfigs and kernels are once 1854ff62bd9SBrooks Davis again interoperable. 1864ff62bd9SBrooks Davis 1871fc4519bSBrooks Davis20040830: 1881fc4519bSBrooks Davis A new variable, ifi_epoch, has been added to struct if_data 1891fc4519bSBrooks Davis which is part if struct ifnet. This means all network drivers 1901fc4519bSBrooks Davis and network monitoring applications need to be recompiled. 1911fc4519bSBrooks Davis 1923789fb75SBrooks Davis WARNING WARNING WARNING WARNING WARNING WARNING WARNING 1933789fb75SBrooks Davis 1943789fb75SBrooks Davis This also breaks ifconfig compatibility. An old ifconfig will 1953789fb75SBrooks Davis not work with the new kernel and a new ifconfig will not work 1963789fb75SBrooks Davis with the old. It is strongly recommended that you make a copy 1973789fb75SBrooks Davis of your old ifconfig before installworld. If you are installing 1983789fb75SBrooks Davis remotely, you must copy over a new ifconfig before rebooting in 1993789fb75SBrooks Davis to the new kernel. 2003789fb75SBrooks Davis 201c1c94d5cSRobert Watson20040828: 202c1c94d5cSRobert Watson The default configuration for the network stack has been changed 203c1c94d5cSRobert Watson such that it now runs without the Giant lock unless configured 204c1c94d5cSRobert Watson otherwise. If you experience network-related instability, you 205c1c94d5cSRobert Watson may wish to try setting "debug.mpsafenet=0" or compiling the 206c1c94d5cSRobert Watson kernel with "options NET_WITH_GIANT". Details on the netperf 207c1c94d5cSRobert Watson project may be found at: 208c1c94d5cSRobert Watson 209c1c94d5cSRobert Watson http://www.watson.org/~robert/freebsd/netperf/ 210c1c94d5cSRobert Watson 211c1c94d5cSRobert Watson Including the 20040828 announcement of configuration change 212c1c94d5cSRobert Watson details. 213c1c94d5cSRobert Watson 214c21fd232SAndre Oppermann20040827: 215c21fd232SAndre Oppermann PFIL_HOOKS are a fixed part of the network stack now and do not 216c21fd232SAndre Oppermann need to be specified in the kernel configuration file anymore. 217c21fd232SAndre Oppermann 218f036d408SJulian Elischer20040819: 219f036d408SJulian Elischer Netgraph changed its message format slightly to align the data 220f036d408SJulian Elischer portion well on 64 bit machines. 221f036d408SJulian Elischer Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd, 222f036d408SJulian Elischer pppoed, bluetooth, ATM) should be recompiled when a new kernel 223f036d408SJulian Elischer is installed. 224f036d408SJulian Elischer 225b067abfaSAndre Oppermann20040817: 226b05bb3e7SMax Laier IPFW has been converted to use pfil(9). This change is 227b067abfaSAndre Oppermann transparent to userland and preserves the ipfw ABI. The ipfw 228b067abfaSAndre Oppermann core packet inspection and filtering functions have not been 229b05bb3e7SMax Laier changed, only how ipfw is invoked is different. 230b067abfaSAndre Oppermann 231f13a7951SDavid Malone20040814: 232f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 233f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 234f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 235f13a7951SDavid Malone 2363a004637SMax Laier20040807: 2373a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 2383a004637SMax Laier if_carp placeholder. All kernel modules implementing network 2393a004637SMax Laier interfaces must be recompiled as a result. 2403a004637SMax Laier 2414f34d8d1SJohn-Mark Gurney20040806: 2424f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 243ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 2444f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 2454f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 2464f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 2474f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 2484f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 2494f34d8d1SJohn-Mark Gurney 2508f075db4SMark Murray20040802: 2518f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 2528f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 2538f075db4SMark Murray 254d064d6dbSMark Murray20040801: 255d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 256d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 257d064d6dbSMark Murray GENERIC for examples. 258d064d6dbSMark Murray 259b289983eSAlexander Kabaev20040728: 26054bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 26154bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 26254bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 26354bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 264d0e54ab4SDavid E. O'Brien compiler. If you are getting run-time error such as 265d0e54ab4SDavid E. O'Brien /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" 266d0e54ab4SDavid E. O'Brien This entry does apply to you. 267d0e54ab4SDavid E. O'Brien 268d0e54ab4SDavid E. O'Brien A new unit-at-a-time optimization mode, which is default in this 269d0e54ab4SDavid E. O'Brien compiler release, is more aggressive in removing unused static 270d0e54ab4SDavid E. O'Brien symbols. This is the likely cause of 'make buildworld' breakages 271cd5f061cSWarner Losh with non-default CFLAGS where optimization level is set to -O2 272cd5f061cSWarner Losh or higher. 27354bd5271SAlexander Kabaev 2746e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 2756e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 2766e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 2776e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 2786e1afae3SWarner Losh 27936ed21e6SRobert Watson20040727: 28036ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 28136ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 28236ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 28336ed21e6SRobert Watson a result. 28436ed21e6SRobert Watson 2856305ac24SSeigo Tanimura20040716: 2866305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 2876305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 2886305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 2896305ac24SSeigo Tanimura 290e623dcb7SMarcel Moolenaar20040710: 291e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 292e623dcb7SMarcel Moolenaar 293e623dcb7SMarcel Moolenaar20040710: 294e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 295e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 296e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 297773322d5SDavid E. O'Brien hints (hint.sio.0.flags="0x10") are now required for the sio(4) 298773322d5SDavid E. O'Brien driver to become a console or debug port. The NO_SIO option has 299773322d5SDavid E. O'Brien been decommissioned because of this. 300773322d5SDavid E. O'Brien Running mergemaster is the easiest way to ensure your 301773322d5SDavid E. O'Brien 'boot/device.hints' has the needed line. 302e623dcb7SMarcel Moolenaar 303e623dcb7SMarcel Moolenaar20040710: 304e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 305e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 306e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 307e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 308e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 309e623dcb7SMarcel Moolenaar option for this. 310e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 311e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 312e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 313e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 3145bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 315e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 316e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 317e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 318e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 319e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 320e623dcb7SMarcel Moolenaar symbol lookups through the linker. 321e623dcb7SMarcel Moolenaar 3226421d1dbSMaksim Yevmenkin20040708: 3236421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 3246421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 3256421d1dbSMaksim Yevmenkin 32658af3216SWarner Losh20040702: 32758af3216SWarner Losh The native preemption has been added to the kernel scheduler. 3285bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 3295bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 3305bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 33158af3216SWarner Losh scheduler as a workaround. 33258af3216SWarner Losh 333c2dba668SNate Lawson20040630: 3348ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 3358ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 336a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 337a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 338a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 339a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 340a6c26e1cSBruce M Simpson example of such changes. 3418ed370fdSJulian Elischer 34258af3216SWarner Losh This also broke i4b, although the compile problem has been papered 34358af3216SWarner Losh over. 34458af3216SWarner Losh 3458ed370fdSJulian Elischer20040630: 346c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 3475bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 348c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 349c2dba668SNate Lawson If you think ACPI does work on your system and want to override 350c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 351c2dba668SNate Lawson loader prompt. 352c2dba668SNate Lawson 3538ee2ac9eSMax Laier20040623: 3545bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 3558ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 3568ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 3578ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 3588ee2ac9eSMax Laier 3593db5687dSBrooks Davis20040622: 3603db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 3613db5687dSBrooks Davis require a recompile of modules using cloning and modification of 3623db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 3633db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 3643db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 3653db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 3663db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 3673db5687dSBrooks Davis 368e0ae81f3SDag-Erling Smørgrav20040621: 369e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 370e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 371e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 372e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 373e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 374e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 375e0ae81f3SDag-Erling Smørgrav during the next reboot. 376e0ae81f3SDag-Erling Smørgrav 3774717d22aSJohn Polstra20040614: 3784717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 3794717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 3804717d22aSJohn Polstra the ips module and any third-party modules which call 3814717d22aSJohn Polstra sema_timedwait. 3824717d22aSJohn Polstra 3836cb7a382SMax Laier20040613: 3846cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 3856cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 386df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 387df843493SMax Laier please recompile and reinstall world. 3886cb7a382SMax Laier 3892454685eSJulian Elischer20040607: 3902454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 3912454685eSJulian Elischer requires that you re-run config after updating your tree. 3922454685eSJulian Elischer 39364fef830SSeigo Tanimura20040601: 39464fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 39564fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 39664fef830SSeigo Tanimura kernel configuration. 39764fef830SSeigo Tanimura 398bb4f06e7SAndre Oppermann20040423: 399bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 400bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 401bb4f06e7SAndre Oppermann options are not affected but those with options may break until 402bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 403bb4f06e7SAndre Oppermann 40405641e82SColin Percival20040420: 40505641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 40605641e82SColin Percival date may be incompatible with kernel modules compiled prior to 40705641e82SColin Percival 20040406. 40805641e82SColin Percival 409d0dc9183SWarner Losh20040414: 410d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 411d0dc9183SWarner Losh problems for your system, please disable it using the tunable 412d0dc9183SWarner Losh hw.pci.do_powerstate=0. 413d0dc9183SWarner Losh 414d0dc9183SWarner Losh20040412: 415d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 416d0dc9183SWarner Losh drive is still broken. 417d0dc9183SWarner Losh 418d0dc9183SWarner Losh20040410: 419d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 420d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 421d0dc9183SWarner Losh the unanticipated problems have been resolved. 422d0dc9183SWarner Losh 4238633bbeaSBrooks Davis20040409: 4248633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 4258633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 4268633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 4278633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 42876c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 4298633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 4308633bbeaSBrooks Davis 431d40d033aSRobert Watson20040322: 432d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 433d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 434d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 435d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 436d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 437d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 438d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 439d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 440d40d033aSRobert Watson locking is merged to permit this to take place. 441d40d033aSRobert Watson 442ec9b318eSGarance A Drosehn20040310: 443ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 444ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 445ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 446ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 447ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 448ec9b318eSGarance A Drosehn 449fc28f1ffSMax Laier20040308: 450fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 451fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 4524c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 4534c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 454b05bb3e7SMax Laier The pf system consists of the following three devices: 455fc28f1ffSMax Laier device pf # required 456fc28f1ffSMax Laier device pflog # optional 457fc28f1ffSMax Laier device pfsync # optional 458fc28f1ffSMax Laier 4593aff5d06SDag-Erling Smørgrav20040303: 4603aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 4613aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 4623aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 4633aff5d06SDag-Erling Smørgrav 4643aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 4653aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 4663aff5d06SDag-Erling Smørgrav 4673aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 4683aff5d06SDag-Erling Smørgrav to use libpthread instead. 4693aff5d06SDag-Erling Smørgrav 470fd63c5b3SDag-Erling Smørgrav20040226: 4719d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 472fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 473fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 474fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 475fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 476fd63c5b3SDag-Erling Smørgrav 477714ae42aSBruce M Simpson20040225: 478e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 479e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 480e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 481e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 482e07a40f3SBrian Feldman should remain unaffected. 483e07a40f3SBrian Feldman 484e07a40f3SBrian Feldman20040225: 485714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 486714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 487714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 488714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 489714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 490714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 491714ae42aSBruce M Simpson 492fbd2e692SAndre Oppermann20040224: 493fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 4945bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 495fbd2e692SAndre Oppermann 496158b90daSWarner Losh20040222: 497158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 498158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 499158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 500158b90daSWarner Losh Drivers outside the tree will need to be updated. 501158b90daSWarner Losh 502b7b1e150SMike Makonnen20040207: 503b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 504b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 505b7b1e150SMike Makonnen 506aca89ee6SDaniel Eischen20040130: 507aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 508aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 509aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 510aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 511aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 512aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 513aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 514aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 515aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 516aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 517aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 518aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 519aca89ee6SDaniel Eischen do not work with libpthread. 520aca89ee6SDaniel Eischen 52168b7b3a9SAlex Dupre20040125: 52268b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 52368b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 52468b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 52568b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 52668b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 52768b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 52868b7b3a9SAlex Dupre 529ff46e0deSWarner Losh20040125: 530ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 531ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 532ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 533ff46e0deSWarner Losh 534ce41f4bfSRobert Watson20031213: 535ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 536ce41f4bfSRobert Watson if the login process is unable to successfully set the 537ce41f4bfSRobert Watson process credentials to include all groups defined for the 538ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 539ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 540ce41f4bfSRobert Watson defined, or they will be unable to log in. 541ce41f4bfSRobert Watson 542c124fa05SJohn Baldwin20031203: 543c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 544c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 545c124fa05SJohn Baldwin 5468ad1f5e4SHartmut Brandt20031112: 54730093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 54830093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 54997209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 55097209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 55197209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 55297209ca3SRobert Watson not know about the new system calls that support the new statfs 5533f631d52SMarcel Moolenaar structure. 5543f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 5553f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 5563f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 5573f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 5583f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 5593f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 5603f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 5613f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 5623f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 5633f631d52SMarcel Moolenaar these changes are installed. 56430093b05SWarner Losh 56530093b05SWarner Losh ****************************DANGER******************************* 56630093b05SWarner Losh 56730093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 56830093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 56930093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 57030093b05SWarner Losh kernel. 57164a18d6fSKirk McKusick 57264a18d6fSKirk McKusick20031112: 5738ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 5748ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 5758ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 5768ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 5778ad1f5e4SHartmut Brandt sync before rebooting. 5788ad1f5e4SHartmut Brandt 579c53a5d8fSJohn Baldwin20031111: 580c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 581c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 582c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 583c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 584c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 585c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 586c53a5d8fSJohn Baldwin 5878bf455a5SJohn Baldwin20031103: 5888bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 5898bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 5902a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 5918bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 5928bf455a5SJohn Baldwin 5939bf40edeSBrooks Davis20031031: 5949bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 5959bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 5969bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 5979bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 5989bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 5999bf40edeSBrooks Davis reflect this change. 6009bf40edeSBrooks Davis 60147a42c7aSPoul-Henning Kamp20030928: 60247a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 60347a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 6045bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 60547a42c7aSPoul-Henning Kamp 60607105342SMax Khon20030926: 60707105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 60807105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 60907105342SMax Khon 610fedf1d01SBruce M Simpson20030923: 611fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 612fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 613fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 614fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 615fedf1d01SBruce M Simpson 616db38f9cbSJacques Vidrine20030915: 617db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 618db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 619db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 620db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 621db38f9cbSJacques Vidrine 622c09d2c2bSMike Makonnen20030829: 623c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 624c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 625c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 626c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 627c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 628c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 629c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 630c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 631c09d2c2bSMike Makonnen may or may not exist on your system. 632c09d2c2bSMike Makonnen 63317c159dcSSøren Schmidt20030824: 63417c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 63517c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 636f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 637f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 63817c159dcSSøren Schmidt 639c1f61aa9SDavid E. O'Brien20030819: 640c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 641c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 642c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 643c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 64469f7bcf3SWarner Losh 64538c962e7SNate Lawson20030728: 64638c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 64738c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 64838c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 64938c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 65038c962e7SNate Lawson so the quirk can be re-enabled. 65138c962e7SNate Lawson 65274111097SWarner Losh20030724: 65374111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 65474111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 65574111097SWarner Losh 656178cf4e9SWarner Losh20030722: 657178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 658178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 659178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 660178cf4e9SWarner Losh FPU hardware. 661178cf4e9SWarner Losh 662178cf4e9SWarner Losh20030714: 663178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 664178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 665178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 666178cf4e9SWarner Losh People should report those issues to current@. 667178cf4e9SWarner Losh 668157c629aSWarner Losh20030711: 669157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 6708b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 67105538fa9SWarner Losh /usr/obj. 672157c629aSWarner Losh 67374111097SWarner Losh20030610: 67474111097SWarner Losh Remove deprecated locale names and transition period code 67574111097SWarner Losh for them, finishing switching to the new scheme. Check your 67674111097SWarner Losh LANG environment variable. 67774111097SWarner Losh 67874111097SWarner Losh20030609: 67974111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 68074111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 68174111097SWarner Losh important to remember beforehand if your source tree is on 68274111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 68374111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 68474111097SWarner Losh kernel. 68574111097SWarner Losh 68674111097SWarner Losh20030605: 6876cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 6886cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 6896cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 6906cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 6916cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 6926cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 6936cc6353fSMarcel Moolenaar 6946cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 6956cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 6966cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 6976cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 6986cc6353fSMarcel Moolenaar : 6996cc6353fSMarcel Moolenaar 7006cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 7016cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 7026cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 7036cc6353fSMarcel Moolenaar 70452b47445SMark Murray20030505: 70552b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 70652b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 70752b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 70852b47445SMark Murray 709a26df538SWarner Losh20030502: 710a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 711a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 712a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 713a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 714a26df538SWarner Losh 7154b065e2cSDoug Barton20030501: 7164b065e2cSDoug Barton The old rc system has been removed. Please report any problems 7174b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 7184b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 7194b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 7204b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 7214b065e2cSDoug Barton utilizes these old scripts has also been removed. 7224b065e2cSDoug Barton 72381cda3d9SWarner Losh20030423: 72481cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 72581cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 72681cda3d9SWarner Losh work around in devd will be removed around 20030507. You 72781cda3d9SWarner Losh have until then to upgrade your kernel before updating 72881cda3d9SWarner Losh userland. In general, you should have a userland and 72981cda3d9SWarner Losh kernel that's in sync with each other. However, given the 73081cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 73181cda3d9SWarner Losh allowances are made. 73281cda3d9SWarner Losh 73347a657d1SRuslan Ermilov20030329: 73447a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 73547a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 73647a657d1SRuslan Ermilov while upgrading the system through a buildworld. 73747a657d1SRuslan Ermilov 73847a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 73947a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 74047a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 74147a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 74247a657d1SRuslan Ermilov 74347a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 74447a657d1SRuslan Ermilov make cleandir && make obj && \ 74547a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 74647a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 74747a657d1SRuslan Ermilov 7485d2af00cSGregory Neil Shapiro20030208: 7495d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 7505d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 7515d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 7525d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 7535d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 7545d2af00cSGregory Neil Shapiro 7555d2af00cSGregory Neil Shapiro20030128: 7569db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 757ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 7589db58771SPoul-Henning Kamp be removed when convenient. 7599db58771SPoul-Henning Kamp 7608d9b3f57SJake Burkholder20030126: 7618d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 7628d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 7638d9b3f57SJake Burkholder 7641c5efda5SJeff Roberson20030125: 7651c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 7661c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 767ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 7681c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 7691c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 7701c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 7711c5efda5SJeff Roberson 7729d1d64f5SWarner Losh20030115: 7739d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 7749d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 7759d1d64f5SWarner Losh properly. 7769d1d64f5SWarner Losh 777c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 778c9fdb80aSWarner Losh configured for point to point links to bring it more in line 779c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 780c9fdb80aSWarner Losh with NetBSD. 781c9fdb80aSWarner Losh 782161dc364SAlexander Kabaev20021222: 783161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 784161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 785161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 786161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 787161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 788161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 78984cc83efSAlexander Kabaev rebuilt. 790161dc364SAlexander Kabaev 791fb4c8061SMartin Blapp20021216: 792fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 79389056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 794fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 7959d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 796fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 797fb4c8061SMartin Blapp 79817d47eb3SGiorgos Keramidas20021202: 79917d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 80017d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 80117d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 80217d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 80317d47eb3SGiorgos Keramidas 804a4459294SBill Fenner20021029: 805a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 806a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 807a4459294SBill Fenner consumers in sync. 808a4459294SBill Fenner 809fc8c157fSWarner Losh20021024: 810c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 811c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 812c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 813c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 814c57404feSRuslan Ermilov partition really is on. The old device names have gone 815c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 816c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 817c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 81869f7bcf3SWarner Losh 819fd9e8bdaSAndrew Gallatin20021023: 820fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 821fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 822fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 823fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 824fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 825fd9e8bdaSAndrew Gallatin 826fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 827fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 828fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 829fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 830fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 831fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 832fd9e8bdaSAndrew Gallatin 833f8a4c901SWarner Losh20020831: 834f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 835f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 836f8a4c901SWarner Losh programs and libraries need to be recompiled. 837f8a4c901SWarner Losh 838f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 839f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 840f8a4c901SWarner Losh 841c2248fa2SJens Schweikhardt20020827: 842c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 843c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 844c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 845c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 846c2248fa2SJens Schweikhardt 8470d533e43SRuslan Ermilov20020815: 8480d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 8490d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 8500d533e43SRuslan Ermilov again. 8510d533e43SRuslan Ermilov 85233c1de7dSRuslan Ermilov20020729: 85333c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 85433c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 85533c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 85633c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 85733c1de7dSRuslan Ermilov 8582b877facSJulian Elischer20020702: 8592b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 8602b877facSJulian Elischer There are still some minor problems with some signals but the 8612b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 8622b877facSJulian Elischer but each can successfully complete multiple buildworlds. 8632b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 8642b877facSJulian Elischer 86506596d37SWarner Losh20020701: 86606596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 86706596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 86806596d37SWarner Losh GNOME. 86906596d37SWarner Losh 87095ba4330SJacques Vidrine20020511: 87195ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 87295ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 87395ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 87495ba4330SJacques Vidrine with the set-user-ID bit set. 87595ba4330SJacques Vidrine 876a81da3c9SDavid E. O'Brien20020510: 877f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 878f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 8794b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 880f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 881f50caf6fSDavid E. O'Brien 882f50caf6fSDavid E. O'Brien20020510: 883a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 884a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 885a81da3c9SDavid E. O'Brien and then do a cvs update. 886a81da3c9SDavid E. O'Brien 887528a0ef5SJacques Vidrine20020421: 888528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 889528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 890528a0ef5SJacques Vidrine 89185aa5a2eSGregory Neil Shapiro20020404: 89285aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 89385aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 89485aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 89585aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 89685aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 89785aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 89885aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 89985aa5a2eSGregory Neil Shapiro 9008f1e4358SRuslan Ermilov20020403: 9018f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 9028f1e4358SRuslan Ermilov 9032292c02eSWarner Losh20020315: 9042292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 9052292c02eSWarner Losh 90669f7bcf3SWarner Losh20020225: 90769f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 90869f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 90969f7bcf3SWarner Losh 9108f35c493SWarner Losh20020217: 9118f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 9128f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 9138f35c493SWarner Losh command line mail submission has changed. Be sure to run 9148f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 9158f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 9168f35c493SWarner Losh 917835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 918835284beSWarner Losh required in order for sendmail to run as a set-group-ID 919835284beSWarner Losh binary. A 'make installworld' will use the new user and group 920835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 921835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 922835284beSWarner Losh and group must be merged from src/etc/group and 923835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 924835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 925835284beSWarner Losh mergemaster before this will work if you are updating from a 926835284beSWarner Losh very old version of current. The updating recipe has changed 927835284beSWarner Losh as of this date. 928835284beSWarner Losh 929fa9401c1SWarner Losh20020112: 930fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 931fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 932fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 933fa9401c1SWarner Losh you have local modifications, you can use 934fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 935fa9401c1SWarner Losh /etc/pam.d. 936fa9401c1SWarner Losh 937fa9401c1SWarner Losh Please see the following url for more details: 938fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 93947d0d01fSWarner Losh20011229: 94047d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 94147d0d01fSWarner Losh networkfs_types, please note that it has changed 94247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 94347d0d01fSWarner Losh 944514318a8SWarner Losh20011220: 945514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 946514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 947514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 948514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 949514318a8SWarner Losh version have now been merged back into the base system's 950514318a8SWarner Losh version now. The only user-visible change resulting from this 951514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 952514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 953514318a8SWarner Losh as well. (There has never been rc file support for 954514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 955514318a8SWarner Losh reverted by the time the changes are MFCed.) 956514318a8SWarner Losh 957514318a8SWarner Losh20011215: 958514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 959514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 960514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 961514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 962514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 963514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 964514318a8SWarner Losh will need to be customized then for `odd' densities using 965514318a8SWarner Losh fdcontrol(8). 966514318a8SWarner Losh 9672d22e2bfSWarner Losh20011209: 9682d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 9692d22e2bfSWarner Losh and truss(1) now works again. 9702d22e2bfSWarner Losh 9719e0428e2SWarner Losh20011207: 9729e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 9739e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 9749e0428e2SWarner Losh see 9759e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 9769e0428e2SWarner Losh for details. 9779e0428e2SWarner Losh 9789bab8c59SWarner Losh20011204: 9799bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 9809bab8c59SWarner Losh kernel and burncd to be in sync. 9819bab8c59SWarner Losh 982e57d8b01SWarner Losh20011203: 983e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 984e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 985e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 986e57d8b01SWarner Losh not there already. 987e57d8b01SWarner Losh 988e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 989e57d8b01SWarner Losh until the issue has been resolved. 990e57d8b01SWarner Losh 991b001d36fSJacques Vidrine20011202: 992b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 993b001d36fSJacques Vidrine patched. 994b001d36fSJacques Vidrine 9954b676ec1SWarner Losh20011126: 9964b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 9975ebbf43eSWarner Losh after this date. You need to do this only once. 9984b676ec1SWarner Losh 999d961e462SWarner Losh20011103: 1000d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 1001d961e462SWarner Losh edges may be left, but for the most part things should be 10024b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 1003d961e462SWarner Losh 1004d961e462SWarner Losh20011030: 1005d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 1006d961e462SWarner Losh choppy waves in the upgrade process. 1007d961e462SWarner Losh 10081fe003b6SWarner Losh20011030: 1009a4b6fda0SWarner Losh The asr driver problem has been resolved. 10101fe003b6SWarner Losh 10111fe003b6SWarner Losh20011027: 10121fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 10131fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 10141fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 10151fe003b6SWarner Losh try to use from this date forward. 10161fe003b6SWarner Losh 10171fe003b6SWarner Losh20011025: 10181fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 10191fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 10201fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 10211fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 10221fe003b6SWarner Losh TARGET_ARCH=i386. 10231fe003b6SWarner Losh 1024d05f9643SWarner Losh20011001: 1025d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 1026d05f9643SWarner Losh You must recompile both the kernel and userland applications 1027d05f9643SWarner Losh at the same time. 1028d05f9643SWarner Losh 102958970f85SWarner Losh20010929: 103058970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 103158970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 103258970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 103358970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 10349d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 103558970f85SWarner Losh 103658970f85SWarner Losh20010927: 103758970f85SWarner Losh Some weird problems result from using ACPI on some machines. 103858970f85SWarner Losh To disable ACPI you can add 103966ff0e67SMax Khon hint.acpi.0.disabled="1" 104058970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 104158970f85SWarner Losh loader "ok" prompt). 104258970f85SWarner Losh 104358970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 104458970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 104558970f85SWarner Losh file and not list acpi in that list. 1046378f4486SAlfred Perlstein 10475119d237SWarner Losh20010924: 10485119d237SWarner Losh The buildworld has been fixed. You may need to install 10495119d237SWarner Losh the 4.x compatibility libraries for some old binaries 10508b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 10518b039fffSWarner Losh get them installed on every installworld, or execute the 10528b039fffSWarner Losh following to get them installed only once: 10538b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 105458970f85SWarner Losh make all install 10558b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 10565119d237SWarner Losh 10573c293725SWarner Losh20010919: 10583c293725SWarner Losh There's a bug in the world build process. The cross-tools 10593c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 10603c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 1061772730c7SWarner Losh workaround is to add 10623c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 10633c293725SWarner Losh before building world when upgrading from 4.x to current. This 10643c293725SWarner Losh can be removed afterwards. 10653c293725SWarner Losh 10663c293725SWarner Losh A proper fix to the buildworld target is needed. 10673c293725SWarner Losh 10683c293725SWarner Losh20010918: 10693c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 10703c293725SWarner Losh NFS may be unstable after this date. 10713c293725SWarner Losh 10723c293725SWarner Losh20010912: 10733c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 10743c293725SWarner Losh the kernel. While a few problems were introduced in the 10753c293725SWarner Losh initial commit, most of the major ones have been found and 10763c293725SWarner Losh corrected. 10773c293725SWarner Losh 10783c293725SWarner Losh20010901: 10793c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 10803c293725SWarner Losh arounds described in the 20010604 entry are now no longer 10813c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 10823c293725SWarner Losh have been rectified around this date. 10833c293725SWarner Losh 108498b17b95SWarner Losh20010823: 108598b17b95SWarner Losh named now runs as user bind and group bind rather than as 108698b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 108798b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 108898b17b95SWarner Losh and that group bind is available in /etc/group. Also make 108998b17b95SWarner Losh sure that user or group bind has read (and not write) 109098b17b95SWarner Losh permission for your name server configuration and that it 109198b17b95SWarner Losh has read and write permission for your slave zone files and 109298b17b95SWarner Losh directory. 109398b17b95SWarner Losh 109498b17b95SWarner Losh If you wish to continue to run named as root (a less secure 109598b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 109698b17b95SWarner Losh 109798b17b95SWarner Losh named_flags= 109898b17b95SWarner Losh 10997b9786edSMark Murray20010709: 11007b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 11017b9786edSMark Murray the ability of the shared library major number to handle. 11027b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 11037b9786edSMark Murray solution is to rebuild those ports. 11047b9786edSMark Murray 11051d28950eSWarner Losh20010628: 11061d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 11071d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 11081d28950eSWarner Losh 1109e72fd46aSWarner Losh20010625: 111098b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 111198b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 111298b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 111398b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 111498b17b95SWarner Losh IRQ configuration needs more safety belts. 111516de1a07SWarner Losh 11160d415dffSWarner Losh20010617: 1117e72fd46aSWarner Losh Softupdates problems have been corrected. 11180d415dffSWarner Losh 11190d415dffSWarner Losh20010614: 11200d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 11210d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 11220d415dffSWarner Losh kernel building methods. 11230d415dffSWarner Losh 11248b9959adSWarner Losh20010613: 11258b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 11268b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 1127e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 1128e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 11298b9959adSWarner Losh 1130e72fd46aSWarner Losh20010613: 11318b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 1132e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 1133e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 11348b9959adSWarner Losh 11350d415dffSWarner Losh20010612: 11360d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 11370d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 11380d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 11390d415dffSWarner Losh work around this issue, please use only one or the other mechanism 11400d415dffSWarner Losh until this bug is fixed. 11410d415dffSWarner Losh 1142e72fd46aSWarner Losh Please note that a feature of config is that if you have config 1143e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 1144ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 1145e72fd46aSWarner Losh 11460d415dffSWarner Losh20010610: 11470d415dffSWarner Losh Locale names have changed to match other systems better. 11480d415dffSWarner Losh 11496ccdb5e4SWarner Losh20010604: 11506ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 11516ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 11526ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 11533590182eSWarner Losh Interrupt storms look a lot like a hang. 11543590182eSWarner Losh 11553590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 11563590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 11573590182eSWarner Losh it is). 11583590182eSWarner Losh 11593590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 11603590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 11613590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 11623590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 11636ccdb5e4SWarner Losh 11640bc62786SWarner Losh20010530: 11650bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 11660bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 11670bc62786SWarner Losh a limited time. If you see 11680bc62786SWarner Losh 11690bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 11700bc62786SWarner Losh 11710bc62786SWarner Losh in your makeworld, then you need to migrate towards using 11720bc62786SWarner Losh COPY=-C. 11730bc62786SWarner Losh 117468a38c6cSWarner Losh20010525: 1175b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 1176c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 1177c4f4a728SWarner Losh definitely is in bad shape. 117868a38c6cSWarner Losh 1179ed0f29caSWarner Losh20010521: 1180ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 1181ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 1182ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 1183ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 1184ed0f29caSWarner Losh is 1185ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 1186ed0f29caSWarner Losh 118780c16af9SWarner Losh20010520: 118868a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 118980c16af9SWarner Losh 119080c16af9SWarner Losh20010519: 119180c16af9SWarner Losh pccard has had much reorganizational work done to it over 119280c16af9SWarner Losh the past few days. Everything should still work, but if 119380c16af9SWarner Losh not, please contact imp@freebsd.org. 119480c16af9SWarner Losh 1195a45f2d05SWarner Losh20010517: 1196a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 1197a45f2d05SWarner Losh userland at the same time. 1198a45f2d05SWarner Losh 1199a45f2d05SWarner Losh20010517: 1200a45f2d05SWarner Losh New ncurses imported. 1201a45f2d05SWarner Losh 12022988afcaSWarner Losh20010512: 12032988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 12042988afcaSWarner Losh will be the only way to go starting July 1. 12052988afcaSWarner Losh 12061a33dba7SWarner Losh20010504: 12071a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 12081a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 12091a33dba7SWarner Losh 121009946a51SWarner Losh20010502: 121109946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 121209946a51SWarner Losh 121309946a51SWarner Losh20010501: 121409946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 121509946a51SWarner Losh 121609946a51SWarner Losh20010430: 1217a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 121809946a51SWarner Losh go back in the water. 121909946a51SWarner Losh 122009946a51SWarner Losh20010429: 122109946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 122209946a51SWarner Losh this date, but before the correction date. 122309946a51SWarner Losh 122491dd3b53SWarner Losh20010423: 122591dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 122691dd3b53SWarner Losh 122791dd3b53SWarner Losh20010411: 122891dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 122991dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 123091dd3b53SWarner Losh Update only if you understand that you must not use the old 123191dd3b53SWarner Losh fsck with the new kernel ever. 123291dd3b53SWarner Losh 1233933b3269SWarner Losh20010330: 1234933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1235c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1236933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1237933b3269SWarner Losh 1238933b3269SWarner Losh20010319: 1239933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1240933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1241933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1242f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 124309946a51SWarner Losh 124409946a51SWarner Losh20010315: 124509946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1246ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 124709946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1248933b3269SWarner Losh 1249933b3269SWarner Losh20010312: 1250933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1251933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1252933b3269SWarner Losh 1253933b3269SWarner Losh20010312: 1254933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1255933b3269SWarner Losh instead of ad-hoc. 1256933b3269SWarner Losh 1257933b3269SWarner Losh20010310: 1258f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1259933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1260933b3269SWarner Losh ssh might not work if you don't. 1261933b3269SWarner Losh 126262353691SWarner Losh20010303: 126362353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 126462353691SWarner Losh which means that you must include the miibus in your kernel if 126562353691SWarner Losh you use the ed driver. 126662353691SWarner Losh 1267d325cf65SWarner Losh20010220: 1268d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1269d325cf65SWarner Losh safe to go back into the water. 1270d325cf65SWarner Losh 1271024daae6SWarner Losh20010211: 1272024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1273024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1274024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1275024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1276024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1277024daae6SWarner Losh 1278024daae6SWarner Losh To get to the new system, you'll need to use the following 1279024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1280024daae6SWarner Losh don't have to move this to the updating section. 1281024daae6SWarner Losh 1282024daae6SWarner Losh To get around the installworld problem, do: 1283024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1284024daae6SWarner Losh # make install 1285024daae6SWarner Losh # cd /usr/src 1286024daae6SWarner Losh # make installworld 1287024daae6SWarner Losh If that doesn't work, then try: 1288024daae6SWarner Losh # make -k installworld 1289024daae6SWarner Losh # make installworld 1290024daae6SWarner Losh 1291024daae6SWarner Losh20010207: 1292024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1293024daae6SWarner Losh do not include devfs in your kernel as problems result. 1294024daae6SWarner Losh 1295024daae6SWarner Losh20010205: 12967595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1297024daae6SWarner Losh Remove them from your config. 1298024daae6SWarner Losh 12991e159248SWarner Losh20010122: 13001e159248SWarner Losh ****************************** WARNING ****************************** 13011e159248SWarner Losh buildkernel has been changed slightly 13021e159248SWarner Losh ****************************** WARNING ****************************** 13031e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 13041e159248SWarner Losh should update your scripts and make.conf accordingly. 13051e159248SWarner Losh 13061e159248SWarner Losh20010119: 13071e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 13081e159248SWarner Losh This requires a new config to build correctly. 13091e159248SWarner Losh 1310aac7dfeaSWarner Losh20010116: 1311ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1312aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1313aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1314aac7dfeaSWarner Losh 1315aac7dfeaSWarner Losh20010110: 1316aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1317aac7dfeaSWarner Losh 1318aac7dfeaSWarner Losh20010102: 1319aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1320aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1321aac7dfeaSWarner Losh 132263c90c9eSWarner Losh20010101: 132363c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 132463c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 13255fd2a895SWarner Losh dump while building termcap. You can work around this problem 132663c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 132763c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 132863c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 132963c90c9eSWarner Losh might have been ignored by the -k option. 133063c90c9eSWarner Losh 13315fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 13325fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 13335fd2a895SWarner Losh of this working. 13345fd2a895SWarner Losh 1335aac7dfeaSWarner Losh20001228: 1336aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1337ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1338aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1339aac7dfeaSWarner Losh 1340de2bcc63SWarner Losh20001218: 1341de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1342de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1343de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1344de2bcc63SWarner Losh cards will not be recognized without it. 1345de2bcc63SWarner Losh 1346960773f7SWarner Losh20001205: 1347960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1348960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1349960773f7SWarner Losh adding the following in pam.conf: 1350960773f7SWarner Losh 1351960773f7SWarner Losh sshd auth sufficient pam_skey.so 1352960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1353960773f7SWarner Losh sshd session required pam_permit.so 1354960773f7SWarner Losh 13550acc635eSWarner Losh20001031: 13560acc635eSWarner Losh cvs updated to 1.11. 13570acc635eSWarner Losh 13580acc635eSWarner Losh20001020: 13590acc635eSWarner Losh The random device needs more entropy, so you need to make sure 13600acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 13610acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 13620acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 13630acc635eSWarner Losh workaround. 13640acc635eSWarner Losh 13650acc635eSWarner Losh20001010: 13660acc635eSWarner Losh ****************************** WARNING ****************************** 13670acc635eSWarner Losh Sendmail has been updated. 13680acc635eSWarner Losh ****************************** WARNING ****************************** 13690acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 13700acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 13710acc635eSWarner Losh is set. 13720acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 13730acc635eSWarner Losh commands. 13740acc635eSWarner Losh o Now using sendmail's version of vacation(1). 13750acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 13760acc635eSWarner Losh in /usr/share/sendmail/cf. 13770acc635eSWarner Losh o sendmail.cw changed to local-host-names 13780acc635eSWarner Losh 13790acc635eSWarner Losh More details can be found at 13800acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 13810acc635eSWarner Losh 13826e98a146SWarner Losh20001009: 13836e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 13846e98a146SWarner Losh your entire ports tree, or you will have problems. 13856e98a146SWarner Losh 13866e98a146SWarner Losh20001006: 1387685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 13886e98a146SWarner Losh the installed miniperl. It is recommended that you delete 13896e98a146SWarner Losh /usr/bin/miniperl. 13906e98a146SWarner Losh 1391073113a4SWarner Losh20001005: 1392073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1393685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1394073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1395073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1396073113a4SWarner Losh tree for anything to work. 1397073113a4SWarner Losh 13980acc635eSWarner Losh20000928: 13990acc635eSWarner Losh There was a change in the passwd format. Need more information. 14000acc635eSWarner Losh 1401be3885b3SWarner Losh20000916: 1402be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1403be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1404be3885b3SWarner Losh same time as your kernel. 1405be3885b3SWarner Losh 140676ec9675SWarner Losh20000914: 140776ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 140876ec9675SWarner Losh include the device will cause suspended laptops losing time 140976ec9675SWarner Losh when they resume. Include 141076ec9675SWarner Losh device pmtimer 141176ec9675SWarner Losh in your config file and 141201b9a434SWarner Losh hint.pmtimer.0.at="isa" 141376ec9675SWarner Losh to your /boot/device.hints file. 141476ec9675SWarner Losh 1415f4865386SMark Murray20000911: 1416f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1417f4865386SMark Murray rather than an option. The supplied kernel config files have 1418f4865386SMark Murray been updated. You will need to do something similar in your 1419f4865386SMark Murray own kernel config file. 1420f4865386SMark Murray Remove: 1421f4865386SMark Murray options RANDOMDEV 1422f4865386SMark Murray Add: 1423f4865386SMark Murray device random 1424f4865386SMark Murray If you prefer to load the loadable module, you need to do 1425f4865386SMark Murray nothing. 1426f4865386SMark Murray 1427d594498fSWarner Losh20000909: 1428d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1429d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1430d594498fSWarner Losh reflect this if you load this module at boot time. 1431d594498fSWarner Losh The line should read: 1432d594498fSWarner Losh random_load="YES" 1433d594498fSWarner Losh 14340deb7ddcSWarner Losh20000907: 14350deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 143616eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 143716eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 143816eb772dSWarner Losh sure you don't have model loading problems which might at 143916eb772dSWarner Losh first blush appear related to SMP. 144052bf24e7SWarner Losh 14415a01880bSWarner Losh20000906: 14425a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 14435a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 14445a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 14455a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 14465a01880bSWarner Losh don't have one, and you have host.conf. 14475a01880bSWarner Losh 14482b41163cSWarner Losh20000905: 144938d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 145038d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 145138d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 145238d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 145338d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 145438d6ecd2SWarner Losh 145538d6ecd2SWarner Losh20000905: 14568aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 14578aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 14588aab4bc7SWarner Losh is /boot/kernel. 14598aab4bc7SWarner Losh 14608aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 146138d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 146238d6ecd2SWarner Losh installkernel/installworld dance. 14632b41163cSWarner Losh 1464d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1465d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1466d594498fSWarner Losh modules in that directory instead of finding them in the correct 1467d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1468d594498fSWarner Losh is that the linux module crashes your machine after the update. 1469d594498fSWarner Losh 1470d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1471d594498fSWarner Losh mv /modules.old /boot/kernel.old 1472d594498fSWarner Losh chflags noschg /kernel.old 1473d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1474d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1475d594498fSWarner Losh fi 1476d594498fSWarner Losh 1477c22a309cSWarner Losh20000904: 1478c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1479c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1480c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1481c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1482c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1483c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1484c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1485c22a309cSWarner Losh is not likely to be generated. 1486c22a309cSWarner Losh 1487fdb9f54dSWarner Losh20000825: 1488fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 14899c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 14909c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 14919c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 14929c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 14939c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 14949c1a7444SWarner Losh messages will appear after the boot loader tries to start the 14959c1a7444SWarner Losh kernel. 14969c1a7444SWarner Losh 14979c1a7444SWarner Losh20000821: 14989c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 14999c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 15009c1a7444SWarner Losh /boot/loader.conf. 1501fdb9f54dSWarner Losh 15028f250aa7SWarner Losh20000812: 15035da0d091SWarner Losh suidperl is now always built and installed on the system, but 15045da0d091SWarner Losh with permissions of 511. If you have applications that use 15055da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 15065da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 15075da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 15085da0d091SWarner Losh will fix this until the next build. 15095da0d091SWarner Losh 15105da0d091SWarner Losh20000812: 15118f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 15128f250aa7SWarner Losh visible changes that may immediately affect your configuration 15138f250aa7SWarner Losh include: 15148f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 15158f250aa7SWarner Losh - newaliases limited to root and trusted users 15168f250aa7SWarner Losh - MSA port (587) turned on by default 15178f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 15188f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 15198f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 15208f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 15218f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 15228f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 15238f250aa7SWarner Losh 152471c38472SWarner Losh20000810: 152571c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 152671c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 152771c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 152871c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 152971c38472SWarner Losh specific use for it. 153071c38472SWarner Losh 153171c38472SWarner Losh20000729: 153271c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 153371c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 153471c38472SWarner Losh /etc/rc.conf if they want to have the same setup 153571c38472SWarner Losh afterwards (unless the variables already are set, of course): 153671c38472SWarner Losh # Enable network daemons for user convenience. 153771c38472SWarner Losh inetd_enable="YES" 153871c38472SWarner Losh portmap_enable="YES" 153971c38472SWarner Losh sendmail_enable="YES" 154071c38472SWarner Losh 154171c38472SWarner Losh20000728: 154271c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 154371c38472SWarner Losh will need to change that to nullfs_load="YES". 154471c38472SWarner Losh 15451dece4a9SWarner Losh20000728: 15461dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 15471dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 15481dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 15491dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 15501dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 15511dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 15521dece4a9SWarner Losh to /MYKERNEL. 15531dece4a9SWarner Losh 1554409e887cSWarner Losh20000711: 1555409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1556409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1557409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1558409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1559409e887cSWarner Losh for details on potential problems that you might have and how 1560409e887cSWarner Losh to get around them. 1561409e887cSWarner Losh 1562409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1563409e887cSWarner Losh clauses above, you needn't worry. 1564409e887cSWarner Losh 1565409e887cSWarner Losh20000711: 1566409e887cSWarner Losh /etc/security has been updated to print the inode number of 1567409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1568409e887cSWarner Losh in the number of changed programs the first time when you run 1569409e887cSWarner Losh mergemaster to get a new /etc/security. 1570409e887cSWarner Losh 1571673d13f2SWarner Losh20000710: 1572673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1573673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1574673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1575673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1576673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1577673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1578673d13f2SWarner Losh errors. (see below, 20000624). 1579673d13f2SWarner Losh 1580bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 15811dece4a9SWarner Losh 1582673d13f2SWarner Losh20000709: 1583c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1584c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1585c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1586673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1587673d13f2SWarner Losh 1588e98e26cdSWarner Losh20000706: 1589e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1590e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1591e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1592f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1593e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 15942c021c6cSMark Ovens interim if needed. 1595e98e26cdSWarner Losh 1596e98e26cdSWarner Losh20000705: 1597e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1598e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1599e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1600e98e26cdSWarner Losh details. 1601e98e26cdSWarner Losh 1602c373950eSWarner Losh20000704: 16032f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 16042f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 16052f961bc8SWarner Losh 16062f961bc8SWarner Losh20000704: 1607c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1608c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1609c373950eSWarner Losh rc.d scripts that haven't been updated. 1610c373950eSWarner Losh 161127dc3a2bSWarner Losh20000630: 161227dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 161327dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 161427dc3a2bSWarner Losh which should be reported to des@freebsd.org. 161527dc3a2bSWarner Losh 1616b8c215acSWarner Losh20000625: 1617b8c215acSWarner Losh From approximately this date forward, one must have the crypto 161827dc3a2bSWarner Losh system installed in order to build the system and kernel. 161927dc3a2bSWarner Losh While not technically strictly true, one should treat it as 162027dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 162127dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 162227dc3a2bSWarner Losh were required. You should check with the latest collections 162327dc3a2bSWarner Losh to make sure that these haven't changed. 1624b8c215acSWarner Losh 16257b990719SWarner Losh20000624: 16267b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 16277b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 16287b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 16291a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 16307b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 16317b990719SWarner Losh openssh and openssl should not be used to generate keys from this 16327b990719SWarner Losh date to the completion of the work. 16337b990719SWarner Losh 163427dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 163527dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 163627dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 163727dc3a2bSWarner Losh recreate the random and urandom devices. 163827dc3a2bSWarner Losh 163981e54c50SWarner Losh20000622: 164081e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 164181e54c50SWarner Losh BSD license. You may need to remove your symbolic links 164281e54c50SWarner Losh that used to be required when updating. 164381e54c50SWarner Losh 164439943833SWarner Losh20000621: 16452c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 16462a2f33fbSDaniel Baker the config file update procedure. 16472a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1648c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 164959df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 165059df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 165139943833SWarner Losh 1652290f9ad8SWarner Losh20000620: 1653290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1654290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1655290f9ad8SWarner Losh that workaround will no longer be required. 1656290f9ad8SWarner Losh 165790fb6346SWarner Losh20000615: 165890fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 165990fb6346SWarner Losh ad driver. If you haven't done so already, you must update 166090fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 166190fb6346SWarner Losh devices. 166290fb6346SWarner Losh 1663f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1664f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1665f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1666f75f65bbSWarner Losh may work). 1667f75f65bbSWarner Losh 1668ba26da8eSWarner Losh20000612: 1669ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1670290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1671c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1672290f9ad8SWarner Losh to your config file to compile them in statically. The format 1673f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1674f54a3542SWarner Losh NEWCARD for examples of the new format. 1675290f9ad8SWarner Losh 16769698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 16779698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 16789698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 16799698f2c0SWarner Losh in it. 1680bbcc5149SWarner Losh 1681d65850ebSWarner Losh20000522: 1682ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1683d65850ebSWarner Losh building a kernel after this point is advised that they need 1684d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1685d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1686d65850ebSWarner Losh 1687d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1688d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1689d9583a00SWarner Losh is recommended that you don't set this option until the problem 1690d9583a00SWarner Losh is resolved. 1691d9583a00SWarner Losh 16928039cedeSWarner Losh20000513: 16938039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 16948039cedeSWarner Losh 1695d65850ebSWarner Losh20000510: 16968039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 16978039cedeSWarner Losh This will require some care in updating alphas. A new libstand 16988039cedeSWarner Losh is requires for the boot blocks to build properly. 16998039cedeSWarner Losh 17008039cedeSWarner Losh20000503: 17018039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 17028039cedeSWarner Losh is now available. 17038039cedeSWarner Losh 1704d65850ebSWarner Losh20000502: 1705d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1706d65850ebSWarner Losh connected to the kernel building instead. 1707d65850ebSWarner Losh 1708be149406SNik Clayton20000427: 17098039cedeSWarner Losh You may need to build gperf 17108039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 17118039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 17128039cedeSWarner Losh an option only in -current. 17138039cedeSWarner Losh 17142b8dd5f4SWarner Losh20000417: 17152b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1716f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 17172b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 17182b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 17192c021c6cSMark Ovens before you reboot, you'll need to issue: 17202b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 17212b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 17222b8dd5f4SWarner Losh 17238d9f1945SWarner Losh20000320: 17242b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 17252b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 17262b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1727ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 17282b8dd5f4SWarner Losh to the start of /etc/rc.conf. 17298d9f1945SWarner Losh 1730f8ab1dd6SWarner Losh20000319: 1731f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1732f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1733f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1734f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1735f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1736f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1737f8ab1dd6SWarner Losh 173819cada77SWarner Losh20000318: 1739f699bbbbSMark Ovens We've entered the traditional post release dumping party. 174019cada77SWarner Losh Large kernel changes are being committed and are in the 174119cada77SWarner Losh works. It is important to keep the systems' klds and kernel 174219cada77SWarner Losh in sync as kernel interfaces and structures are changing. 174319cada77SWarner Losh Before reporting kernel panics, make sure that all modules 174419cada77SWarner Losh that you are loading are up to date. 1745ba228352SWarner Losh 174619cada77SWarner Losh20000315: 17476d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 17486d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 17496d23c382SWarner Losh will do the trick. This isn't critical until you remove your 17506d23c382SWarner Losh wd device entries in /dev, at which point your system will not 17516d23c382SWarner Losh boot. 17526d23c382SWarner Losh 17536d23c382SWarner Losh20000315: 175419cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 175519cada77SWarner Losh to upgrade to 4.0 from 3.x. 175657199806SWarner Losh 1757dc0dbf5cSWarner LoshCOMMON ITEMS: 1758dc0dbf5cSWarner Losh 1759cd5f061cSWarner Losh # NOTE: 5.x below applies to 6.0-currrent as well, for the 1760cd5f061cSWarner Losh # momemnt. 4.any -> 5.any upgrade support will remain in 1761cd5f061cSWarner Losh # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 1762cd5f061cSWarner Losh # 6.0-current upgrade path will require moving through 5.3 1763cd5f061cSWarner Losh # RELEASE or newer. 1764cd5f061cSWarner Losh 1765a24eff53SWarner Losh General Notes 1766a24eff53SWarner Losh ------------- 1767a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1768a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1769a24eff53SWarner Losh installworld. This is especially true when upgrading between 1770a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1771a24eff53SWarner Losh or several minor releases, or when several months have passed 1772a24eff53SWarner Losh on the -current branch). 1773a24eff53SWarner Losh 17745780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 17755780f3baSWarner Losh poisoning. This can happen because the make utility reads its 17765780f3baSWarner Losh environment when searching for values for global variables. 17775780f3baSWarner Losh To run your build attempts in an "environmental clean room", 17785780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 17795780f3baSWarner Losh page for more details. 17805780f3baSWarner Losh 1781dc0dbf5cSWarner Losh To build a kernel 1782dc0dbf5cSWarner Losh ----------------- 1783ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1784f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1785ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1786282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1787282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1788dc0dbf5cSWarner Losh 1789ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1790ba01eb20SWarner Losh -------------------------------------------------------------- 17910fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 17920fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 17930fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 17940fbd2da9SKen Smith 17950fbd2da9SKen Smith cd src/sys/${arch}/conf 179647d0d01fSWarner Losh config KERNEL_NAME_HERE 17970fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1798ba01eb20SWarner Losh make depend 1799ba01eb20SWarner Losh make 1800ba01eb20SWarner Losh make install 1801ba01eb20SWarner Losh 1802ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1803ba01eb20SWarner Losh 1804ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1805ba01eb20SWarner Losh ----------------------------------------------------------- 180663cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 180763cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 180863cb445eSWarner Losh 1809f643de42SWarner Losh <make sure you have good level 0 dumps> 181063cb445eSWarner Losh <maybe fix /etc/fstab> [7] 181163cb445eSWarner Losh make buildworld 18126586253aSWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE 181363cb445eSWarner Losh [1] 181463cb445eSWarner Losh <reboot in single user> [3] 18156586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 181663cb445eSWarner Losh mergemaster -p [5] 181763cb445eSWarner Losh make installworld 181863cb445eSWarner Losh mergemaster [4] 181963cb445eSWarner Losh <reboot> 182063cb445eSWarner Losh 1821759f0aefSWarner Losh 1822f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1823f27b1fceSJoseph Koshy -------------------------------------------------- 1824f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1825f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1826f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1827f27b1fceSJoseph Koshy # size. 1828f27b1fceSJoseph Koshy 1829f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1830f27b1fceSJoseph Koshy <boot into -stable> 1831f27b1fceSJoseph Koshy make buildworld 1832f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1833f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1834f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1835f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 18366586253aSWarner Losh cp src/sys/${ARCH}/conf/GENERIC.hints \ 1837f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1838f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 18396586253aSWarner Losh cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1840f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1841f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1842f27b1fceSJoseph Koshy <reboot into current> 1843f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 18446586253aSWarner Losh <maybe install compatibility libraries from src/lib/compat> 1845f27b1fceSJoseph Koshy <reboot> 1846f27b1fceSJoseph Koshy 1847f27b1fceSJoseph Koshy 1848f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1849f27b1fceSJoseph Koshy ---------------------------------------------- 18505c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 1851e5dc5f61SWarner Losh # modules has changed. If you are installing 5.x onto a 4.x 18525c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 18535c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1854ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1855f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1856f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1857f643de42SWarner Losh # space on /. 1858f643de42SWarner Losh 1859f643de42SWarner Losh <make sure you have good level 0 dumps> 1860fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 186121c075eaSWarner Losh make buildworld [9] 1862802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1863e5dc5f61SWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1864802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1865fc8c157fSWarner Losh [1] 1866fc8c157fSWarner Losh <reboot in single user> [3] 18676586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 1868835284beSWarner Losh mergemaster -p [5] 1869f8a4c901SWarner Losh rm -rf /usr/include/g++ 1870ba26da8eSWarner Losh make installworld 1871802fc49dSBrian Feldman mergemaster -i [4] 1872ba26da8eSWarner Losh <reboot> 1873ba26da8eSWarner Losh 1874fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1875fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1876fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1877fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1878fdb9f54dSWarner Losh the UPDATING entries. 1879ba26da8eSWarner Losh 18801dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 18811dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 18821dece4a9SWarner Losh your sources that you have read and understood all the recent 18831dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 18841dece4a9SWarner Losh much fewer pitfalls. 18851dece4a9SWarner Losh 1886134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1887134d2e86SWarner Losh should disable them at this point so they don't crash your 1888134d2e86SWarner Losh system on reboot. 1889134d2e86SWarner Losh 18909c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 18919c1a7444SWarner Losh your own device.hints to reflect your unique hardware 18929c1a7444SWarner Losh configuration. 18939c1a7444SWarner Losh 1894ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1895ee6e1fc3SWarner Losh fsck -p 1896ee6e1fc3SWarner Losh mount -u / 1897ee6e1fc3SWarner Losh mount -a 18986586253aSWarner Losh cd src 189947d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1900f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1901f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 190266986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1903b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1904b705ae10SWarner Losh be ignored while you proceed to the next step. 1905ee6e1fc3SWarner Losh 1906a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1907a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1908a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1909a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1910a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1911a6cd4f9dSWarner Losh for potential gotchas. 1912a6cd4f9dSWarner Losh 1913835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1914835284beSWarner Losh you may need to do this if you get unknown user in the following 1915835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1916835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1917835284beSWarner Losh install) after the buildworld before this step if you last updated 1918835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1919835284beSWarner Losh 1920bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1921bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1922bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1923bd79cf40SWarner Losh ok unload 1924bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1925bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1926bd79cf40SWarner Losh described here. 1927fc8c157fSWarner Losh 1928fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1929e5dc5f61SWarner Losh compatibility slices. These are device names of the form /dev/ad0a 1930e5dc5f61SWarner Losh without the actual slice name. These will break with 5.x and newer. 1931fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1932e5dc5f61SWarner Losh 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha 1933e5dc5f61SWarner Losh is not. 1934fc8c157fSWarner Losh 1935c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1936c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1937c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1938c74fe6afSWarner Losh that is hard to boot to recover. 1939c74fe6afSWarner Losh 1940e5dc5f61SWarner Losh Make sure that you merge any new devices from GENERIC since the 1941e5dc5f61SWarner Losh last time you updated your kernel config file. 1942e5dc5f61SWarner Losh 194321c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1944e5dc5f61SWarner Losh cvs prune empty directories. 1945e5dc5f61SWarner Losh 1946e5dc5f61SWarner Losh If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1947e5dc5f61SWarner Losh "?=" instead of the "=" assignment operator, so that buildworld can 1948e5dc5f61SWarner Losh override the CPUTYPE if it needs to. 1949e5dc5f61SWarner Losh 1950e5dc5f61SWarner Losh MAKEOBJDIRPREFIX must be defined in an environment variable, and 1951e5dc5f61SWarner Losh not on the command line, or in /etc/make.conf. buildworld will 1952e5dc5f61SWarner Losh warn if it is improperly defined. 1953e5dc5f61SWarner Losh 1954802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1955802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 195666986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1957e5dc5f61SWarner Losh using your existing software for a while. Alternatively, you can 1958e5dc5f61SWarner Losh install the misc/compat4x port. 19598633bbeaSBrooks Davis 19608633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 19616586253aSWarner Losh initialized by feeding data into it. src/etc/rc.d/preseedrandom 19628633bbeaSBrooks Davis takes care of this. 1963dc0dbf5cSWarner LoshFORMAT: 1964dc0dbf5cSWarner Losh 1965f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 19661fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1967f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1968f8ab1dd6SWarner Loshprevious releases if your system is older than this. 19691fc1a0dcSWarner Losh 1970e72fd46aSWarner LoshCopyright information: 1971e72fd46aSWarner Losh 1972e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh. All Rights Reserved. 1973e72fd46aSWarner Losh 1974772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1975772730c7SWarner Loshmodification, in full or in part, in any form or format of this 19769698f2c0SWarner Loshdocument are permitted without further permission from the author. 1977e72fd46aSWarner Losh 1978e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1979e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1980e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1981e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1982e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1983e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1984e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1985e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1986e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1987e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1988e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1989e72fd46aSWarner Losh 1990e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1991e72fd46aSWarner Loshauthor a beer. 1992e72fd46aSWarner Losh 199322306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1994772730c7SWarner Loshthis document. 1995772730c7SWarner Losh 199697d92980SPeter Wemm$FreeBSD$ 1997