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 20fd63c5b3SDag-Erling Smørgrav20040226: 219d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 22fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 23fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 24fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 25fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 26fd63c5b3SDag-Erling Smørgrav 27714ae42aSBruce M Simpson20040225: 28714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 29714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 30714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 31714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 32714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 33714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 34714ae42aSBruce M Simpson 35fbd2e692SAndre Oppermann20040224: 36fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 37fbd2e692SAndre Oppermann and related userland network utilities neccessary. 38fbd2e692SAndre Oppermann 39158b90daSWarner Losh20040222: 40158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 41158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 42158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 43158b90daSWarner Losh Drivers outside the tree will need to be updated. 44158b90daSWarner Losh 45b7b1e150SMike Makonnen20040207: 46b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 47b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 48b7b1e150SMike Makonnen 49aca89ee6SDaniel Eischen20040130: 50aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 51aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 52aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 53aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 54aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 55aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 56aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 57aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 58aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 59aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 60aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 61aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 62aca89ee6SDaniel Eischen do not work with libpthread. 63aca89ee6SDaniel Eischen 6468b7b3a9SAlex Dupre20040125: 6568b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 6668b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 6768b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 6868b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 6968b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 7068b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 7168b7b3a9SAlex Dupre 72ff46e0deSWarner Losh20040125: 73ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 74ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 75ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 76ff46e0deSWarner Losh 77ce41f4bfSRobert Watson20031213: 78ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 79ce41f4bfSRobert Watson if the login process is unable to successfully set the 80ce41f4bfSRobert Watson process credentials to include all groups defined for the 81ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 82ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 83ce41f4bfSRobert Watson defined, or they will be unable to log in. 84ce41f4bfSRobert Watson 85c124fa05SJohn Baldwin20031203: 86c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 87c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 88c124fa05SJohn Baldwin 898ad1f5e4SHartmut Brandt20031112: 9030093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 9130093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 9297209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 9397209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 9497209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 9597209ca3SRobert Watson not know about the new system calls that support the new statfs 963f631d52SMarcel Moolenaar structure. 973f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 983f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 993f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 1003f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 1013f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 1023f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 1033f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 1043f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 1053f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 1063f631d52SMarcel Moolenaar these changes are installed. 10730093b05SWarner Losh 10830093b05SWarner Losh ****************************DANGER******************************* 10930093b05SWarner Losh 11030093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 11130093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 11230093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 11330093b05SWarner Losh kernel. 11464a18d6fSKirk McKusick 11564a18d6fSKirk McKusick20031112: 1168ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 1178ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 1188ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 1198ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 1208ad1f5e4SHartmut Brandt sync before rebooting. 1218ad1f5e4SHartmut Brandt 122c53a5d8fSJohn Baldwin20031111: 123c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 124c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 125c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 126c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 127c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 128c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 129c53a5d8fSJohn Baldwin 1308bf455a5SJohn Baldwin20031103: 1318bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 1328bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 1332a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 1348bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 1358bf455a5SJohn Baldwin 1369bf40edeSBrooks Davis20031031: 1379bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 1389bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 1399bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 1409bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 1419bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 1429bf40edeSBrooks Davis reflect this change. 1439bf40edeSBrooks Davis 14447a42c7aSPoul-Henning Kamp20030928: 14547a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 14647a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 14747a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 14847a42c7aSPoul-Henning Kamp 14907105342SMax Khon20030926: 15007105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 15107105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 15207105342SMax Khon 15317dcd026SSam Leffler20030925: 15417dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 15517dcd026SSam Leffler also be explicitly configured. Previously this dependency was 15617dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 15717dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 15817dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 15917dcd026SSam Leffler 160fedf1d01SBruce M Simpson20030923: 161fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 162fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 163fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 164fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 165fedf1d01SBruce M Simpson 166db38f9cbSJacques Vidrine20030915: 167db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 168db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 169db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 170db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 171db38f9cbSJacques Vidrine 172c09d2c2bSMike Makonnen20030829: 173c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 174c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 175c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 176c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 177c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 178c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 179c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 180c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 181c09d2c2bSMike Makonnen may or may not exist on your system. 182c09d2c2bSMike Makonnen 18317c159dcSSøren Schmidt20030824: 18417c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 18517c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 186f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 187f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 18817c159dcSSøren Schmidt 189c1f61aa9SDavid E. O'Brien20030819: 190c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 191c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 192c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 193c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 19469f7bcf3SWarner Losh 19538c962e7SNate Lawson20030728: 19638c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 19738c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 19838c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 19938c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 20038c962e7SNate Lawson so the quirk can be re-enabled. 20138c962e7SNate Lawson 20274111097SWarner Losh20030724: 20374111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 20474111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 20574111097SWarner Losh 206178cf4e9SWarner Losh20030722: 207178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 208178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 209178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 210178cf4e9SWarner Losh FPU hardware. 211178cf4e9SWarner Losh 212178cf4e9SWarner Losh20030714: 213178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 214178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 215178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 216178cf4e9SWarner Losh People should report those issues to current@. 217178cf4e9SWarner Losh 218157c629aSWarner Losh20030711: 219157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 2208b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 22105538fa9SWarner Losh /usr/obj. 222157c629aSWarner Losh 22374111097SWarner Losh20030610: 22474111097SWarner Losh Remove deprecated locale names and transition period code 22574111097SWarner Losh for them, finishing switching to the new scheme. Check your 22674111097SWarner Losh LANG environment variable. 22774111097SWarner Losh 22874111097SWarner Losh20030609: 22974111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 23074111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 23174111097SWarner Losh important to remember beforehand if your source tree is on 23274111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 23374111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 23474111097SWarner Losh kernel. 23574111097SWarner Losh 23674111097SWarner Losh20030605: 2376cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 2386cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 2396cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 2406cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 2416cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 2426cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 2436cc6353fSMarcel Moolenaar 2446cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 2456cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 2466cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 2476cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 2486cc6353fSMarcel Moolenaar : 2496cc6353fSMarcel Moolenaar 2506cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 2516cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 2526cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 2536cc6353fSMarcel Moolenaar 25452b47445SMark Murray20030505: 25552b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 25652b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 25752b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 25852b47445SMark Murray 259a26df538SWarner Losh20030502: 260a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 261a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 262a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 263a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 264a26df538SWarner Losh 2654b065e2cSDoug Barton20030501: 2664b065e2cSDoug Barton The old rc system has been removed. Please report any problems 2674b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 2684b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 2694b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 2704b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 2714b065e2cSDoug Barton utilizes these old scripts has also been removed. 2724b065e2cSDoug Barton 27381cda3d9SWarner Losh20030423: 27481cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 27581cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 27681cda3d9SWarner Losh work around in devd will be removed around 20030507. You 27781cda3d9SWarner Losh have until then to upgrade your kernel before updating 27881cda3d9SWarner Losh userland. In general, you should have a userland and 27981cda3d9SWarner Losh kernel that's in sync with each other. However, given the 28081cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 28181cda3d9SWarner Losh allowances are made. 28281cda3d9SWarner Losh 28347a657d1SRuslan Ermilov20030329: 28447a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 28547a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 28647a657d1SRuslan Ermilov while upgrading the system through a buildworld. 28747a657d1SRuslan Ermilov 28847a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 28947a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 29047a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 29147a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 29247a657d1SRuslan Ermilov 29347a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 29447a657d1SRuslan Ermilov make cleandir && make obj && \ 29547a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 29647a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 29747a657d1SRuslan Ermilov 2985d2af00cSGregory Neil Shapiro20030208: 2995d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 3005d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 3015d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 3025d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 3035d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 3045d2af00cSGregory Neil Shapiro 3055d2af00cSGregory Neil Shapiro20030128: 3069db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 307ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 3089db58771SPoul-Henning Kamp be removed when convenient. 3099db58771SPoul-Henning Kamp 3108d9b3f57SJake Burkholder20030126: 3118d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 3128d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 3138d9b3f57SJake Burkholder 3141c5efda5SJeff Roberson20030125: 3151c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 3161c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 317ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 3181c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 3191c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 3201c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 3211c5efda5SJeff Roberson 3229d1d64f5SWarner Losh20030115: 3239d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 3249d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 3259d1d64f5SWarner Losh properly. 3269d1d64f5SWarner Losh 327c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 328c9fdb80aSWarner Losh configured for point to point links to bring it more in line 329c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 330c9fdb80aSWarner Losh with NetBSD. 331c9fdb80aSWarner Losh 332161dc364SAlexander Kabaev20021222: 333161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 334161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 335161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 336161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 337161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 338161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 33984cc83efSAlexander Kabaev rebuilt. 340161dc364SAlexander Kabaev 341fb4c8061SMartin Blapp20021216: 342fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 34389056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 344fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 3459d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 346fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 347fb4c8061SMartin Blapp 34817d47eb3SGiorgos Keramidas20021202: 34917d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 35017d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 35117d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 35217d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 35317d47eb3SGiorgos Keramidas 354a4459294SBill Fenner20021029: 355a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 356a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 357a4459294SBill Fenner consumers in sync. 358a4459294SBill Fenner 359fc8c157fSWarner Losh20021024: 360c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 361c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 362c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 363c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 364c57404feSRuslan Ermilov partition really is on. The old device names have gone 365c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 366c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 367c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 36869f7bcf3SWarner Losh 369fd9e8bdaSAndrew Gallatin20021023: 370fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 371fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 372fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 373fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 374fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 375fd9e8bdaSAndrew Gallatin 376fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 377fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 378fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 379fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 380fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 381fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 382fd9e8bdaSAndrew Gallatin 383f8a4c901SWarner Losh20020831: 384f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 385f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 386f8a4c901SWarner Losh programs and libraries need to be recompiled. 387f8a4c901SWarner Losh 388f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 389f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 390f8a4c901SWarner Losh 391c2248fa2SJens Schweikhardt20020827: 392c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 393c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 394c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 395c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 396c2248fa2SJens Schweikhardt 3970d533e43SRuslan Ermilov20020815: 3980d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 3990d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 4000d533e43SRuslan Ermilov again. 4010d533e43SRuslan Ermilov 40233c1de7dSRuslan Ermilov20020729: 40333c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 40433c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 40533c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 40633c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 40733c1de7dSRuslan Ermilov 4082b877facSJulian Elischer20020702: 4092b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 4102b877facSJulian Elischer There are still some minor problems with some signals but the 4112b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 4122b877facSJulian Elischer but each can successfully complete multiple buildworlds. 4132b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 4142b877facSJulian Elischer 41506596d37SWarner Losh20020701: 41606596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 41706596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 41806596d37SWarner Losh GNOME. 41906596d37SWarner Losh 42095ba4330SJacques Vidrine20020511: 42195ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 42295ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 42395ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 42495ba4330SJacques Vidrine with the set-user-ID bit set. 42595ba4330SJacques Vidrine 426a81da3c9SDavid E. O'Brien20020510: 427f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 428f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 4294b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 430f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 431f50caf6fSDavid E. O'Brien 432f50caf6fSDavid E. O'Brien20020510: 433a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 434a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 435a81da3c9SDavid E. O'Brien and then do a cvs update. 436a81da3c9SDavid E. O'Brien 437528a0ef5SJacques Vidrine20020421: 438528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 439528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 440528a0ef5SJacques Vidrine 44185aa5a2eSGregory Neil Shapiro20020404: 44285aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 44385aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 44485aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 44585aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 44685aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 44785aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 44885aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 44985aa5a2eSGregory Neil Shapiro 4508f1e4358SRuslan Ermilov20020403: 4518f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 4528f1e4358SRuslan Ermilov 4532292c02eSWarner Losh20020315: 4542292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 4552292c02eSWarner Losh 45669f7bcf3SWarner Losh20020225: 45769f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 45869f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 45969f7bcf3SWarner Losh 4608f35c493SWarner Losh20020217: 4618f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 4628f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 4638f35c493SWarner Losh command line mail submission has changed. Be sure to run 4648f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 4658f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 4668f35c493SWarner Losh 467835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 468835284beSWarner Losh required in order for sendmail to run as a set-group-ID 469835284beSWarner Losh binary. A 'make installworld' will use the new user and group 470835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 471835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 472835284beSWarner Losh and group must be merged from src/etc/group and 473835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 474835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 475835284beSWarner Losh mergemaster before this will work if you are updating from a 476835284beSWarner Losh very old version of current. The updating recipe has changed 477835284beSWarner Losh as of this date. 478835284beSWarner Losh 479fa9401c1SWarner Losh20020112: 480fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 481fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 482fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 483fa9401c1SWarner Losh you have local modifications, you can use 484fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 485fa9401c1SWarner Losh /etc/pam.d. 486fa9401c1SWarner Losh 487fa9401c1SWarner Losh Please see the following url for more details: 488fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 48947d0d01fSWarner Losh20011229: 49047d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 49147d0d01fSWarner Losh networkfs_types, please note that it has changed 49247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 49347d0d01fSWarner Losh 494514318a8SWarner Losh20011220: 495514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 496514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 497514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 498514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 499514318a8SWarner Losh version have now been merged back into the base system's 500514318a8SWarner Losh version now. The only user-visible change resulting from this 501514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 502514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 503514318a8SWarner Losh as well. (There has never been rc file support for 504514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 505514318a8SWarner Losh reverted by the time the changes are MFCed.) 506514318a8SWarner Losh 507514318a8SWarner Losh20011215: 508514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 509514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 510514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 511514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 512514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 513514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 514514318a8SWarner Losh will need to be customized then for `odd' densities using 515514318a8SWarner Losh fdcontrol(8). 516514318a8SWarner Losh 5172d22e2bfSWarner Losh20011209: 5182d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 5192d22e2bfSWarner Losh and truss(1) now works again. 5202d22e2bfSWarner Losh 5219e0428e2SWarner Losh20011207: 5229e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 5239e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 5249e0428e2SWarner Losh see 5259e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 5269e0428e2SWarner Losh for details. 5279e0428e2SWarner Losh 5289bab8c59SWarner Losh20011204: 5299bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 5309bab8c59SWarner Losh kernel and burncd to be in sync. 5319bab8c59SWarner Losh 532e57d8b01SWarner Losh20011203: 533e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 534e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 535e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 536e57d8b01SWarner Losh not there already. 537e57d8b01SWarner Losh 538e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 539e57d8b01SWarner Losh until the issue has been resolved. 540e57d8b01SWarner Losh 541b001d36fSJacques Vidrine20011202: 542b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 543b001d36fSJacques Vidrine patched. 544b001d36fSJacques Vidrine 5454b676ec1SWarner Losh20011126: 5464b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 5475ebbf43eSWarner Losh after this date. You need to do this only once. 5484b676ec1SWarner Losh 549d961e462SWarner Losh20011103: 550d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 551d961e462SWarner Losh edges may be left, but for the most part things should be 5524b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 553d961e462SWarner Losh 554d961e462SWarner Losh20011030: 555d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 556d961e462SWarner Losh choppy waves in the upgrade process. 557d961e462SWarner Losh 5581fe003b6SWarner Losh20011030: 559a4b6fda0SWarner Losh The asr driver problem has been resolved. 5601fe003b6SWarner Losh 5611fe003b6SWarner Losh20011027: 5621fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 5631fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 5641fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 5651fe003b6SWarner Losh try to use from this date forward. 5661fe003b6SWarner Losh 5671fe003b6SWarner Losh20011025: 5681fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 5691fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 5701fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 5711fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 5721fe003b6SWarner Losh TARGET_ARCH=i386. 5731fe003b6SWarner Losh 574d05f9643SWarner Losh20011001: 575d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 576d05f9643SWarner Losh You must recompile both the kernel and userland applications 577d05f9643SWarner Losh at the same time. 578d05f9643SWarner Losh 57958970f85SWarner Losh20010929: 58058970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 58158970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 58258970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 58358970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 5849d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 58558970f85SWarner Losh 58658970f85SWarner Losh20010927: 58758970f85SWarner Losh Some weird problems result from using ACPI on some machines. 58858970f85SWarner Losh To disable ACPI you can add 58966ff0e67SMax Khon hint.acpi.0.disabled="1" 59058970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 59158970f85SWarner Losh loader "ok" prompt). 59258970f85SWarner Losh 59358970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 59458970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 59558970f85SWarner Losh file and not list acpi in that list. 596378f4486SAlfred Perlstein 5975119d237SWarner Losh20010924: 5985119d237SWarner Losh The buildworld has been fixed. You may need to install 5995119d237SWarner Losh the 4.x compatibility libraries for some old binaries 6008b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 6018b039fffSWarner Losh get them installed on every installworld, or execute the 6028b039fffSWarner Losh following to get them installed only once: 6038b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 60458970f85SWarner Losh make all install 6058b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 6065119d237SWarner Losh 6073c293725SWarner Losh20010919: 6083c293725SWarner Losh There's a bug in the world build process. The cross-tools 6093c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 6103c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 611772730c7SWarner Losh workaround is to add 6123c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 6133c293725SWarner Losh before building world when upgrading from 4.x to current. This 6143c293725SWarner Losh can be removed afterwards. 6153c293725SWarner Losh 6163c293725SWarner Losh A proper fix to the buildworld target is needed. 6173c293725SWarner Losh 6183c293725SWarner Losh20010918: 6193c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 6203c293725SWarner Losh NFS may be unstable after this date. 6213c293725SWarner Losh 6223c293725SWarner Losh20010912: 6233c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 6243c293725SWarner Losh the kernel. While a few problems were introduced in the 6253c293725SWarner Losh initial commit, most of the major ones have been found and 6263c293725SWarner Losh corrected. 6273c293725SWarner Losh 6283c293725SWarner Losh20010901: 6293c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 6303c293725SWarner Losh arounds described in the 20010604 entry are now no longer 6313c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 6323c293725SWarner Losh have been rectified around this date. 6333c293725SWarner Losh 63498b17b95SWarner Losh20010823: 63598b17b95SWarner Losh named now runs as user bind and group bind rather than as 63698b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 63798b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 63898b17b95SWarner Losh and that group bind is available in /etc/group. Also make 63998b17b95SWarner Losh sure that user or group bind has read (and not write) 64098b17b95SWarner Losh permission for your name server configuration and that it 64198b17b95SWarner Losh has read and write permission for your slave zone files and 64298b17b95SWarner Losh directory. 64398b17b95SWarner Losh 64498b17b95SWarner Losh If you wish to continue to run named as root (a less secure 64598b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 64698b17b95SWarner Losh 64798b17b95SWarner Losh named_flags= 64898b17b95SWarner Losh 6497b9786edSMark Murray20010709: 6507b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 6517b9786edSMark Murray the ability of the shared library major number to handle. 6527b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 6537b9786edSMark Murray solution is to rebuild those ports. 6547b9786edSMark Murray 6551d28950eSWarner Losh20010628: 6561d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 6571d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 6581d28950eSWarner Losh 659e72fd46aSWarner Losh20010625: 66098b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 66198b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 66298b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 66398b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 66498b17b95SWarner Losh IRQ configuration needs more safety belts. 66516de1a07SWarner Losh 6660d415dffSWarner Losh20010617: 667e72fd46aSWarner Losh Softupdates problems have been corrected. 6680d415dffSWarner Losh 6690d415dffSWarner Losh20010614: 6700d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 6710d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 6720d415dffSWarner Losh kernel building methods. 6730d415dffSWarner Losh 6748b9959adSWarner Losh20010613: 6758b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 6768b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 677e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 678e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 6798b9959adSWarner Losh 680e72fd46aSWarner Losh20010613: 6818b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 682e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 683e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 6848b9959adSWarner Losh 6850d415dffSWarner Losh20010612: 6860d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 6870d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 6880d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 6890d415dffSWarner Losh work around this issue, please use only one or the other mechanism 6900d415dffSWarner Losh until this bug is fixed. 6910d415dffSWarner Losh 692e72fd46aSWarner Losh Please note that a feature of config is that if you have config 693e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 694ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 695e72fd46aSWarner Losh 6960d415dffSWarner Losh20010610: 6970d415dffSWarner Losh Locale names have changed to match other systems better. 6980d415dffSWarner Losh 6996ccdb5e4SWarner Losh20010604: 7006ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 7016ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 7026ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 7033590182eSWarner Losh Interrupt storms look a lot like a hang. 7043590182eSWarner Losh 7053590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 7063590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 7073590182eSWarner Losh it is). 7083590182eSWarner Losh 7093590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 7103590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 7113590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 7123590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 7136ccdb5e4SWarner Losh 7140bc62786SWarner Losh20010530: 7150bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 7160bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 7170bc62786SWarner Losh a limited time. If you see 7180bc62786SWarner Losh 7190bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 7200bc62786SWarner Losh 7210bc62786SWarner Losh in your makeworld, then you need to migrate towards using 7220bc62786SWarner Losh COPY=-C. 7230bc62786SWarner Losh 72468a38c6cSWarner Losh20010525: 725b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 726c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 727c4f4a728SWarner Losh definitely is in bad shape. 72868a38c6cSWarner Losh 729ed0f29caSWarner Losh20010521: 730ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 731ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 732ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 733ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 734ed0f29caSWarner Losh is 735ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 736ed0f29caSWarner Losh 73780c16af9SWarner Losh20010520: 73868a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 73980c16af9SWarner Losh 74080c16af9SWarner Losh20010519: 74180c16af9SWarner Losh pccard has had much reorganizational work done to it over 74280c16af9SWarner Losh the past few days. Everything should still work, but if 74380c16af9SWarner Losh not, please contact imp@freebsd.org. 74480c16af9SWarner Losh 745a45f2d05SWarner Losh20010517: 746a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 747a45f2d05SWarner Losh userland at the same time. 748a45f2d05SWarner Losh 749a45f2d05SWarner Losh20010517: 750a45f2d05SWarner Losh New ncurses imported. 751a45f2d05SWarner Losh 7522988afcaSWarner Losh20010512: 7532988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 7542988afcaSWarner Losh will be the only way to go starting July 1. 7552988afcaSWarner Losh 7561a33dba7SWarner Losh20010504: 7571a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 7581a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 7591a33dba7SWarner Losh 76009946a51SWarner Losh20010502: 76109946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 76209946a51SWarner Losh 76309946a51SWarner Losh20010501: 76409946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 76509946a51SWarner Losh 76609946a51SWarner Losh20010430: 767a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 76809946a51SWarner Losh go back in the water. 76909946a51SWarner Losh 77009946a51SWarner Losh20010429: 77109946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 77209946a51SWarner Losh this date, but before the correction date. 77309946a51SWarner Losh 77491dd3b53SWarner Losh20010423: 77591dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 77691dd3b53SWarner Losh 77791dd3b53SWarner Losh20010411: 77891dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 77991dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 78091dd3b53SWarner Losh Update only if you understand that you must not use the old 78191dd3b53SWarner Losh fsck with the new kernel ever. 78291dd3b53SWarner Losh 783933b3269SWarner Losh20010330: 784933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 785c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 786933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 787933b3269SWarner Losh 788933b3269SWarner Losh20010319: 789933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 790933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 791933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 792f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 79309946a51SWarner Losh 79409946a51SWarner Losh20010315: 79509946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 796ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 79709946a51SWarner Losh been replaced by tunables. See ata.4 for details. 798933b3269SWarner Losh 799933b3269SWarner Losh20010312: 800933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 801933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 802933b3269SWarner Losh 803933b3269SWarner Losh20010312: 804933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 805933b3269SWarner Losh instead of ad-hoc. 806933b3269SWarner Losh 807933b3269SWarner Losh20010310: 808f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 809933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 810933b3269SWarner Losh ssh might not work if you don't. 811933b3269SWarner Losh 81262353691SWarner Losh20010303: 81362353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 81462353691SWarner Losh which means that you must include the miibus in your kernel if 81562353691SWarner Losh you use the ed driver. 81662353691SWarner Losh 817d325cf65SWarner Losh20010220: 818d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 819d325cf65SWarner Losh safe to go back into the water. 820d325cf65SWarner Losh 821024daae6SWarner Losh20010211: 822024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 823024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 824024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 825024daae6SWarner Losh that before upgrading would be a good time to do a level 0 826024daae6SWarner Losh dump of your system. No, really, I mean it this time. 827024daae6SWarner Losh 828024daae6SWarner Losh To get to the new system, you'll need to use the following 829024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 830024daae6SWarner Losh don't have to move this to the updating section. 831024daae6SWarner Losh 832024daae6SWarner Losh To get around the installworld problem, do: 833024daae6SWarner Losh # cd /usr/src/usr.bin/sed 834024daae6SWarner Losh # make install 835024daae6SWarner Losh # cd /usr/src 836024daae6SWarner Losh # make installworld 837024daae6SWarner Losh If that doesn't work, then try: 838024daae6SWarner Losh # make -k installworld 839024daae6SWarner Losh # make installworld 840024daae6SWarner Losh 841024daae6SWarner Losh20010207: 842024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 843024daae6SWarner Losh do not include devfs in your kernel as problems result. 844024daae6SWarner Losh 845024daae6SWarner Losh20010205: 8467595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 847024daae6SWarner Losh Remove them from your config. 848024daae6SWarner Losh 8491e159248SWarner Losh20010122: 8501e159248SWarner Losh ****************************** WARNING ****************************** 8511e159248SWarner Losh buildkernel has been changed slightly 8521e159248SWarner Losh ****************************** WARNING ****************************** 8531e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 8541e159248SWarner Losh should update your scripts and make.conf accordingly. 8551e159248SWarner Losh 8561e159248SWarner Losh20010119: 8571e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 8581e159248SWarner Losh This requires a new config to build correctly. 8591e159248SWarner Losh 860aac7dfeaSWarner Losh20010116: 861ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 862aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 863aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 864aac7dfeaSWarner Losh 865aac7dfeaSWarner Losh20010110: 866aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 867aac7dfeaSWarner Losh 868aac7dfeaSWarner Losh20010102: 869aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 870aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 871aac7dfeaSWarner Losh 87263c90c9eSWarner Losh20010101: 87363c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 87463c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 8755fd2a895SWarner Losh dump while building termcap. You can work around this problem 87663c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 87763c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 87863c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 87963c90c9eSWarner Losh might have been ignored by the -k option. 88063c90c9eSWarner Losh 8815fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 8825fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 8835fd2a895SWarner Losh of this working. 8845fd2a895SWarner Losh 885aac7dfeaSWarner Losh20001228: 886aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 887ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 888aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 889aac7dfeaSWarner Losh 890de2bcc63SWarner Losh20001218: 891de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 892de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 893de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 894de2bcc63SWarner Losh cards will not be recognized without it. 895de2bcc63SWarner Losh 896960773f7SWarner Losh20001205: 897960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 898960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 899960773f7SWarner Losh adding the following in pam.conf: 900960773f7SWarner Losh 901960773f7SWarner Losh sshd auth sufficient pam_skey.so 902960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 903960773f7SWarner Losh sshd session required pam_permit.so 904960773f7SWarner Losh 9050acc635eSWarner Losh20001031: 9060acc635eSWarner Losh cvs updated to 1.11. 9070acc635eSWarner Losh 9080acc635eSWarner Losh20001020: 9090acc635eSWarner Losh The random device needs more entropy, so you need to make sure 9100acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 9110acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 9120acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 9130acc635eSWarner Losh workaround. 9140acc635eSWarner Losh 9150acc635eSWarner Losh20001010: 9160acc635eSWarner Losh ****************************** WARNING ****************************** 9170acc635eSWarner Losh Sendmail has been updated. 9180acc635eSWarner Losh ****************************** WARNING ****************************** 9190acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 9200acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 9210acc635eSWarner Losh is set. 9220acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 9230acc635eSWarner Losh commands. 9240acc635eSWarner Losh o Now using sendmail's version of vacation(1). 9250acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 9260acc635eSWarner Losh in /usr/share/sendmail/cf. 9270acc635eSWarner Losh o sendmail.cw changed to local-host-names 9280acc635eSWarner Losh 9290acc635eSWarner Losh More details can be found at 9300acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 9310acc635eSWarner Losh 9326e98a146SWarner Losh20001009: 9336e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 9346e98a146SWarner Losh your entire ports tree, or you will have problems. 9356e98a146SWarner Losh 9366e98a146SWarner Losh20001006: 937685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 9386e98a146SWarner Losh the installed miniperl. It is recommended that you delete 9396e98a146SWarner Losh /usr/bin/miniperl. 9406e98a146SWarner Losh 941073113a4SWarner Losh20001005: 942073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 943685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 944073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 945073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 946073113a4SWarner Losh tree for anything to work. 947073113a4SWarner Losh 9480acc635eSWarner Losh20000928: 9490acc635eSWarner Losh There was a change in the passwd format. Need more information. 9500acc635eSWarner Losh 951be3885b3SWarner Losh20000916: 952be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 953be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 954be3885b3SWarner Losh same time as your kernel. 955be3885b3SWarner Losh 95676ec9675SWarner Losh20000914: 95776ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 95876ec9675SWarner Losh include the device will cause suspended laptops losing time 95976ec9675SWarner Losh when they resume. Include 96076ec9675SWarner Losh device pmtimer 96176ec9675SWarner Losh in your config file and 96201b9a434SWarner Losh hint.pmtimer.0.at="isa" 96376ec9675SWarner Losh to your /boot/device.hints file. 96476ec9675SWarner Losh 965f4865386SMark Murray20000911: 966f4865386SMark Murray The random device has been turned into a (pseudo-)device, 967f4865386SMark Murray rather than an option. The supplied kernel config files have 968f4865386SMark Murray been updated. You will need to do something similar in your 969f4865386SMark Murray own kernel config file. 970f4865386SMark Murray Remove: 971f4865386SMark Murray options RANDOMDEV 972f4865386SMark Murray Add: 973f4865386SMark Murray device random 974f4865386SMark Murray If you prefer to load the loadable module, you need to do 975f4865386SMark Murray nothing. 976f4865386SMark Murray 977d594498fSWarner Losh20000909: 978d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 979d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 980d594498fSWarner Losh reflect this if you load this module at boot time. 981d594498fSWarner Losh The line should read: 982d594498fSWarner Losh random_load="YES" 983d594498fSWarner Losh 9840deb7ddcSWarner Losh20000907: 9850deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 98616eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 98716eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 98816eb772dSWarner Losh sure you don't have model loading problems which might at 98916eb772dSWarner Losh first blush appear related to SMP. 99052bf24e7SWarner Losh 9915a01880bSWarner Losh20000906: 9925a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 9935a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 9945a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 9955a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 9965a01880bSWarner Losh don't have one, and you have host.conf. 9975a01880bSWarner Losh 9982b41163cSWarner Losh20000905: 99938d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 100038d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 100138d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 100238d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 100338d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 100438d6ecd2SWarner Losh 100538d6ecd2SWarner Losh20000905: 10068aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 10078aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 10088aab4bc7SWarner Losh is /boot/kernel. 10098aab4bc7SWarner Losh 10108aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 101138d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 101238d6ecd2SWarner Losh installkernel/installworld dance. 10132b41163cSWarner Losh 1014d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1015d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1016d594498fSWarner Losh modules in that directory instead of finding them in the correct 1017d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1018d594498fSWarner Losh is that the linux module crashes your machine after the update. 1019d594498fSWarner Losh 1020d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1021d594498fSWarner Losh mv /modules.old /boot/kernel.old 1022d594498fSWarner Losh chflags noschg /kernel.old 1023d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1024d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1025d594498fSWarner Losh fi 1026d594498fSWarner Losh 1027c22a309cSWarner Losh20000904: 1028c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1029c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1030c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1031c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1032c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1033c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1034c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1035c22a309cSWarner Losh is not likely to be generated. 1036c22a309cSWarner Losh 1037fdb9f54dSWarner Losh20000825: 1038fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 10399c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 10409c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 10419c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 10429c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 10439c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 10449c1a7444SWarner Losh messages will appear after the boot loader tries to start the 10459c1a7444SWarner Losh kernel. 10469c1a7444SWarner Losh 10479c1a7444SWarner Losh20000821: 10489c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 10499c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 10509c1a7444SWarner Losh /boot/loader.conf. 1051fdb9f54dSWarner Losh 10528f250aa7SWarner Losh20000812: 10535da0d091SWarner Losh suidperl is now always built and installed on the system, but 10545da0d091SWarner Losh with permissions of 511. If you have applications that use 10555da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 10565da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 10575da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 10585da0d091SWarner Losh will fix this until the next build. 10595da0d091SWarner Losh 10605da0d091SWarner Losh20000812: 10618f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 10628f250aa7SWarner Losh visible changes that may immediately affect your configuration 10638f250aa7SWarner Losh include: 10648f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 10658f250aa7SWarner Losh - newaliases limited to root and trusted users 10668f250aa7SWarner Losh - MSA port (587) turned on by default 10678f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 10688f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 10698f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 10708f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 10718f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 10728f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 10738f250aa7SWarner Losh 107471c38472SWarner Losh20000810: 107571c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 107671c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 107771c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 107871c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 107971c38472SWarner Losh specific use for it. 108071c38472SWarner Losh 108171c38472SWarner Losh20000729: 108271c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 108371c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 108471c38472SWarner Losh /etc/rc.conf if they want to have the same setup 108571c38472SWarner Losh afterwards (unless the variables already are set, of course): 108671c38472SWarner Losh # Enable network daemons for user convenience. 108771c38472SWarner Losh inetd_enable="YES" 108871c38472SWarner Losh portmap_enable="YES" 108971c38472SWarner Losh sendmail_enable="YES" 109071c38472SWarner Losh 109171c38472SWarner Losh20000728: 109271c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 109371c38472SWarner Losh will need to change that to nullfs_load="YES". 109471c38472SWarner Losh 10951dece4a9SWarner Losh20000728: 10961dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 10971dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 10981dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 10991dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 11001dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 11011dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 11021dece4a9SWarner Losh to /MYKERNEL. 11031dece4a9SWarner Losh 1104409e887cSWarner Losh20000711: 1105409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1106409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1107409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1108409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1109409e887cSWarner Losh for details on potential problems that you might have and how 1110409e887cSWarner Losh to get around them. 1111409e887cSWarner Losh 1112409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1113409e887cSWarner Losh clauses above, you needn't worry. 1114409e887cSWarner Losh 1115409e887cSWarner Losh20000711: 1116409e887cSWarner Losh /etc/security has been updated to print the inode number of 1117409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1118409e887cSWarner Losh in the number of changed programs the first time when you run 1119409e887cSWarner Losh mergemaster to get a new /etc/security. 1120409e887cSWarner Losh 1121673d13f2SWarner Losh20000710: 1122673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1123673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1124673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1125673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1126673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1127673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1128673d13f2SWarner Losh errors. (see below, 20000624). 1129673d13f2SWarner Losh 1130bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 11311dece4a9SWarner Losh 1132673d13f2SWarner Losh20000709: 1133c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1134c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1135c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1136673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1137673d13f2SWarner Losh 1138e98e26cdSWarner Losh20000706: 1139e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1140e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1141e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1142f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1143e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 11442c021c6cSMark Ovens interim if needed. 1145e98e26cdSWarner Losh 1146e98e26cdSWarner Losh20000705: 1147e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1148e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1149e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1150e98e26cdSWarner Losh details. 1151e98e26cdSWarner Losh 1152c373950eSWarner Losh20000704: 11532f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 11542f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 11552f961bc8SWarner Losh 11562f961bc8SWarner Losh20000704: 1157c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1158c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1159c373950eSWarner Losh rc.d scripts that haven't been updated. 1160c373950eSWarner Losh 116127dc3a2bSWarner Losh20000630: 116227dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 116327dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 116427dc3a2bSWarner Losh which should be reported to des@freebsd.org. 116527dc3a2bSWarner Losh 1166b8c215acSWarner Losh20000625: 1167b8c215acSWarner Losh From approximately this date forward, one must have the crypto 116827dc3a2bSWarner Losh system installed in order to build the system and kernel. 116927dc3a2bSWarner Losh While not technically strictly true, one should treat it as 117027dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 117127dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 117227dc3a2bSWarner Losh were required. You should check with the latest collections 117327dc3a2bSWarner Losh to make sure that these haven't changed. 1174b8c215acSWarner Losh 11757b990719SWarner Losh20000624: 11767b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 11777b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 11787b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 11791a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 11807b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 11817b990719SWarner Losh openssh and openssl should not be used to generate keys from this 11827b990719SWarner Losh date to the completion of the work. 11837b990719SWarner Losh 118427dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 118527dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 118627dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 118727dc3a2bSWarner Losh recreate the random and urandom devices. 118827dc3a2bSWarner Losh 118981e54c50SWarner Losh20000622: 119081e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 119181e54c50SWarner Losh BSD license. You may need to remove your symbolic links 119281e54c50SWarner Losh that used to be required when updating. 119381e54c50SWarner Losh 119439943833SWarner Losh20000621: 11952c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 11962a2f33fbSDaniel Baker the config file update procedure. 11972a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1198c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 119959df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 120059df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 120139943833SWarner Losh 1202290f9ad8SWarner Losh20000620: 1203290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1204290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1205290f9ad8SWarner Losh that workaround will no longer be required. 1206290f9ad8SWarner Losh 120790fb6346SWarner Losh20000615: 120890fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 120990fb6346SWarner Losh ad driver. If you haven't done so already, you must update 121090fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 121190fb6346SWarner Losh devices. 121290fb6346SWarner Losh 1213f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1214f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1215f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1216f75f65bbSWarner Losh may work). 1217f75f65bbSWarner Losh 1218ba26da8eSWarner Losh20000612: 1219ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1220290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1221c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1222290f9ad8SWarner Losh to your config file to compile them in statically. The format 1223f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1224f54a3542SWarner Losh NEWCARD for examples of the new format. 1225290f9ad8SWarner Losh 12269698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 12279698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 12289698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 12299698f2c0SWarner Losh in it. 1230bbcc5149SWarner Losh 1231d65850ebSWarner Losh20000522: 1232ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1233d65850ebSWarner Losh building a kernel after this point is advised that they need 1234d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1235d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1236d65850ebSWarner Losh 1237d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1238d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1239d9583a00SWarner Losh is recommended that you don't set this option until the problem 1240d9583a00SWarner Losh is resolved. 1241d9583a00SWarner Losh 12428039cedeSWarner Losh20000513: 12438039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 12448039cedeSWarner Losh 1245d65850ebSWarner Losh20000510: 12468039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 12478039cedeSWarner Losh This will require some care in updating alphas. A new libstand 12488039cedeSWarner Losh is requires for the boot blocks to build properly. 12498039cedeSWarner Losh 12508039cedeSWarner Losh20000503: 12518039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 12528039cedeSWarner Losh is now available. 12538039cedeSWarner Losh 1254d65850ebSWarner Losh20000502: 1255d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1256d65850ebSWarner Losh connected to the kernel building instead. 1257d65850ebSWarner Losh 1258be149406SNik Clayton20000427: 12598039cedeSWarner Losh You may need to build gperf 12608039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 12618039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 12628039cedeSWarner Losh an option only in -current. 12638039cedeSWarner Losh 12642b8dd5f4SWarner Losh20000417: 12652b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1266f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 12672b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 12682b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 12692c021c6cSMark Ovens before you reboot, you'll need to issue: 12702b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 12712b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 12722b8dd5f4SWarner Losh 12738d9f1945SWarner Losh20000320: 12742b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 12752b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 12762b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1277ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 12782b8dd5f4SWarner Losh to the start of /etc/rc.conf. 12798d9f1945SWarner Losh 1280f8ab1dd6SWarner Losh20000319: 1281f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1282f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1283f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1284f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1285f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1286f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1287f8ab1dd6SWarner Losh 128819cada77SWarner Losh20000318: 1289f699bbbbSMark Ovens We've entered the traditional post release dumping party. 129019cada77SWarner Losh Large kernel changes are being committed and are in the 129119cada77SWarner Losh works. It is important to keep the systems' klds and kernel 129219cada77SWarner Losh in sync as kernel interfaces and structures are changing. 129319cada77SWarner Losh Before reporting kernel panics, make sure that all modules 129419cada77SWarner Losh that you are loading are up to date. 1295ba228352SWarner Losh 129619cada77SWarner Losh20000315: 12976d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 12986d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 12996d23c382SWarner Losh will do the trick. This isn't critical until you remove your 13006d23c382SWarner Losh wd device entries in /dev, at which point your system will not 13016d23c382SWarner Losh boot. 13026d23c382SWarner Losh 13036d23c382SWarner Losh20000315: 130419cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 130519cada77SWarner Losh to upgrade to 4.0 from 3.x. 130657199806SWarner Losh 1307dc0dbf5cSWarner LoshCOMMON ITEMS: 1308dc0dbf5cSWarner Losh 1309a24eff53SWarner Losh General Notes 1310a24eff53SWarner Losh ------------- 1311a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1312a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1313a24eff53SWarner Losh installworld. This is especially true when upgrading between 1314a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1315a24eff53SWarner Losh or several minor releases, or when several months have passed 1316a24eff53SWarner Losh on the -current branch). 1317a24eff53SWarner Losh 13185780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 13195780f3baSWarner Losh poisoning. This can happen because the make utility reads its 13205780f3baSWarner Losh environment when searching for values for global variables. 13215780f3baSWarner Losh To run your build attempts in an "environmental clean room", 13225780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 13235780f3baSWarner Losh page for more details. 13245780f3baSWarner Losh 1325dc0dbf5cSWarner Losh To build a kernel 1326dc0dbf5cSWarner Losh ----------------- 1327ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1328f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1329ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1330282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1331282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1332dc0dbf5cSWarner Losh 1333ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1334ba01eb20SWarner Losh -------------------------------------------------------------- 1335ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 133647d0d01fSWarner Losh config KERNEL_NAME_HERE 1337ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1338ba01eb20SWarner Losh make depend 1339ba01eb20SWarner Losh make 1340ba01eb20SWarner Losh make install 1341ba01eb20SWarner Losh 1342ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1343ba01eb20SWarner Losh 1344ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1345ba01eb20SWarner Losh ----------------------------------------------------------- 134663cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 134763cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 134863cb445eSWarner Losh 1349f643de42SWarner Losh <make sure you have good level 0 dumps> 135063cb445eSWarner Losh <maybe fix /etc/fstab> [7] 135163cb445eSWarner Losh make buildworld 135263cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 135363cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 135463cb445eSWarner Losh [1] 135563cb445eSWarner Losh <reboot in single user> [3] 135663cb445eSWarner Losh mergemaster -p [5] 135763cb445eSWarner Losh make installworld 135863cb445eSWarner Losh mergemaster [4] 135963cb445eSWarner Losh <reboot> 136063cb445eSWarner Losh 1361759f0aefSWarner Losh 1362f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1363f27b1fceSJoseph Koshy -------------------------------------------------- 1364f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1365f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1366f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1367f27b1fceSJoseph Koshy # size. 1368f27b1fceSJoseph Koshy 1369f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1370f27b1fceSJoseph Koshy <boot into -stable> 1371f27b1fceSJoseph Koshy make buildworld 1372f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1373f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1374f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1375f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1376f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1377f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1378f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1379f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1380f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1381f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1382f27b1fceSJoseph Koshy <reboot into current> 1383f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1384f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1385f27b1fceSJoseph Koshy <reboot> 1386f27b1fceSJoseph Koshy 1387f27b1fceSJoseph Koshy 1388f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1389f27b1fceSJoseph Koshy ---------------------------------------------- 13905c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 13915c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 13925c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 13935c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1394ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1395f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1396f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1397f643de42SWarner Losh # space on /. 1398f643de42SWarner Losh 1399f643de42SWarner Losh <make sure you have good level 0 dumps> 1400fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 140121c075eaSWarner Losh make buildworld [9] 1402c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1403d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1404be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1405fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1406fc8c157fSWarner Losh [1] 1407fc8c157fSWarner Losh <reboot in single user> [3] 1408835284beSWarner Losh mergemaster -p [5] 1409f8a4c901SWarner Losh rm -rf /usr/include/g++ 1410ba26da8eSWarner Losh make installworld 1411a6cd4f9dSWarner Losh mergemaster [4] 1412ba26da8eSWarner Losh <reboot> 1413ba26da8eSWarner Losh 1414fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1415fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1416fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1417fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1418fdb9f54dSWarner Losh the UPDATING entries. 1419ba26da8eSWarner Losh 14201dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 14211dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 14221dece4a9SWarner Losh your sources that you have read and understood all the recent 14231dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 14241dece4a9SWarner Losh much fewer pitfalls. 14251dece4a9SWarner Losh 1426134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1427134d2e86SWarner Losh should disable them at this point so they don't crash your 1428134d2e86SWarner Losh system on reboot. 1429134d2e86SWarner Losh 14309c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 14319c1a7444SWarner Losh your own device.hints to reflect your unique hardware 14329c1a7444SWarner Losh configuration. 14339c1a7444SWarner Losh 1434ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1435ee6e1fc3SWarner Losh fsck -p 1436ee6e1fc3SWarner Losh mount -u / 1437ee6e1fc3SWarner Losh mount -a 1438ee6e1fc3SWarner Losh cd /usr/src 143947d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1440f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1441f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1442b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1443b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1444b705ae10SWarner Losh be ignored while you proceed to the next step. 1445ee6e1fc3SWarner Losh 1446a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1447a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1448a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1449a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1450a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1451a6cd4f9dSWarner Losh for potential gotchas. 1452a6cd4f9dSWarner Losh 1453835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1454835284beSWarner Losh you may need to do this if you get unknown user in the following 1455835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1456835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1457835284beSWarner Losh install) after the buildworld before this step if you last updated 1458835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1459835284beSWarner Losh 1460bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1461bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1462bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1463bd79cf40SWarner Losh ok unload 1464bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1465bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1466bd79cf40SWarner Losh described here. 1467fc8c157fSWarner Losh 1468fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1469fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1470fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1471fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1472fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1473fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1474fc8c157fSWarner Losh 1475c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1476c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1477c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1478c74fe6afSWarner Losh that is hard to boot to recover. 1479c74fe6afSWarner Losh 148021c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 148121c075eaSWarner Losh cvs prune empty directories. 1482dc0dbf5cSWarner LoshFORMAT: 1483dc0dbf5cSWarner Losh 1484f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 14851fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1486f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1487f8ab1dd6SWarner Loshprevious releases if your system is older than this. 14881fc1a0dcSWarner Losh 1489e72fd46aSWarner LoshCopyright information: 1490e72fd46aSWarner Losh 14919698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1492e72fd46aSWarner Losh 1493772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1494772730c7SWarner Loshmodification, in full or in part, in any form or format of this 14959698f2c0SWarner Loshdocument are permitted without further permission from the author. 1496e72fd46aSWarner Losh 1497e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1498e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1499e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1500e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1501e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1502e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1503e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1504e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1505e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1506e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1507e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1508e72fd46aSWarner Losh 1509e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1510e72fd46aSWarner Loshauthor a beer. 1511e72fd46aSWarner Losh 151222306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1513772730c7SWarner Loshthis document. 1514772730c7SWarner Losh 151597d92980SPeter Wemm$FreeBSD$ 1516