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: 28e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 29e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 30e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 31e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 32e07a40f3SBrian Feldman should remain unaffected. 33e07a40f3SBrian Feldman 34e07a40f3SBrian Feldman20040225: 35714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 36714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 37714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 38714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 39714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 40714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 41714ae42aSBruce M Simpson 42fbd2e692SAndre Oppermann20040224: 43fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 44fbd2e692SAndre Oppermann and related userland network utilities neccessary. 45fbd2e692SAndre Oppermann 46158b90daSWarner Losh20040222: 47158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 48158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 49158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 50158b90daSWarner Losh Drivers outside the tree will need to be updated. 51158b90daSWarner Losh 52b7b1e150SMike Makonnen20040207: 53b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 54b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 55b7b1e150SMike Makonnen 56aca89ee6SDaniel Eischen20040130: 57aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 58aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 59aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 60aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 61aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 62aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 63aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 64aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 65aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 66aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 67aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 68aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 69aca89ee6SDaniel Eischen do not work with libpthread. 70aca89ee6SDaniel Eischen 7168b7b3a9SAlex Dupre20040125: 7268b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 7368b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 7468b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 7568b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 7668b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 7768b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 7868b7b3a9SAlex Dupre 79ff46e0deSWarner Losh20040125: 80ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 81ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 82ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 83ff46e0deSWarner Losh 84ce41f4bfSRobert Watson20031213: 85ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 86ce41f4bfSRobert Watson if the login process is unable to successfully set the 87ce41f4bfSRobert Watson process credentials to include all groups defined for the 88ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 89ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 90ce41f4bfSRobert Watson defined, or they will be unable to log in. 91ce41f4bfSRobert Watson 92c124fa05SJohn Baldwin20031203: 93c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 94c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 95c124fa05SJohn Baldwin 968ad1f5e4SHartmut Brandt20031112: 9730093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 9830093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 9997209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 10097209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 10197209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 10297209ca3SRobert Watson not know about the new system calls that support the new statfs 1033f631d52SMarcel Moolenaar structure. 1043f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 1053f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 1063f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 1073f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 1083f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 1093f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 1103f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 1113f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 1123f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 1133f631d52SMarcel Moolenaar these changes are installed. 11430093b05SWarner Losh 11530093b05SWarner Losh ****************************DANGER******************************* 11630093b05SWarner Losh 11730093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 11830093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 11930093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 12030093b05SWarner Losh kernel. 12164a18d6fSKirk McKusick 12264a18d6fSKirk McKusick20031112: 1238ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 1248ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 1258ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 1268ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 1278ad1f5e4SHartmut Brandt sync before rebooting. 1288ad1f5e4SHartmut Brandt 129c53a5d8fSJohn Baldwin20031111: 130c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 131c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 132c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 133c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 134c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 135c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 136c53a5d8fSJohn Baldwin 1378bf455a5SJohn Baldwin20031103: 1388bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 1398bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 1402a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 1418bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 1428bf455a5SJohn Baldwin 1439bf40edeSBrooks Davis20031031: 1449bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 1459bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 1469bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 1479bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 1489bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 1499bf40edeSBrooks Davis reflect this change. 1509bf40edeSBrooks Davis 15147a42c7aSPoul-Henning Kamp20030928: 15247a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 15347a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 15447a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 15547a42c7aSPoul-Henning Kamp 15607105342SMax Khon20030926: 15707105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 15807105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 15907105342SMax Khon 16017dcd026SSam Leffler20030925: 16117dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 16217dcd026SSam Leffler also be explicitly configured. Previously this dependency was 16317dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 16417dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 16517dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 16617dcd026SSam Leffler 167fedf1d01SBruce M Simpson20030923: 168fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 169fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 170fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 171fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 172fedf1d01SBruce M Simpson 173db38f9cbSJacques Vidrine20030915: 174db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 175db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 176db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 177db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 178db38f9cbSJacques Vidrine 179c09d2c2bSMike Makonnen20030829: 180c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 181c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 182c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 183c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 184c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 185c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 186c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 187c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 188c09d2c2bSMike Makonnen may or may not exist on your system. 189c09d2c2bSMike Makonnen 19017c159dcSSøren Schmidt20030824: 19117c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 19217c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 193f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 194f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 19517c159dcSSøren Schmidt 196c1f61aa9SDavid E. O'Brien20030819: 197c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 198c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 199c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 200c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 20169f7bcf3SWarner Losh 20238c962e7SNate Lawson20030728: 20338c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 20438c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 20538c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 20638c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 20738c962e7SNate Lawson so the quirk can be re-enabled. 20838c962e7SNate Lawson 20974111097SWarner Losh20030724: 21074111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 21174111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 21274111097SWarner Losh 213178cf4e9SWarner Losh20030722: 214178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 215178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 216178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 217178cf4e9SWarner Losh FPU hardware. 218178cf4e9SWarner Losh 219178cf4e9SWarner Losh20030714: 220178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 221178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 222178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 223178cf4e9SWarner Losh People should report those issues to current@. 224178cf4e9SWarner Losh 225157c629aSWarner Losh20030711: 226157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 2278b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 22805538fa9SWarner Losh /usr/obj. 229157c629aSWarner Losh 23074111097SWarner Losh20030610: 23174111097SWarner Losh Remove deprecated locale names and transition period code 23274111097SWarner Losh for them, finishing switching to the new scheme. Check your 23374111097SWarner Losh LANG environment variable. 23474111097SWarner Losh 23574111097SWarner Losh20030609: 23674111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 23774111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 23874111097SWarner Losh important to remember beforehand if your source tree is on 23974111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 24074111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 24174111097SWarner Losh kernel. 24274111097SWarner Losh 24374111097SWarner Losh20030605: 2446cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 2456cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 2466cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 2476cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 2486cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 2496cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 2506cc6353fSMarcel Moolenaar 2516cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 2526cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 2536cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 2546cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 2556cc6353fSMarcel Moolenaar : 2566cc6353fSMarcel Moolenaar 2576cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 2586cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 2596cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 2606cc6353fSMarcel Moolenaar 26152b47445SMark Murray20030505: 26252b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 26352b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 26452b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 26552b47445SMark Murray 266a26df538SWarner Losh20030502: 267a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 268a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 269a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 270a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 271a26df538SWarner Losh 2724b065e2cSDoug Barton20030501: 2734b065e2cSDoug Barton The old rc system has been removed. Please report any problems 2744b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 2754b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 2764b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 2774b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 2784b065e2cSDoug Barton utilizes these old scripts has also been removed. 2794b065e2cSDoug Barton 28081cda3d9SWarner Losh20030423: 28181cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 28281cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 28381cda3d9SWarner Losh work around in devd will be removed around 20030507. You 28481cda3d9SWarner Losh have until then to upgrade your kernel before updating 28581cda3d9SWarner Losh userland. In general, you should have a userland and 28681cda3d9SWarner Losh kernel that's in sync with each other. However, given the 28781cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 28881cda3d9SWarner Losh allowances are made. 28981cda3d9SWarner Losh 29047a657d1SRuslan Ermilov20030329: 29147a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 29247a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 29347a657d1SRuslan Ermilov while upgrading the system through a buildworld. 29447a657d1SRuslan Ermilov 29547a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 29647a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 29747a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 29847a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 29947a657d1SRuslan Ermilov 30047a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 30147a657d1SRuslan Ermilov make cleandir && make obj && \ 30247a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 30347a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 30447a657d1SRuslan Ermilov 3055d2af00cSGregory Neil Shapiro20030208: 3065d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 3075d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 3085d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 3095d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 3105d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 3115d2af00cSGregory Neil Shapiro 3125d2af00cSGregory Neil Shapiro20030128: 3139db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 314ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 3159db58771SPoul-Henning Kamp be removed when convenient. 3169db58771SPoul-Henning Kamp 3178d9b3f57SJake Burkholder20030126: 3188d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 3198d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 3208d9b3f57SJake Burkholder 3211c5efda5SJeff Roberson20030125: 3221c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 3231c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 324ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 3251c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 3261c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 3271c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 3281c5efda5SJeff Roberson 3299d1d64f5SWarner Losh20030115: 3309d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 3319d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 3329d1d64f5SWarner Losh properly. 3339d1d64f5SWarner Losh 334c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 335c9fdb80aSWarner Losh configured for point to point links to bring it more in line 336c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 337c9fdb80aSWarner Losh with NetBSD. 338c9fdb80aSWarner Losh 339161dc364SAlexander Kabaev20021222: 340161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 341161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 342161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 343161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 344161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 345161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 34684cc83efSAlexander Kabaev rebuilt. 347161dc364SAlexander Kabaev 348fb4c8061SMartin Blapp20021216: 349fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 35089056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 351fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 3529d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 353fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 354fb4c8061SMartin Blapp 35517d47eb3SGiorgos Keramidas20021202: 35617d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 35717d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 35817d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 35917d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 36017d47eb3SGiorgos Keramidas 361a4459294SBill Fenner20021029: 362a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 363a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 364a4459294SBill Fenner consumers in sync. 365a4459294SBill Fenner 366fc8c157fSWarner Losh20021024: 367c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 368c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 369c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 370c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 371c57404feSRuslan Ermilov partition really is on. The old device names have gone 372c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 373c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 374c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 37569f7bcf3SWarner Losh 376fd9e8bdaSAndrew Gallatin20021023: 377fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 378fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 379fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 380fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 381fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 382fd9e8bdaSAndrew Gallatin 383fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 384fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 385fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 386fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 387fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 388fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 389fd9e8bdaSAndrew Gallatin 390f8a4c901SWarner Losh20020831: 391f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 392f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 393f8a4c901SWarner Losh programs and libraries need to be recompiled. 394f8a4c901SWarner Losh 395f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 396f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 397f8a4c901SWarner Losh 398c2248fa2SJens Schweikhardt20020827: 399c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 400c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 401c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 402c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 403c2248fa2SJens Schweikhardt 4040d533e43SRuslan Ermilov20020815: 4050d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 4060d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 4070d533e43SRuslan Ermilov again. 4080d533e43SRuslan Ermilov 40933c1de7dSRuslan Ermilov20020729: 41033c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 41133c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 41233c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 41333c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 41433c1de7dSRuslan Ermilov 4152b877facSJulian Elischer20020702: 4162b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 4172b877facSJulian Elischer There are still some minor problems with some signals but the 4182b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 4192b877facSJulian Elischer but each can successfully complete multiple buildworlds. 4202b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 4212b877facSJulian Elischer 42206596d37SWarner Losh20020701: 42306596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 42406596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 42506596d37SWarner Losh GNOME. 42606596d37SWarner Losh 42795ba4330SJacques Vidrine20020511: 42895ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 42995ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 43095ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 43195ba4330SJacques Vidrine with the set-user-ID bit set. 43295ba4330SJacques Vidrine 433a81da3c9SDavid E. O'Brien20020510: 434f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 435f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 4364b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 437f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 438f50caf6fSDavid E. O'Brien 439f50caf6fSDavid E. O'Brien20020510: 440a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 441a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 442a81da3c9SDavid E. O'Brien and then do a cvs update. 443a81da3c9SDavid E. O'Brien 444528a0ef5SJacques Vidrine20020421: 445528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 446528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 447528a0ef5SJacques Vidrine 44885aa5a2eSGregory Neil Shapiro20020404: 44985aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 45085aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 45185aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 45285aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 45385aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 45485aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 45585aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 45685aa5a2eSGregory Neil Shapiro 4578f1e4358SRuslan Ermilov20020403: 4588f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 4598f1e4358SRuslan Ermilov 4602292c02eSWarner Losh20020315: 4612292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 4622292c02eSWarner Losh 46369f7bcf3SWarner Losh20020225: 46469f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 46569f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 46669f7bcf3SWarner Losh 4678f35c493SWarner Losh20020217: 4688f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 4698f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 4708f35c493SWarner Losh command line mail submission has changed. Be sure to run 4718f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 4728f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 4738f35c493SWarner Losh 474835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 475835284beSWarner Losh required in order for sendmail to run as a set-group-ID 476835284beSWarner Losh binary. A 'make installworld' will use the new user and group 477835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 478835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 479835284beSWarner Losh and group must be merged from src/etc/group and 480835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 481835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 482835284beSWarner Losh mergemaster before this will work if you are updating from a 483835284beSWarner Losh very old version of current. The updating recipe has changed 484835284beSWarner Losh as of this date. 485835284beSWarner Losh 486fa9401c1SWarner Losh20020112: 487fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 488fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 489fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 490fa9401c1SWarner Losh you have local modifications, you can use 491fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 492fa9401c1SWarner Losh /etc/pam.d. 493fa9401c1SWarner Losh 494fa9401c1SWarner Losh Please see the following url for more details: 495fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 49647d0d01fSWarner Losh20011229: 49747d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 49847d0d01fSWarner Losh networkfs_types, please note that it has changed 49947d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 50047d0d01fSWarner Losh 501514318a8SWarner Losh20011220: 502514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 503514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 504514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 505514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 506514318a8SWarner Losh version have now been merged back into the base system's 507514318a8SWarner Losh version now. The only user-visible change resulting from this 508514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 509514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 510514318a8SWarner Losh as well. (There has never been rc file support for 511514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 512514318a8SWarner Losh reverted by the time the changes are MFCed.) 513514318a8SWarner Losh 514514318a8SWarner Losh20011215: 515514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 516514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 517514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 518514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 519514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 520514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 521514318a8SWarner Losh will need to be customized then for `odd' densities using 522514318a8SWarner Losh fdcontrol(8). 523514318a8SWarner Losh 5242d22e2bfSWarner Losh20011209: 5252d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 5262d22e2bfSWarner Losh and truss(1) now works again. 5272d22e2bfSWarner Losh 5289e0428e2SWarner Losh20011207: 5299e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 5309e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 5319e0428e2SWarner Losh see 5329e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 5339e0428e2SWarner Losh for details. 5349e0428e2SWarner Losh 5359bab8c59SWarner Losh20011204: 5369bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 5379bab8c59SWarner Losh kernel and burncd to be in sync. 5389bab8c59SWarner Losh 539e57d8b01SWarner Losh20011203: 540e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 541e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 542e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 543e57d8b01SWarner Losh not there already. 544e57d8b01SWarner Losh 545e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 546e57d8b01SWarner Losh until the issue has been resolved. 547e57d8b01SWarner Losh 548b001d36fSJacques Vidrine20011202: 549b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 550b001d36fSJacques Vidrine patched. 551b001d36fSJacques Vidrine 5524b676ec1SWarner Losh20011126: 5534b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 5545ebbf43eSWarner Losh after this date. You need to do this only once. 5554b676ec1SWarner Losh 556d961e462SWarner Losh20011103: 557d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 558d961e462SWarner Losh edges may be left, but for the most part things should be 5594b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 560d961e462SWarner Losh 561d961e462SWarner Losh20011030: 562d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 563d961e462SWarner Losh choppy waves in the upgrade process. 564d961e462SWarner Losh 5651fe003b6SWarner Losh20011030: 566a4b6fda0SWarner Losh The asr driver problem has been resolved. 5671fe003b6SWarner Losh 5681fe003b6SWarner Losh20011027: 5691fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 5701fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 5711fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 5721fe003b6SWarner Losh try to use from this date forward. 5731fe003b6SWarner Losh 5741fe003b6SWarner Losh20011025: 5751fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 5761fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 5771fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 5781fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 5791fe003b6SWarner Losh TARGET_ARCH=i386. 5801fe003b6SWarner Losh 581d05f9643SWarner Losh20011001: 582d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 583d05f9643SWarner Losh You must recompile both the kernel and userland applications 584d05f9643SWarner Losh at the same time. 585d05f9643SWarner Losh 58658970f85SWarner Losh20010929: 58758970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 58858970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 58958970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 59058970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 5919d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 59258970f85SWarner Losh 59358970f85SWarner Losh20010927: 59458970f85SWarner Losh Some weird problems result from using ACPI on some machines. 59558970f85SWarner Losh To disable ACPI you can add 59666ff0e67SMax Khon hint.acpi.0.disabled="1" 59758970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 59858970f85SWarner Losh loader "ok" prompt). 59958970f85SWarner Losh 60058970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 60158970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 60258970f85SWarner Losh file and not list acpi in that list. 603378f4486SAlfred Perlstein 6045119d237SWarner Losh20010924: 6055119d237SWarner Losh The buildworld has been fixed. You may need to install 6065119d237SWarner Losh the 4.x compatibility libraries for some old binaries 6078b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 6088b039fffSWarner Losh get them installed on every installworld, or execute the 6098b039fffSWarner Losh following to get them installed only once: 6108b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 61158970f85SWarner Losh make all install 6128b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 6135119d237SWarner Losh 6143c293725SWarner Losh20010919: 6153c293725SWarner Losh There's a bug in the world build process. The cross-tools 6163c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 6173c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 618772730c7SWarner Losh workaround is to add 6193c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 6203c293725SWarner Losh before building world when upgrading from 4.x to current. This 6213c293725SWarner Losh can be removed afterwards. 6223c293725SWarner Losh 6233c293725SWarner Losh A proper fix to the buildworld target is needed. 6243c293725SWarner Losh 6253c293725SWarner Losh20010918: 6263c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 6273c293725SWarner Losh NFS may be unstable after this date. 6283c293725SWarner Losh 6293c293725SWarner Losh20010912: 6303c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 6313c293725SWarner Losh the kernel. While a few problems were introduced in the 6323c293725SWarner Losh initial commit, most of the major ones have been found and 6333c293725SWarner Losh corrected. 6343c293725SWarner Losh 6353c293725SWarner Losh20010901: 6363c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 6373c293725SWarner Losh arounds described in the 20010604 entry are now no longer 6383c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 6393c293725SWarner Losh have been rectified around this date. 6403c293725SWarner Losh 64198b17b95SWarner Losh20010823: 64298b17b95SWarner Losh named now runs as user bind and group bind rather than as 64398b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 64498b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 64598b17b95SWarner Losh and that group bind is available in /etc/group. Also make 64698b17b95SWarner Losh sure that user or group bind has read (and not write) 64798b17b95SWarner Losh permission for your name server configuration and that it 64898b17b95SWarner Losh has read and write permission for your slave zone files and 64998b17b95SWarner Losh directory. 65098b17b95SWarner Losh 65198b17b95SWarner Losh If you wish to continue to run named as root (a less secure 65298b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 65398b17b95SWarner Losh 65498b17b95SWarner Losh named_flags= 65598b17b95SWarner Losh 6567b9786edSMark Murray20010709: 6577b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 6587b9786edSMark Murray the ability of the shared library major number to handle. 6597b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 6607b9786edSMark Murray solution is to rebuild those ports. 6617b9786edSMark Murray 6621d28950eSWarner Losh20010628: 6631d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 6641d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 6651d28950eSWarner Losh 666e72fd46aSWarner Losh20010625: 66798b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 66898b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 66998b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 67098b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 67198b17b95SWarner Losh IRQ configuration needs more safety belts. 67216de1a07SWarner Losh 6730d415dffSWarner Losh20010617: 674e72fd46aSWarner Losh Softupdates problems have been corrected. 6750d415dffSWarner Losh 6760d415dffSWarner Losh20010614: 6770d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 6780d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 6790d415dffSWarner Losh kernel building methods. 6800d415dffSWarner Losh 6818b9959adSWarner Losh20010613: 6828b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 6838b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 684e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 685e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 6868b9959adSWarner Losh 687e72fd46aSWarner Losh20010613: 6888b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 689e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 690e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 6918b9959adSWarner Losh 6920d415dffSWarner Losh20010612: 6930d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 6940d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 6950d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 6960d415dffSWarner Losh work around this issue, please use only one or the other mechanism 6970d415dffSWarner Losh until this bug is fixed. 6980d415dffSWarner Losh 699e72fd46aSWarner Losh Please note that a feature of config is that if you have config 700e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 701ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 702e72fd46aSWarner Losh 7030d415dffSWarner Losh20010610: 7040d415dffSWarner Losh Locale names have changed to match other systems better. 7050d415dffSWarner Losh 7066ccdb5e4SWarner Losh20010604: 7076ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 7086ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 7096ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 7103590182eSWarner Losh Interrupt storms look a lot like a hang. 7113590182eSWarner Losh 7123590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 7133590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 7143590182eSWarner Losh it is). 7153590182eSWarner Losh 7163590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 7173590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 7183590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 7193590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 7206ccdb5e4SWarner Losh 7210bc62786SWarner Losh20010530: 7220bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 7230bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 7240bc62786SWarner Losh a limited time. If you see 7250bc62786SWarner Losh 7260bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 7270bc62786SWarner Losh 7280bc62786SWarner Losh in your makeworld, then you need to migrate towards using 7290bc62786SWarner Losh COPY=-C. 7300bc62786SWarner Losh 73168a38c6cSWarner Losh20010525: 732b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 733c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 734c4f4a728SWarner Losh definitely is in bad shape. 73568a38c6cSWarner Losh 736ed0f29caSWarner Losh20010521: 737ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 738ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 739ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 740ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 741ed0f29caSWarner Losh is 742ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 743ed0f29caSWarner Losh 74480c16af9SWarner Losh20010520: 74568a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 74680c16af9SWarner Losh 74780c16af9SWarner Losh20010519: 74880c16af9SWarner Losh pccard has had much reorganizational work done to it over 74980c16af9SWarner Losh the past few days. Everything should still work, but if 75080c16af9SWarner Losh not, please contact imp@freebsd.org. 75180c16af9SWarner Losh 752a45f2d05SWarner Losh20010517: 753a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 754a45f2d05SWarner Losh userland at the same time. 755a45f2d05SWarner Losh 756a45f2d05SWarner Losh20010517: 757a45f2d05SWarner Losh New ncurses imported. 758a45f2d05SWarner Losh 7592988afcaSWarner Losh20010512: 7602988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 7612988afcaSWarner Losh will be the only way to go starting July 1. 7622988afcaSWarner Losh 7631a33dba7SWarner Losh20010504: 7641a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 7651a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 7661a33dba7SWarner Losh 76709946a51SWarner Losh20010502: 76809946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 76909946a51SWarner Losh 77009946a51SWarner Losh20010501: 77109946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 77209946a51SWarner Losh 77309946a51SWarner Losh20010430: 774a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 77509946a51SWarner Losh go back in the water. 77609946a51SWarner Losh 77709946a51SWarner Losh20010429: 77809946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 77909946a51SWarner Losh this date, but before the correction date. 78009946a51SWarner Losh 78191dd3b53SWarner Losh20010423: 78291dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 78391dd3b53SWarner Losh 78491dd3b53SWarner Losh20010411: 78591dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 78691dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 78791dd3b53SWarner Losh Update only if you understand that you must not use the old 78891dd3b53SWarner Losh fsck with the new kernel ever. 78991dd3b53SWarner Losh 790933b3269SWarner Losh20010330: 791933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 792c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 793933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 794933b3269SWarner Losh 795933b3269SWarner Losh20010319: 796933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 797933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 798933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 799f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 80009946a51SWarner Losh 80109946a51SWarner Losh20010315: 80209946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 803ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 80409946a51SWarner Losh been replaced by tunables. See ata.4 for details. 805933b3269SWarner Losh 806933b3269SWarner Losh20010312: 807933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 808933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 809933b3269SWarner Losh 810933b3269SWarner Losh20010312: 811933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 812933b3269SWarner Losh instead of ad-hoc. 813933b3269SWarner Losh 814933b3269SWarner Losh20010310: 815f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 816933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 817933b3269SWarner Losh ssh might not work if you don't. 818933b3269SWarner Losh 81962353691SWarner Losh20010303: 82062353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 82162353691SWarner Losh which means that you must include the miibus in your kernel if 82262353691SWarner Losh you use the ed driver. 82362353691SWarner Losh 824d325cf65SWarner Losh20010220: 825d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 826d325cf65SWarner Losh safe to go back into the water. 827d325cf65SWarner Losh 828024daae6SWarner Losh20010211: 829024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 830024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 831024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 832024daae6SWarner Losh that before upgrading would be a good time to do a level 0 833024daae6SWarner Losh dump of your system. No, really, I mean it this time. 834024daae6SWarner Losh 835024daae6SWarner Losh To get to the new system, you'll need to use the following 836024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 837024daae6SWarner Losh don't have to move this to the updating section. 838024daae6SWarner Losh 839024daae6SWarner Losh To get around the installworld problem, do: 840024daae6SWarner Losh # cd /usr/src/usr.bin/sed 841024daae6SWarner Losh # make install 842024daae6SWarner Losh # cd /usr/src 843024daae6SWarner Losh # make installworld 844024daae6SWarner Losh If that doesn't work, then try: 845024daae6SWarner Losh # make -k installworld 846024daae6SWarner Losh # make installworld 847024daae6SWarner Losh 848024daae6SWarner Losh20010207: 849024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 850024daae6SWarner Losh do not include devfs in your kernel as problems result. 851024daae6SWarner Losh 852024daae6SWarner Losh20010205: 8537595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 854024daae6SWarner Losh Remove them from your config. 855024daae6SWarner Losh 8561e159248SWarner Losh20010122: 8571e159248SWarner Losh ****************************** WARNING ****************************** 8581e159248SWarner Losh buildkernel has been changed slightly 8591e159248SWarner Losh ****************************** WARNING ****************************** 8601e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 8611e159248SWarner Losh should update your scripts and make.conf accordingly. 8621e159248SWarner Losh 8631e159248SWarner Losh20010119: 8641e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 8651e159248SWarner Losh This requires a new config to build correctly. 8661e159248SWarner Losh 867aac7dfeaSWarner Losh20010116: 868ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 869aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 870aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 871aac7dfeaSWarner Losh 872aac7dfeaSWarner Losh20010110: 873aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 874aac7dfeaSWarner Losh 875aac7dfeaSWarner Losh20010102: 876aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 877aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 878aac7dfeaSWarner Losh 87963c90c9eSWarner Losh20010101: 88063c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 88163c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 8825fd2a895SWarner Losh dump while building termcap. You can work around this problem 88363c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 88463c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 88563c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 88663c90c9eSWarner Losh might have been ignored by the -k option. 88763c90c9eSWarner Losh 8885fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 8895fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 8905fd2a895SWarner Losh of this working. 8915fd2a895SWarner Losh 892aac7dfeaSWarner Losh20001228: 893aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 894ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 895aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 896aac7dfeaSWarner Losh 897de2bcc63SWarner Losh20001218: 898de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 899de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 900de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 901de2bcc63SWarner Losh cards will not be recognized without it. 902de2bcc63SWarner Losh 903960773f7SWarner Losh20001205: 904960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 905960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 906960773f7SWarner Losh adding the following in pam.conf: 907960773f7SWarner Losh 908960773f7SWarner Losh sshd auth sufficient pam_skey.so 909960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 910960773f7SWarner Losh sshd session required pam_permit.so 911960773f7SWarner Losh 9120acc635eSWarner Losh20001031: 9130acc635eSWarner Losh cvs updated to 1.11. 9140acc635eSWarner Losh 9150acc635eSWarner Losh20001020: 9160acc635eSWarner Losh The random device needs more entropy, so you need to make sure 9170acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 9180acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 9190acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 9200acc635eSWarner Losh workaround. 9210acc635eSWarner Losh 9220acc635eSWarner Losh20001010: 9230acc635eSWarner Losh ****************************** WARNING ****************************** 9240acc635eSWarner Losh Sendmail has been updated. 9250acc635eSWarner Losh ****************************** WARNING ****************************** 9260acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 9270acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 9280acc635eSWarner Losh is set. 9290acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 9300acc635eSWarner Losh commands. 9310acc635eSWarner Losh o Now using sendmail's version of vacation(1). 9320acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 9330acc635eSWarner Losh in /usr/share/sendmail/cf. 9340acc635eSWarner Losh o sendmail.cw changed to local-host-names 9350acc635eSWarner Losh 9360acc635eSWarner Losh More details can be found at 9370acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 9380acc635eSWarner Losh 9396e98a146SWarner Losh20001009: 9406e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 9416e98a146SWarner Losh your entire ports tree, or you will have problems. 9426e98a146SWarner Losh 9436e98a146SWarner Losh20001006: 944685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 9456e98a146SWarner Losh the installed miniperl. It is recommended that you delete 9466e98a146SWarner Losh /usr/bin/miniperl. 9476e98a146SWarner Losh 948073113a4SWarner Losh20001005: 949073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 950685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 951073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 952073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 953073113a4SWarner Losh tree for anything to work. 954073113a4SWarner Losh 9550acc635eSWarner Losh20000928: 9560acc635eSWarner Losh There was a change in the passwd format. Need more information. 9570acc635eSWarner Losh 958be3885b3SWarner Losh20000916: 959be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 960be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 961be3885b3SWarner Losh same time as your kernel. 962be3885b3SWarner Losh 96376ec9675SWarner Losh20000914: 96476ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 96576ec9675SWarner Losh include the device will cause suspended laptops losing time 96676ec9675SWarner Losh when they resume. Include 96776ec9675SWarner Losh device pmtimer 96876ec9675SWarner Losh in your config file and 96901b9a434SWarner Losh hint.pmtimer.0.at="isa" 97076ec9675SWarner Losh to your /boot/device.hints file. 97176ec9675SWarner Losh 972f4865386SMark Murray20000911: 973f4865386SMark Murray The random device has been turned into a (pseudo-)device, 974f4865386SMark Murray rather than an option. The supplied kernel config files have 975f4865386SMark Murray been updated. You will need to do something similar in your 976f4865386SMark Murray own kernel config file. 977f4865386SMark Murray Remove: 978f4865386SMark Murray options RANDOMDEV 979f4865386SMark Murray Add: 980f4865386SMark Murray device random 981f4865386SMark Murray If you prefer to load the loadable module, you need to do 982f4865386SMark Murray nothing. 983f4865386SMark Murray 984d594498fSWarner Losh20000909: 985d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 986d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 987d594498fSWarner Losh reflect this if you load this module at boot time. 988d594498fSWarner Losh The line should read: 989d594498fSWarner Losh random_load="YES" 990d594498fSWarner Losh 9910deb7ddcSWarner Losh20000907: 9920deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 99316eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 99416eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 99516eb772dSWarner Losh sure you don't have model loading problems which might at 99616eb772dSWarner Losh first blush appear related to SMP. 99752bf24e7SWarner Losh 9985a01880bSWarner Losh20000906: 9995a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 10005a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 10015a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 10025a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 10035a01880bSWarner Losh don't have one, and you have host.conf. 10045a01880bSWarner Losh 10052b41163cSWarner Losh20000905: 100638d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 100738d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 100838d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 100938d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 101038d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 101138d6ecd2SWarner Losh 101238d6ecd2SWarner Losh20000905: 10138aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 10148aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 10158aab4bc7SWarner Losh is /boot/kernel. 10168aab4bc7SWarner Losh 10178aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 101838d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 101938d6ecd2SWarner Losh installkernel/installworld dance. 10202b41163cSWarner Losh 1021d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1022d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1023d594498fSWarner Losh modules in that directory instead of finding them in the correct 1024d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1025d594498fSWarner Losh is that the linux module crashes your machine after the update. 1026d594498fSWarner Losh 1027d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1028d594498fSWarner Losh mv /modules.old /boot/kernel.old 1029d594498fSWarner Losh chflags noschg /kernel.old 1030d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1031d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1032d594498fSWarner Losh fi 1033d594498fSWarner Losh 1034c22a309cSWarner Losh20000904: 1035c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1036c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1037c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1038c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1039c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1040c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1041c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1042c22a309cSWarner Losh is not likely to be generated. 1043c22a309cSWarner Losh 1044fdb9f54dSWarner Losh20000825: 1045fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 10469c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 10479c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 10489c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 10499c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 10509c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 10519c1a7444SWarner Losh messages will appear after the boot loader tries to start the 10529c1a7444SWarner Losh kernel. 10539c1a7444SWarner Losh 10549c1a7444SWarner Losh20000821: 10559c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 10569c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 10579c1a7444SWarner Losh /boot/loader.conf. 1058fdb9f54dSWarner Losh 10598f250aa7SWarner Losh20000812: 10605da0d091SWarner Losh suidperl is now always built and installed on the system, but 10615da0d091SWarner Losh with permissions of 511. If you have applications that use 10625da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 10635da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 10645da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 10655da0d091SWarner Losh will fix this until the next build. 10665da0d091SWarner Losh 10675da0d091SWarner Losh20000812: 10688f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 10698f250aa7SWarner Losh visible changes that may immediately affect your configuration 10708f250aa7SWarner Losh include: 10718f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 10728f250aa7SWarner Losh - newaliases limited to root and trusted users 10738f250aa7SWarner Losh - MSA port (587) turned on by default 10748f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 10758f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 10768f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 10778f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 10788f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 10798f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 10808f250aa7SWarner Losh 108171c38472SWarner Losh20000810: 108271c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 108371c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 108471c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 108571c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 108671c38472SWarner Losh specific use for it. 108771c38472SWarner Losh 108871c38472SWarner Losh20000729: 108971c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 109071c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 109171c38472SWarner Losh /etc/rc.conf if they want to have the same setup 109271c38472SWarner Losh afterwards (unless the variables already are set, of course): 109371c38472SWarner Losh # Enable network daemons for user convenience. 109471c38472SWarner Losh inetd_enable="YES" 109571c38472SWarner Losh portmap_enable="YES" 109671c38472SWarner Losh sendmail_enable="YES" 109771c38472SWarner Losh 109871c38472SWarner Losh20000728: 109971c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 110071c38472SWarner Losh will need to change that to nullfs_load="YES". 110171c38472SWarner Losh 11021dece4a9SWarner Losh20000728: 11031dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 11041dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 11051dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 11061dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 11071dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 11081dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 11091dece4a9SWarner Losh to /MYKERNEL. 11101dece4a9SWarner Losh 1111409e887cSWarner Losh20000711: 1112409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1113409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1114409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1115409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1116409e887cSWarner Losh for details on potential problems that you might have and how 1117409e887cSWarner Losh to get around them. 1118409e887cSWarner Losh 1119409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1120409e887cSWarner Losh clauses above, you needn't worry. 1121409e887cSWarner Losh 1122409e887cSWarner Losh20000711: 1123409e887cSWarner Losh /etc/security has been updated to print the inode number of 1124409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1125409e887cSWarner Losh in the number of changed programs the first time when you run 1126409e887cSWarner Losh mergemaster to get a new /etc/security. 1127409e887cSWarner Losh 1128673d13f2SWarner Losh20000710: 1129673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1130673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1131673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1132673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1133673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1134673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1135673d13f2SWarner Losh errors. (see below, 20000624). 1136673d13f2SWarner Losh 1137bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 11381dece4a9SWarner Losh 1139673d13f2SWarner Losh20000709: 1140c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1141c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1142c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1143673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1144673d13f2SWarner Losh 1145e98e26cdSWarner Losh20000706: 1146e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1147e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1148e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1149f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1150e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 11512c021c6cSMark Ovens interim if needed. 1152e98e26cdSWarner Losh 1153e98e26cdSWarner Losh20000705: 1154e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1155e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1156e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1157e98e26cdSWarner Losh details. 1158e98e26cdSWarner Losh 1159c373950eSWarner Losh20000704: 11602f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 11612f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 11622f961bc8SWarner Losh 11632f961bc8SWarner Losh20000704: 1164c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1165c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1166c373950eSWarner Losh rc.d scripts that haven't been updated. 1167c373950eSWarner Losh 116827dc3a2bSWarner Losh20000630: 116927dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 117027dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 117127dc3a2bSWarner Losh which should be reported to des@freebsd.org. 117227dc3a2bSWarner Losh 1173b8c215acSWarner Losh20000625: 1174b8c215acSWarner Losh From approximately this date forward, one must have the crypto 117527dc3a2bSWarner Losh system installed in order to build the system and kernel. 117627dc3a2bSWarner Losh While not technically strictly true, one should treat it as 117727dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 117827dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 117927dc3a2bSWarner Losh were required. You should check with the latest collections 118027dc3a2bSWarner Losh to make sure that these haven't changed. 1181b8c215acSWarner Losh 11827b990719SWarner Losh20000624: 11837b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 11847b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 11857b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 11861a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 11877b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 11887b990719SWarner Losh openssh and openssl should not be used to generate keys from this 11897b990719SWarner Losh date to the completion of the work. 11907b990719SWarner Losh 119127dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 119227dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 119327dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 119427dc3a2bSWarner Losh recreate the random and urandom devices. 119527dc3a2bSWarner Losh 119681e54c50SWarner Losh20000622: 119781e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 119881e54c50SWarner Losh BSD license. You may need to remove your symbolic links 119981e54c50SWarner Losh that used to be required when updating. 120081e54c50SWarner Losh 120139943833SWarner Losh20000621: 12022c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 12032a2f33fbSDaniel Baker the config file update procedure. 12042a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1205c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 120659df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 120759df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 120839943833SWarner Losh 1209290f9ad8SWarner Losh20000620: 1210290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1211290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1212290f9ad8SWarner Losh that workaround will no longer be required. 1213290f9ad8SWarner Losh 121490fb6346SWarner Losh20000615: 121590fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 121690fb6346SWarner Losh ad driver. If you haven't done so already, you must update 121790fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 121890fb6346SWarner Losh devices. 121990fb6346SWarner Losh 1220f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1221f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1222f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1223f75f65bbSWarner Losh may work). 1224f75f65bbSWarner Losh 1225ba26da8eSWarner Losh20000612: 1226ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1227290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1228c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1229290f9ad8SWarner Losh to your config file to compile them in statically. The format 1230f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1231f54a3542SWarner Losh NEWCARD for examples of the new format. 1232290f9ad8SWarner Losh 12339698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 12349698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 12359698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 12369698f2c0SWarner Losh in it. 1237bbcc5149SWarner Losh 1238d65850ebSWarner Losh20000522: 1239ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1240d65850ebSWarner Losh building a kernel after this point is advised that they need 1241d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1242d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1243d65850ebSWarner Losh 1244d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1245d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1246d9583a00SWarner Losh is recommended that you don't set this option until the problem 1247d9583a00SWarner Losh is resolved. 1248d9583a00SWarner Losh 12498039cedeSWarner Losh20000513: 12508039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 12518039cedeSWarner Losh 1252d65850ebSWarner Losh20000510: 12538039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 12548039cedeSWarner Losh This will require some care in updating alphas. A new libstand 12558039cedeSWarner Losh is requires for the boot blocks to build properly. 12568039cedeSWarner Losh 12578039cedeSWarner Losh20000503: 12588039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 12598039cedeSWarner Losh is now available. 12608039cedeSWarner Losh 1261d65850ebSWarner Losh20000502: 1262d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1263d65850ebSWarner Losh connected to the kernel building instead. 1264d65850ebSWarner Losh 1265be149406SNik Clayton20000427: 12668039cedeSWarner Losh You may need to build gperf 12678039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 12688039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 12698039cedeSWarner Losh an option only in -current. 12708039cedeSWarner Losh 12712b8dd5f4SWarner Losh20000417: 12722b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1273f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 12742b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 12752b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 12762c021c6cSMark Ovens before you reboot, you'll need to issue: 12772b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 12782b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 12792b8dd5f4SWarner Losh 12808d9f1945SWarner Losh20000320: 12812b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 12822b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 12832b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1284ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 12852b8dd5f4SWarner Losh to the start of /etc/rc.conf. 12868d9f1945SWarner Losh 1287f8ab1dd6SWarner Losh20000319: 1288f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1289f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1290f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1291f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1292f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1293f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1294f8ab1dd6SWarner Losh 129519cada77SWarner Losh20000318: 1296f699bbbbSMark Ovens We've entered the traditional post release dumping party. 129719cada77SWarner Losh Large kernel changes are being committed and are in the 129819cada77SWarner Losh works. It is important to keep the systems' klds and kernel 129919cada77SWarner Losh in sync as kernel interfaces and structures are changing. 130019cada77SWarner Losh Before reporting kernel panics, make sure that all modules 130119cada77SWarner Losh that you are loading are up to date. 1302ba228352SWarner Losh 130319cada77SWarner Losh20000315: 13046d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 13056d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 13066d23c382SWarner Losh will do the trick. This isn't critical until you remove your 13076d23c382SWarner Losh wd device entries in /dev, at which point your system will not 13086d23c382SWarner Losh boot. 13096d23c382SWarner Losh 13106d23c382SWarner Losh20000315: 131119cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 131219cada77SWarner Losh to upgrade to 4.0 from 3.x. 131357199806SWarner Losh 1314dc0dbf5cSWarner LoshCOMMON ITEMS: 1315dc0dbf5cSWarner Losh 1316a24eff53SWarner Losh General Notes 1317a24eff53SWarner Losh ------------- 1318a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1319a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1320a24eff53SWarner Losh installworld. This is especially true when upgrading between 1321a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1322a24eff53SWarner Losh or several minor releases, or when several months have passed 1323a24eff53SWarner Losh on the -current branch). 1324a24eff53SWarner Losh 13255780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 13265780f3baSWarner Losh poisoning. This can happen because the make utility reads its 13275780f3baSWarner Losh environment when searching for values for global variables. 13285780f3baSWarner Losh To run your build attempts in an "environmental clean room", 13295780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 13305780f3baSWarner Losh page for more details. 13315780f3baSWarner Losh 1332dc0dbf5cSWarner Losh To build a kernel 1333dc0dbf5cSWarner Losh ----------------- 1334ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1335f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1336ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1337282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1338282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1339dc0dbf5cSWarner Losh 1340ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1341ba01eb20SWarner Losh -------------------------------------------------------------- 1342ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 134347d0d01fSWarner Losh config KERNEL_NAME_HERE 1344ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1345ba01eb20SWarner Losh make depend 1346ba01eb20SWarner Losh make 1347ba01eb20SWarner Losh make install 1348ba01eb20SWarner Losh 1349ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1350ba01eb20SWarner Losh 1351ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1352ba01eb20SWarner Losh ----------------------------------------------------------- 135363cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 135463cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 135563cb445eSWarner Losh 1356f643de42SWarner Losh <make sure you have good level 0 dumps> 135763cb445eSWarner Losh <maybe fix /etc/fstab> [7] 135863cb445eSWarner Losh make buildworld 135963cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 136063cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 136163cb445eSWarner Losh [1] 136263cb445eSWarner Losh <reboot in single user> [3] 136363cb445eSWarner Losh mergemaster -p [5] 136463cb445eSWarner Losh make installworld 136563cb445eSWarner Losh mergemaster [4] 136663cb445eSWarner Losh <reboot> 136763cb445eSWarner Losh 1368759f0aefSWarner Losh 1369f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1370f27b1fceSJoseph Koshy -------------------------------------------------- 1371f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1372f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1373f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1374f27b1fceSJoseph Koshy # size. 1375f27b1fceSJoseph Koshy 1376f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1377f27b1fceSJoseph Koshy <boot into -stable> 1378f27b1fceSJoseph Koshy make buildworld 1379f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1380f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1381f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1382f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1383f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1384f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1385f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1386f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1387f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1388f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1389f27b1fceSJoseph Koshy <reboot into current> 1390f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1391f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1392f27b1fceSJoseph Koshy <reboot> 1393f27b1fceSJoseph Koshy 1394f27b1fceSJoseph Koshy 1395f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1396f27b1fceSJoseph Koshy ---------------------------------------------- 13975c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 13985c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 13995c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 14005c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1401ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1402f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1403f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1404f643de42SWarner Losh # space on /. 1405f643de42SWarner Losh 1406f643de42SWarner Losh <make sure you have good level 0 dumps> 1407fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 140821c075eaSWarner Losh make buildworld [9] 1409c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1410d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1411be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1412fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1413fc8c157fSWarner Losh [1] 1414fc8c157fSWarner Losh <reboot in single user> [3] 1415835284beSWarner Losh mergemaster -p [5] 1416f8a4c901SWarner Losh rm -rf /usr/include/g++ 1417ba26da8eSWarner Losh make installworld 1418a6cd4f9dSWarner Losh mergemaster [4] 1419ba26da8eSWarner Losh <reboot> 1420ba26da8eSWarner Losh 1421fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1422fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1423fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1424fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1425fdb9f54dSWarner Losh the UPDATING entries. 1426ba26da8eSWarner Losh 14271dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 14281dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 14291dece4a9SWarner Losh your sources that you have read and understood all the recent 14301dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 14311dece4a9SWarner Losh much fewer pitfalls. 14321dece4a9SWarner Losh 1433134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1434134d2e86SWarner Losh should disable them at this point so they don't crash your 1435134d2e86SWarner Losh system on reboot. 1436134d2e86SWarner Losh 14379c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 14389c1a7444SWarner Losh your own device.hints to reflect your unique hardware 14399c1a7444SWarner Losh configuration. 14409c1a7444SWarner Losh 1441ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1442ee6e1fc3SWarner Losh fsck -p 1443ee6e1fc3SWarner Losh mount -u / 1444ee6e1fc3SWarner Losh mount -a 1445ee6e1fc3SWarner Losh cd /usr/src 144647d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1447f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1448f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1449b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1450b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1451b705ae10SWarner Losh be ignored while you proceed to the next step. 1452ee6e1fc3SWarner Losh 1453a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1454a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1455a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1456a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1457a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1458a6cd4f9dSWarner Losh for potential gotchas. 1459a6cd4f9dSWarner Losh 1460835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1461835284beSWarner Losh you may need to do this if you get unknown user in the following 1462835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1463835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1464835284beSWarner Losh install) after the buildworld before this step if you last updated 1465835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1466835284beSWarner Losh 1467bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1468bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1469bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1470bd79cf40SWarner Losh ok unload 1471bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1472bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1473bd79cf40SWarner Losh described here. 1474fc8c157fSWarner Losh 1475fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1476fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1477fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1478fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1479fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1480fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1481fc8c157fSWarner Losh 1482c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1483c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1484c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1485c74fe6afSWarner Losh that is hard to boot to recover. 1486c74fe6afSWarner Losh 148721c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 148821c075eaSWarner Losh cvs prune empty directories. 1489dc0dbf5cSWarner LoshFORMAT: 1490dc0dbf5cSWarner Losh 1491f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 14921fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1493f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1494f8ab1dd6SWarner Loshprevious releases if your system is older than this. 14951fc1a0dcSWarner Losh 1496e72fd46aSWarner LoshCopyright information: 1497e72fd46aSWarner Losh 14989698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1499e72fd46aSWarner Losh 1500772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1501772730c7SWarner Loshmodification, in full or in part, in any form or format of this 15029698f2c0SWarner Loshdocument are permitted without further permission from the author. 1503e72fd46aSWarner Losh 1504e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1505e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1506e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1507e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1508e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1509e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1510e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1511e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1512e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1513e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1514e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1515e72fd46aSWarner Losh 1516e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1517e72fd46aSWarner Loshauthor a beer. 1518e72fd46aSWarner Losh 151922306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1520772730c7SWarner Loshthis document. 1521772730c7SWarner Losh 152297d92980SPeter Wemm$FreeBSD$ 1523