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 7f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW: 8f59d5f7aSPoul-Henning Kamp FreeBSD 5.x 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 18a19f8ddaSDavid E. O'Brien to maximize performance. 19c1f61aa9SDavid E. O'Brien 20714ae42aSBruce M Simpson20040225: 21714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 22714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 23714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 24714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 25714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 26714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 27714ae42aSBruce M Simpson 28fbd2e692SAndre Oppermann20040224: 29fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 30fbd2e692SAndre Oppermann and related userland network utilities neccessary. 31fbd2e692SAndre Oppermann 32158b90daSWarner Losh20040222: 33158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 34158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 35158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 36158b90daSWarner Losh Drivers outside the tree will need to be updated. 37158b90daSWarner Losh 38b7b1e150SMike Makonnen20040207: 39b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 40b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 41b7b1e150SMike Makonnen 42aca89ee6SDaniel Eischen20040130: 43aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 44aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 45aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 46aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 47aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 48aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 49aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 50aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 51aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 52aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 53aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 54aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 55aca89ee6SDaniel Eischen do not work with libpthread. 56aca89ee6SDaniel Eischen 5768b7b3a9SAlex Dupre20040125: 5868b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 5968b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 6068b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 6168b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 6268b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 6368b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 6468b7b3a9SAlex Dupre 65ff46e0deSWarner Losh20040125: 66ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 67ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 68ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 69ff46e0deSWarner Losh 70ce41f4bfSRobert Watson20031213: 71ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 72ce41f4bfSRobert Watson if the login process is unable to successfully set the 73ce41f4bfSRobert Watson process credentials to include all groups defined for the 74ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 75ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 76ce41f4bfSRobert Watson defined, or they will be unable to log in. 77ce41f4bfSRobert Watson 78c124fa05SJohn Baldwin20031203: 79c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 80c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 81c124fa05SJohn Baldwin 828ad1f5e4SHartmut Brandt20031112: 8330093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 8430093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 8597209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 8697209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 8797209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 8897209ca3SRobert Watson not know about the new system calls that support the new statfs 893f631d52SMarcel Moolenaar structure. 903f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 913f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 923f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 933f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 943f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 953f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 963f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 973f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 983f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 993f631d52SMarcel Moolenaar these changes are installed. 10030093b05SWarner Losh 10130093b05SWarner Losh ****************************DANGER******************************* 10230093b05SWarner Losh 10330093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 10430093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 10530093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 10630093b05SWarner Losh kernel. 10764a18d6fSKirk McKusick 10864a18d6fSKirk McKusick20031112: 1098ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 1108ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 1118ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 1128ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 1138ad1f5e4SHartmut Brandt sync before rebooting. 1148ad1f5e4SHartmut Brandt 115c53a5d8fSJohn Baldwin20031111: 116c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 117c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 118c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 119c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 120c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 121c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 122c53a5d8fSJohn Baldwin 1238bf455a5SJohn Baldwin20031103: 1248bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 1258bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 1262a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 1278bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 1288bf455a5SJohn Baldwin 1299bf40edeSBrooks Davis20031031: 1309bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 1319bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 1329bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 1339bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 1349bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 1359bf40edeSBrooks Davis reflect this change. 1369bf40edeSBrooks Davis 13747a42c7aSPoul-Henning Kamp20030928: 13847a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 13947a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 14047a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 14147a42c7aSPoul-Henning Kamp 14207105342SMax Khon20030926: 14307105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 14407105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 14507105342SMax Khon 14617dcd026SSam Leffler20030925: 14717dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 14817dcd026SSam Leffler also be explicitly configured. Previously this dependency was 14917dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 15017dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 15117dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 15217dcd026SSam Leffler 153fedf1d01SBruce M Simpson20030923: 154fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 155fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 156fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 157fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 158fedf1d01SBruce M Simpson 159db38f9cbSJacques Vidrine20030915: 160db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 161db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 162db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 163db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 164db38f9cbSJacques Vidrine 165c09d2c2bSMike Makonnen20030829: 166c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 167c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 168c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 169c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 170c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 171c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 172c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 173c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 174c09d2c2bSMike Makonnen may or may not exist on your system. 175c09d2c2bSMike Makonnen 17617c159dcSSøren Schmidt20030824: 17717c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 17817c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 179f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 180f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 18117c159dcSSøren Schmidt 182c1f61aa9SDavid E. O'Brien20030819: 183c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 184c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 185c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 186c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 18769f7bcf3SWarner Losh 18838c962e7SNate Lawson20030728: 18938c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 19038c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 19138c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 19238c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 19338c962e7SNate Lawson so the quirk can be re-enabled. 19438c962e7SNate Lawson 19574111097SWarner Losh20030724: 19674111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 19774111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 19874111097SWarner Losh 199178cf4e9SWarner Losh20030722: 200178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 201178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 202178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 203178cf4e9SWarner Losh FPU hardware. 204178cf4e9SWarner Losh 205178cf4e9SWarner Losh20030714: 206178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 207178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 208178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 209178cf4e9SWarner Losh People should report those issues to current@. 210178cf4e9SWarner Losh 211157c629aSWarner Losh20030711: 212157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 2138b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 21405538fa9SWarner Losh /usr/obj. 215157c629aSWarner Losh 21674111097SWarner Losh20030610: 21774111097SWarner Losh Remove deprecated locale names and transition period code 21874111097SWarner Losh for them, finishing switching to the new scheme. Check your 21974111097SWarner Losh LANG environment variable. 22074111097SWarner Losh 22174111097SWarner Losh20030609: 22274111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 22374111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 22474111097SWarner Losh important to remember beforehand if your source tree is on 22574111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 22674111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 22774111097SWarner Losh kernel. 22874111097SWarner Losh 22974111097SWarner Losh20030605: 2306cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 2316cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 2326cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 2336cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 2346cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 2356cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 2366cc6353fSMarcel Moolenaar 2376cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 2386cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 2396cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 2406cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 2416cc6353fSMarcel Moolenaar : 2426cc6353fSMarcel Moolenaar 2436cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 2446cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 2456cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 2466cc6353fSMarcel Moolenaar 24752b47445SMark Murray20030505: 24852b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 24952b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 25052b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 25152b47445SMark Murray 252a26df538SWarner Losh20030502: 253a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 254a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 255a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 256a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 257a26df538SWarner Losh 2584b065e2cSDoug Barton20030501: 2594b065e2cSDoug Barton The old rc system has been removed. Please report any problems 2604b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 2614b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 2624b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 2634b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 2644b065e2cSDoug Barton utilizes these old scripts has also been removed. 2654b065e2cSDoug Barton 26681cda3d9SWarner Losh20030423: 26781cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 26881cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 26981cda3d9SWarner Losh work around in devd will be removed around 20030507. You 27081cda3d9SWarner Losh have until then to upgrade your kernel before updating 27181cda3d9SWarner Losh userland. In general, you should have a userland and 27281cda3d9SWarner Losh kernel that's in sync with each other. However, given the 27381cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 27481cda3d9SWarner Losh allowances are made. 27581cda3d9SWarner Losh 27647a657d1SRuslan Ermilov20030329: 27747a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 27847a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 27947a657d1SRuslan Ermilov while upgrading the system through a buildworld. 28047a657d1SRuslan Ermilov 28147a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 28247a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 28347a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 28447a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 28547a657d1SRuslan Ermilov 28647a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 28747a657d1SRuslan Ermilov make cleandir && make obj && \ 28847a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 28947a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 29047a657d1SRuslan Ermilov 2915d2af00cSGregory Neil Shapiro20030208: 2925d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 2935d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 2945d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 2955d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 2965d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 2975d2af00cSGregory Neil Shapiro 2985d2af00cSGregory Neil Shapiro20030128: 2999db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 300ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 3019db58771SPoul-Henning Kamp be removed when convenient. 3029db58771SPoul-Henning Kamp 3038d9b3f57SJake Burkholder20030126: 3048d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 3058d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 3068d9b3f57SJake Burkholder 3071c5efda5SJeff Roberson20030125: 3081c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 3091c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 310ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 3111c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 3121c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 3131c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 3141c5efda5SJeff Roberson 3159d1d64f5SWarner Losh20030115: 3169d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 3179d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 3189d1d64f5SWarner Losh properly. 3199d1d64f5SWarner Losh 320c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 321c9fdb80aSWarner Losh configured for point to point links to bring it more in line 322c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 323c9fdb80aSWarner Losh with NetBSD. 324c9fdb80aSWarner Losh 325161dc364SAlexander Kabaev20021222: 326161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 327161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 328161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 329161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 330161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 331161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 33284cc83efSAlexander Kabaev rebuilt. 333161dc364SAlexander Kabaev 334fb4c8061SMartin Blapp20021216: 335fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 33689056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 337fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 3389d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 339fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 340fb4c8061SMartin Blapp 34117d47eb3SGiorgos Keramidas20021202: 34217d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 34317d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 34417d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 34517d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 34617d47eb3SGiorgos Keramidas 347a4459294SBill Fenner20021029: 348a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 349a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 350a4459294SBill Fenner consumers in sync. 351a4459294SBill Fenner 352fc8c157fSWarner Losh20021024: 353c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 354c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 355c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 356c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 357c57404feSRuslan Ermilov partition really is on. The old device names have gone 358c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 359c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 360c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 36169f7bcf3SWarner Losh 362fd9e8bdaSAndrew Gallatin20021023: 363fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 364fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 365fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 366fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 367fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 368fd9e8bdaSAndrew Gallatin 369fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 370fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 371fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 372fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 373fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 374fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 375fd9e8bdaSAndrew Gallatin 376f8a4c901SWarner Losh20020831: 377f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 378f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 379f8a4c901SWarner Losh programs and libraries need to be recompiled. 380f8a4c901SWarner Losh 381f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 382f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 383f8a4c901SWarner Losh 384c2248fa2SJens Schweikhardt20020827: 385c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 386c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 387c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 388c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 389c2248fa2SJens Schweikhardt 3900d533e43SRuslan Ermilov20020815: 3910d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 3920d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 3930d533e43SRuslan Ermilov again. 3940d533e43SRuslan Ermilov 39533c1de7dSRuslan Ermilov20020729: 39633c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 39733c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 39833c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 39933c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 40033c1de7dSRuslan Ermilov 4012b877facSJulian Elischer20020702: 4022b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 4032b877facSJulian Elischer There are still some minor problems with some signals but the 4042b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 4052b877facSJulian Elischer but each can successfully complete multiple buildworlds. 4062b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 4072b877facSJulian Elischer 40806596d37SWarner Losh20020701: 40906596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 41006596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 41106596d37SWarner Losh GNOME. 41206596d37SWarner Losh 41395ba4330SJacques Vidrine20020511: 41495ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 41595ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 41695ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 41795ba4330SJacques Vidrine with the set-user-ID bit set. 41895ba4330SJacques Vidrine 419a81da3c9SDavid E. O'Brien20020510: 420f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 421f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 4224b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 423f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 424f50caf6fSDavid E. O'Brien 425f50caf6fSDavid E. O'Brien20020510: 426a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 427a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 428a81da3c9SDavid E. O'Brien and then do a cvs update. 429a81da3c9SDavid E. O'Brien 430528a0ef5SJacques Vidrine20020421: 431528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 432528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 433528a0ef5SJacques Vidrine 43485aa5a2eSGregory Neil Shapiro20020404: 43585aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 43685aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 43785aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 43885aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 43985aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 44085aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 44185aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 44285aa5a2eSGregory Neil Shapiro 4438f1e4358SRuslan Ermilov20020403: 4448f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 4458f1e4358SRuslan Ermilov 4462292c02eSWarner Losh20020315: 4472292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 4482292c02eSWarner Losh 44969f7bcf3SWarner Losh20020225: 45069f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 45169f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 45269f7bcf3SWarner Losh 4538f35c493SWarner Losh20020217: 4548f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 4558f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 4568f35c493SWarner Losh command line mail submission has changed. Be sure to run 4578f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 4588f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 4598f35c493SWarner Losh 460835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 461835284beSWarner Losh required in order for sendmail to run as a set-group-ID 462835284beSWarner Losh binary. A 'make installworld' will use the new user and group 463835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 464835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 465835284beSWarner Losh and group must be merged from src/etc/group and 466835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 467835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 468835284beSWarner Losh mergemaster before this will work if you are updating from a 469835284beSWarner Losh very old version of current. The updating recipe has changed 470835284beSWarner Losh as of this date. 471835284beSWarner Losh 472fa9401c1SWarner Losh20020112: 473fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 474fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 475fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 476fa9401c1SWarner Losh you have local modifications, you can use 477fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 478fa9401c1SWarner Losh /etc/pam.d. 479fa9401c1SWarner Losh 480fa9401c1SWarner Losh Please see the following url for more details: 481fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 48247d0d01fSWarner Losh20011229: 48347d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 48447d0d01fSWarner Losh networkfs_types, please note that it has changed 48547d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 48647d0d01fSWarner Losh 487514318a8SWarner Losh20011220: 488514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 489514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 490514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 491514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 492514318a8SWarner Losh version have now been merged back into the base system's 493514318a8SWarner Losh version now. The only user-visible change resulting from this 494514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 495514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 496514318a8SWarner Losh as well. (There has never been rc file support for 497514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 498514318a8SWarner Losh reverted by the time the changes are MFCed.) 499514318a8SWarner Losh 500514318a8SWarner Losh20011215: 501514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 502514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 503514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 504514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 505514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 506514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 507514318a8SWarner Losh will need to be customized then for `odd' densities using 508514318a8SWarner Losh fdcontrol(8). 509514318a8SWarner Losh 5102d22e2bfSWarner Losh20011209: 5112d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 5122d22e2bfSWarner Losh and truss(1) now works again. 5132d22e2bfSWarner Losh 5149e0428e2SWarner Losh20011207: 5159e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 5169e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 5179e0428e2SWarner Losh see 5189e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 5199e0428e2SWarner Losh for details. 5209e0428e2SWarner Losh 5219bab8c59SWarner Losh20011204: 5229bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 5239bab8c59SWarner Losh kernel and burncd to be in sync. 5249bab8c59SWarner Losh 525e57d8b01SWarner Losh20011203: 526e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 527e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 528e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 529e57d8b01SWarner Losh not there already. 530e57d8b01SWarner Losh 531e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 532e57d8b01SWarner Losh until the issue has been resolved. 533e57d8b01SWarner Losh 534b001d36fSJacques Vidrine20011202: 535b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 536b001d36fSJacques Vidrine patched. 537b001d36fSJacques Vidrine 5384b676ec1SWarner Losh20011126: 5394b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 5405ebbf43eSWarner Losh after this date. You need to do this only once. 5414b676ec1SWarner Losh 542d961e462SWarner Losh20011103: 543d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 544d961e462SWarner Losh edges may be left, but for the most part things should be 5454b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 546d961e462SWarner Losh 547d961e462SWarner Losh20011030: 548d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 549d961e462SWarner Losh choppy waves in the upgrade process. 550d961e462SWarner Losh 5511fe003b6SWarner Losh20011030: 552a4b6fda0SWarner Losh The asr driver problem has been resolved. 5531fe003b6SWarner Losh 5541fe003b6SWarner Losh20011027: 5551fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 5561fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 5571fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 5581fe003b6SWarner Losh try to use from this date forward. 5591fe003b6SWarner Losh 5601fe003b6SWarner Losh20011025: 5611fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 5621fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 5631fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 5641fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 5651fe003b6SWarner Losh TARGET_ARCH=i386. 5661fe003b6SWarner Losh 567d05f9643SWarner Losh20011001: 568d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 569d05f9643SWarner Losh You must recompile both the kernel and userland applications 570d05f9643SWarner Losh at the same time. 571d05f9643SWarner Losh 57258970f85SWarner Losh20010929: 57358970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 57458970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 57558970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 57658970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 5779d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 57858970f85SWarner Losh 57958970f85SWarner Losh20010927: 58058970f85SWarner Losh Some weird problems result from using ACPI on some machines. 58158970f85SWarner Losh To disable ACPI you can add 58266ff0e67SMax Khon hint.acpi.0.disabled="1" 58358970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 58458970f85SWarner Losh loader "ok" prompt). 58558970f85SWarner Losh 58658970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 58758970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 58858970f85SWarner Losh file and not list acpi in that list. 589378f4486SAlfred Perlstein 5905119d237SWarner Losh20010924: 5915119d237SWarner Losh The buildworld has been fixed. You may need to install 5925119d237SWarner Losh the 4.x compatibility libraries for some old binaries 5938b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 5948b039fffSWarner Losh get them installed on every installworld, or execute the 5958b039fffSWarner Losh following to get them installed only once: 5968b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 59758970f85SWarner Losh make all install 5988b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 5995119d237SWarner Losh 6003c293725SWarner Losh20010919: 6013c293725SWarner Losh There's a bug in the world build process. The cross-tools 6023c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 6033c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 604772730c7SWarner Losh workaround is to add 6053c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 6063c293725SWarner Losh before building world when upgrading from 4.x to current. This 6073c293725SWarner Losh can be removed afterwards. 6083c293725SWarner Losh 6093c293725SWarner Losh A proper fix to the buildworld target is needed. 6103c293725SWarner Losh 6113c293725SWarner Losh20010918: 6123c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 6133c293725SWarner Losh NFS may be unstable after this date. 6143c293725SWarner Losh 6153c293725SWarner Losh20010912: 6163c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 6173c293725SWarner Losh the kernel. While a few problems were introduced in the 6183c293725SWarner Losh initial commit, most of the major ones have been found and 6193c293725SWarner Losh corrected. 6203c293725SWarner Losh 6213c293725SWarner Losh20010901: 6223c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 6233c293725SWarner Losh arounds described in the 20010604 entry are now no longer 6243c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 6253c293725SWarner Losh have been rectified around this date. 6263c293725SWarner Losh 62798b17b95SWarner Losh20010823: 62898b17b95SWarner Losh named now runs as user bind and group bind rather than as 62998b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 63098b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 63198b17b95SWarner Losh and that group bind is available in /etc/group. Also make 63298b17b95SWarner Losh sure that user or group bind has read (and not write) 63398b17b95SWarner Losh permission for your name server configuration and that it 63498b17b95SWarner Losh has read and write permission for your slave zone files and 63598b17b95SWarner Losh directory. 63698b17b95SWarner Losh 63798b17b95SWarner Losh If you wish to continue to run named as root (a less secure 63898b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 63998b17b95SWarner Losh 64098b17b95SWarner Losh named_flags= 64198b17b95SWarner Losh 6427b9786edSMark Murray20010709: 6437b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 6447b9786edSMark Murray the ability of the shared library major number to handle. 6457b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 6467b9786edSMark Murray solution is to rebuild those ports. 6477b9786edSMark Murray 6481d28950eSWarner Losh20010628: 6491d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 6501d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 6511d28950eSWarner Losh 652e72fd46aSWarner Losh20010625: 65398b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 65498b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 65598b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 65698b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 65798b17b95SWarner Losh IRQ configuration needs more safety belts. 65816de1a07SWarner Losh 6590d415dffSWarner Losh20010617: 660e72fd46aSWarner Losh Softupdates problems have been corrected. 6610d415dffSWarner Losh 6620d415dffSWarner Losh20010614: 6630d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 6640d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 6650d415dffSWarner Losh kernel building methods. 6660d415dffSWarner Losh 6678b9959adSWarner Losh20010613: 6688b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 6698b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 670e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 671e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 6728b9959adSWarner Losh 673e72fd46aSWarner Losh20010613: 6748b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 675e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 676e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 6778b9959adSWarner Losh 6780d415dffSWarner Losh20010612: 6790d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 6800d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 6810d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 6820d415dffSWarner Losh work around this issue, please use only one or the other mechanism 6830d415dffSWarner Losh until this bug is fixed. 6840d415dffSWarner Losh 685e72fd46aSWarner Losh Please note that a feature of config is that if you have config 686e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 687ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 688e72fd46aSWarner Losh 6890d415dffSWarner Losh20010610: 6900d415dffSWarner Losh Locale names have changed to match other systems better. 6910d415dffSWarner Losh 6926ccdb5e4SWarner Losh20010604: 6936ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 6946ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 6956ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 6963590182eSWarner Losh Interrupt storms look a lot like a hang. 6973590182eSWarner Losh 6983590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 6993590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 7003590182eSWarner Losh it is). 7013590182eSWarner Losh 7023590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 7033590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 7043590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 7053590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 7066ccdb5e4SWarner Losh 7070bc62786SWarner Losh20010530: 7080bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 7090bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 7100bc62786SWarner Losh a limited time. If you see 7110bc62786SWarner Losh 7120bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 7130bc62786SWarner Losh 7140bc62786SWarner Losh in your makeworld, then you need to migrate towards using 7150bc62786SWarner Losh COPY=-C. 7160bc62786SWarner Losh 71768a38c6cSWarner Losh20010525: 718b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 719c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 720c4f4a728SWarner Losh definitely is in bad shape. 72168a38c6cSWarner Losh 722ed0f29caSWarner Losh20010521: 723ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 724ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 725ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 726ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 727ed0f29caSWarner Losh is 728ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 729ed0f29caSWarner Losh 73080c16af9SWarner Losh20010520: 73168a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 73280c16af9SWarner Losh 73380c16af9SWarner Losh20010519: 73480c16af9SWarner Losh pccard has had much reorganizational work done to it over 73580c16af9SWarner Losh the past few days. Everything should still work, but if 73680c16af9SWarner Losh not, please contact imp@freebsd.org. 73780c16af9SWarner Losh 738a45f2d05SWarner Losh20010517: 739a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 740a45f2d05SWarner Losh userland at the same time. 741a45f2d05SWarner Losh 742a45f2d05SWarner Losh20010517: 743a45f2d05SWarner Losh New ncurses imported. 744a45f2d05SWarner Losh 7452988afcaSWarner Losh20010512: 7462988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 7472988afcaSWarner Losh will be the only way to go starting July 1. 7482988afcaSWarner Losh 7491a33dba7SWarner Losh20010504: 7501a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 7511a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 7521a33dba7SWarner Losh 75309946a51SWarner Losh20010502: 75409946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 75509946a51SWarner Losh 75609946a51SWarner Losh20010501: 75709946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 75809946a51SWarner Losh 75909946a51SWarner Losh20010430: 760a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 76109946a51SWarner Losh go back in the water. 76209946a51SWarner Losh 76309946a51SWarner Losh20010429: 76409946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 76509946a51SWarner Losh this date, but before the correction date. 76609946a51SWarner Losh 76791dd3b53SWarner Losh20010423: 76891dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 76991dd3b53SWarner Losh 77091dd3b53SWarner Losh20010411: 77191dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 77291dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 77391dd3b53SWarner Losh Update only if you understand that you must not use the old 77491dd3b53SWarner Losh fsck with the new kernel ever. 77591dd3b53SWarner Losh 776933b3269SWarner Losh20010330: 777933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 778c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 779933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 780933b3269SWarner Losh 781933b3269SWarner Losh20010319: 782933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 783933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 784933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 785f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 78609946a51SWarner Losh 78709946a51SWarner Losh20010315: 78809946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 789ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 79009946a51SWarner Losh been replaced by tunables. See ata.4 for details. 791933b3269SWarner Losh 792933b3269SWarner Losh20010312: 793933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 794933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 795933b3269SWarner Losh 796933b3269SWarner Losh20010312: 797933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 798933b3269SWarner Losh instead of ad-hoc. 799933b3269SWarner Losh 800933b3269SWarner Losh20010310: 801f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 802933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 803933b3269SWarner Losh ssh might not work if you don't. 804933b3269SWarner Losh 80562353691SWarner Losh20010303: 80662353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 80762353691SWarner Losh which means that you must include the miibus in your kernel if 80862353691SWarner Losh you use the ed driver. 80962353691SWarner Losh 810d325cf65SWarner Losh20010220: 811d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 812d325cf65SWarner Losh safe to go back into the water. 813d325cf65SWarner Losh 814024daae6SWarner Losh20010211: 815024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 816024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 817024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 818024daae6SWarner Losh that before upgrading would be a good time to do a level 0 819024daae6SWarner Losh dump of your system. No, really, I mean it this time. 820024daae6SWarner Losh 821024daae6SWarner Losh To get to the new system, you'll need to use the following 822024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 823024daae6SWarner Losh don't have to move this to the updating section. 824024daae6SWarner Losh 825024daae6SWarner Losh To get around the installworld problem, do: 826024daae6SWarner Losh # cd /usr/src/usr.bin/sed 827024daae6SWarner Losh # make install 828024daae6SWarner Losh # cd /usr/src 829024daae6SWarner Losh # make installworld 830024daae6SWarner Losh If that doesn't work, then try: 831024daae6SWarner Losh # make -k installworld 832024daae6SWarner Losh # make installworld 833024daae6SWarner Losh 834024daae6SWarner Losh20010207: 835024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 836024daae6SWarner Losh do not include devfs in your kernel as problems result. 837024daae6SWarner Losh 838024daae6SWarner Losh20010205: 8397595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 840024daae6SWarner Losh Remove them from your config. 841024daae6SWarner Losh 8421e159248SWarner Losh20010122: 8431e159248SWarner Losh ****************************** WARNING ****************************** 8441e159248SWarner Losh buildkernel has been changed slightly 8451e159248SWarner Losh ****************************** WARNING ****************************** 8461e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 8471e159248SWarner Losh should update your scripts and make.conf accordingly. 8481e159248SWarner Losh 8491e159248SWarner Losh20010119: 8501e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 8511e159248SWarner Losh This requires a new config to build correctly. 8521e159248SWarner Losh 853aac7dfeaSWarner Losh20010116: 854ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 855aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 856aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 857aac7dfeaSWarner Losh 858aac7dfeaSWarner Losh20010110: 859aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 860aac7dfeaSWarner Losh 861aac7dfeaSWarner Losh20010102: 862aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 863aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 864aac7dfeaSWarner Losh 86563c90c9eSWarner Losh20010101: 86663c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 86763c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 8685fd2a895SWarner Losh dump while building termcap. You can work around this problem 86963c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 87063c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 87163c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 87263c90c9eSWarner Losh might have been ignored by the -k option. 87363c90c9eSWarner Losh 8745fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 8755fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 8765fd2a895SWarner Losh of this working. 8775fd2a895SWarner Losh 878aac7dfeaSWarner Losh20001228: 879aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 880ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 881aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 882aac7dfeaSWarner Losh 883de2bcc63SWarner Losh20001218: 884de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 885de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 886de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 887de2bcc63SWarner Losh cards will not be recognized without it. 888de2bcc63SWarner Losh 889960773f7SWarner Losh20001205: 890960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 891960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 892960773f7SWarner Losh adding the following in pam.conf: 893960773f7SWarner Losh 894960773f7SWarner Losh sshd auth sufficient pam_skey.so 895960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 896960773f7SWarner Losh sshd session required pam_permit.so 897960773f7SWarner Losh 8980acc635eSWarner Losh20001031: 8990acc635eSWarner Losh cvs updated to 1.11. 9000acc635eSWarner Losh 9010acc635eSWarner Losh20001020: 9020acc635eSWarner Losh The random device needs more entropy, so you need to make sure 9030acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 9040acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 9050acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 9060acc635eSWarner Losh workaround. 9070acc635eSWarner Losh 9080acc635eSWarner Losh20001010: 9090acc635eSWarner Losh ****************************** WARNING ****************************** 9100acc635eSWarner Losh Sendmail has been updated. 9110acc635eSWarner Losh ****************************** WARNING ****************************** 9120acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 9130acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 9140acc635eSWarner Losh is set. 9150acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 9160acc635eSWarner Losh commands. 9170acc635eSWarner Losh o Now using sendmail's version of vacation(1). 9180acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 9190acc635eSWarner Losh in /usr/share/sendmail/cf. 9200acc635eSWarner Losh o sendmail.cw changed to local-host-names 9210acc635eSWarner Losh 9220acc635eSWarner Losh More details can be found at 9230acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 9240acc635eSWarner Losh 9256e98a146SWarner Losh20001009: 9266e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 9276e98a146SWarner Losh your entire ports tree, or you will have problems. 9286e98a146SWarner Losh 9296e98a146SWarner Losh20001006: 930685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 9316e98a146SWarner Losh the installed miniperl. It is recommended that you delete 9326e98a146SWarner Losh /usr/bin/miniperl. 9336e98a146SWarner Losh 934073113a4SWarner Losh20001005: 935073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 936685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 937073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 938073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 939073113a4SWarner Losh tree for anything to work. 940073113a4SWarner Losh 9410acc635eSWarner Losh20000928: 9420acc635eSWarner Losh There was a change in the passwd format. Need more information. 9430acc635eSWarner Losh 944be3885b3SWarner Losh20000916: 945be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 946be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 947be3885b3SWarner Losh same time as your kernel. 948be3885b3SWarner Losh 94976ec9675SWarner Losh20000914: 95076ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 95176ec9675SWarner Losh include the device will cause suspended laptops losing time 95276ec9675SWarner Losh when they resume. Include 95376ec9675SWarner Losh device pmtimer 95476ec9675SWarner Losh in your config file and 95501b9a434SWarner Losh hint.pmtimer.0.at="isa" 95676ec9675SWarner Losh to your /boot/device.hints file. 95776ec9675SWarner Losh 958f4865386SMark Murray20000911: 959f4865386SMark Murray The random device has been turned into a (pseudo-)device, 960f4865386SMark Murray rather than an option. The supplied kernel config files have 961f4865386SMark Murray been updated. You will need to do something similar in your 962f4865386SMark Murray own kernel config file. 963f4865386SMark Murray Remove: 964f4865386SMark Murray options RANDOMDEV 965f4865386SMark Murray Add: 966f4865386SMark Murray device random 967f4865386SMark Murray If you prefer to load the loadable module, you need to do 968f4865386SMark Murray nothing. 969f4865386SMark Murray 970d594498fSWarner Losh20000909: 971d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 972d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 973d594498fSWarner Losh reflect this if you load this module at boot time. 974d594498fSWarner Losh The line should read: 975d594498fSWarner Losh random_load="YES" 976d594498fSWarner Losh 9770deb7ddcSWarner Losh20000907: 9780deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 97916eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 98016eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 98116eb772dSWarner Losh sure you don't have model loading problems which might at 98216eb772dSWarner Losh first blush appear related to SMP. 98352bf24e7SWarner Losh 9845a01880bSWarner Losh20000906: 9855a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 9865a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 9875a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 9885a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 9895a01880bSWarner Losh don't have one, and you have host.conf. 9905a01880bSWarner Losh 9912b41163cSWarner Losh20000905: 99238d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 99338d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 99438d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 99538d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 99638d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 99738d6ecd2SWarner Losh 99838d6ecd2SWarner Losh20000905: 9998aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 10008aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 10018aab4bc7SWarner Losh is /boot/kernel. 10028aab4bc7SWarner Losh 10038aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 100438d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 100538d6ecd2SWarner Losh installkernel/installworld dance. 10062b41163cSWarner Losh 1007d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1008d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1009d594498fSWarner Losh modules in that directory instead of finding them in the correct 1010d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1011d594498fSWarner Losh is that the linux module crashes your machine after the update. 1012d594498fSWarner Losh 1013d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1014d594498fSWarner Losh mv /modules.old /boot/kernel.old 1015d594498fSWarner Losh chflags noschg /kernel.old 1016d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1017d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1018d594498fSWarner Losh fi 1019d594498fSWarner Losh 1020c22a309cSWarner Losh20000904: 1021c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1022c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1023c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1024c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1025c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1026c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1027c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1028c22a309cSWarner Losh is not likely to be generated. 1029c22a309cSWarner Losh 1030fdb9f54dSWarner Losh20000825: 1031fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 10329c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 10339c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 10349c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 10359c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 10369c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 10379c1a7444SWarner Losh messages will appear after the boot loader tries to start the 10389c1a7444SWarner Losh kernel. 10399c1a7444SWarner Losh 10409c1a7444SWarner Losh20000821: 10419c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 10429c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 10439c1a7444SWarner Losh /boot/loader.conf. 1044fdb9f54dSWarner Losh 10458f250aa7SWarner Losh20000812: 10465da0d091SWarner Losh suidperl is now always built and installed on the system, but 10475da0d091SWarner Losh with permissions of 511. If you have applications that use 10485da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 10495da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 10505da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 10515da0d091SWarner Losh will fix this until the next build. 10525da0d091SWarner Losh 10535da0d091SWarner Losh20000812: 10548f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 10558f250aa7SWarner Losh visible changes that may immediately affect your configuration 10568f250aa7SWarner Losh include: 10578f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 10588f250aa7SWarner Losh - newaliases limited to root and trusted users 10598f250aa7SWarner Losh - MSA port (587) turned on by default 10608f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 10618f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 10628f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 10638f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 10648f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 10658f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 10668f250aa7SWarner Losh 106771c38472SWarner Losh20000810: 106871c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 106971c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 107071c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 107171c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 107271c38472SWarner Losh specific use for it. 107371c38472SWarner Losh 107471c38472SWarner Losh20000729: 107571c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 107671c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 107771c38472SWarner Losh /etc/rc.conf if they want to have the same setup 107871c38472SWarner Losh afterwards (unless the variables already are set, of course): 107971c38472SWarner Losh # Enable network daemons for user convenience. 108071c38472SWarner Losh inetd_enable="YES" 108171c38472SWarner Losh portmap_enable="YES" 108271c38472SWarner Losh sendmail_enable="YES" 108371c38472SWarner Losh 108471c38472SWarner Losh20000728: 108571c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 108671c38472SWarner Losh will need to change that to nullfs_load="YES". 108771c38472SWarner Losh 10881dece4a9SWarner Losh20000728: 10891dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 10901dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 10911dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 10921dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 10931dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 10941dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 10951dece4a9SWarner Losh to /MYKERNEL. 10961dece4a9SWarner Losh 1097409e887cSWarner Losh20000711: 1098409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1099409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1100409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1101409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1102409e887cSWarner Losh for details on potential problems that you might have and how 1103409e887cSWarner Losh to get around them. 1104409e887cSWarner Losh 1105409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1106409e887cSWarner Losh clauses above, you needn't worry. 1107409e887cSWarner Losh 1108409e887cSWarner Losh20000711: 1109409e887cSWarner Losh /etc/security has been updated to print the inode number of 1110409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1111409e887cSWarner Losh in the number of changed programs the first time when you run 1112409e887cSWarner Losh mergemaster to get a new /etc/security. 1113409e887cSWarner Losh 1114673d13f2SWarner Losh20000710: 1115673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1116673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1117673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1118673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1119673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1120673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1121673d13f2SWarner Losh errors. (see below, 20000624). 1122673d13f2SWarner Losh 1123bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 11241dece4a9SWarner Losh 1125673d13f2SWarner Losh20000709: 1126c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1127c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1128c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1129673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1130673d13f2SWarner Losh 1131e98e26cdSWarner Losh20000706: 1132e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1133e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1134e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1135f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1136e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 11372c021c6cSMark Ovens interim if needed. 1138e98e26cdSWarner Losh 1139e98e26cdSWarner Losh20000705: 1140e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1141e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1142e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1143e98e26cdSWarner Losh details. 1144e98e26cdSWarner Losh 1145c373950eSWarner Losh20000704: 11462f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 11472f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 11482f961bc8SWarner Losh 11492f961bc8SWarner Losh20000704: 1150c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1151c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1152c373950eSWarner Losh rc.d scripts that haven't been updated. 1153c373950eSWarner Losh 115427dc3a2bSWarner Losh20000630: 115527dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 115627dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 115727dc3a2bSWarner Losh which should be reported to des@freebsd.org. 115827dc3a2bSWarner Losh 1159b8c215acSWarner Losh20000625: 1160b8c215acSWarner Losh From approximately this date forward, one must have the crypto 116127dc3a2bSWarner Losh system installed in order to build the system and kernel. 116227dc3a2bSWarner Losh While not technically strictly true, one should treat it as 116327dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 116427dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 116527dc3a2bSWarner Losh were required. You should check with the latest collections 116627dc3a2bSWarner Losh to make sure that these haven't changed. 1167b8c215acSWarner Losh 11687b990719SWarner Losh20000624: 11697b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 11707b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 11717b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 11721a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 11737b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 11747b990719SWarner Losh openssh and openssl should not be used to generate keys from this 11757b990719SWarner Losh date to the completion of the work. 11767b990719SWarner Losh 117727dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 117827dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 117927dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 118027dc3a2bSWarner Losh recreate the random and urandom devices. 118127dc3a2bSWarner Losh 118281e54c50SWarner Losh20000622: 118381e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 118481e54c50SWarner Losh BSD license. You may need to remove your symbolic links 118581e54c50SWarner Losh that used to be required when updating. 118681e54c50SWarner Losh 118739943833SWarner Losh20000621: 11882c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 11892a2f33fbSDaniel Baker the config file update procedure. 11902a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1191c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 119259df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 119359df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 119439943833SWarner Losh 1195290f9ad8SWarner Losh20000620: 1196290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1197290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1198290f9ad8SWarner Losh that workaround will no longer be required. 1199290f9ad8SWarner Losh 120090fb6346SWarner Losh20000615: 120190fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 120290fb6346SWarner Losh ad driver. If you haven't done so already, you must update 120390fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 120490fb6346SWarner Losh devices. 120590fb6346SWarner Losh 1206f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1207f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1208f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1209f75f65bbSWarner Losh may work). 1210f75f65bbSWarner Losh 1211ba26da8eSWarner Losh20000612: 1212ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1213290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1214c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1215290f9ad8SWarner Losh to your config file to compile them in statically. The format 1216f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1217f54a3542SWarner Losh NEWCARD for examples of the new format. 1218290f9ad8SWarner Losh 12199698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 12209698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 12219698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 12229698f2c0SWarner Losh in it. 1223bbcc5149SWarner Losh 1224d65850ebSWarner Losh20000522: 1225ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1226d65850ebSWarner Losh building a kernel after this point is advised that they need 1227d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1228d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1229d65850ebSWarner Losh 1230d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1231d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1232d9583a00SWarner Losh is recommended that you don't set this option until the problem 1233d9583a00SWarner Losh is resolved. 1234d9583a00SWarner Losh 12358039cedeSWarner Losh20000513: 12368039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 12378039cedeSWarner Losh 1238d65850ebSWarner Losh20000510: 12398039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 12408039cedeSWarner Losh This will require some care in updating alphas. A new libstand 12418039cedeSWarner Losh is requires for the boot blocks to build properly. 12428039cedeSWarner Losh 12438039cedeSWarner Losh20000503: 12448039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 12458039cedeSWarner Losh is now available. 12468039cedeSWarner Losh 1247d65850ebSWarner Losh20000502: 1248d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1249d65850ebSWarner Losh connected to the kernel building instead. 1250d65850ebSWarner Losh 1251be149406SNik Clayton20000427: 12528039cedeSWarner Losh You may need to build gperf 12538039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 12548039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 12558039cedeSWarner Losh an option only in -current. 12568039cedeSWarner Losh 12572b8dd5f4SWarner Losh20000417: 12582b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1259f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 12602b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 12612b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 12622c021c6cSMark Ovens before you reboot, you'll need to issue: 12632b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 12642b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 12652b8dd5f4SWarner Losh 12668d9f1945SWarner Losh20000320: 12672b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 12682b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 12692b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1270ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 12712b8dd5f4SWarner Losh to the start of /etc/rc.conf. 12728d9f1945SWarner Losh 1273f8ab1dd6SWarner Losh20000319: 1274f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1275f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1276f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1277f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1278f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1279f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1280f8ab1dd6SWarner Losh 128119cada77SWarner Losh20000318: 1282f699bbbbSMark Ovens We've entered the traditional post release dumping party. 128319cada77SWarner Losh Large kernel changes are being committed and are in the 128419cada77SWarner Losh works. It is important to keep the systems' klds and kernel 128519cada77SWarner Losh in sync as kernel interfaces and structures are changing. 128619cada77SWarner Losh Before reporting kernel panics, make sure that all modules 128719cada77SWarner Losh that you are loading are up to date. 1288ba228352SWarner Losh 128919cada77SWarner Losh20000315: 12906d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 12916d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 12926d23c382SWarner Losh will do the trick. This isn't critical until you remove your 12936d23c382SWarner Losh wd device entries in /dev, at which point your system will not 12946d23c382SWarner Losh boot. 12956d23c382SWarner Losh 12966d23c382SWarner Losh20000315: 129719cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 129819cada77SWarner Losh to upgrade to 4.0 from 3.x. 129957199806SWarner Losh 1300dc0dbf5cSWarner LoshCOMMON ITEMS: 1301dc0dbf5cSWarner Losh 1302a24eff53SWarner Losh General Notes 1303a24eff53SWarner Losh ------------- 1304a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1305a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1306a24eff53SWarner Losh installworld. This is especially true when upgrading between 1307a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1308a24eff53SWarner Losh or several minor releases, or when several months have passed 1309a24eff53SWarner Losh on the -current branch). 1310a24eff53SWarner Losh 13115780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 13125780f3baSWarner Losh poisoning. This can happen because the make utility reads its 13135780f3baSWarner Losh environment when searching for values for global variables. 13145780f3baSWarner Losh To run your build attempts in an "environmental clean room", 13155780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 13165780f3baSWarner Losh page for more details. 13175780f3baSWarner Losh 1318dc0dbf5cSWarner Losh To build a kernel 1319dc0dbf5cSWarner Losh ----------------- 1320ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1321f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1322ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1323282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1324282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1325dc0dbf5cSWarner Losh 1326ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1327ba01eb20SWarner Losh -------------------------------------------------------------- 1328ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 132947d0d01fSWarner Losh config KERNEL_NAME_HERE 1330ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1331ba01eb20SWarner Losh make depend 1332ba01eb20SWarner Losh make 1333ba01eb20SWarner Losh make install 1334ba01eb20SWarner Losh 1335ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1336ba01eb20SWarner Losh 1337ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1338ba01eb20SWarner Losh ----------------------------------------------------------- 133963cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 134063cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 134163cb445eSWarner Losh 1342f643de42SWarner Losh <make sure you have good level 0 dumps> 134363cb445eSWarner Losh <maybe fix /etc/fstab> [7] 134463cb445eSWarner Losh make buildworld 134563cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 134663cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 134763cb445eSWarner Losh [1] 134863cb445eSWarner Losh <reboot in single user> [3] 134963cb445eSWarner Losh mergemaster -p [5] 135063cb445eSWarner Losh make installworld 135163cb445eSWarner Losh mergemaster [4] 135263cb445eSWarner Losh <reboot> 135363cb445eSWarner Losh 1354759f0aefSWarner Losh 1355f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1356f27b1fceSJoseph Koshy -------------------------------------------------- 1357f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1358f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1359f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1360f27b1fceSJoseph Koshy # size. 1361f27b1fceSJoseph Koshy 1362f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1363f27b1fceSJoseph Koshy <boot into -stable> 1364f27b1fceSJoseph Koshy make buildworld 1365f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1366f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1367f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1368f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1369f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1370f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1371f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1372f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1373f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1374f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1375f27b1fceSJoseph Koshy <reboot into current> 1376f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1377f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1378f27b1fceSJoseph Koshy <reboot> 1379f27b1fceSJoseph Koshy 1380f27b1fceSJoseph Koshy 1381f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1382f27b1fceSJoseph Koshy ---------------------------------------------- 13835c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 13845c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 13855c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 13865c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1387ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1388f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1389f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1390f643de42SWarner Losh # space on /. 1391f643de42SWarner Losh 1392f643de42SWarner Losh <make sure you have good level 0 dumps> 1393fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 139421c075eaSWarner Losh make buildworld [9] 1395c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1396d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1397be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1398fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1399fc8c157fSWarner Losh [1] 1400fc8c157fSWarner Losh <reboot in single user> [3] 1401835284beSWarner Losh mergemaster -p [5] 1402f8a4c901SWarner Losh rm -rf /usr/include/g++ 1403ba26da8eSWarner Losh make installworld 1404a6cd4f9dSWarner Losh mergemaster [4] 1405ba26da8eSWarner Losh <reboot> 1406ba26da8eSWarner Losh 1407fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1408fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1409fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1410fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1411fdb9f54dSWarner Losh the UPDATING entries. 1412ba26da8eSWarner Losh 14131dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 14141dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 14151dece4a9SWarner Losh your sources that you have read and understood all the recent 14161dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 14171dece4a9SWarner Losh much fewer pitfalls. 14181dece4a9SWarner Losh 1419134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1420134d2e86SWarner Losh should disable them at this point so they don't crash your 1421134d2e86SWarner Losh system on reboot. 1422134d2e86SWarner Losh 14239c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 14249c1a7444SWarner Losh your own device.hints to reflect your unique hardware 14259c1a7444SWarner Losh configuration. 14269c1a7444SWarner Losh 1427ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1428ee6e1fc3SWarner Losh fsck -p 1429ee6e1fc3SWarner Losh mount -u / 1430ee6e1fc3SWarner Losh mount -a 1431ee6e1fc3SWarner Losh cd /usr/src 143247d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1433f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1434f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1435b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1436b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1437b705ae10SWarner Losh be ignored while you proceed to the next step. 1438ee6e1fc3SWarner Losh 1439a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1440a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1441a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1442a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1443a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1444a6cd4f9dSWarner Losh for potential gotchas. 1445a6cd4f9dSWarner Losh 1446835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1447835284beSWarner Losh you may need to do this if you get unknown user in the following 1448835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1449835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1450835284beSWarner Losh install) after the buildworld before this step if you last updated 1451835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1452835284beSWarner Losh 1453bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1454bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1455bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1456bd79cf40SWarner Losh ok unload 1457bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1458bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1459bd79cf40SWarner Losh described here. 1460fc8c157fSWarner Losh 1461fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1462fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1463fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1464fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1465fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1466fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1467fc8c157fSWarner Losh 1468c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1469c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1470c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1471c74fe6afSWarner Losh that is hard to boot to recover. 1472c74fe6afSWarner Losh 147321c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 147421c075eaSWarner Losh cvs prune empty directories. 1475dc0dbf5cSWarner LoshFORMAT: 1476dc0dbf5cSWarner Losh 1477f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 14781fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1479f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1480f8ab1dd6SWarner Loshprevious releases if your system is older than this. 14811fc1a0dcSWarner Losh 1482e72fd46aSWarner LoshCopyright information: 1483e72fd46aSWarner Losh 14849698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1485e72fd46aSWarner Losh 1486772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1487772730c7SWarner Loshmodification, in full or in part, in any form or format of this 14889698f2c0SWarner Loshdocument are permitted without further permission from the author. 1489e72fd46aSWarner Losh 1490e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1491e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1492e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1493e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1494e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1495e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1496e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1497e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1498e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1499e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1500e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1501e72fd46aSWarner Losh 1502e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1503e72fd46aSWarner Loshauthor a beer. 1504e72fd46aSWarner Losh 150522306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1506772730c7SWarner Loshthis document. 1507772730c7SWarner Losh 150897d92980SPeter Wemm$FreeBSD$ 1509