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 208ee2ac9eSMax Laier20040623: 218ee2ac9eSMax Laier pf was updated to OpenBSD-stable 3.5 and pflogd(8) is priviledge 228ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 238ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 248ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 258ee2ac9eSMax Laier 263db5687dSBrooks Davis20040622: 273db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 283db5687dSBrooks Davis require a recompile of modules using cloning and modification of 293db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 303db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 313db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 323db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 333db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 343db5687dSBrooks Davis 35e0ae81f3SDag-Erling Smørgrav20040621: 36e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 37e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 38e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 39e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 40e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 41e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 42e0ae81f3SDag-Erling Smørgrav during the next reboot. 43e0ae81f3SDag-Erling Smørgrav 444717d22aSJohn Polstra20040614: 454717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 464717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 474717d22aSJohn Polstra the ips module and any third-party modules which call 484717d22aSJohn Polstra sema_timedwait. 494717d22aSJohn Polstra 506cb7a382SMax Laier20040613: 516cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 526cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 53df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 54df843493SMax Laier please recompile and reinstall world. 556cb7a382SMax Laier 562454685eSJulian Elischer20040607: 572454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 582454685eSJulian Elischer requires that you re-run config after updating your tree. 592454685eSJulian Elischer 6064fef830SSeigo Tanimura20040601: 6164fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 6264fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 6364fef830SSeigo Tanimura kernel configuration. 6464fef830SSeigo Tanimura 65bb4f06e7SAndre Oppermann20040423: 66bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 67bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 68bb4f06e7SAndre Oppermann options are not affected but those with options may break until 69bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 70bb4f06e7SAndre Oppermann 7105641e82SColin Percival20040420: 7205641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 7305641e82SColin Percival date may be incompatible with kernel modules compiled prior to 7405641e82SColin Percival 20040406. 7505641e82SColin Percival 76d0dc9183SWarner Losh20040414: 77d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 78d0dc9183SWarner Losh problems for your system, please disable it using the tunable 79d0dc9183SWarner Losh hw.pci.do_powerstate=0. 80d0dc9183SWarner Losh 81d0dc9183SWarner Losh20040412: 82d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 83d0dc9183SWarner Losh drive is still broken. 84d0dc9183SWarner Losh 85d0dc9183SWarner Losh20040410: 86d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 87d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 88d0dc9183SWarner Losh the unanticipated problems have been resolved. 89d0dc9183SWarner Losh 908633bbeaSBrooks Davis20040409: 918633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 928633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 938633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 948633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 9576c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 968633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 978633bbeaSBrooks Davis 98d40d033aSRobert Watson20040322: 99d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 100d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 101d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 102d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 103d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 104d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 105d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 106d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 107d40d033aSRobert Watson locking is merged to permit this to take place. 108d40d033aSRobert Watson 109ec9b318eSGarance A Drosehn20040310: 110ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 111ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 112ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 113ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 114ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 115ec9b318eSGarance A Drosehn 116fc28f1ffSMax Laier20040308: 117fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 118fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 1194c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 1204c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 121fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 122fc28f1ffSMax Laier pf system consists of the following three devices: 123fc28f1ffSMax Laier device pf # required 124fc28f1ffSMax Laier device pflog # optional 125fc28f1ffSMax Laier device pfsync # optional 126fc28f1ffSMax Laier 1273aff5d06SDag-Erling Smørgrav20040303: 1283aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 1293aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 1303aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 1313aff5d06SDag-Erling Smørgrav 1323aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 1333aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 1343aff5d06SDag-Erling Smørgrav 1353aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 1363aff5d06SDag-Erling Smørgrav to use libpthread instead. 1373aff5d06SDag-Erling Smørgrav 138fd63c5b3SDag-Erling Smørgrav20040226: 1399d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 140fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 141fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 142fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 143fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 144fd63c5b3SDag-Erling Smørgrav 145714ae42aSBruce M Simpson20040225: 146e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 147e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 148e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 149e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 150e07a40f3SBrian Feldman should remain unaffected. 151e07a40f3SBrian Feldman 152e07a40f3SBrian Feldman20040225: 153714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 154714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 155714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 156714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 157714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 158714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 159714ae42aSBruce M Simpson 160fbd2e692SAndre Oppermann20040224: 161fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 162fbd2e692SAndre Oppermann and related userland network utilities neccessary. 163fbd2e692SAndre Oppermann 164158b90daSWarner Losh20040222: 165158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 166158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 167158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 168158b90daSWarner Losh Drivers outside the tree will need to be updated. 169158b90daSWarner Losh 170b7b1e150SMike Makonnen20040207: 171b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 172b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 173b7b1e150SMike Makonnen 174aca89ee6SDaniel Eischen20040130: 175aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 176aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 177aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 178aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 179aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 180aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 181aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 182aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 183aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 184aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 185aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 186aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 187aca89ee6SDaniel Eischen do not work with libpthread. 188aca89ee6SDaniel Eischen 18968b7b3a9SAlex Dupre20040125: 19068b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 19168b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 19268b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 19368b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 19468b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 19568b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 19668b7b3a9SAlex Dupre 197ff46e0deSWarner Losh20040125: 198ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 199ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 200ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 201ff46e0deSWarner Losh 202ce41f4bfSRobert Watson20031213: 203ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 204ce41f4bfSRobert Watson if the login process is unable to successfully set the 205ce41f4bfSRobert Watson process credentials to include all groups defined for the 206ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 207ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 208ce41f4bfSRobert Watson defined, or they will be unable to log in. 209ce41f4bfSRobert Watson 210c124fa05SJohn Baldwin20031203: 211c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 212c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 213c124fa05SJohn Baldwin 2148ad1f5e4SHartmut Brandt20031112: 21530093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 21630093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 21797209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 21897209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 21997209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 22097209ca3SRobert Watson not know about the new system calls that support the new statfs 2213f631d52SMarcel Moolenaar structure. 2223f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 2233f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 2243f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 2253f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 2263f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 2273f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 2283f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 2293f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 2303f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 2313f631d52SMarcel Moolenaar these changes are installed. 23230093b05SWarner Losh 23330093b05SWarner Losh ****************************DANGER******************************* 23430093b05SWarner Losh 23530093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 23630093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 23730093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 23830093b05SWarner Losh kernel. 23964a18d6fSKirk McKusick 24064a18d6fSKirk McKusick20031112: 2418ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 2428ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 2438ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 2448ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 2458ad1f5e4SHartmut Brandt sync before rebooting. 2468ad1f5e4SHartmut Brandt 247c53a5d8fSJohn Baldwin20031111: 248c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 249c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 250c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 251c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 252c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 253c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 254c53a5d8fSJohn Baldwin 2558bf455a5SJohn Baldwin20031103: 2568bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 2578bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 2582a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 2598bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 2608bf455a5SJohn Baldwin 2619bf40edeSBrooks Davis20031031: 2629bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 2639bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 2649bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 2659bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 2669bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 2679bf40edeSBrooks Davis reflect this change. 2689bf40edeSBrooks Davis 26947a42c7aSPoul-Henning Kamp20030928: 27047a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 27147a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 27247a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 27347a42c7aSPoul-Henning Kamp 27407105342SMax Khon20030926: 27507105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 27607105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 27707105342SMax Khon 27817dcd026SSam Leffler20030925: 27917dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 28017dcd026SSam Leffler also be explicitly configured. Previously this dependency was 28117dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 28217dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 28317dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 28417dcd026SSam Leffler 285fedf1d01SBruce M Simpson20030923: 286fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 287fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 288fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 289fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 290fedf1d01SBruce M Simpson 291db38f9cbSJacques Vidrine20030915: 292db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 293db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 294db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 295db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 296db38f9cbSJacques Vidrine 297c09d2c2bSMike Makonnen20030829: 298c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 299c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 300c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 301c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 302c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 303c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 304c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 305c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 306c09d2c2bSMike Makonnen may or may not exist on your system. 307c09d2c2bSMike Makonnen 30817c159dcSSøren Schmidt20030824: 30917c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 31017c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 311f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 312f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 31317c159dcSSøren Schmidt 314c1f61aa9SDavid E. O'Brien20030819: 315c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 316c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 317c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 318c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 31969f7bcf3SWarner Losh 32038c962e7SNate Lawson20030728: 32138c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 32238c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 32338c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 32438c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 32538c962e7SNate Lawson so the quirk can be re-enabled. 32638c962e7SNate Lawson 32774111097SWarner Losh20030724: 32874111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 32974111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 33074111097SWarner Losh 331178cf4e9SWarner Losh20030722: 332178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 333178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 334178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 335178cf4e9SWarner Losh FPU hardware. 336178cf4e9SWarner Losh 337178cf4e9SWarner Losh20030714: 338178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 339178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 340178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 341178cf4e9SWarner Losh People should report those issues to current@. 342178cf4e9SWarner Losh 343157c629aSWarner Losh20030711: 344157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 3458b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 34605538fa9SWarner Losh /usr/obj. 347157c629aSWarner Losh 34874111097SWarner Losh20030610: 34974111097SWarner Losh Remove deprecated locale names and transition period code 35074111097SWarner Losh for them, finishing switching to the new scheme. Check your 35174111097SWarner Losh LANG environment variable. 35274111097SWarner Losh 35374111097SWarner Losh20030609: 35474111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 35574111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 35674111097SWarner Losh important to remember beforehand if your source tree is on 35774111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 35874111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 35974111097SWarner Losh kernel. 36074111097SWarner Losh 36174111097SWarner Losh20030605: 3626cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 3636cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 3646cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 3656cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 3666cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 3676cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 3686cc6353fSMarcel Moolenaar 3696cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 3706cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 3716cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 3726cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 3736cc6353fSMarcel Moolenaar : 3746cc6353fSMarcel Moolenaar 3756cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 3766cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 3776cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 3786cc6353fSMarcel Moolenaar 37952b47445SMark Murray20030505: 38052b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 38152b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 38252b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 38352b47445SMark Murray 384a26df538SWarner Losh20030502: 385a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 386a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 387a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 388a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 389a26df538SWarner Losh 3904b065e2cSDoug Barton20030501: 3914b065e2cSDoug Barton The old rc system has been removed. Please report any problems 3924b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 3934b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 3944b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 3954b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 3964b065e2cSDoug Barton utilizes these old scripts has also been removed. 3974b065e2cSDoug Barton 39881cda3d9SWarner Losh20030423: 39981cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 40081cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 40181cda3d9SWarner Losh work around in devd will be removed around 20030507. You 40281cda3d9SWarner Losh have until then to upgrade your kernel before updating 40381cda3d9SWarner Losh userland. In general, you should have a userland and 40481cda3d9SWarner Losh kernel that's in sync with each other. However, given the 40581cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 40681cda3d9SWarner Losh allowances are made. 40781cda3d9SWarner Losh 40847a657d1SRuslan Ermilov20030329: 40947a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 41047a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 41147a657d1SRuslan Ermilov while upgrading the system through a buildworld. 41247a657d1SRuslan Ermilov 41347a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 41447a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 41547a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 41647a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 41747a657d1SRuslan Ermilov 41847a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 41947a657d1SRuslan Ermilov make cleandir && make obj && \ 42047a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 42147a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 42247a657d1SRuslan Ermilov 4235d2af00cSGregory Neil Shapiro20030208: 4245d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 4255d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 4265d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 4275d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 4285d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 4295d2af00cSGregory Neil Shapiro 4305d2af00cSGregory Neil Shapiro20030128: 4319db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 432ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 4339db58771SPoul-Henning Kamp be removed when convenient. 4349db58771SPoul-Henning Kamp 4358d9b3f57SJake Burkholder20030126: 4368d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 4378d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 4388d9b3f57SJake Burkholder 4391c5efda5SJeff Roberson20030125: 4401c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 4411c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 442ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 4431c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 4441c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 4451c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 4461c5efda5SJeff Roberson 4479d1d64f5SWarner Losh20030115: 4489d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 4499d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 4509d1d64f5SWarner Losh properly. 4519d1d64f5SWarner Losh 452c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 453c9fdb80aSWarner Losh configured for point to point links to bring it more in line 454c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 455c9fdb80aSWarner Losh with NetBSD. 456c9fdb80aSWarner Losh 457161dc364SAlexander Kabaev20021222: 458161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 459161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 460161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 461161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 462161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 463161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 46484cc83efSAlexander Kabaev rebuilt. 465161dc364SAlexander Kabaev 466fb4c8061SMartin Blapp20021216: 467fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 46889056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 469fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 4709d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 471fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 472fb4c8061SMartin Blapp 47317d47eb3SGiorgos Keramidas20021202: 47417d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 47517d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 47617d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 47717d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 47817d47eb3SGiorgos Keramidas 479a4459294SBill Fenner20021029: 480a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 481a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 482a4459294SBill Fenner consumers in sync. 483a4459294SBill Fenner 484fc8c157fSWarner Losh20021024: 485c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 486c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 487c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 488c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 489c57404feSRuslan Ermilov partition really is on. The old device names have gone 490c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 491c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 492c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 49369f7bcf3SWarner Losh 494fd9e8bdaSAndrew Gallatin20021023: 495fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 496fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 497fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 498fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 499fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 500fd9e8bdaSAndrew Gallatin 501fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 502fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 503fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 504fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 505fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 506fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 507fd9e8bdaSAndrew Gallatin 508f8a4c901SWarner Losh20020831: 509f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 510f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 511f8a4c901SWarner Losh programs and libraries need to be recompiled. 512f8a4c901SWarner Losh 513f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 514f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 515f8a4c901SWarner Losh 516c2248fa2SJens Schweikhardt20020827: 517c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 518c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 519c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 520c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 521c2248fa2SJens Schweikhardt 5220d533e43SRuslan Ermilov20020815: 5230d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 5240d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 5250d533e43SRuslan Ermilov again. 5260d533e43SRuslan Ermilov 52733c1de7dSRuslan Ermilov20020729: 52833c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 52933c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 53033c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 53133c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 53233c1de7dSRuslan Ermilov 5332b877facSJulian Elischer20020702: 5342b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 5352b877facSJulian Elischer There are still some minor problems with some signals but the 5362b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 5372b877facSJulian Elischer but each can successfully complete multiple buildworlds. 5382b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 5392b877facSJulian Elischer 54006596d37SWarner Losh20020701: 54106596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 54206596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 54306596d37SWarner Losh GNOME. 54406596d37SWarner Losh 54595ba4330SJacques Vidrine20020511: 54695ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 54795ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 54895ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 54995ba4330SJacques Vidrine with the set-user-ID bit set. 55095ba4330SJacques Vidrine 551a81da3c9SDavid E. O'Brien20020510: 552f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 553f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 5544b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 555f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 556f50caf6fSDavid E. O'Brien 557f50caf6fSDavid E. O'Brien20020510: 558a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 559a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 560a81da3c9SDavid E. O'Brien and then do a cvs update. 561a81da3c9SDavid E. O'Brien 562528a0ef5SJacques Vidrine20020421: 563528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 564528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 565528a0ef5SJacques Vidrine 56685aa5a2eSGregory Neil Shapiro20020404: 56785aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 56885aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 56985aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 57085aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 57185aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 57285aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 57385aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 57485aa5a2eSGregory Neil Shapiro 5758f1e4358SRuslan Ermilov20020403: 5768f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 5778f1e4358SRuslan Ermilov 5782292c02eSWarner Losh20020315: 5792292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 5802292c02eSWarner Losh 58169f7bcf3SWarner Losh20020225: 58269f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 58369f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 58469f7bcf3SWarner Losh 5858f35c493SWarner Losh20020217: 5868f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 5878f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 5888f35c493SWarner Losh command line mail submission has changed. Be sure to run 5898f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 5908f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 5918f35c493SWarner Losh 592835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 593835284beSWarner Losh required in order for sendmail to run as a set-group-ID 594835284beSWarner Losh binary. A 'make installworld' will use the new user and group 595835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 596835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 597835284beSWarner Losh and group must be merged from src/etc/group and 598835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 599835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 600835284beSWarner Losh mergemaster before this will work if you are updating from a 601835284beSWarner Losh very old version of current. The updating recipe has changed 602835284beSWarner Losh as of this date. 603835284beSWarner Losh 604fa9401c1SWarner Losh20020112: 605fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 606fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 607fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 608fa9401c1SWarner Losh you have local modifications, you can use 609fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 610fa9401c1SWarner Losh /etc/pam.d. 611fa9401c1SWarner Losh 612fa9401c1SWarner Losh Please see the following url for more details: 613fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 61447d0d01fSWarner Losh20011229: 61547d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 61647d0d01fSWarner Losh networkfs_types, please note that it has changed 61747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 61847d0d01fSWarner Losh 619514318a8SWarner Losh20011220: 620514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 621514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 622514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 623514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 624514318a8SWarner Losh version have now been merged back into the base system's 625514318a8SWarner Losh version now. The only user-visible change resulting from this 626514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 627514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 628514318a8SWarner Losh as well. (There has never been rc file support for 629514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 630514318a8SWarner Losh reverted by the time the changes are MFCed.) 631514318a8SWarner Losh 632514318a8SWarner Losh20011215: 633514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 634514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 635514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 636514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 637514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 638514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 639514318a8SWarner Losh will need to be customized then for `odd' densities using 640514318a8SWarner Losh fdcontrol(8). 641514318a8SWarner Losh 6422d22e2bfSWarner Losh20011209: 6432d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 6442d22e2bfSWarner Losh and truss(1) now works again. 6452d22e2bfSWarner Losh 6469e0428e2SWarner Losh20011207: 6479e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 6489e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 6499e0428e2SWarner Losh see 6509e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 6519e0428e2SWarner Losh for details. 6529e0428e2SWarner Losh 6539bab8c59SWarner Losh20011204: 6549bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 6559bab8c59SWarner Losh kernel and burncd to be in sync. 6569bab8c59SWarner Losh 657e57d8b01SWarner Losh20011203: 658e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 659e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 660e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 661e57d8b01SWarner Losh not there already. 662e57d8b01SWarner Losh 663e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 664e57d8b01SWarner Losh until the issue has been resolved. 665e57d8b01SWarner Losh 666b001d36fSJacques Vidrine20011202: 667b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 668b001d36fSJacques Vidrine patched. 669b001d36fSJacques Vidrine 6704b676ec1SWarner Losh20011126: 6714b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 6725ebbf43eSWarner Losh after this date. You need to do this only once. 6734b676ec1SWarner Losh 674d961e462SWarner Losh20011103: 675d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 676d961e462SWarner Losh edges may be left, but for the most part things should be 6774b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 678d961e462SWarner Losh 679d961e462SWarner Losh20011030: 680d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 681d961e462SWarner Losh choppy waves in the upgrade process. 682d961e462SWarner Losh 6831fe003b6SWarner Losh20011030: 684a4b6fda0SWarner Losh The asr driver problem has been resolved. 6851fe003b6SWarner Losh 6861fe003b6SWarner Losh20011027: 6871fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 6881fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 6891fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 6901fe003b6SWarner Losh try to use from this date forward. 6911fe003b6SWarner Losh 6921fe003b6SWarner Losh20011025: 6931fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 6941fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 6951fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 6961fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 6971fe003b6SWarner Losh TARGET_ARCH=i386. 6981fe003b6SWarner Losh 699d05f9643SWarner Losh20011001: 700d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 701d05f9643SWarner Losh You must recompile both the kernel and userland applications 702d05f9643SWarner Losh at the same time. 703d05f9643SWarner Losh 70458970f85SWarner Losh20010929: 70558970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 70658970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 70758970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 70858970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 7099d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 71058970f85SWarner Losh 71158970f85SWarner Losh20010927: 71258970f85SWarner Losh Some weird problems result from using ACPI on some machines. 71358970f85SWarner Losh To disable ACPI you can add 71466ff0e67SMax Khon hint.acpi.0.disabled="1" 71558970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 71658970f85SWarner Losh loader "ok" prompt). 71758970f85SWarner Losh 71858970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 71958970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 72058970f85SWarner Losh file and not list acpi in that list. 721378f4486SAlfred Perlstein 7225119d237SWarner Losh20010924: 7235119d237SWarner Losh The buildworld has been fixed. You may need to install 7245119d237SWarner Losh the 4.x compatibility libraries for some old binaries 7258b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 7268b039fffSWarner Losh get them installed on every installworld, or execute the 7278b039fffSWarner Losh following to get them installed only once: 7288b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 72958970f85SWarner Losh make all install 7308b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 7315119d237SWarner Losh 7323c293725SWarner Losh20010919: 7333c293725SWarner Losh There's a bug in the world build process. The cross-tools 7343c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 7353c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 736772730c7SWarner Losh workaround is to add 7373c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 7383c293725SWarner Losh before building world when upgrading from 4.x to current. This 7393c293725SWarner Losh can be removed afterwards. 7403c293725SWarner Losh 7413c293725SWarner Losh A proper fix to the buildworld target is needed. 7423c293725SWarner Losh 7433c293725SWarner Losh20010918: 7443c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 7453c293725SWarner Losh NFS may be unstable after this date. 7463c293725SWarner Losh 7473c293725SWarner Losh20010912: 7483c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 7493c293725SWarner Losh the kernel. While a few problems were introduced in the 7503c293725SWarner Losh initial commit, most of the major ones have been found and 7513c293725SWarner Losh corrected. 7523c293725SWarner Losh 7533c293725SWarner Losh20010901: 7543c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 7553c293725SWarner Losh arounds described in the 20010604 entry are now no longer 7563c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 7573c293725SWarner Losh have been rectified around this date. 7583c293725SWarner Losh 75998b17b95SWarner Losh20010823: 76098b17b95SWarner Losh named now runs as user bind and group bind rather than as 76198b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 76298b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 76398b17b95SWarner Losh and that group bind is available in /etc/group. Also make 76498b17b95SWarner Losh sure that user or group bind has read (and not write) 76598b17b95SWarner Losh permission for your name server configuration and that it 76698b17b95SWarner Losh has read and write permission for your slave zone files and 76798b17b95SWarner Losh directory. 76898b17b95SWarner Losh 76998b17b95SWarner Losh If you wish to continue to run named as root (a less secure 77098b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 77198b17b95SWarner Losh 77298b17b95SWarner Losh named_flags= 77398b17b95SWarner Losh 7747b9786edSMark Murray20010709: 7757b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 7767b9786edSMark Murray the ability of the shared library major number to handle. 7777b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 7787b9786edSMark Murray solution is to rebuild those ports. 7797b9786edSMark Murray 7801d28950eSWarner Losh20010628: 7811d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 7821d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 7831d28950eSWarner Losh 784e72fd46aSWarner Losh20010625: 78598b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 78698b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 78798b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 78898b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 78998b17b95SWarner Losh IRQ configuration needs more safety belts. 79016de1a07SWarner Losh 7910d415dffSWarner Losh20010617: 792e72fd46aSWarner Losh Softupdates problems have been corrected. 7930d415dffSWarner Losh 7940d415dffSWarner Losh20010614: 7950d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 7960d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 7970d415dffSWarner Losh kernel building methods. 7980d415dffSWarner Losh 7998b9959adSWarner Losh20010613: 8008b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 8018b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 802e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 803e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 8048b9959adSWarner Losh 805e72fd46aSWarner Losh20010613: 8068b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 807e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 808e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 8098b9959adSWarner Losh 8100d415dffSWarner Losh20010612: 8110d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 8120d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 8130d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 8140d415dffSWarner Losh work around this issue, please use only one or the other mechanism 8150d415dffSWarner Losh until this bug is fixed. 8160d415dffSWarner Losh 817e72fd46aSWarner Losh Please note that a feature of config is that if you have config 818e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 819ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 820e72fd46aSWarner Losh 8210d415dffSWarner Losh20010610: 8220d415dffSWarner Losh Locale names have changed to match other systems better. 8230d415dffSWarner Losh 8246ccdb5e4SWarner Losh20010604: 8256ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 8266ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 8276ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 8283590182eSWarner Losh Interrupt storms look a lot like a hang. 8293590182eSWarner Losh 8303590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 8313590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 8323590182eSWarner Losh it is). 8333590182eSWarner Losh 8343590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 8353590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 8363590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 8373590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 8386ccdb5e4SWarner Losh 8390bc62786SWarner Losh20010530: 8400bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 8410bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 8420bc62786SWarner Losh a limited time. If you see 8430bc62786SWarner Losh 8440bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 8450bc62786SWarner Losh 8460bc62786SWarner Losh in your makeworld, then you need to migrate towards using 8470bc62786SWarner Losh COPY=-C. 8480bc62786SWarner Losh 84968a38c6cSWarner Losh20010525: 850b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 851c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 852c4f4a728SWarner Losh definitely is in bad shape. 85368a38c6cSWarner Losh 854ed0f29caSWarner Losh20010521: 855ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 856ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 857ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 858ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 859ed0f29caSWarner Losh is 860ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 861ed0f29caSWarner Losh 86280c16af9SWarner Losh20010520: 86368a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 86480c16af9SWarner Losh 86580c16af9SWarner Losh20010519: 86680c16af9SWarner Losh pccard has had much reorganizational work done to it over 86780c16af9SWarner Losh the past few days. Everything should still work, but if 86880c16af9SWarner Losh not, please contact imp@freebsd.org. 86980c16af9SWarner Losh 870a45f2d05SWarner Losh20010517: 871a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 872a45f2d05SWarner Losh userland at the same time. 873a45f2d05SWarner Losh 874a45f2d05SWarner Losh20010517: 875a45f2d05SWarner Losh New ncurses imported. 876a45f2d05SWarner Losh 8772988afcaSWarner Losh20010512: 8782988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 8792988afcaSWarner Losh will be the only way to go starting July 1. 8802988afcaSWarner Losh 8811a33dba7SWarner Losh20010504: 8821a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 8831a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 8841a33dba7SWarner Losh 88509946a51SWarner Losh20010502: 88609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 88709946a51SWarner Losh 88809946a51SWarner Losh20010501: 88909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 89009946a51SWarner Losh 89109946a51SWarner Losh20010430: 892a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 89309946a51SWarner Losh go back in the water. 89409946a51SWarner Losh 89509946a51SWarner Losh20010429: 89609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 89709946a51SWarner Losh this date, but before the correction date. 89809946a51SWarner Losh 89991dd3b53SWarner Losh20010423: 90091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 90191dd3b53SWarner Losh 90291dd3b53SWarner Losh20010411: 90391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 90491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 90591dd3b53SWarner Losh Update only if you understand that you must not use the old 90691dd3b53SWarner Losh fsck with the new kernel ever. 90791dd3b53SWarner Losh 908933b3269SWarner Losh20010330: 909933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 910c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 911933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 912933b3269SWarner Losh 913933b3269SWarner Losh20010319: 914933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 915933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 916933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 917f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 91809946a51SWarner Losh 91909946a51SWarner Losh20010315: 92009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 921ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 92209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 923933b3269SWarner Losh 924933b3269SWarner Losh20010312: 925933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 926933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 927933b3269SWarner Losh 928933b3269SWarner Losh20010312: 929933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 930933b3269SWarner Losh instead of ad-hoc. 931933b3269SWarner Losh 932933b3269SWarner Losh20010310: 933f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 934933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 935933b3269SWarner Losh ssh might not work if you don't. 936933b3269SWarner Losh 93762353691SWarner Losh20010303: 93862353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 93962353691SWarner Losh which means that you must include the miibus in your kernel if 94062353691SWarner Losh you use the ed driver. 94162353691SWarner Losh 942d325cf65SWarner Losh20010220: 943d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 944d325cf65SWarner Losh safe to go back into the water. 945d325cf65SWarner Losh 946024daae6SWarner Losh20010211: 947024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 948024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 949024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 950024daae6SWarner Losh that before upgrading would be a good time to do a level 0 951024daae6SWarner Losh dump of your system. No, really, I mean it this time. 952024daae6SWarner Losh 953024daae6SWarner Losh To get to the new system, you'll need to use the following 954024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 955024daae6SWarner Losh don't have to move this to the updating section. 956024daae6SWarner Losh 957024daae6SWarner Losh To get around the installworld problem, do: 958024daae6SWarner Losh # cd /usr/src/usr.bin/sed 959024daae6SWarner Losh # make install 960024daae6SWarner Losh # cd /usr/src 961024daae6SWarner Losh # make installworld 962024daae6SWarner Losh If that doesn't work, then try: 963024daae6SWarner Losh # make -k installworld 964024daae6SWarner Losh # make installworld 965024daae6SWarner Losh 966024daae6SWarner Losh20010207: 967024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 968024daae6SWarner Losh do not include devfs in your kernel as problems result. 969024daae6SWarner Losh 970024daae6SWarner Losh20010205: 9717595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 972024daae6SWarner Losh Remove them from your config. 973024daae6SWarner Losh 9741e159248SWarner Losh20010122: 9751e159248SWarner Losh ****************************** WARNING ****************************** 9761e159248SWarner Losh buildkernel has been changed slightly 9771e159248SWarner Losh ****************************** WARNING ****************************** 9781e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 9791e159248SWarner Losh should update your scripts and make.conf accordingly. 9801e159248SWarner Losh 9811e159248SWarner Losh20010119: 9821e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 9831e159248SWarner Losh This requires a new config to build correctly. 9841e159248SWarner Losh 985aac7dfeaSWarner Losh20010116: 986ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 987aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 988aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 989aac7dfeaSWarner Losh 990aac7dfeaSWarner Losh20010110: 991aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 992aac7dfeaSWarner Losh 993aac7dfeaSWarner Losh20010102: 994aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 995aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 996aac7dfeaSWarner Losh 99763c90c9eSWarner Losh20010101: 99863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 99963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 10005fd2a895SWarner Losh dump while building termcap. You can work around this problem 100163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 100263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 100363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 100463c90c9eSWarner Losh might have been ignored by the -k option. 100563c90c9eSWarner Losh 10065fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 10075fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 10085fd2a895SWarner Losh of this working. 10095fd2a895SWarner Losh 1010aac7dfeaSWarner Losh20001228: 1011aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1012ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1013aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1014aac7dfeaSWarner Losh 1015de2bcc63SWarner Losh20001218: 1016de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1017de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1018de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1019de2bcc63SWarner Losh cards will not be recognized without it. 1020de2bcc63SWarner Losh 1021960773f7SWarner Losh20001205: 1022960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1023960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1024960773f7SWarner Losh adding the following in pam.conf: 1025960773f7SWarner Losh 1026960773f7SWarner Losh sshd auth sufficient pam_skey.so 1027960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1028960773f7SWarner Losh sshd session required pam_permit.so 1029960773f7SWarner Losh 10300acc635eSWarner Losh20001031: 10310acc635eSWarner Losh cvs updated to 1.11. 10320acc635eSWarner Losh 10330acc635eSWarner Losh20001020: 10340acc635eSWarner Losh The random device needs more entropy, so you need to make sure 10350acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 10360acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 10370acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 10380acc635eSWarner Losh workaround. 10390acc635eSWarner Losh 10400acc635eSWarner Losh20001010: 10410acc635eSWarner Losh ****************************** WARNING ****************************** 10420acc635eSWarner Losh Sendmail has been updated. 10430acc635eSWarner Losh ****************************** WARNING ****************************** 10440acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 10450acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 10460acc635eSWarner Losh is set. 10470acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 10480acc635eSWarner Losh commands. 10490acc635eSWarner Losh o Now using sendmail's version of vacation(1). 10500acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 10510acc635eSWarner Losh in /usr/share/sendmail/cf. 10520acc635eSWarner Losh o sendmail.cw changed to local-host-names 10530acc635eSWarner Losh 10540acc635eSWarner Losh More details can be found at 10550acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 10560acc635eSWarner Losh 10576e98a146SWarner Losh20001009: 10586e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 10596e98a146SWarner Losh your entire ports tree, or you will have problems. 10606e98a146SWarner Losh 10616e98a146SWarner Losh20001006: 1062685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 10636e98a146SWarner Losh the installed miniperl. It is recommended that you delete 10646e98a146SWarner Losh /usr/bin/miniperl. 10656e98a146SWarner Losh 1066073113a4SWarner Losh20001005: 1067073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1068685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1069073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1070073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1071073113a4SWarner Losh tree for anything to work. 1072073113a4SWarner Losh 10730acc635eSWarner Losh20000928: 10740acc635eSWarner Losh There was a change in the passwd format. Need more information. 10750acc635eSWarner Losh 1076be3885b3SWarner Losh20000916: 1077be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1078be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1079be3885b3SWarner Losh same time as your kernel. 1080be3885b3SWarner Losh 108176ec9675SWarner Losh20000914: 108276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 108376ec9675SWarner Losh include the device will cause suspended laptops losing time 108476ec9675SWarner Losh when they resume. Include 108576ec9675SWarner Losh device pmtimer 108676ec9675SWarner Losh in your config file and 108701b9a434SWarner Losh hint.pmtimer.0.at="isa" 108876ec9675SWarner Losh to your /boot/device.hints file. 108976ec9675SWarner Losh 1090f4865386SMark Murray20000911: 1091f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1092f4865386SMark Murray rather than an option. The supplied kernel config files have 1093f4865386SMark Murray been updated. You will need to do something similar in your 1094f4865386SMark Murray own kernel config file. 1095f4865386SMark Murray Remove: 1096f4865386SMark Murray options RANDOMDEV 1097f4865386SMark Murray Add: 1098f4865386SMark Murray device random 1099f4865386SMark Murray If you prefer to load the loadable module, you need to do 1100f4865386SMark Murray nothing. 1101f4865386SMark Murray 1102d594498fSWarner Losh20000909: 1103d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1104d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1105d594498fSWarner Losh reflect this if you load this module at boot time. 1106d594498fSWarner Losh The line should read: 1107d594498fSWarner Losh random_load="YES" 1108d594498fSWarner Losh 11090deb7ddcSWarner Losh20000907: 11100deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 111116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 111216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 111316eb772dSWarner Losh sure you don't have model loading problems which might at 111416eb772dSWarner Losh first blush appear related to SMP. 111552bf24e7SWarner Losh 11165a01880bSWarner Losh20000906: 11175a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 11185a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 11195a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 11205a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 11215a01880bSWarner Losh don't have one, and you have host.conf. 11225a01880bSWarner Losh 11232b41163cSWarner Losh20000905: 112438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 112538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 112638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 112738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 112838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 112938d6ecd2SWarner Losh 113038d6ecd2SWarner Losh20000905: 11318aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 11328aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 11338aab4bc7SWarner Losh is /boot/kernel. 11348aab4bc7SWarner Losh 11358aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 113638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 113738d6ecd2SWarner Losh installkernel/installworld dance. 11382b41163cSWarner Losh 1139d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1140d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1141d594498fSWarner Losh modules in that directory instead of finding them in the correct 1142d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1143d594498fSWarner Losh is that the linux module crashes your machine after the update. 1144d594498fSWarner Losh 1145d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1146d594498fSWarner Losh mv /modules.old /boot/kernel.old 1147d594498fSWarner Losh chflags noschg /kernel.old 1148d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1149d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1150d594498fSWarner Losh fi 1151d594498fSWarner Losh 1152c22a309cSWarner Losh20000904: 1153c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1154c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1155c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1156c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1157c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1158c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1159c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1160c22a309cSWarner Losh is not likely to be generated. 1161c22a309cSWarner Losh 1162fdb9f54dSWarner Losh20000825: 1163fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 11649c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 11659c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 11669c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 11679c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 11689c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 11699c1a7444SWarner Losh messages will appear after the boot loader tries to start the 11709c1a7444SWarner Losh kernel. 11719c1a7444SWarner Losh 11729c1a7444SWarner Losh20000821: 11739c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 11749c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 11759c1a7444SWarner Losh /boot/loader.conf. 1176fdb9f54dSWarner Losh 11778f250aa7SWarner Losh20000812: 11785da0d091SWarner Losh suidperl is now always built and installed on the system, but 11795da0d091SWarner Losh with permissions of 511. If you have applications that use 11805da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 11815da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 11825da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 11835da0d091SWarner Losh will fix this until the next build. 11845da0d091SWarner Losh 11855da0d091SWarner Losh20000812: 11868f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 11878f250aa7SWarner Losh visible changes that may immediately affect your configuration 11888f250aa7SWarner Losh include: 11898f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 11908f250aa7SWarner Losh - newaliases limited to root and trusted users 11918f250aa7SWarner Losh - MSA port (587) turned on by default 11928f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 11938f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 11948f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 11958f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 11968f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 11978f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 11988f250aa7SWarner Losh 119971c38472SWarner Losh20000810: 120071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 120171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 120271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 120371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 120471c38472SWarner Losh specific use for it. 120571c38472SWarner Losh 120671c38472SWarner Losh20000729: 120771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 120871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 120971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 121071c38472SWarner Losh afterwards (unless the variables already are set, of course): 121171c38472SWarner Losh # Enable network daemons for user convenience. 121271c38472SWarner Losh inetd_enable="YES" 121371c38472SWarner Losh portmap_enable="YES" 121471c38472SWarner Losh sendmail_enable="YES" 121571c38472SWarner Losh 121671c38472SWarner Losh20000728: 121771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 121871c38472SWarner Losh will need to change that to nullfs_load="YES". 121971c38472SWarner Losh 12201dece4a9SWarner Losh20000728: 12211dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 12221dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 12231dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 12241dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 12251dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 12261dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 12271dece4a9SWarner Losh to /MYKERNEL. 12281dece4a9SWarner Losh 1229409e887cSWarner Losh20000711: 1230409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1231409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1232409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1233409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1234409e887cSWarner Losh for details on potential problems that you might have and how 1235409e887cSWarner Losh to get around them. 1236409e887cSWarner Losh 1237409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1238409e887cSWarner Losh clauses above, you needn't worry. 1239409e887cSWarner Losh 1240409e887cSWarner Losh20000711: 1241409e887cSWarner Losh /etc/security has been updated to print the inode number of 1242409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1243409e887cSWarner Losh in the number of changed programs the first time when you run 1244409e887cSWarner Losh mergemaster to get a new /etc/security. 1245409e887cSWarner Losh 1246673d13f2SWarner Losh20000710: 1247673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1248673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1249673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1250673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1251673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1252673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1253673d13f2SWarner Losh errors. (see below, 20000624). 1254673d13f2SWarner Losh 1255bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 12561dece4a9SWarner Losh 1257673d13f2SWarner Losh20000709: 1258c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1259c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1260c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1261673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1262673d13f2SWarner Losh 1263e98e26cdSWarner Losh20000706: 1264e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1265e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1266e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1267f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1268e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 12692c021c6cSMark Ovens interim if needed. 1270e98e26cdSWarner Losh 1271e98e26cdSWarner Losh20000705: 1272e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1273e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1274e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1275e98e26cdSWarner Losh details. 1276e98e26cdSWarner Losh 1277c373950eSWarner Losh20000704: 12782f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 12792f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 12802f961bc8SWarner Losh 12812f961bc8SWarner Losh20000704: 1282c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1283c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1284c373950eSWarner Losh rc.d scripts that haven't been updated. 1285c373950eSWarner Losh 128627dc3a2bSWarner Losh20000630: 128727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 128827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 128927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 129027dc3a2bSWarner Losh 1291b8c215acSWarner Losh20000625: 1292b8c215acSWarner Losh From approximately this date forward, one must have the crypto 129327dc3a2bSWarner Losh system installed in order to build the system and kernel. 129427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 129527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 129627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 129727dc3a2bSWarner Losh were required. You should check with the latest collections 129827dc3a2bSWarner Losh to make sure that these haven't changed. 1299b8c215acSWarner Losh 13007b990719SWarner Losh20000624: 13017b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 13027b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 13037b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 13041a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 13057b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 13067b990719SWarner Losh openssh and openssl should not be used to generate keys from this 13077b990719SWarner Losh date to the completion of the work. 13087b990719SWarner Losh 130927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 131027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 131127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 131227dc3a2bSWarner Losh recreate the random and urandom devices. 131327dc3a2bSWarner Losh 131481e54c50SWarner Losh20000622: 131581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 131681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 131781e54c50SWarner Losh that used to be required when updating. 131881e54c50SWarner Losh 131939943833SWarner Losh20000621: 13202c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 13212a2f33fbSDaniel Baker the config file update procedure. 13222a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1323c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 132459df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 132559df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 132639943833SWarner Losh 1327290f9ad8SWarner Losh20000620: 1328290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1329290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1330290f9ad8SWarner Losh that workaround will no longer be required. 1331290f9ad8SWarner Losh 133290fb6346SWarner Losh20000615: 133390fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 133490fb6346SWarner Losh ad driver. If you haven't done so already, you must update 133590fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 133690fb6346SWarner Losh devices. 133790fb6346SWarner Losh 1338f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1339f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1340f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1341f75f65bbSWarner Losh may work). 1342f75f65bbSWarner Losh 1343ba26da8eSWarner Losh20000612: 1344ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1345290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1346c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1347290f9ad8SWarner Losh to your config file to compile them in statically. The format 1348f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1349f54a3542SWarner Losh NEWCARD for examples of the new format. 1350290f9ad8SWarner Losh 13519698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 13529698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 13539698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 13549698f2c0SWarner Losh in it. 1355bbcc5149SWarner Losh 1356d65850ebSWarner Losh20000522: 1357ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1358d65850ebSWarner Losh building a kernel after this point is advised that they need 1359d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1360d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1361d65850ebSWarner Losh 1362d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1363d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1364d9583a00SWarner Losh is recommended that you don't set this option until the problem 1365d9583a00SWarner Losh is resolved. 1366d9583a00SWarner Losh 13678039cedeSWarner Losh20000513: 13688039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 13698039cedeSWarner Losh 1370d65850ebSWarner Losh20000510: 13718039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 13728039cedeSWarner Losh This will require some care in updating alphas. A new libstand 13738039cedeSWarner Losh is requires for the boot blocks to build properly. 13748039cedeSWarner Losh 13758039cedeSWarner Losh20000503: 13768039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 13778039cedeSWarner Losh is now available. 13788039cedeSWarner Losh 1379d65850ebSWarner Losh20000502: 1380d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1381d65850ebSWarner Losh connected to the kernel building instead. 1382d65850ebSWarner Losh 1383be149406SNik Clayton20000427: 13848039cedeSWarner Losh You may need to build gperf 13858039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 13868039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 13878039cedeSWarner Losh an option only in -current. 13888039cedeSWarner Losh 13892b8dd5f4SWarner Losh20000417: 13902b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1391f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 13922b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 13932b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 13942c021c6cSMark Ovens before you reboot, you'll need to issue: 13952b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 13962b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 13972b8dd5f4SWarner Losh 13988d9f1945SWarner Losh20000320: 13992b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 14002b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 14012b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1402ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 14032b8dd5f4SWarner Losh to the start of /etc/rc.conf. 14048d9f1945SWarner Losh 1405f8ab1dd6SWarner Losh20000319: 1406f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1407f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1408f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1409f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1410f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1411f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1412f8ab1dd6SWarner Losh 141319cada77SWarner Losh20000318: 1414f699bbbbSMark Ovens We've entered the traditional post release dumping party. 141519cada77SWarner Losh Large kernel changes are being committed and are in the 141619cada77SWarner Losh works. It is important to keep the systems' klds and kernel 141719cada77SWarner Losh in sync as kernel interfaces and structures are changing. 141819cada77SWarner Losh Before reporting kernel panics, make sure that all modules 141919cada77SWarner Losh that you are loading are up to date. 1420ba228352SWarner Losh 142119cada77SWarner Losh20000315: 14226d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 14236d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 14246d23c382SWarner Losh will do the trick. This isn't critical until you remove your 14256d23c382SWarner Losh wd device entries in /dev, at which point your system will not 14266d23c382SWarner Losh boot. 14276d23c382SWarner Losh 14286d23c382SWarner Losh20000315: 142919cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 143019cada77SWarner Losh to upgrade to 4.0 from 3.x. 143157199806SWarner Losh 1432dc0dbf5cSWarner LoshCOMMON ITEMS: 1433dc0dbf5cSWarner Losh 1434a24eff53SWarner Losh General Notes 1435a24eff53SWarner Losh ------------- 1436a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1437a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1438a24eff53SWarner Losh installworld. This is especially true when upgrading between 1439a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1440a24eff53SWarner Losh or several minor releases, or when several months have passed 1441a24eff53SWarner Losh on the -current branch). 1442a24eff53SWarner Losh 14435780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 14445780f3baSWarner Losh poisoning. This can happen because the make utility reads its 14455780f3baSWarner Losh environment when searching for values for global variables. 14465780f3baSWarner Losh To run your build attempts in an "environmental clean room", 14475780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 14485780f3baSWarner Losh page for more details. 14495780f3baSWarner Losh 1450dc0dbf5cSWarner Losh To build a kernel 1451dc0dbf5cSWarner Losh ----------------- 1452ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1453f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1454ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1455282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1456282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1457dc0dbf5cSWarner Losh 1458ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1459ba01eb20SWarner Losh -------------------------------------------------------------- 14600fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 14610fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 14620fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 14630fbd2da9SKen Smith 14640fbd2da9SKen Smith cd src/sys/${arch}/conf 146547d0d01fSWarner Losh config KERNEL_NAME_HERE 14660fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1467ba01eb20SWarner Losh make depend 1468ba01eb20SWarner Losh make 1469ba01eb20SWarner Losh make install 1470ba01eb20SWarner Losh 1471ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1472ba01eb20SWarner Losh 1473ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1474ba01eb20SWarner Losh ----------------------------------------------------------- 147563cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 147663cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 147763cb445eSWarner Losh 1478f643de42SWarner Losh <make sure you have good level 0 dumps> 147963cb445eSWarner Losh <maybe fix /etc/fstab> [7] 148063cb445eSWarner Losh make buildworld 148163cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 148263cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 148363cb445eSWarner Losh [1] 148463cb445eSWarner Losh <reboot in single user> [3] 14858633bbeaSBrooks Davis /etc/rc.d/preseedrandom [10] 148663cb445eSWarner Losh mergemaster -p [5] 148763cb445eSWarner Losh make installworld 148863cb445eSWarner Losh mergemaster [4] 148963cb445eSWarner Losh <reboot> 149063cb445eSWarner Losh 1491759f0aefSWarner Losh 1492f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1493f27b1fceSJoseph Koshy -------------------------------------------------- 1494f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1495f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1496f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1497f27b1fceSJoseph Koshy # size. 1498f27b1fceSJoseph Koshy 1499f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1500f27b1fceSJoseph Koshy <boot into -stable> 1501f27b1fceSJoseph Koshy make buildworld 1502f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1503f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1504f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1505f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1506f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1507f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1508f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1509f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1510f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1511f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1512f27b1fceSJoseph Koshy <reboot into current> 1513f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1514f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1515f27b1fceSJoseph Koshy <reboot> 1516f27b1fceSJoseph Koshy 1517f27b1fceSJoseph Koshy 1518f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1519f27b1fceSJoseph Koshy ---------------------------------------------- 15205c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 15215c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 15225c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 15235c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1524ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1525f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1526f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1527f643de42SWarner Losh # space on /. 1528f643de42SWarner Losh 1529f643de42SWarner Losh <make sure you have good level 0 dumps> 1530fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 153121c075eaSWarner Losh make buildworld [9] 1532c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1533802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1534be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1535802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1536fc8c157fSWarner Losh [1] 1537fc8c157fSWarner Losh <reboot in single user> [3] 1538802fc49dSBrian Feldman /usr/src/etc/rc.d/preseedrandom [10] 1539835284beSWarner Losh mergemaster -p [5] 1540f8a4c901SWarner Losh rm -rf /usr/include/g++ 1541ba26da8eSWarner Losh make installworld 1542802fc49dSBrian Feldman mergemaster -i [4] 1543ba26da8eSWarner Losh <reboot> 1544ba26da8eSWarner Losh 1545fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1546fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1547fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1548fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1549fdb9f54dSWarner Losh the UPDATING entries. 1550ba26da8eSWarner Losh 15511dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 15521dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 15531dece4a9SWarner Losh your sources that you have read and understood all the recent 15541dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 15551dece4a9SWarner Losh much fewer pitfalls. 15561dece4a9SWarner Losh 1557134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1558134d2e86SWarner Losh should disable them at this point so they don't crash your 1559134d2e86SWarner Losh system on reboot. 1560134d2e86SWarner Losh 15619c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 15629c1a7444SWarner Losh your own device.hints to reflect your unique hardware 15639c1a7444SWarner Losh configuration. 15649c1a7444SWarner Losh 1565ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1566ee6e1fc3SWarner Losh fsck -p 1567ee6e1fc3SWarner Losh mount -u / 1568ee6e1fc3SWarner Losh mount -a 1569ee6e1fc3SWarner Losh cd /usr/src 157047d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1571f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1572f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1573b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1574b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1575b705ae10SWarner Losh be ignored while you proceed to the next step. 1576ee6e1fc3SWarner Losh 1577a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1578a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1579a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1580a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1581a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1582a6cd4f9dSWarner Losh for potential gotchas. 1583a6cd4f9dSWarner Losh 1584835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1585835284beSWarner Losh you may need to do this if you get unknown user in the following 1586835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1587835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1588835284beSWarner Losh install) after the buildworld before this step if you last updated 1589835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1590835284beSWarner Losh 1591bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1592bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1593bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1594bd79cf40SWarner Losh ok unload 1595bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1596bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1597bd79cf40SWarner Losh described here. 1598fc8c157fSWarner Losh 1599fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1600fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1601fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1602fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1603fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1604fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1605fc8c157fSWarner Losh 1606c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1607c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1608c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1609c74fe6afSWarner Losh that is hard to boot to recover. 1610c74fe6afSWarner Losh 161121c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1612802fc49dSBrian Feldman cvs prune empty directories. Also, if CPUTYPE is defined in your 1613802fc49dSBrian Feldman /etc/make.conf, make sure to use the "?=" instead of the "=" assignment 1614802fc49dSBrian Feldman operator, so that buildworld can override the CPUTYPE if it needs to. 1615802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1616802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 1617802fc49dSBrian Feldman compatibility libraries are build which should allow you to continue 1618802fc49dSBrian Feldman using your existing software for a while. 16198633bbeaSBrooks Davis 16208633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 16218633bbeaSBrooks Davis initialized by feeding data into it. /etc/rc.d/preseedrandom 16228633bbeaSBrooks Davis takes care of this. 1623dc0dbf5cSWarner LoshFORMAT: 1624dc0dbf5cSWarner Losh 1625f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 16261fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1627f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1628f8ab1dd6SWarner Loshprevious releases if your system is older than this. 16291fc1a0dcSWarner Losh 1630e72fd46aSWarner LoshCopyright information: 1631e72fd46aSWarner Losh 16329698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1633e72fd46aSWarner Losh 1634772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1635772730c7SWarner Loshmodification, in full or in part, in any form or format of this 16369698f2c0SWarner Loshdocument are permitted without further permission from the author. 1637e72fd46aSWarner Losh 1638e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1639e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1640e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1641e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1642e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1643e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1644e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1645e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1646e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1647e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1648e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1649e72fd46aSWarner Losh 1650e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1651e72fd46aSWarner Loshauthor a beer. 1652e72fd46aSWarner Losh 165322306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1654772730c7SWarner Loshthis document. 1655772730c7SWarner Losh 165697d92980SPeter Wemm$FreeBSD$ 1657