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 769f7bcf3SWarner LoshNOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW: 869f7bcf3SWarner Losh FreeBSD 5.0-CURRENT has many debugging features turned on, in 969f7bcf3SWarner Losh both the kernel and userland. These features attempt to detect 1069f7bcf3SWarner Losh incorrect use of system primitives, and encourage loud failure 1169f7bcf3SWarner Losh through extra sanity checking and fail stop semantics. They 1269f7bcf3SWarner Losh also substantially impact system performance. If you want to 1369f7bcf3SWarner Losh do performance measurement, benchmarking, and optimization, 1469f7bcf3SWarner Losh you'll want to turn them off. This includes various WITNESS- 1569f7bcf3SWarner Losh related kernel options, INVARIANTS, malloc debugging flags 1669f7bcf3SWarner Losh in userland, and various verbose features in the kernel. Many 1769f7bcf3SWarner Losh developers choose to disable these features on build machines 1869f7bcf3SWarner Losh to maximize performance. 1969f7bcf3SWarner Losh 20161dc364SAlexander Kabaev20021222: 21161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 22161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 23161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 24161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 25161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 26161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 27161dc364SAlexander Kabaev 28fb4c8061SMartin Blapp20021216: 29fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 30fb4c8061SMartin Blapp compatible with with suns TIRPC and also with NetBSD. You need 31fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 32fb4c8061SMartin Blapp with a outdated /etc/netconfig for some time, but you'll get 33fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 34fb4c8061SMartin Blapp 3517d47eb3SGiorgos Keramidas20021202: 3617d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 3717d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 3817d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 3917d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 4017d47eb3SGiorgos Keramidas 41a4459294SBill Fenner20021029: 42a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 43a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 44a4459294SBill Fenner consumers in sync. 45a4459294SBill Fenner 46fc8c157fSWarner Losh20021024: 47fc8c157fSWarner Losh Old, compatibility slices have been removed in GEOM kernels. This 48fc8c157fSWarner Losh means that you will have to update your /etc/fstab to not use 49fc8c157fSWarner Losh disk devices of the form /dev/ad0a. Instead, you now must 50fc8c157fSWarner Losh specify /dev/ad0s1a, or whatever slice your FreeBSD partition 51fc8c157fSWarner Losh really is on. The old device names have gone away, so if you 52fc8c157fSWarner Losh use them anywhere else, you must also adjust those uses. 5369f7bcf3SWarner Losh 54fd9e8bdaSAndrew Gallatin20021023: 55fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 56fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 57fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 58fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 59fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 60fd9e8bdaSAndrew Gallatin 61fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 62fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 63fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 64fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 65fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 66fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 67fd9e8bdaSAndrew Gallatin 68f8a4c901SWarner Losh20020831: 69f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 70f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 71f8a4c901SWarner Losh programs and libraries need to be recompiled. 72f8a4c901SWarner Losh 73f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 74f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 75f8a4c901SWarner Losh 76c2248fa2SJens Schweikhardt20020827: 77c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 78c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 79c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 80c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 81c2248fa2SJens Schweikhardt 820d533e43SRuslan Ermilov20020815: 830d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 840d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 850d533e43SRuslan Ermilov again. 860d533e43SRuslan Ermilov 8733c1de7dSRuslan Ermilov20020729: 8833c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 8933c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 9033c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 9133c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 9233c1de7dSRuslan Ermilov 932b877facSJulian Elischer20020702: 942b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 952b877facSJulian Elischer There are still some minor problems with some signals but the 962b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 972b877facSJulian Elischer but each can successfully complete multiple buildworlds. 982b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 992b877facSJulian Elischer 10006596d37SWarner Losh20020701: 10106596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 10206596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 10306596d37SWarner Losh GNOME. 10406596d37SWarner Losh 10595ba4330SJacques Vidrine20020511: 10695ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 10795ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 10895ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 10995ba4330SJacques Vidrine with the set-user-ID bit set. 11095ba4330SJacques Vidrine 111a81da3c9SDavid E. O'Brien20020510: 112f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 113f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 1144b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 115f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 116f50caf6fSDavid E. O'Brien 117f50caf6fSDavid E. O'Brien20020510: 118a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 119a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 120a81da3c9SDavid E. O'Brien and then do a cvs update. 121a81da3c9SDavid E. O'Brien 122528a0ef5SJacques Vidrine20020421: 123528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 124528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 125528a0ef5SJacques Vidrine 12685aa5a2eSGregory Neil Shapiro20020404: 12785aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 12885aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 12985aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 13085aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 13185aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 13285aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 13385aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 13485aa5a2eSGregory Neil Shapiro 1358f1e4358SRuslan Ermilov20020403: 1368f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 1378f1e4358SRuslan Ermilov 1382292c02eSWarner Losh20020315: 1392292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 1402292c02eSWarner Losh 14169f7bcf3SWarner Losh20020225: 14269f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 14369f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 14469f7bcf3SWarner Losh 1458f35c493SWarner Losh20020217: 1468f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 1478f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 1488f35c493SWarner Losh command line mail submission has changed. Be sure to run 1498f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 1508f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 1518f35c493SWarner Losh 152835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 153835284beSWarner Losh required in order for sendmail to run as a set-group-ID 154835284beSWarner Losh binary. A 'make installworld' will use the new user and group 155835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 156835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 157835284beSWarner Losh and group must be merged from src/etc/group and 158835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 159835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 160835284beSWarner Losh mergemaster before this will work if you are updating from a 161835284beSWarner Losh very old version of current. The updating recipe has changed 162835284beSWarner Losh as of this date. 163835284beSWarner Losh 164fa9401c1SWarner Losh20020112: 165fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 166fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 167fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 168fa9401c1SWarner Losh you have local modifications, you can use 169fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 170fa9401c1SWarner Losh /etc/pam.d. 171fa9401c1SWarner Losh 172fa9401c1SWarner Losh Please see the following url for more details: 173fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 17447d0d01fSWarner Losh20011229: 17547d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 17647d0d01fSWarner Losh networkfs_types, please note that it has changed 17747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 17847d0d01fSWarner Losh 179514318a8SWarner Losh20011220: 180514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 181514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 182514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 183514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 184514318a8SWarner Losh version have now been merged back into the base system's 185514318a8SWarner Losh version now. The only user-visible change resulting from this 186514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 187514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 188514318a8SWarner Losh as well. (There has never been rc file support for 189514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 190514318a8SWarner Losh reverted by the time the changes are MFCed.) 191514318a8SWarner Losh 192514318a8SWarner Losh20011215: 193514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 194514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 195514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 196514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 197514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 198514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 199514318a8SWarner Losh will need to be customized then for `odd' densities using 200514318a8SWarner Losh fdcontrol(8). 201514318a8SWarner Losh 2022d22e2bfSWarner Losh20011209: 2032d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 2042d22e2bfSWarner Losh and truss(1) now works again. 2052d22e2bfSWarner Losh 2069e0428e2SWarner Losh20011207: 2079e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 2089e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 2099e0428e2SWarner Losh see 2109e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 2119e0428e2SWarner Losh for details. 2129e0428e2SWarner Losh 2139bab8c59SWarner Losh20011204: 2149bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 2159bab8c59SWarner Losh kernel and burncd to be in sync. 2169bab8c59SWarner Losh 217e57d8b01SWarner Losh20011203: 218e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 219e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 220e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 221e57d8b01SWarner Losh not there already. 222e57d8b01SWarner Losh 223e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 224e57d8b01SWarner Losh until the issue has been resolved. 225e57d8b01SWarner Losh 226b001d36fSJacques Vidrine20011202: 227b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 228b001d36fSJacques Vidrine patched. 229b001d36fSJacques Vidrine 2304b676ec1SWarner Losh20011126: 2314b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 2325ebbf43eSWarner Losh after this date. You need to do this only once. 2334b676ec1SWarner Losh 234d961e462SWarner Losh20011103: 235d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 236d961e462SWarner Losh edges may be left, but for the most part things should be 2374b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 238d961e462SWarner Losh 239d961e462SWarner Losh20011030: 240d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 241d961e462SWarner Losh choppy waves in the upgrade process. 242d961e462SWarner Losh 2431fe003b6SWarner Losh20011030: 244a4b6fda0SWarner Losh The asr driver problem has been resolved. 2451fe003b6SWarner Losh 2461fe003b6SWarner Losh20011027: 2471fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 2481fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 2491fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 2501fe003b6SWarner Losh try to use from this date forward. 2511fe003b6SWarner Losh 2521fe003b6SWarner Losh20011025: 2531fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 2541fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 2551fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 2561fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 2571fe003b6SWarner Losh TARGET_ARCH=i386. 2581fe003b6SWarner Losh 259d05f9643SWarner Losh20011001: 260d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 261d05f9643SWarner Losh You must recompile both the kernel and userland applications 262d05f9643SWarner Losh at the same time. 263d05f9643SWarner Losh 26458970f85SWarner Losh20010929: 26558970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 26658970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 26758970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 26858970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 26958970f85SWarner Losh (eg, you can build pc98 on a i386 machine and vice versa). 27058970f85SWarner Losh 27158970f85SWarner Losh20010927: 27258970f85SWarner Losh Some weird problems result from using ACPI on some machines. 27358970f85SWarner Losh To disable ACPI you can add 274378f4486SAlfred Perlstein hint.acpi.0.disable="1" 27558970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 27658970f85SWarner Losh loader "ok" prompt). 27758970f85SWarner Losh 27858970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 27958970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 28058970f85SWarner Losh file and not list acpi in that list. 281378f4486SAlfred Perlstein 2825119d237SWarner Losh20010924: 2835119d237SWarner Losh The buildworld has been fixed. You may need to install 2845119d237SWarner Losh the 4.x compatibility libraries for some old binaries 2858b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 2868b039fffSWarner Losh get them installed on every installworld, or execute the 2878b039fffSWarner Losh following to get them installed only once: 2888b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 28958970f85SWarner Losh make all install 2908b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 2915119d237SWarner Losh 2923c293725SWarner Losh20010919: 2933c293725SWarner Losh There's a bug in the world build process. The cross-tools 2943c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 2953c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 296772730c7SWarner Losh workaround is to add 2973c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 2983c293725SWarner Losh before building world when upgrading from 4.x to current. This 2993c293725SWarner Losh can be removed afterwards. 3003c293725SWarner Losh 3013c293725SWarner Losh A proper fix to the buildworld target is needed. 3023c293725SWarner Losh 3033c293725SWarner Losh20010918: 3043c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 3053c293725SWarner Losh NFS may be unstable after this date. 3063c293725SWarner Losh 3073c293725SWarner Losh20010912: 3083c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 3093c293725SWarner Losh the kernel. While a few problems were introduced in the 3103c293725SWarner Losh initial commit, most of the major ones have been found and 3113c293725SWarner Losh corrected. 3123c293725SWarner Losh 3133c293725SWarner Losh20010901: 3143c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 3153c293725SWarner Losh arounds described in the 20010604 entry are now no longer 3163c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 3173c293725SWarner Losh have been rectified around this date. 3183c293725SWarner Losh 31998b17b95SWarner Losh20010823: 32098b17b95SWarner Losh named now runs as user bind and group bind rather than as 32198b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 32298b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 32398b17b95SWarner Losh and that group bind is available in /etc/group. Also make 32498b17b95SWarner Losh sure that user or group bind has read (and not write) 32598b17b95SWarner Losh permission for your name server configuration and that it 32698b17b95SWarner Losh has read and write permission for your slave zone files and 32798b17b95SWarner Losh directory. 32898b17b95SWarner Losh 32998b17b95SWarner Losh If you wish to continue to run named as root (a less secure 33098b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 33198b17b95SWarner Losh 33298b17b95SWarner Losh named_flags= 33398b17b95SWarner Losh 3347b9786edSMark Murray20010709: 3357b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 3367b9786edSMark Murray the ability of the shared library major number to handle. 3377b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 3387b9786edSMark Murray solution is to rebuild those ports. 3397b9786edSMark Murray 3401d28950eSWarner Losh20010628: 3411d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 3421d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 3431d28950eSWarner Losh 344e72fd46aSWarner Losh20010625: 34598b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 34698b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 34798b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 34898b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 34998b17b95SWarner Losh IRQ configuration needs more safety belts. 35016de1a07SWarner Losh 3510d415dffSWarner Losh20010617: 352e72fd46aSWarner Losh Softupdates problems have been corrected. 3530d415dffSWarner Losh 3540d415dffSWarner Losh20010614: 3550d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 3560d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 3570d415dffSWarner Losh kernel building methods. 3580d415dffSWarner Losh 3598b9959adSWarner Losh20010613: 3608b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 3618b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 362e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 363e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 3648b9959adSWarner Losh 365e72fd46aSWarner Losh20010613: 3668b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 367e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 368e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 3698b9959adSWarner Losh 3700d415dffSWarner Losh20010612: 3710d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 3720d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 3730d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 3740d415dffSWarner Losh work around this issue, please use only one or the other mechanism 3750d415dffSWarner Losh until this bug is fixed. 3760d415dffSWarner Losh 377e72fd46aSWarner Losh Please note that a feature of config is that if you have config 378e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 379e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 380e72fd46aSWarner Losh 3810d415dffSWarner Losh20010610: 3820d415dffSWarner Losh Locale names have changed to match other systems better. 3830d415dffSWarner Losh 3846ccdb5e4SWarner Losh20010604: 3856ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 3866ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 3876ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 3883590182eSWarner Losh Interrupt storms look a lot like a hang. 3893590182eSWarner Losh 3903590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 3913590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 3923590182eSWarner Losh it is). 3933590182eSWarner Losh 3943590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 3953590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 3963590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 3973590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 3986ccdb5e4SWarner Losh 3990bc62786SWarner Losh20010530: 4000bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 4010bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 4020bc62786SWarner Losh a limited time. If you see 4030bc62786SWarner Losh 4040bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 4050bc62786SWarner Losh 4060bc62786SWarner Losh in your makeworld, then you need to migrate towards using 4070bc62786SWarner Losh COPY=-C. 4080bc62786SWarner Losh 40968a38c6cSWarner Losh20010525: 410b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 411c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 412c4f4a728SWarner Losh definitely is in bad shape. 41368a38c6cSWarner Losh 414ed0f29caSWarner Losh20010521: 415f10d3145SWarner Losh Minor repo damange has happened. This may cause problems 416ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 417ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 418ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 419ed0f29caSWarner Losh is 420ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 421ed0f29caSWarner Losh 42280c16af9SWarner Losh20010520: 42368a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 42480c16af9SWarner Losh 42580c16af9SWarner Losh20010519: 42680c16af9SWarner Losh pccard has had much reorganizational work done to it over 42780c16af9SWarner Losh the past few days. Everything should still work, but if 42880c16af9SWarner Losh not, please contact imp@freebsd.org. 42980c16af9SWarner Losh 430a45f2d05SWarner Losh20010517: 431a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 432a45f2d05SWarner Losh userland at the same time. 433a45f2d05SWarner Losh 434a45f2d05SWarner Losh20010517: 435a45f2d05SWarner Losh New ncurses imported. 436a45f2d05SWarner Losh 4372988afcaSWarner Losh20010512: 4382988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 4392988afcaSWarner Losh will be the only way to go starting July 1. 4402988afcaSWarner Losh 4411a33dba7SWarner Losh20010504: 4421a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 4431a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 4441a33dba7SWarner Losh 44509946a51SWarner Losh20010502: 44609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 44709946a51SWarner Losh 44809946a51SWarner Losh20010501: 44909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 45009946a51SWarner Losh 45109946a51SWarner Losh20010430: 452a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 45309946a51SWarner Losh go back in the water. 45409946a51SWarner Losh 45509946a51SWarner Losh20010429: 45609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 45709946a51SWarner Losh this date, but before the correction date. 45809946a51SWarner Losh 45991dd3b53SWarner Losh20010423: 46091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 46191dd3b53SWarner Losh 46291dd3b53SWarner Losh20010411: 46391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 46491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 46591dd3b53SWarner Losh Update only if you understand that you must not use the old 46691dd3b53SWarner Losh fsck with the new kernel ever. 46791dd3b53SWarner Losh 468933b3269SWarner Losh20010330: 469933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 470c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 471933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 472933b3269SWarner Losh 473933b3269SWarner Losh20010319: 474933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 475933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 476933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 477f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 47809946a51SWarner Losh 47909946a51SWarner Losh20010315: 48009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 48109946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 48209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 483933b3269SWarner Losh 484933b3269SWarner Losh20010312: 485933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 486933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 487933b3269SWarner Losh 488933b3269SWarner Losh20010312: 489933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 490933b3269SWarner Losh instead of ad-hoc. 491933b3269SWarner Losh 492933b3269SWarner Losh20010310: 493f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 494933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 495933b3269SWarner Losh ssh might not work if you don't. 496933b3269SWarner Losh 49762353691SWarner Losh20010303: 49862353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 49962353691SWarner Losh which means that you must include the miibus in your kernel if 50062353691SWarner Losh you use the ed driver. 50162353691SWarner Losh 502d325cf65SWarner Losh20010220: 503d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 504d325cf65SWarner Losh safe to go back into the water. 505d325cf65SWarner Losh 506024daae6SWarner Losh20010211: 507024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 508024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 509024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 510024daae6SWarner Losh that before upgrading would be a good time to do a level 0 511024daae6SWarner Losh dump of your system. No, really, I mean it this time. 512024daae6SWarner Losh 513024daae6SWarner Losh To get to the new system, you'll need to use the following 514024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 515024daae6SWarner Losh don't have to move this to the updating section. 516024daae6SWarner Losh 517024daae6SWarner Losh To get around the installworld problem, do: 518024daae6SWarner Losh # cd /usr/src/usr.bin/sed 519024daae6SWarner Losh # make install 520024daae6SWarner Losh # cd /usr/src 521024daae6SWarner Losh # make installworld 522024daae6SWarner Losh If that doesn't work, then try: 523024daae6SWarner Losh # make -k installworld 524024daae6SWarner Losh # make installworld 525024daae6SWarner Losh 526024daae6SWarner Losh20010207: 527024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 528024daae6SWarner Losh do not include devfs in your kernel as problems result. 529024daae6SWarner Losh 530024daae6SWarner Losh20010205: 5317595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 532024daae6SWarner Losh Remove them from your config. 533024daae6SWarner Losh 5341e159248SWarner Losh20010122: 5351e159248SWarner Losh ****************************** WARNING ****************************** 5361e159248SWarner Losh buildkernel has been changed slightly 5371e159248SWarner Losh ****************************** WARNING ****************************** 5381e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 5391e159248SWarner Losh should update your scripts and make.conf accordingly. 5401e159248SWarner Losh 5411e159248SWarner Losh20010119: 5421e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 5431e159248SWarner Losh This requires a new config to build correctly. 5441e159248SWarner Losh 545aac7dfeaSWarner Losh20010116: 546aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 547aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 548aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 549aac7dfeaSWarner Losh 550aac7dfeaSWarner Losh20010110: 551aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 552aac7dfeaSWarner Losh 553aac7dfeaSWarner Losh20010102: 554aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 555aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 556aac7dfeaSWarner Losh 55763c90c9eSWarner Losh20010101: 55863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 55963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 5605fd2a895SWarner Losh dump while building termcap. You can work around this problem 56163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 56263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 56363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 56463c90c9eSWarner Losh might have been ignored by the -k option. 56563c90c9eSWarner Losh 5665fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 5675fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 5685fd2a895SWarner Losh of this working. 5695fd2a895SWarner Losh 570aac7dfeaSWarner Losh20001228: 571aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 572aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 573aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 574aac7dfeaSWarner Losh 575de2bcc63SWarner Losh20001218: 576de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 577de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 578de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 579de2bcc63SWarner Losh cards will not be recognized without it. 580de2bcc63SWarner Losh 581960773f7SWarner Losh20001205: 582960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 583960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 584960773f7SWarner Losh adding the following in pam.conf: 585960773f7SWarner Losh 586960773f7SWarner Losh sshd auth sufficient pam_skey.so 587960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 588960773f7SWarner Losh sshd session required pam_permit.so 589960773f7SWarner Losh 5900acc635eSWarner Losh20001031: 5910acc635eSWarner Losh cvs updated to 1.11. 5920acc635eSWarner Losh 5930acc635eSWarner Losh20001020: 5940acc635eSWarner Losh The random device needs more entropy, so you need to make sure 5950acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 5960acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 5970acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 5980acc635eSWarner Losh workaround. 5990acc635eSWarner Losh 6000acc635eSWarner Losh20001010: 6010acc635eSWarner Losh ****************************** WARNING ****************************** 6020acc635eSWarner Losh Sendmail has been updated. 6030acc635eSWarner Losh ****************************** WARNING ****************************** 6040acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 6050acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 6060acc635eSWarner Losh is set. 6070acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 6080acc635eSWarner Losh commands. 6090acc635eSWarner Losh o Now using sendmail's version of vacation(1). 6100acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 6110acc635eSWarner Losh in /usr/share/sendmail/cf. 6120acc635eSWarner Losh o sendmail.cw changed to local-host-names 6130acc635eSWarner Losh 6140acc635eSWarner Losh More details can be found at 6150acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 6160acc635eSWarner Losh 6176e98a146SWarner Losh20001009: 6186e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 6196e98a146SWarner Losh your entire ports tree, or you will have problems. 6206e98a146SWarner Losh 6216e98a146SWarner Losh20001006: 622685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 6236e98a146SWarner Losh the installed miniperl. It is recommended that you delete 6246e98a146SWarner Losh /usr/bin/miniperl. 6256e98a146SWarner Losh 626073113a4SWarner Losh20001005: 627073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 628685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 629073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 630073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 631073113a4SWarner Losh tree for anything to work. 632073113a4SWarner Losh 6330acc635eSWarner Losh20000928: 6340acc635eSWarner Losh There was a change in the passwd format. Need more information. 6350acc635eSWarner Losh 636be3885b3SWarner Losh20000916: 637be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 638be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 639be3885b3SWarner Losh same time as your kernel. 640be3885b3SWarner Losh 64176ec9675SWarner Losh20000914: 64276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 64376ec9675SWarner Losh include the device will cause suspended laptops losing time 64476ec9675SWarner Losh when they resume. Include 64576ec9675SWarner Losh device pmtimer 64676ec9675SWarner Losh in your config file and 64701b9a434SWarner Losh hint.pmtimer.0.at="isa" 64876ec9675SWarner Losh to your /boot/device.hints file. 64976ec9675SWarner Losh 650f4865386SMark Murray20000911: 651f4865386SMark Murray The random device has been turned into a (pseudo-)device, 652f4865386SMark Murray rather than an option. The supplied kernel config files have 653f4865386SMark Murray been updated. You will need to do something similar in your 654f4865386SMark Murray own kernel config file. 655f4865386SMark Murray Remove: 656f4865386SMark Murray options RANDOMDEV 657f4865386SMark Murray Add: 658f4865386SMark Murray device random 659f4865386SMark Murray If you prefer to load the loadable module, you need to do 660f4865386SMark Murray nothing. 661f4865386SMark Murray 662d594498fSWarner Losh20000909: 663d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 664d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 665d594498fSWarner Losh reflect this if you load this module at boot time. 666d594498fSWarner Losh The line should read: 667d594498fSWarner Losh random_load="YES" 668d594498fSWarner Losh 6690deb7ddcSWarner Losh20000907: 6700deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 67116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 67216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 67316eb772dSWarner Losh sure you don't have model loading problems which might at 67416eb772dSWarner Losh first blush appear related to SMP. 67552bf24e7SWarner Losh 6765a01880bSWarner Losh20000906: 6775a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 6785a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 6795a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 6805a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 6815a01880bSWarner Losh don't have one, and you have host.conf. 6825a01880bSWarner Losh 6832b41163cSWarner Losh20000905: 68438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 68538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 68638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 68738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 68838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 68938d6ecd2SWarner Losh 69038d6ecd2SWarner Losh20000905: 6918aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 6928aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 6938aab4bc7SWarner Losh is /boot/kernel. 6948aab4bc7SWarner Losh 6958aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 69638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 69738d6ecd2SWarner Losh installkernel/installworld dance. 6982b41163cSWarner Losh 699d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 700d594498fSWarner Losh before booting the new kernel, since kldload will find stale 701d594498fSWarner Losh modules in that directory instead of finding them in the correct 702d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 703d594498fSWarner Losh is that the linux module crashes your machine after the update. 704d594498fSWarner Losh 705d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 706d594498fSWarner Losh mv /modules.old /boot/kernel.old 707d594498fSWarner Losh chflags noschg /kernel.old 708d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 709d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 710d594498fSWarner Losh fi 711d594498fSWarner Losh 712c22a309cSWarner Losh20000904: 713c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 714c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 715c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 716c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 717c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 718c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 719c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 720c22a309cSWarner Losh is not likely to be generated. 721c22a309cSWarner Losh 722fdb9f54dSWarner Losh20000825: 723fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 7249c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 7259c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 7269c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 7279c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 7289c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 7299c1a7444SWarner Losh messages will appear after the boot loader tries to start the 7309c1a7444SWarner Losh kernel. 7319c1a7444SWarner Losh 7329c1a7444SWarner Losh20000821: 7339c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 7349c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 7359c1a7444SWarner Losh /boot/loader.conf. 736fdb9f54dSWarner Losh 7378f250aa7SWarner Losh20000812: 7385da0d091SWarner Losh suidperl is now always built and installed on the system, but 7395da0d091SWarner Losh with permissions of 511. If you have applications that use 7405da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 7415da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 7425da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 7435da0d091SWarner Losh will fix this until the next build. 7445da0d091SWarner Losh 7455da0d091SWarner Losh20000812: 7468f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 7478f250aa7SWarner Losh visible changes that may immediately affect your configuration 7488f250aa7SWarner Losh include: 7498f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 7508f250aa7SWarner Losh - newaliases limited to root and trusted users 7518f250aa7SWarner Losh - MSA port (587) turned on by default 7528f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 7538f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 7548f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 7558f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 7568f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 7578f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 7588f250aa7SWarner Losh 75971c38472SWarner Losh20000810: 76071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 76171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 76271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 76371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 76471c38472SWarner Losh specific use for it. 76571c38472SWarner Losh 76671c38472SWarner Losh20000729: 76771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 76871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 76971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 77071c38472SWarner Losh afterwards (unless the variables already are set, of course): 77171c38472SWarner Losh # Enable network daemons for user convenience. 77271c38472SWarner Losh inetd_enable="YES" 77371c38472SWarner Losh portmap_enable="YES" 77471c38472SWarner Losh sendmail_enable="YES" 77571c38472SWarner Losh 77671c38472SWarner Losh20000728: 77771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 77871c38472SWarner Losh will need to change that to nullfs_load="YES". 77971c38472SWarner Losh 7801dece4a9SWarner Losh20000728: 7811dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 7821dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 7831dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 7841dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 7851dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 7861dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 7871dece4a9SWarner Losh to /MYKERNEL. 7881dece4a9SWarner Losh 789409e887cSWarner Losh20000711: 790409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 791409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 792409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 793409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 794409e887cSWarner Losh for details on potential problems that you might have and how 795409e887cSWarner Losh to get around them. 796409e887cSWarner Losh 797409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 798409e887cSWarner Losh clauses above, you needn't worry. 799409e887cSWarner Losh 800409e887cSWarner Losh20000711: 801409e887cSWarner Losh /etc/security has been updated to print the inode number of 802409e887cSWarner Losh setuid programs that have changed. You will see a large spike 803409e887cSWarner Losh in the number of changed programs the first time when you run 804409e887cSWarner Losh mergemaster to get a new /etc/security. 805409e887cSWarner Losh 806673d13f2SWarner Losh20000710: 807673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 808673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 809673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 810673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 811673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 812673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 813673d13f2SWarner Losh errors. (see below, 20000624). 814673d13f2SWarner Losh 815bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 8161dece4a9SWarner Losh 817673d13f2SWarner Losh20000709: 818c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 819c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 820c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 821673d13f2SWarner Losh ln -s aj /etc/malloc.conf 822673d13f2SWarner Losh 823e98e26cdSWarner Losh20000706: 824e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 825e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 826e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 827f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 828e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 8292c021c6cSMark Ovens interim if needed. 830e98e26cdSWarner Losh 831e98e26cdSWarner Losh20000705: 832e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 833e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 834e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 835e98e26cdSWarner Losh details. 836e98e26cdSWarner Losh 837c373950eSWarner Losh20000704: 8382f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 8392f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 8402f961bc8SWarner Losh 8412f961bc8SWarner Losh20000704: 842c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 843c373950eSWarner Losh or stop. This may cause some harmless warnings from older 844c373950eSWarner Losh rc.d scripts that haven't been updated. 845c373950eSWarner Losh 84627dc3a2bSWarner Losh20000630: 84727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 84827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 84927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 85027dc3a2bSWarner Losh 851b8c215acSWarner Losh20000625: 852b8c215acSWarner Losh From approximately this date forward, one must have the crypto 85327dc3a2bSWarner Losh system installed in order to build the system and kernel. 85427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 85527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 85627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 85727dc3a2bSWarner Losh were required. You should check with the latest collections 85827dc3a2bSWarner Losh to make sure that these haven't changed. 859b8c215acSWarner Losh 8607b990719SWarner Losh20000624: 8617b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 8627b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 8637b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 8641a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 8657b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 8667b990719SWarner Losh openssh and openssl should not be used to generate keys from this 8677b990719SWarner Losh date to the completion of the work. 8687b990719SWarner Losh 86927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 87027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 87127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 87227dc3a2bSWarner Losh recreate the random and urandom devices. 87327dc3a2bSWarner Losh 87481e54c50SWarner Losh20000622: 87581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 87681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 87781e54c50SWarner Losh that used to be required when updating. 87881e54c50SWarner Losh 87939943833SWarner Losh20000621: 8802c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 8812a2f33fbSDaniel Baker the config file update procedure. 8822a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 883c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 884a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 88539943833SWarner Losh 886290f9ad8SWarner Losh20000620: 887290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 888290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 889290f9ad8SWarner Losh that workaround will no longer be required. 890290f9ad8SWarner Losh 89190fb6346SWarner Losh20000615: 89290fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 89390fb6346SWarner Losh ad driver. If you haven't done so already, you must update 89490fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 89590fb6346SWarner Losh devices. 89690fb6346SWarner Losh 897f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 898f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 899f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 900f75f65bbSWarner Losh may work). 901f75f65bbSWarner Losh 902ba26da8eSWarner Losh20000612: 903ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 904290f9ad8SWarner Losh on the topic before even thinking about updating. You will 905c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 906290f9ad8SWarner Losh to your config file to compile them in statically. The format 907f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 908f54a3542SWarner Losh NEWCARD for examples of the new format. 909290f9ad8SWarner Losh 9109698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 9119698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 9129698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 9139698f2c0SWarner Losh in it. 914bbcc5149SWarner Losh 915d65850ebSWarner Losh20000522: 916ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 917d65850ebSWarner Losh building a kernel after this point is advised that they need 918d65850ebSWarner Losh to rebuild their binutils (or better yet do a 919d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 920d65850ebSWarner Losh 921d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 922d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 923d9583a00SWarner Losh is recommended that you don't set this option until the problem 924d9583a00SWarner Losh is resolved. 925d9583a00SWarner Losh 9268039cedeSWarner Losh20000513: 9278039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 9288039cedeSWarner Losh 929d65850ebSWarner Losh20000510: 9308039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 9318039cedeSWarner Losh This will require some care in updating alphas. A new libstand 9328039cedeSWarner Losh is requires for the boot blocks to build properly. 9338039cedeSWarner Losh 9348039cedeSWarner Losh20000503: 9358039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 9368039cedeSWarner Losh is now available. 9378039cedeSWarner Losh 938d65850ebSWarner Losh20000502: 939d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 940d65850ebSWarner Losh connected to the kernel building instead. 941d65850ebSWarner Losh 942be149406SNik Clayton20000427: 9438039cedeSWarner Losh You may need to build gperf 9448039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 9458039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 9468039cedeSWarner Losh an option only in -current. 9478039cedeSWarner Losh 9482b8dd5f4SWarner Losh20000417: 9492b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 950f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 9512b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 9522b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 9532c021c6cSMark Ovens before you reboot, you'll need to issue: 9542b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 9552b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 9562b8dd5f4SWarner Losh 9578d9f1945SWarner Losh20000320: 9582b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 9592b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 9602b8dd5f4SWarner Losh cope if you have a problem combination is to add: 961ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 9622b8dd5f4SWarner Losh to the start of /etc/rc.conf. 9638d9f1945SWarner Losh 964f8ab1dd6SWarner Losh20000319: 965f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 966f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 967f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 968f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 969f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 970f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 971f8ab1dd6SWarner Losh 97219cada77SWarner Losh20000318: 973f699bbbbSMark Ovens We've entered the traditional post release dumping party. 97419cada77SWarner Losh Large kernel changes are being committed and are in the 97519cada77SWarner Losh works. It is important to keep the systems' klds and kernel 97619cada77SWarner Losh in sync as kernel interfaces and structures are changing. 97719cada77SWarner Losh Before reporting kernel panics, make sure that all modules 97819cada77SWarner Losh that you are loading are up to date. 979ba228352SWarner Losh 98019cada77SWarner Losh20000315: 9816d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 9826d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 9836d23c382SWarner Losh will do the trick. This isn't critical until you remove your 9846d23c382SWarner Losh wd device entries in /dev, at which point your system will not 9856d23c382SWarner Losh boot. 9866d23c382SWarner Losh 9876d23c382SWarner Losh20000315: 98819cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 98919cada77SWarner Losh to upgrade to 4.0 from 3.x. 99057199806SWarner Losh 991dc0dbf5cSWarner LoshCOMMON ITEMS: 992dc0dbf5cSWarner Losh 993a24eff53SWarner Losh General Notes 994a24eff53SWarner Losh ------------- 995a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 996a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 997a24eff53SWarner Losh installworld. This is especially true when upgrading between 998a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 999a24eff53SWarner Losh or several minor releases, or when several months have passed 1000a24eff53SWarner Losh on the -current branch). 1001a24eff53SWarner Losh 10025780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 10035780f3baSWarner Losh poisoning. This can happen because the make utility reads its 10045780f3baSWarner Losh environment when searching for values for global variables. 10055780f3baSWarner Losh To run your build attempts in an "environmental clean room", 10065780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 10075780f3baSWarner Losh page for more details. 10085780f3baSWarner Losh 1009dc0dbf5cSWarner Losh To build a kernel 1010dc0dbf5cSWarner Losh ----------------- 1011ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1012f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1013ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 10141e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 10151e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 1016dc0dbf5cSWarner Losh 1017ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1018ba01eb20SWarner Losh -------------------------------------------------------------- 1019ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 102047d0d01fSWarner Losh config KERNEL_NAME_HERE 1021ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1022ba01eb20SWarner Losh make depend 1023ba01eb20SWarner Losh make 1024ba01eb20SWarner Losh make install 1025ba01eb20SWarner Losh 1026ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1027ba01eb20SWarner Losh 1028ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1029ba01eb20SWarner Losh ----------------------------------------------------------- 103063cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 103163cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 103263cb445eSWarner Losh 1033f643de42SWarner Losh <make sure you have good level 0 dumps> 103463cb445eSWarner Losh <maybe fix /etc/fstab> [7] 103563cb445eSWarner Losh make buildworld 103663cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 103763cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 103863cb445eSWarner Losh [1] 103963cb445eSWarner Losh <reboot in single user> [3] 104063cb445eSWarner Losh mergemaster -p [5] 104163cb445eSWarner Losh make installworld 104263cb445eSWarner Losh mergemaster [4] 104363cb445eSWarner Losh <reboot> 104463cb445eSWarner Losh 1045759f0aefSWarner Losh 10461dece4a9SWarner Losh To upgrade from 4.x-stable to current 1047ba26da8eSWarner Losh ------------------------------------- 10485c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 10495c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 10505c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 10515c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1052f643de42SWarner Losh # to back out of problems with this proceedure. If /tmp is on 1053f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1054f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1055f643de42SWarner Losh # space on /. 1056f643de42SWarner Losh 1057f643de42SWarner Losh <make sure you have good level 0 dumps> 1058fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 105921c075eaSWarner Losh make buildworld [9] 1060c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1061d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1062be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1063fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1064fc8c157fSWarner Losh [1] 1065fc8c157fSWarner Losh <reboot in single user> [3] 1066835284beSWarner Losh mergemaster -p [5] 1067f8a4c901SWarner Losh rm -rf /usr/include/g++ 1068ba26da8eSWarner Losh make installworld 1069a6cd4f9dSWarner Losh mergemaster [4] 1070ba26da8eSWarner Losh <reboot> 1071ba26da8eSWarner Losh 1072fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1073fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1074fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1075fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1076fdb9f54dSWarner Losh the UPDATING entries. 1077ba26da8eSWarner Losh 10781dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 10791dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 10801dece4a9SWarner Losh your sources that you have read and understood all the recent 10811dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 10821dece4a9SWarner Losh much fewer pitfalls. 10831dece4a9SWarner Losh 1084134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1085134d2e86SWarner Losh should disable them at this point so they don't crash your 1086134d2e86SWarner Losh system on reboot. 1087134d2e86SWarner Losh 10889c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 10899c1a7444SWarner Losh your own device.hints to reflect your unique hardware 10909c1a7444SWarner Losh configuration. 10919c1a7444SWarner Losh 1092ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1093ee6e1fc3SWarner Losh fsck -p 1094ee6e1fc3SWarner Losh mount -u / 1095ee6e1fc3SWarner Losh mount -a 1096ee6e1fc3SWarner Losh cd /usr/src 109747d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1098f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1099f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1100b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1101b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1102b705ae10SWarner Losh be ignored while you proceed to the next step. 1103ee6e1fc3SWarner Losh 1104a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1105a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1106a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1107a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1108a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1109a6cd4f9dSWarner Losh for potential gotchas. 1110a6cd4f9dSWarner Losh 1111835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1112835284beSWarner Losh you may need to do this if you get unknown user in the following 1113835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1114835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1115835284beSWarner Losh install) after the buildworld before this step if you last updated 1116835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1117835284beSWarner Losh 1118bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1119bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1120bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1121bd79cf40SWarner Losh ok unload 1122bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1123bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1124bd79cf40SWarner Losh described here. 1125fc8c157fSWarner Losh 1126fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1127fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1128fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1129fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1130fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1131fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1132fc8c157fSWarner Losh 1133c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1134c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1135c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1136c74fe6afSWarner Losh that is hard to boot to recover. 1137c74fe6afSWarner Losh 113821c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 113921c075eaSWarner Losh cvs prune empty directories. 1140dc0dbf5cSWarner LoshFORMAT: 1141dc0dbf5cSWarner Losh 1142f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 11431fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1144f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1145f8ab1dd6SWarner Loshprevious releases if your system is older than this. 11461fc1a0dcSWarner Losh 1147e72fd46aSWarner LoshCopyright information: 1148e72fd46aSWarner Losh 11499698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1150e72fd46aSWarner Losh 1151772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1152772730c7SWarner Loshmodification, in full or in part, in any form or format of this 11539698f2c0SWarner Loshdocument are permitted without further permission from the author. 1154e72fd46aSWarner Losh 1155e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1156e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1157e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1158e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1159e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1160e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1161e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1162e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1163e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1164e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1165e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1166e72fd46aSWarner Losh 1167e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1168e72fd46aSWarner Loshauthor a beer. 1169e72fd46aSWarner Losh 117022306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1171772730c7SWarner Loshthis document. 1172772730c7SWarner Losh 117397d92980SPeter Wemm$FreeBSD$ 1174