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 20d0dc9183SWarner Losh20040414: 21d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 22d0dc9183SWarner Losh problems for your system, please disable it using the tunable 23d0dc9183SWarner Losh hw.pci.do_powerstate=0. 24d0dc9183SWarner Losh 25d0dc9183SWarner Losh20040412: 26d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 27d0dc9183SWarner Losh drive is still broken. 28d0dc9183SWarner Losh 29d0dc9183SWarner Losh20040410: 30d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 31d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 32d0dc9183SWarner Losh the unanticipated problems have been resolved. 33d0dc9183SWarner Losh 348633bbeaSBrooks Davis20040409: 358633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 368633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 378633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 388633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 3976c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 408633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 418633bbeaSBrooks Davis 42d40d033aSRobert Watson20040322: 43d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 44d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 45d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 46d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 47d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 48d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 49d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 50d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 51d40d033aSRobert Watson locking is merged to permit this to take place. 52d40d033aSRobert Watson 53ec9b318eSGarance A Drosehn20040310: 54ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 55ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 56ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 57ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 58ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 59ec9b318eSGarance A Drosehn 60fc28f1ffSMax Laier20040308: 61fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 62fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 634c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 644c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 65fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 66fc28f1ffSMax Laier pf system consists of the following three devices: 67fc28f1ffSMax Laier device pf # required 68fc28f1ffSMax Laier device pflog # optional 69fc28f1ffSMax Laier device pfsync # optional 70fc28f1ffSMax Laier 713aff5d06SDag-Erling Smørgrav20040303: 723aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 733aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 743aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 753aff5d06SDag-Erling Smørgrav 763aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 773aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 783aff5d06SDag-Erling Smørgrav 793aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 803aff5d06SDag-Erling Smørgrav to use libpthread instead. 813aff5d06SDag-Erling Smørgrav 82fd63c5b3SDag-Erling Smørgrav20040226: 839d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 84fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 85fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 86fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 87fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 88fd63c5b3SDag-Erling Smørgrav 89714ae42aSBruce M Simpson20040225: 90e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 91e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 92e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 93e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 94e07a40f3SBrian Feldman should remain unaffected. 95e07a40f3SBrian Feldman 96e07a40f3SBrian Feldman20040225: 97714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 98714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 99714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 100714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 101714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 102714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 103714ae42aSBruce M Simpson 104fbd2e692SAndre Oppermann20040224: 105fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 106fbd2e692SAndre Oppermann and related userland network utilities neccessary. 107fbd2e692SAndre Oppermann 108158b90daSWarner Losh20040222: 109158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 110158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 111158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 112158b90daSWarner Losh Drivers outside the tree will need to be updated. 113158b90daSWarner Losh 114b7b1e150SMike Makonnen20040207: 115b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 116b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 117b7b1e150SMike Makonnen 118aca89ee6SDaniel Eischen20040130: 119aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 120aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 121aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 122aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 123aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 124aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 125aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 126aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 127aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 128aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 129aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 130aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 131aca89ee6SDaniel Eischen do not work with libpthread. 132aca89ee6SDaniel Eischen 13368b7b3a9SAlex Dupre20040125: 13468b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 13568b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 13668b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 13768b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 13868b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 13968b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 14068b7b3a9SAlex Dupre 141ff46e0deSWarner Losh20040125: 142ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 143ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 144ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 145ff46e0deSWarner Losh 146ce41f4bfSRobert Watson20031213: 147ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 148ce41f4bfSRobert Watson if the login process is unable to successfully set the 149ce41f4bfSRobert Watson process credentials to include all groups defined for the 150ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 151ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 152ce41f4bfSRobert Watson defined, or they will be unable to log in. 153ce41f4bfSRobert Watson 154c124fa05SJohn Baldwin20031203: 155c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 156c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 157c124fa05SJohn Baldwin 1588ad1f5e4SHartmut Brandt20031112: 15930093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 16030093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 16197209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 16297209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 16397209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 16497209ca3SRobert Watson not know about the new system calls that support the new statfs 1653f631d52SMarcel Moolenaar structure. 1663f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 1673f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 1683f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 1693f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 1703f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 1713f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 1723f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 1733f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 1743f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 1753f631d52SMarcel Moolenaar these changes are installed. 17630093b05SWarner Losh 17730093b05SWarner Losh ****************************DANGER******************************* 17830093b05SWarner Losh 17930093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 18030093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 18130093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 18230093b05SWarner Losh kernel. 18364a18d6fSKirk McKusick 18464a18d6fSKirk McKusick20031112: 1858ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 1868ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 1878ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 1888ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 1898ad1f5e4SHartmut Brandt sync before rebooting. 1908ad1f5e4SHartmut Brandt 191c53a5d8fSJohn Baldwin20031111: 192c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 193c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 194c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 195c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 196c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 197c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 198c53a5d8fSJohn Baldwin 1998bf455a5SJohn Baldwin20031103: 2008bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 2018bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 2022a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 2038bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 2048bf455a5SJohn Baldwin 2059bf40edeSBrooks Davis20031031: 2069bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 2079bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 2089bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 2099bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 2109bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 2119bf40edeSBrooks Davis reflect this change. 2129bf40edeSBrooks Davis 21347a42c7aSPoul-Henning Kamp20030928: 21447a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 21547a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 21647a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 21747a42c7aSPoul-Henning Kamp 21807105342SMax Khon20030926: 21907105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 22007105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 22107105342SMax Khon 22217dcd026SSam Leffler20030925: 22317dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 22417dcd026SSam Leffler also be explicitly configured. Previously this dependency was 22517dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 22617dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 22717dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 22817dcd026SSam Leffler 229fedf1d01SBruce M Simpson20030923: 230fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 231fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 232fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 233fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 234fedf1d01SBruce M Simpson 235db38f9cbSJacques Vidrine20030915: 236db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 237db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 238db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 239db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 240db38f9cbSJacques Vidrine 241c09d2c2bSMike Makonnen20030829: 242c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 243c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 244c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 245c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 246c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 247c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 248c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 249c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 250c09d2c2bSMike Makonnen may or may not exist on your system. 251c09d2c2bSMike Makonnen 25217c159dcSSøren Schmidt20030824: 25317c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 25417c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 255f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 256f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 25717c159dcSSøren Schmidt 258c1f61aa9SDavid E. O'Brien20030819: 259c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 260c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 261c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 262c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 26369f7bcf3SWarner Losh 26438c962e7SNate Lawson20030728: 26538c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 26638c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 26738c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 26838c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 26938c962e7SNate Lawson so the quirk can be re-enabled. 27038c962e7SNate Lawson 27174111097SWarner Losh20030724: 27274111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 27374111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 27474111097SWarner Losh 275178cf4e9SWarner Losh20030722: 276178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 277178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 278178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 279178cf4e9SWarner Losh FPU hardware. 280178cf4e9SWarner Losh 281178cf4e9SWarner Losh20030714: 282178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 283178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 284178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 285178cf4e9SWarner Losh People should report those issues to current@. 286178cf4e9SWarner Losh 287157c629aSWarner Losh20030711: 288157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 2898b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 29005538fa9SWarner Losh /usr/obj. 291157c629aSWarner Losh 29274111097SWarner Losh20030610: 29374111097SWarner Losh Remove deprecated locale names and transition period code 29474111097SWarner Losh for them, finishing switching to the new scheme. Check your 29574111097SWarner Losh LANG environment variable. 29674111097SWarner Losh 29774111097SWarner Losh20030609: 29874111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 29974111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 30074111097SWarner Losh important to remember beforehand if your source tree is on 30174111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 30274111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 30374111097SWarner Losh kernel. 30474111097SWarner Losh 30574111097SWarner Losh20030605: 3066cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 3076cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 3086cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 3096cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 3106cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 3116cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 3126cc6353fSMarcel Moolenaar 3136cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 3146cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 3156cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 3166cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 3176cc6353fSMarcel Moolenaar : 3186cc6353fSMarcel Moolenaar 3196cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 3206cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 3216cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 3226cc6353fSMarcel Moolenaar 32352b47445SMark Murray20030505: 32452b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 32552b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 32652b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 32752b47445SMark Murray 328a26df538SWarner Losh20030502: 329a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 330a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 331a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 332a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 333a26df538SWarner Losh 3344b065e2cSDoug Barton20030501: 3354b065e2cSDoug Barton The old rc system has been removed. Please report any problems 3364b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 3374b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 3384b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 3394b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 3404b065e2cSDoug Barton utilizes these old scripts has also been removed. 3414b065e2cSDoug Barton 34281cda3d9SWarner Losh20030423: 34381cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 34481cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 34581cda3d9SWarner Losh work around in devd will be removed around 20030507. You 34681cda3d9SWarner Losh have until then to upgrade your kernel before updating 34781cda3d9SWarner Losh userland. In general, you should have a userland and 34881cda3d9SWarner Losh kernel that's in sync with each other. However, given the 34981cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 35081cda3d9SWarner Losh allowances are made. 35181cda3d9SWarner Losh 35247a657d1SRuslan Ermilov20030329: 35347a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 35447a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 35547a657d1SRuslan Ermilov while upgrading the system through a buildworld. 35647a657d1SRuslan Ermilov 35747a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 35847a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 35947a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 36047a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 36147a657d1SRuslan Ermilov 36247a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 36347a657d1SRuslan Ermilov make cleandir && make obj && \ 36447a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 36547a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 36647a657d1SRuslan Ermilov 3675d2af00cSGregory Neil Shapiro20030208: 3685d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 3695d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 3705d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 3715d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 3725d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 3735d2af00cSGregory Neil Shapiro 3745d2af00cSGregory Neil Shapiro20030128: 3759db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 376ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 3779db58771SPoul-Henning Kamp be removed when convenient. 3789db58771SPoul-Henning Kamp 3798d9b3f57SJake Burkholder20030126: 3808d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 3818d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 3828d9b3f57SJake Burkholder 3831c5efda5SJeff Roberson20030125: 3841c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 3851c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 386ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 3871c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 3881c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 3891c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 3901c5efda5SJeff Roberson 3919d1d64f5SWarner Losh20030115: 3929d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 3939d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 3949d1d64f5SWarner Losh properly. 3959d1d64f5SWarner Losh 396c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 397c9fdb80aSWarner Losh configured for point to point links to bring it more in line 398c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 399c9fdb80aSWarner Losh with NetBSD. 400c9fdb80aSWarner Losh 401161dc364SAlexander Kabaev20021222: 402161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 403161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 404161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 405161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 406161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 407161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 40884cc83efSAlexander Kabaev rebuilt. 409161dc364SAlexander Kabaev 410fb4c8061SMartin Blapp20021216: 411fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 41289056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 413fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 4149d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 415fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 416fb4c8061SMartin Blapp 41717d47eb3SGiorgos Keramidas20021202: 41817d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 41917d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 42017d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 42117d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 42217d47eb3SGiorgos Keramidas 423a4459294SBill Fenner20021029: 424a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 425a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 426a4459294SBill Fenner consumers in sync. 427a4459294SBill Fenner 428fc8c157fSWarner Losh20021024: 429c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 430c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 431c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 432c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 433c57404feSRuslan Ermilov partition really is on. The old device names have gone 434c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 435c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 436c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 43769f7bcf3SWarner Losh 438fd9e8bdaSAndrew Gallatin20021023: 439fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 440fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 441fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 442fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 443fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 444fd9e8bdaSAndrew Gallatin 445fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 446fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 447fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 448fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 449fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 450fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 451fd9e8bdaSAndrew Gallatin 452f8a4c901SWarner Losh20020831: 453f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 454f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 455f8a4c901SWarner Losh programs and libraries need to be recompiled. 456f8a4c901SWarner Losh 457f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 458f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 459f8a4c901SWarner Losh 460c2248fa2SJens Schweikhardt20020827: 461c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 462c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 463c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 464c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 465c2248fa2SJens Schweikhardt 4660d533e43SRuslan Ermilov20020815: 4670d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 4680d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 4690d533e43SRuslan Ermilov again. 4700d533e43SRuslan Ermilov 47133c1de7dSRuslan Ermilov20020729: 47233c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 47333c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 47433c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 47533c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 47633c1de7dSRuslan Ermilov 4772b877facSJulian Elischer20020702: 4782b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 4792b877facSJulian Elischer There are still some minor problems with some signals but the 4802b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 4812b877facSJulian Elischer but each can successfully complete multiple buildworlds. 4822b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 4832b877facSJulian Elischer 48406596d37SWarner Losh20020701: 48506596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 48606596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 48706596d37SWarner Losh GNOME. 48806596d37SWarner Losh 48995ba4330SJacques Vidrine20020511: 49095ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 49195ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 49295ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 49395ba4330SJacques Vidrine with the set-user-ID bit set. 49495ba4330SJacques Vidrine 495a81da3c9SDavid E. O'Brien20020510: 496f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 497f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 4984b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 499f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 500f50caf6fSDavid E. O'Brien 501f50caf6fSDavid E. O'Brien20020510: 502a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 503a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 504a81da3c9SDavid E. O'Brien and then do a cvs update. 505a81da3c9SDavid E. O'Brien 506528a0ef5SJacques Vidrine20020421: 507528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 508528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 509528a0ef5SJacques Vidrine 51085aa5a2eSGregory Neil Shapiro20020404: 51185aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 51285aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 51385aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 51485aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 51585aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 51685aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 51785aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 51885aa5a2eSGregory Neil Shapiro 5198f1e4358SRuslan Ermilov20020403: 5208f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 5218f1e4358SRuslan Ermilov 5222292c02eSWarner Losh20020315: 5232292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 5242292c02eSWarner Losh 52569f7bcf3SWarner Losh20020225: 52669f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 52769f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 52869f7bcf3SWarner Losh 5298f35c493SWarner Losh20020217: 5308f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 5318f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 5328f35c493SWarner Losh command line mail submission has changed. Be sure to run 5338f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 5348f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 5358f35c493SWarner Losh 536835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 537835284beSWarner Losh required in order for sendmail to run as a set-group-ID 538835284beSWarner Losh binary. A 'make installworld' will use the new user and group 539835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 540835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 541835284beSWarner Losh and group must be merged from src/etc/group and 542835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 543835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 544835284beSWarner Losh mergemaster before this will work if you are updating from a 545835284beSWarner Losh very old version of current. The updating recipe has changed 546835284beSWarner Losh as of this date. 547835284beSWarner Losh 548fa9401c1SWarner Losh20020112: 549fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 550fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 551fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 552fa9401c1SWarner Losh you have local modifications, you can use 553fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 554fa9401c1SWarner Losh /etc/pam.d. 555fa9401c1SWarner Losh 556fa9401c1SWarner Losh Please see the following url for more details: 557fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 55847d0d01fSWarner Losh20011229: 55947d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 56047d0d01fSWarner Losh networkfs_types, please note that it has changed 56147d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 56247d0d01fSWarner Losh 563514318a8SWarner Losh20011220: 564514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 565514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 566514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 567514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 568514318a8SWarner Losh version have now been merged back into the base system's 569514318a8SWarner Losh version now. The only user-visible change resulting from this 570514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 571514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 572514318a8SWarner Losh as well. (There has never been rc file support for 573514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 574514318a8SWarner Losh reverted by the time the changes are MFCed.) 575514318a8SWarner Losh 576514318a8SWarner Losh20011215: 577514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 578514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 579514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 580514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 581514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 582514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 583514318a8SWarner Losh will need to be customized then for `odd' densities using 584514318a8SWarner Losh fdcontrol(8). 585514318a8SWarner Losh 5862d22e2bfSWarner Losh20011209: 5872d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 5882d22e2bfSWarner Losh and truss(1) now works again. 5892d22e2bfSWarner Losh 5909e0428e2SWarner Losh20011207: 5919e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 5929e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 5939e0428e2SWarner Losh see 5949e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 5959e0428e2SWarner Losh for details. 5969e0428e2SWarner Losh 5979bab8c59SWarner Losh20011204: 5989bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 5999bab8c59SWarner Losh kernel and burncd to be in sync. 6009bab8c59SWarner Losh 601e57d8b01SWarner Losh20011203: 602e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 603e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 604e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 605e57d8b01SWarner Losh not there already. 606e57d8b01SWarner Losh 607e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 608e57d8b01SWarner Losh until the issue has been resolved. 609e57d8b01SWarner Losh 610b001d36fSJacques Vidrine20011202: 611b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 612b001d36fSJacques Vidrine patched. 613b001d36fSJacques Vidrine 6144b676ec1SWarner Losh20011126: 6154b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 6165ebbf43eSWarner Losh after this date. You need to do this only once. 6174b676ec1SWarner Losh 618d961e462SWarner Losh20011103: 619d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 620d961e462SWarner Losh edges may be left, but for the most part things should be 6214b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 622d961e462SWarner Losh 623d961e462SWarner Losh20011030: 624d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 625d961e462SWarner Losh choppy waves in the upgrade process. 626d961e462SWarner Losh 6271fe003b6SWarner Losh20011030: 628a4b6fda0SWarner Losh The asr driver problem has been resolved. 6291fe003b6SWarner Losh 6301fe003b6SWarner Losh20011027: 6311fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 6321fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 6331fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 6341fe003b6SWarner Losh try to use from this date forward. 6351fe003b6SWarner Losh 6361fe003b6SWarner Losh20011025: 6371fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 6381fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 6391fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 6401fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 6411fe003b6SWarner Losh TARGET_ARCH=i386. 6421fe003b6SWarner Losh 643d05f9643SWarner Losh20011001: 644d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 645d05f9643SWarner Losh You must recompile both the kernel and userland applications 646d05f9643SWarner Losh at the same time. 647d05f9643SWarner Losh 64858970f85SWarner Losh20010929: 64958970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 65058970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 65158970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 65258970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 6539d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 65458970f85SWarner Losh 65558970f85SWarner Losh20010927: 65658970f85SWarner Losh Some weird problems result from using ACPI on some machines. 65758970f85SWarner Losh To disable ACPI you can add 65866ff0e67SMax Khon hint.acpi.0.disabled="1" 65958970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 66058970f85SWarner Losh loader "ok" prompt). 66158970f85SWarner Losh 66258970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 66358970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 66458970f85SWarner Losh file and not list acpi in that list. 665378f4486SAlfred Perlstein 6665119d237SWarner Losh20010924: 6675119d237SWarner Losh The buildworld has been fixed. You may need to install 6685119d237SWarner Losh the 4.x compatibility libraries for some old binaries 6698b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 6708b039fffSWarner Losh get them installed on every installworld, or execute the 6718b039fffSWarner Losh following to get them installed only once: 6728b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 67358970f85SWarner Losh make all install 6748b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 6755119d237SWarner Losh 6763c293725SWarner Losh20010919: 6773c293725SWarner Losh There's a bug in the world build process. The cross-tools 6783c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 6793c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 680772730c7SWarner Losh workaround is to add 6813c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 6823c293725SWarner Losh before building world when upgrading from 4.x to current. This 6833c293725SWarner Losh can be removed afterwards. 6843c293725SWarner Losh 6853c293725SWarner Losh A proper fix to the buildworld target is needed. 6863c293725SWarner Losh 6873c293725SWarner Losh20010918: 6883c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 6893c293725SWarner Losh NFS may be unstable after this date. 6903c293725SWarner Losh 6913c293725SWarner Losh20010912: 6923c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 6933c293725SWarner Losh the kernel. While a few problems were introduced in the 6943c293725SWarner Losh initial commit, most of the major ones have been found and 6953c293725SWarner Losh corrected. 6963c293725SWarner Losh 6973c293725SWarner Losh20010901: 6983c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 6993c293725SWarner Losh arounds described in the 20010604 entry are now no longer 7003c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 7013c293725SWarner Losh have been rectified around this date. 7023c293725SWarner Losh 70398b17b95SWarner Losh20010823: 70498b17b95SWarner Losh named now runs as user bind and group bind rather than as 70598b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 70698b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 70798b17b95SWarner Losh and that group bind is available in /etc/group. Also make 70898b17b95SWarner Losh sure that user or group bind has read (and not write) 70998b17b95SWarner Losh permission for your name server configuration and that it 71098b17b95SWarner Losh has read and write permission for your slave zone files and 71198b17b95SWarner Losh directory. 71298b17b95SWarner Losh 71398b17b95SWarner Losh If you wish to continue to run named as root (a less secure 71498b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 71598b17b95SWarner Losh 71698b17b95SWarner Losh named_flags= 71798b17b95SWarner Losh 7187b9786edSMark Murray20010709: 7197b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 7207b9786edSMark Murray the ability of the shared library major number to handle. 7217b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 7227b9786edSMark Murray solution is to rebuild those ports. 7237b9786edSMark Murray 7241d28950eSWarner Losh20010628: 7251d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 7261d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 7271d28950eSWarner Losh 728e72fd46aSWarner Losh20010625: 72998b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 73098b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 73198b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 73298b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 73398b17b95SWarner Losh IRQ configuration needs more safety belts. 73416de1a07SWarner Losh 7350d415dffSWarner Losh20010617: 736e72fd46aSWarner Losh Softupdates problems have been corrected. 7370d415dffSWarner Losh 7380d415dffSWarner Losh20010614: 7390d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 7400d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 7410d415dffSWarner Losh kernel building methods. 7420d415dffSWarner Losh 7438b9959adSWarner Losh20010613: 7448b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 7458b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 746e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 747e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 7488b9959adSWarner Losh 749e72fd46aSWarner Losh20010613: 7508b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 751e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 752e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 7538b9959adSWarner Losh 7540d415dffSWarner Losh20010612: 7550d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 7560d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 7570d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 7580d415dffSWarner Losh work around this issue, please use only one or the other mechanism 7590d415dffSWarner Losh until this bug is fixed. 7600d415dffSWarner Losh 761e72fd46aSWarner Losh Please note that a feature of config is that if you have config 762e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 763ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 764e72fd46aSWarner Losh 7650d415dffSWarner Losh20010610: 7660d415dffSWarner Losh Locale names have changed to match other systems better. 7670d415dffSWarner Losh 7686ccdb5e4SWarner Losh20010604: 7696ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 7706ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 7716ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 7723590182eSWarner Losh Interrupt storms look a lot like a hang. 7733590182eSWarner Losh 7743590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 7753590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 7763590182eSWarner Losh it is). 7773590182eSWarner Losh 7783590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 7793590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 7803590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 7813590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 7826ccdb5e4SWarner Losh 7830bc62786SWarner Losh20010530: 7840bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 7850bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 7860bc62786SWarner Losh a limited time. If you see 7870bc62786SWarner Losh 7880bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 7890bc62786SWarner Losh 7900bc62786SWarner Losh in your makeworld, then you need to migrate towards using 7910bc62786SWarner Losh COPY=-C. 7920bc62786SWarner Losh 79368a38c6cSWarner Losh20010525: 794b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 795c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 796c4f4a728SWarner Losh definitely is in bad shape. 79768a38c6cSWarner Losh 798ed0f29caSWarner Losh20010521: 799ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 800ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 801ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 802ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 803ed0f29caSWarner Losh is 804ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 805ed0f29caSWarner Losh 80680c16af9SWarner Losh20010520: 80768a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 80880c16af9SWarner Losh 80980c16af9SWarner Losh20010519: 81080c16af9SWarner Losh pccard has had much reorganizational work done to it over 81180c16af9SWarner Losh the past few days. Everything should still work, but if 81280c16af9SWarner Losh not, please contact imp@freebsd.org. 81380c16af9SWarner Losh 814a45f2d05SWarner Losh20010517: 815a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 816a45f2d05SWarner Losh userland at the same time. 817a45f2d05SWarner Losh 818a45f2d05SWarner Losh20010517: 819a45f2d05SWarner Losh New ncurses imported. 820a45f2d05SWarner Losh 8212988afcaSWarner Losh20010512: 8222988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 8232988afcaSWarner Losh will be the only way to go starting July 1. 8242988afcaSWarner Losh 8251a33dba7SWarner Losh20010504: 8261a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 8271a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 8281a33dba7SWarner Losh 82909946a51SWarner Losh20010502: 83009946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 83109946a51SWarner Losh 83209946a51SWarner Losh20010501: 83309946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 83409946a51SWarner Losh 83509946a51SWarner Losh20010430: 836a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 83709946a51SWarner Losh go back in the water. 83809946a51SWarner Losh 83909946a51SWarner Losh20010429: 84009946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 84109946a51SWarner Losh this date, but before the correction date. 84209946a51SWarner Losh 84391dd3b53SWarner Losh20010423: 84491dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 84591dd3b53SWarner Losh 84691dd3b53SWarner Losh20010411: 84791dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 84891dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 84991dd3b53SWarner Losh Update only if you understand that you must not use the old 85091dd3b53SWarner Losh fsck with the new kernel ever. 85191dd3b53SWarner Losh 852933b3269SWarner Losh20010330: 853933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 854c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 855933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 856933b3269SWarner Losh 857933b3269SWarner Losh20010319: 858933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 859933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 860933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 861f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 86209946a51SWarner Losh 86309946a51SWarner Losh20010315: 86409946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 865ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 86609946a51SWarner Losh been replaced by tunables. See ata.4 for details. 867933b3269SWarner Losh 868933b3269SWarner Losh20010312: 869933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 870933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 871933b3269SWarner Losh 872933b3269SWarner Losh20010312: 873933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 874933b3269SWarner Losh instead of ad-hoc. 875933b3269SWarner Losh 876933b3269SWarner Losh20010310: 877f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 878933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 879933b3269SWarner Losh ssh might not work if you don't. 880933b3269SWarner Losh 88162353691SWarner Losh20010303: 88262353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 88362353691SWarner Losh which means that you must include the miibus in your kernel if 88462353691SWarner Losh you use the ed driver. 88562353691SWarner Losh 886d325cf65SWarner Losh20010220: 887d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 888d325cf65SWarner Losh safe to go back into the water. 889d325cf65SWarner Losh 890024daae6SWarner Losh20010211: 891024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 892024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 893024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 894024daae6SWarner Losh that before upgrading would be a good time to do a level 0 895024daae6SWarner Losh dump of your system. No, really, I mean it this time. 896024daae6SWarner Losh 897024daae6SWarner Losh To get to the new system, you'll need to use the following 898024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 899024daae6SWarner Losh don't have to move this to the updating section. 900024daae6SWarner Losh 901024daae6SWarner Losh To get around the installworld problem, do: 902024daae6SWarner Losh # cd /usr/src/usr.bin/sed 903024daae6SWarner Losh # make install 904024daae6SWarner Losh # cd /usr/src 905024daae6SWarner Losh # make installworld 906024daae6SWarner Losh If that doesn't work, then try: 907024daae6SWarner Losh # make -k installworld 908024daae6SWarner Losh # make installworld 909024daae6SWarner Losh 910024daae6SWarner Losh20010207: 911024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 912024daae6SWarner Losh do not include devfs in your kernel as problems result. 913024daae6SWarner Losh 914024daae6SWarner Losh20010205: 9157595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 916024daae6SWarner Losh Remove them from your config. 917024daae6SWarner Losh 9181e159248SWarner Losh20010122: 9191e159248SWarner Losh ****************************** WARNING ****************************** 9201e159248SWarner Losh buildkernel has been changed slightly 9211e159248SWarner Losh ****************************** WARNING ****************************** 9221e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 9231e159248SWarner Losh should update your scripts and make.conf accordingly. 9241e159248SWarner Losh 9251e159248SWarner Losh20010119: 9261e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 9271e159248SWarner Losh This requires a new config to build correctly. 9281e159248SWarner Losh 929aac7dfeaSWarner Losh20010116: 930ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 931aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 932aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 933aac7dfeaSWarner Losh 934aac7dfeaSWarner Losh20010110: 935aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 936aac7dfeaSWarner Losh 937aac7dfeaSWarner Losh20010102: 938aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 939aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 940aac7dfeaSWarner Losh 94163c90c9eSWarner Losh20010101: 94263c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 94363c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 9445fd2a895SWarner Losh dump while building termcap. You can work around this problem 94563c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 94663c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 94763c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 94863c90c9eSWarner Losh might have been ignored by the -k option. 94963c90c9eSWarner Losh 9505fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 9515fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 9525fd2a895SWarner Losh of this working. 9535fd2a895SWarner Losh 954aac7dfeaSWarner Losh20001228: 955aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 956ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 957aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 958aac7dfeaSWarner Losh 959de2bcc63SWarner Losh20001218: 960de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 961de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 962de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 963de2bcc63SWarner Losh cards will not be recognized without it. 964de2bcc63SWarner Losh 965960773f7SWarner Losh20001205: 966960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 967960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 968960773f7SWarner Losh adding the following in pam.conf: 969960773f7SWarner Losh 970960773f7SWarner Losh sshd auth sufficient pam_skey.so 971960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 972960773f7SWarner Losh sshd session required pam_permit.so 973960773f7SWarner Losh 9740acc635eSWarner Losh20001031: 9750acc635eSWarner Losh cvs updated to 1.11. 9760acc635eSWarner Losh 9770acc635eSWarner Losh20001020: 9780acc635eSWarner Losh The random device needs more entropy, so you need to make sure 9790acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 9800acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 9810acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 9820acc635eSWarner Losh workaround. 9830acc635eSWarner Losh 9840acc635eSWarner Losh20001010: 9850acc635eSWarner Losh ****************************** WARNING ****************************** 9860acc635eSWarner Losh Sendmail has been updated. 9870acc635eSWarner Losh ****************************** WARNING ****************************** 9880acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 9890acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 9900acc635eSWarner Losh is set. 9910acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 9920acc635eSWarner Losh commands. 9930acc635eSWarner Losh o Now using sendmail's version of vacation(1). 9940acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 9950acc635eSWarner Losh in /usr/share/sendmail/cf. 9960acc635eSWarner Losh o sendmail.cw changed to local-host-names 9970acc635eSWarner Losh 9980acc635eSWarner Losh More details can be found at 9990acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 10000acc635eSWarner Losh 10016e98a146SWarner Losh20001009: 10026e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 10036e98a146SWarner Losh your entire ports tree, or you will have problems. 10046e98a146SWarner Losh 10056e98a146SWarner Losh20001006: 1006685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 10076e98a146SWarner Losh the installed miniperl. It is recommended that you delete 10086e98a146SWarner Losh /usr/bin/miniperl. 10096e98a146SWarner Losh 1010073113a4SWarner Losh20001005: 1011073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1012685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1013073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1014073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1015073113a4SWarner Losh tree for anything to work. 1016073113a4SWarner Losh 10170acc635eSWarner Losh20000928: 10180acc635eSWarner Losh There was a change in the passwd format. Need more information. 10190acc635eSWarner Losh 1020be3885b3SWarner Losh20000916: 1021be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1022be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1023be3885b3SWarner Losh same time as your kernel. 1024be3885b3SWarner Losh 102576ec9675SWarner Losh20000914: 102676ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 102776ec9675SWarner Losh include the device will cause suspended laptops losing time 102876ec9675SWarner Losh when they resume. Include 102976ec9675SWarner Losh device pmtimer 103076ec9675SWarner Losh in your config file and 103101b9a434SWarner Losh hint.pmtimer.0.at="isa" 103276ec9675SWarner Losh to your /boot/device.hints file. 103376ec9675SWarner Losh 1034f4865386SMark Murray20000911: 1035f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1036f4865386SMark Murray rather than an option. The supplied kernel config files have 1037f4865386SMark Murray been updated. You will need to do something similar in your 1038f4865386SMark Murray own kernel config file. 1039f4865386SMark Murray Remove: 1040f4865386SMark Murray options RANDOMDEV 1041f4865386SMark Murray Add: 1042f4865386SMark Murray device random 1043f4865386SMark Murray If you prefer to load the loadable module, you need to do 1044f4865386SMark Murray nothing. 1045f4865386SMark Murray 1046d594498fSWarner Losh20000909: 1047d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1048d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1049d594498fSWarner Losh reflect this if you load this module at boot time. 1050d594498fSWarner Losh The line should read: 1051d594498fSWarner Losh random_load="YES" 1052d594498fSWarner Losh 10530deb7ddcSWarner Losh20000907: 10540deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 105516eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 105616eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 105716eb772dSWarner Losh sure you don't have model loading problems which might at 105816eb772dSWarner Losh first blush appear related to SMP. 105952bf24e7SWarner Losh 10605a01880bSWarner Losh20000906: 10615a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 10625a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 10635a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 10645a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 10655a01880bSWarner Losh don't have one, and you have host.conf. 10665a01880bSWarner Losh 10672b41163cSWarner Losh20000905: 106838d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 106938d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 107038d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 107138d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 107238d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 107338d6ecd2SWarner Losh 107438d6ecd2SWarner Losh20000905: 10758aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 10768aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 10778aab4bc7SWarner Losh is /boot/kernel. 10788aab4bc7SWarner Losh 10798aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 108038d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 108138d6ecd2SWarner Losh installkernel/installworld dance. 10822b41163cSWarner Losh 1083d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1084d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1085d594498fSWarner Losh modules in that directory instead of finding them in the correct 1086d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1087d594498fSWarner Losh is that the linux module crashes your machine after the update. 1088d594498fSWarner Losh 1089d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1090d594498fSWarner Losh mv /modules.old /boot/kernel.old 1091d594498fSWarner Losh chflags noschg /kernel.old 1092d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1093d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1094d594498fSWarner Losh fi 1095d594498fSWarner Losh 1096c22a309cSWarner Losh20000904: 1097c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1098c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1099c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1100c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1101c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1102c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1103c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1104c22a309cSWarner Losh is not likely to be generated. 1105c22a309cSWarner Losh 1106fdb9f54dSWarner Losh20000825: 1107fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 11089c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 11099c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 11109c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 11119c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 11129c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 11139c1a7444SWarner Losh messages will appear after the boot loader tries to start the 11149c1a7444SWarner Losh kernel. 11159c1a7444SWarner Losh 11169c1a7444SWarner Losh20000821: 11179c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 11189c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 11199c1a7444SWarner Losh /boot/loader.conf. 1120fdb9f54dSWarner Losh 11218f250aa7SWarner Losh20000812: 11225da0d091SWarner Losh suidperl is now always built and installed on the system, but 11235da0d091SWarner Losh with permissions of 511. If you have applications that use 11245da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 11255da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 11265da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 11275da0d091SWarner Losh will fix this until the next build. 11285da0d091SWarner Losh 11295da0d091SWarner Losh20000812: 11308f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 11318f250aa7SWarner Losh visible changes that may immediately affect your configuration 11328f250aa7SWarner Losh include: 11338f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 11348f250aa7SWarner Losh - newaliases limited to root and trusted users 11358f250aa7SWarner Losh - MSA port (587) turned on by default 11368f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 11378f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 11388f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 11398f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 11408f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 11418f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 11428f250aa7SWarner Losh 114371c38472SWarner Losh20000810: 114471c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 114571c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 114671c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 114771c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 114871c38472SWarner Losh specific use for it. 114971c38472SWarner Losh 115071c38472SWarner Losh20000729: 115171c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 115271c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 115371c38472SWarner Losh /etc/rc.conf if they want to have the same setup 115471c38472SWarner Losh afterwards (unless the variables already are set, of course): 115571c38472SWarner Losh # Enable network daemons for user convenience. 115671c38472SWarner Losh inetd_enable="YES" 115771c38472SWarner Losh portmap_enable="YES" 115871c38472SWarner Losh sendmail_enable="YES" 115971c38472SWarner Losh 116071c38472SWarner Losh20000728: 116171c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 116271c38472SWarner Losh will need to change that to nullfs_load="YES". 116371c38472SWarner Losh 11641dece4a9SWarner Losh20000728: 11651dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 11661dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 11671dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 11681dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 11691dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 11701dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 11711dece4a9SWarner Losh to /MYKERNEL. 11721dece4a9SWarner Losh 1173409e887cSWarner Losh20000711: 1174409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1175409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1176409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1177409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1178409e887cSWarner Losh for details on potential problems that you might have and how 1179409e887cSWarner Losh to get around them. 1180409e887cSWarner Losh 1181409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1182409e887cSWarner Losh clauses above, you needn't worry. 1183409e887cSWarner Losh 1184409e887cSWarner Losh20000711: 1185409e887cSWarner Losh /etc/security has been updated to print the inode number of 1186409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1187409e887cSWarner Losh in the number of changed programs the first time when you run 1188409e887cSWarner Losh mergemaster to get a new /etc/security. 1189409e887cSWarner Losh 1190673d13f2SWarner Losh20000710: 1191673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1192673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1193673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1194673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1195673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1196673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1197673d13f2SWarner Losh errors. (see below, 20000624). 1198673d13f2SWarner Losh 1199bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 12001dece4a9SWarner Losh 1201673d13f2SWarner Losh20000709: 1202c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1203c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1204c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1205673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1206673d13f2SWarner Losh 1207e98e26cdSWarner Losh20000706: 1208e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1209e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1210e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1211f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1212e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 12132c021c6cSMark Ovens interim if needed. 1214e98e26cdSWarner Losh 1215e98e26cdSWarner Losh20000705: 1216e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1217e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1218e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1219e98e26cdSWarner Losh details. 1220e98e26cdSWarner Losh 1221c373950eSWarner Losh20000704: 12222f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 12232f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 12242f961bc8SWarner Losh 12252f961bc8SWarner Losh20000704: 1226c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1227c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1228c373950eSWarner Losh rc.d scripts that haven't been updated. 1229c373950eSWarner Losh 123027dc3a2bSWarner Losh20000630: 123127dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 123227dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 123327dc3a2bSWarner Losh which should be reported to des@freebsd.org. 123427dc3a2bSWarner Losh 1235b8c215acSWarner Losh20000625: 1236b8c215acSWarner Losh From approximately this date forward, one must have the crypto 123727dc3a2bSWarner Losh system installed in order to build the system and kernel. 123827dc3a2bSWarner Losh While not technically strictly true, one should treat it as 123927dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 124027dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 124127dc3a2bSWarner Losh were required. You should check with the latest collections 124227dc3a2bSWarner Losh to make sure that these haven't changed. 1243b8c215acSWarner Losh 12447b990719SWarner Losh20000624: 12457b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 12467b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 12477b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 12481a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 12497b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 12507b990719SWarner Losh openssh and openssl should not be used to generate keys from this 12517b990719SWarner Losh date to the completion of the work. 12527b990719SWarner Losh 125327dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 125427dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 125527dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 125627dc3a2bSWarner Losh recreate the random and urandom devices. 125727dc3a2bSWarner Losh 125881e54c50SWarner Losh20000622: 125981e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 126081e54c50SWarner Losh BSD license. You may need to remove your symbolic links 126181e54c50SWarner Losh that used to be required when updating. 126281e54c50SWarner Losh 126339943833SWarner Losh20000621: 12642c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 12652a2f33fbSDaniel Baker the config file update procedure. 12662a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1267c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 126859df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 126959df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 127039943833SWarner Losh 1271290f9ad8SWarner Losh20000620: 1272290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1273290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1274290f9ad8SWarner Losh that workaround will no longer be required. 1275290f9ad8SWarner Losh 127690fb6346SWarner Losh20000615: 127790fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 127890fb6346SWarner Losh ad driver. If you haven't done so already, you must update 127990fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 128090fb6346SWarner Losh devices. 128190fb6346SWarner Losh 1282f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1283f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1284f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1285f75f65bbSWarner Losh may work). 1286f75f65bbSWarner Losh 1287ba26da8eSWarner Losh20000612: 1288ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1289290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1290c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1291290f9ad8SWarner Losh to your config file to compile them in statically. The format 1292f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1293f54a3542SWarner Losh NEWCARD for examples of the new format. 1294290f9ad8SWarner Losh 12959698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 12969698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 12979698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 12989698f2c0SWarner Losh in it. 1299bbcc5149SWarner Losh 1300d65850ebSWarner Losh20000522: 1301ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1302d65850ebSWarner Losh building a kernel after this point is advised that they need 1303d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1304d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1305d65850ebSWarner Losh 1306d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1307d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1308d9583a00SWarner Losh is recommended that you don't set this option until the problem 1309d9583a00SWarner Losh is resolved. 1310d9583a00SWarner Losh 13118039cedeSWarner Losh20000513: 13128039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 13138039cedeSWarner Losh 1314d65850ebSWarner Losh20000510: 13158039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 13168039cedeSWarner Losh This will require some care in updating alphas. A new libstand 13178039cedeSWarner Losh is requires for the boot blocks to build properly. 13188039cedeSWarner Losh 13198039cedeSWarner Losh20000503: 13208039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 13218039cedeSWarner Losh is now available. 13228039cedeSWarner Losh 1323d65850ebSWarner Losh20000502: 1324d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1325d65850ebSWarner Losh connected to the kernel building instead. 1326d65850ebSWarner Losh 1327be149406SNik Clayton20000427: 13288039cedeSWarner Losh You may need to build gperf 13298039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 13308039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 13318039cedeSWarner Losh an option only in -current. 13328039cedeSWarner Losh 13332b8dd5f4SWarner Losh20000417: 13342b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1335f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 13362b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 13372b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 13382c021c6cSMark Ovens before you reboot, you'll need to issue: 13392b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 13402b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 13412b8dd5f4SWarner Losh 13428d9f1945SWarner Losh20000320: 13432b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 13442b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 13452b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1346ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 13472b8dd5f4SWarner Losh to the start of /etc/rc.conf. 13488d9f1945SWarner Losh 1349f8ab1dd6SWarner Losh20000319: 1350f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1351f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1352f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1353f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1354f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1355f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1356f8ab1dd6SWarner Losh 135719cada77SWarner Losh20000318: 1358f699bbbbSMark Ovens We've entered the traditional post release dumping party. 135919cada77SWarner Losh Large kernel changes are being committed and are in the 136019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 136119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 136219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 136319cada77SWarner Losh that you are loading are up to date. 1364ba228352SWarner Losh 136519cada77SWarner Losh20000315: 13666d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 13676d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 13686d23c382SWarner Losh will do the trick. This isn't critical until you remove your 13696d23c382SWarner Losh wd device entries in /dev, at which point your system will not 13706d23c382SWarner Losh boot. 13716d23c382SWarner Losh 13726d23c382SWarner Losh20000315: 137319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 137419cada77SWarner Losh to upgrade to 4.0 from 3.x. 137557199806SWarner Losh 1376dc0dbf5cSWarner LoshCOMMON ITEMS: 1377dc0dbf5cSWarner Losh 1378a24eff53SWarner Losh General Notes 1379a24eff53SWarner Losh ------------- 1380a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1381a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1382a24eff53SWarner Losh installworld. This is especially true when upgrading between 1383a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1384a24eff53SWarner Losh or several minor releases, or when several months have passed 1385a24eff53SWarner Losh on the -current branch). 1386a24eff53SWarner Losh 13875780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 13885780f3baSWarner Losh poisoning. This can happen because the make utility reads its 13895780f3baSWarner Losh environment when searching for values for global variables. 13905780f3baSWarner Losh To run your build attempts in an "environmental clean room", 13915780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 13925780f3baSWarner Losh page for more details. 13935780f3baSWarner Losh 1394dc0dbf5cSWarner Losh To build a kernel 1395dc0dbf5cSWarner Losh ----------------- 1396ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1397f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1398ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1399282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1400282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1401dc0dbf5cSWarner Losh 1402ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1403ba01eb20SWarner Losh -------------------------------------------------------------- 14040fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 14050fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 14060fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 14070fbd2da9SKen Smith 14080fbd2da9SKen Smith cd src/sys/${arch}/conf 140947d0d01fSWarner Losh config KERNEL_NAME_HERE 14100fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1411ba01eb20SWarner Losh make depend 1412ba01eb20SWarner Losh make 1413ba01eb20SWarner Losh make install 1414ba01eb20SWarner Losh 1415ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1416ba01eb20SWarner Losh 1417ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1418ba01eb20SWarner Losh ----------------------------------------------------------- 141963cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 142063cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 142163cb445eSWarner Losh 1422f643de42SWarner Losh <make sure you have good level 0 dumps> 142363cb445eSWarner Losh <maybe fix /etc/fstab> [7] 142463cb445eSWarner Losh make buildworld 142563cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 142663cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 142763cb445eSWarner Losh [1] 142863cb445eSWarner Losh <reboot in single user> [3] 14298633bbeaSBrooks Davis /etc/rc.d/preseedrandom [10] 143063cb445eSWarner Losh mergemaster -p [5] 143163cb445eSWarner Losh make installworld 143263cb445eSWarner Losh mergemaster [4] 143363cb445eSWarner Losh <reboot> 143463cb445eSWarner Losh 1435759f0aefSWarner Losh 1436f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1437f27b1fceSJoseph Koshy -------------------------------------------------- 1438f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1439f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1440f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1441f27b1fceSJoseph Koshy # size. 1442f27b1fceSJoseph Koshy 1443f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1444f27b1fceSJoseph Koshy <boot into -stable> 1445f27b1fceSJoseph Koshy make buildworld 1446f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1447f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1448f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1449f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1450f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1451f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1452f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1453f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1454f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1455f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1456f27b1fceSJoseph Koshy <reboot into current> 1457f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1458f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1459f27b1fceSJoseph Koshy <reboot> 1460f27b1fceSJoseph Koshy 1461f27b1fceSJoseph Koshy 1462f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1463f27b1fceSJoseph Koshy ---------------------------------------------- 14645c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 14655c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 14665c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 14675c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1468ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1469f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1470f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1471f643de42SWarner Losh # space on /. 1472f643de42SWarner Losh 1473f643de42SWarner Losh <make sure you have good level 0 dumps> 1474fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 147521c075eaSWarner Losh make buildworld [9] 1476c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1477d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1478be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1479fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1480fc8c157fSWarner Losh [1] 1481fc8c157fSWarner Losh <reboot in single user> [3] 14828633bbeaSBrooks Davis /etc/rc.d/preseedrandom [10] 1483835284beSWarner Losh mergemaster -p [5] 1484f8a4c901SWarner Losh rm -rf /usr/include/g++ 1485ba26da8eSWarner Losh make installworld 1486a6cd4f9dSWarner Losh mergemaster [4] 1487ba26da8eSWarner Losh <reboot> 1488ba26da8eSWarner Losh 1489fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1490fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1491fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1492fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1493fdb9f54dSWarner Losh the UPDATING entries. 1494ba26da8eSWarner Losh 14951dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 14961dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 14971dece4a9SWarner Losh your sources that you have read and understood all the recent 14981dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 14991dece4a9SWarner Losh much fewer pitfalls. 15001dece4a9SWarner Losh 1501134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1502134d2e86SWarner Losh should disable them at this point so they don't crash your 1503134d2e86SWarner Losh system on reboot. 1504134d2e86SWarner Losh 15059c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 15069c1a7444SWarner Losh your own device.hints to reflect your unique hardware 15079c1a7444SWarner Losh configuration. 15089c1a7444SWarner Losh 1509ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1510ee6e1fc3SWarner Losh fsck -p 1511ee6e1fc3SWarner Losh mount -u / 1512ee6e1fc3SWarner Losh mount -a 1513ee6e1fc3SWarner Losh cd /usr/src 151447d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1515f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1516f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1517b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1518b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1519b705ae10SWarner Losh be ignored while you proceed to the next step. 1520ee6e1fc3SWarner Losh 1521a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1522a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1523a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1524a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1525a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1526a6cd4f9dSWarner Losh for potential gotchas. 1527a6cd4f9dSWarner Losh 1528835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1529835284beSWarner Losh you may need to do this if you get unknown user in the following 1530835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1531835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1532835284beSWarner Losh install) after the buildworld before this step if you last updated 1533835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1534835284beSWarner Losh 1535bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1536bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1537bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1538bd79cf40SWarner Losh ok unload 1539bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1540bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1541bd79cf40SWarner Losh described here. 1542fc8c157fSWarner Losh 1543fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1544fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1545fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1546fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1547fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1548fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1549fc8c157fSWarner Losh 1550c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1551c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1552c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1553c74fe6afSWarner Losh that is hard to boot to recover. 1554c74fe6afSWarner Losh 155521c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 155621c075eaSWarner Losh cvs prune empty directories. 15578633bbeaSBrooks Davis 15588633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 15598633bbeaSBrooks Davis initialized by feeding data into it. /etc/rc.d/preseedrandom 15608633bbeaSBrooks Davis takes care of this. 1561dc0dbf5cSWarner LoshFORMAT: 1562dc0dbf5cSWarner Losh 1563f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 15641fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1565f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1566f8ab1dd6SWarner Loshprevious releases if your system is older than this. 15671fc1a0dcSWarner Losh 1568e72fd46aSWarner LoshCopyright information: 1569e72fd46aSWarner Losh 15709698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1571e72fd46aSWarner Losh 1572772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1573772730c7SWarner Loshmodification, in full or in part, in any form or format of this 15749698f2c0SWarner Loshdocument are permitted without further permission from the author. 1575e72fd46aSWarner Losh 1576e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1577e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1578e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1579e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1580e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1581e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1582e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1583e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1584e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1585e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1586e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1587e72fd46aSWarner Losh 1588e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1589e72fd46aSWarner Loshauthor a beer. 1590e72fd46aSWarner Losh 159122306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1592772730c7SWarner Loshthis document. 1593772730c7SWarner Losh 159497d92980SPeter Wemm$FreeBSD$ 1595