157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3f8c77507SWarner LoshThis file is maintained by imp@village.org. Please send new entries 4dc0dbf5cSWarner Loshdirectly to him. See end of file for further details. For commonly 516de1a07SWarner Loshdone items, please see the end of the file. Search for 'COMMON 616de1a07SWarner LoshITEMS:' 716de1a07SWarner Losh 8de2bcc63SWarner Losh20001218: 9de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 10de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 11de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 12de2bcc63SWarner Losh cards will not be recognized without it. 13de2bcc63SWarner Losh 14960773f7SWarner Losh20001205: 15960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 16960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 17960773f7SWarner Losh adding the following in pam.conf: 18960773f7SWarner Losh 19960773f7SWarner Losh sshd auth sufficient pam_skey.so 20960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 21960773f7SWarner Losh sshd session required pam_permit.so 22960773f7SWarner Losh 230acc635eSWarner Losh20001031: 240acc635eSWarner Losh cvs updated to 1.11. 250acc635eSWarner Losh 260acc635eSWarner Losh20001020: 270acc635eSWarner Losh The random device needs more entropy, so you need to make sure 280acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 290acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 300acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 310acc635eSWarner Losh workaround. 320acc635eSWarner Losh 330acc635eSWarner Losh20001010: 340acc635eSWarner Losh ****************************** WARNING ****************************** 350acc635eSWarner Losh Sendmail has been updated. 360acc635eSWarner Losh ****************************** WARNING ****************************** 370acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 380acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 390acc635eSWarner Losh is set. 400acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 410acc635eSWarner Losh commands. 420acc635eSWarner Losh o Now using sendmail's version of vacation(1). 430acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 440acc635eSWarner Losh in /usr/share/sendmail/cf. 450acc635eSWarner Losh o sendmail.cw changed to local-host-names 460acc635eSWarner Losh 470acc635eSWarner Losh More details can be found at 480acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 490acc635eSWarner Losh 506e98a146SWarner Losh20001009: 516e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 526e98a146SWarner Losh your entire ports tree, or you will have problems. 536e98a146SWarner Losh 546e98a146SWarner Losh20001006: 55685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 566e98a146SWarner Losh the installed miniperl. It is recommended that you delete 576e98a146SWarner Losh /usr/bin/miniperl. 586e98a146SWarner Losh 59073113a4SWarner Losh20001005: 60073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 61685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 62073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 63073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 64073113a4SWarner Losh tree for anything to work. 65073113a4SWarner Losh 660acc635eSWarner Losh20000928: 670acc635eSWarner Losh There was a change in the passwd format. Need more information. 680acc635eSWarner Losh 69be3885b3SWarner Losh20000916: 70be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 71be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 72be3885b3SWarner Losh same time as your kernel. 73be3885b3SWarner Losh 7476ec9675SWarner Losh20000914: 7576ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 7676ec9675SWarner Losh include the device will cause suspended laptops losing time 7776ec9675SWarner Losh when they resume. Include 7876ec9675SWarner Losh device pmtimer 7976ec9675SWarner Losh in your config file and 8001b9a434SWarner Losh hint.pmtimer.0.at="isa" 8176ec9675SWarner Losh to your /boot/device.hints file. 8276ec9675SWarner Losh 83f4865386SMark Murray20000911: 84f4865386SMark Murray The random device has been turned into a (pseudo-)device, 85f4865386SMark Murray rather than an option. The supplied kernel config files have 86f4865386SMark Murray been updated. You will need to do something similar in your 87f4865386SMark Murray own kernel config file. 88f4865386SMark Murray Remove: 89f4865386SMark Murray options RANDOMDEV 90f4865386SMark Murray Add: 91f4865386SMark Murray device random 92f4865386SMark Murray If you prefer to load the loadable module, you need to do 93f4865386SMark Murray nothing. 94f4865386SMark Murray 95d594498fSWarner Losh20000909: 96d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 97d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 98d594498fSWarner Losh reflect this if you load this module at boot time. 99d594498fSWarner Losh The line should read: 100d594498fSWarner Losh random_load="YES" 101d594498fSWarner Losh 1020deb7ddcSWarner Losh20000907: 1030deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 10416eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 10516eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 10616eb772dSWarner Losh sure you don't have model loading problems which might at 10716eb772dSWarner Losh first blush appear related to SMP. 10852bf24e7SWarner Losh 1095a01880bSWarner Losh20000906: 1105a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 1115a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 1125a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 1135a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 1145a01880bSWarner Losh don't have one, and you have host.conf. 1155a01880bSWarner Losh 1162b41163cSWarner Losh20000905: 11738d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 11838d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 11938d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 12038d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 12138d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 12238d6ecd2SWarner Losh 12338d6ecd2SWarner Losh20000905: 1248aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 1258aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 1268aab4bc7SWarner Losh is /boot/kernel. 1278aab4bc7SWarner Losh 1288aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 12938d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 13038d6ecd2SWarner Losh installkernel/installworld dance. 1312b41163cSWarner Losh 132d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 133d594498fSWarner Losh before booting the new kernel, since kldload will find stale 134d594498fSWarner Losh modules in that directory instead of finding them in the correct 135d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 136d594498fSWarner Losh is that the linux module crashes your machine after the update. 137d594498fSWarner Losh 138d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 139d594498fSWarner Losh mv /modules.old /boot/kernel.old 140d594498fSWarner Losh chflags noschg /kernel.old 141d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 142d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 143d594498fSWarner Losh fi 144d594498fSWarner Losh 145c22a309cSWarner Losh20000904: 146c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 147c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 148c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 149c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 150c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 151c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 152c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 153c22a309cSWarner Losh is not likely to be generated. 154c22a309cSWarner Losh 155fdb9f54dSWarner Losh20000825: 156fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 1579c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 1589c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 1599c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 1609c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 1619c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 1629c1a7444SWarner Losh messages will appear after the boot loader tries to start the 1639c1a7444SWarner Losh kernel. 1649c1a7444SWarner Losh 1659c1a7444SWarner Losh20000821: 1669c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 1679c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 1689c1a7444SWarner Losh /boot/loader.conf. 169fdb9f54dSWarner Losh 1708f250aa7SWarner Losh20000812: 1715da0d091SWarner Losh suidperl is now always built and installed on the system, but 1725da0d091SWarner Losh with permissions of 511. If you have applications that use 1735da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 1745da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 1755da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 1765da0d091SWarner Losh will fix this until the next build. 1775da0d091SWarner Losh 1785da0d091SWarner Losh20000812: 1798f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 1808f250aa7SWarner Losh visible changes that may immediately affect your configuration 1818f250aa7SWarner Losh include: 1828f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 1838f250aa7SWarner Losh - newaliases limited to root and trusted users 1848f250aa7SWarner Losh - MSA port (587) turned on by default 1858f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 1868f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 1878f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 1888f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 1898f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 1908f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 1918f250aa7SWarner Losh 19271c38472SWarner Losh20000810: 19371c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 19471c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 19571c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 19671c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 19771c38472SWarner Losh specific use for it. 19871c38472SWarner Losh 19971c38472SWarner Losh20000729: 20071c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 20171c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 20271c38472SWarner Losh /etc/rc.conf if they want to have the same setup 20371c38472SWarner Losh afterwards (unless the variables already are set, of course): 20471c38472SWarner Losh # Enable network daemons for user convenience. 20571c38472SWarner Losh inetd_enable="YES" 20671c38472SWarner Losh portmap_enable="YES" 20771c38472SWarner Losh sendmail_enable="YES" 20871c38472SWarner Losh 20971c38472SWarner Losh20000728: 21071c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 21171c38472SWarner Losh will need to change that to nullfs_load="YES". 21271c38472SWarner Losh 2131dece4a9SWarner Losh20000728: 2141dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 2151dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 2161dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 2171dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 2181dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 2191dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 2201dece4a9SWarner Losh to /MYKERNEL. 2211dece4a9SWarner Losh 222409e887cSWarner Losh20000711: 223409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 224409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 225409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 226409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 227409e887cSWarner Losh for details on potential problems that you might have and how 228409e887cSWarner Losh to get around them. 229409e887cSWarner Losh 230409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 231409e887cSWarner Losh clauses above, you needn't worry. 232409e887cSWarner Losh 233409e887cSWarner Losh20000711: 234409e887cSWarner Losh /etc/security has been updated to print the inode number of 235409e887cSWarner Losh setuid programs that have changed. You will see a large spike 236409e887cSWarner Losh in the number of changed programs the first time when you run 237409e887cSWarner Losh mergemaster to get a new /etc/security. 238409e887cSWarner Losh 239673d13f2SWarner Losh20000710: 240673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 241673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 242673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 243673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 244673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 245673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 246673d13f2SWarner Losh errors. (see below, 20000624). 247673d13f2SWarner Losh 248bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 2491dece4a9SWarner Losh 250673d13f2SWarner Losh20000709: 251c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 252c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 253c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 254673d13f2SWarner Losh ln -s aj /etc/malloc.conf 255673d13f2SWarner Losh 256e98e26cdSWarner Losh20000706: 257e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 258e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 259e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 260f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 261e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 2622c021c6cSMark Ovens interim if needed. 263e98e26cdSWarner Losh 264e98e26cdSWarner Losh20000705: 265e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 266e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 267e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 268e98e26cdSWarner Losh details. 269e98e26cdSWarner Losh 270c373950eSWarner Losh20000704: 2712f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 2722f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 2732f961bc8SWarner Losh 2742f961bc8SWarner Losh20000704: 275c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 276c373950eSWarner Losh or stop. This may cause some harmless warnings from older 277c373950eSWarner Losh rc.d scripts that haven't been updated. 278c373950eSWarner Losh 27927dc3a2bSWarner Losh20000630: 28027dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 28127dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 28227dc3a2bSWarner Losh which should be reported to des@freebsd.org. 28327dc3a2bSWarner Losh 284b8c215acSWarner Losh20000625: 285b8c215acSWarner Losh From approximately this date forward, one must have the crypto 28627dc3a2bSWarner Losh system installed in order to build the system and kernel. 28727dc3a2bSWarner Losh While not technically strictly true, one should treat it as 28827dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 28927dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 29027dc3a2bSWarner Losh were required. You should check with the latest collections 29127dc3a2bSWarner Losh to make sure that these haven't changed. 292b8c215acSWarner Losh 2937b990719SWarner Losh20000624: 2947b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 2957b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 2967b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 2977b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 2987b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 2997b990719SWarner Losh openssh and openssl should not be used to generate keys from this 3007b990719SWarner Losh date to the completion of the work. 3017b990719SWarner Losh 30227dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 30327dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 30427dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 30527dc3a2bSWarner Losh recreate the random and urandom devices. 30627dc3a2bSWarner Losh 30781e54c50SWarner Losh20000622: 30881e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 30981e54c50SWarner Losh BSD license. You may need to remove your symbolic links 31081e54c50SWarner Losh that used to be required when updating. 31181e54c50SWarner Losh 31239943833SWarner Losh20000621: 3132c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 3142a2f33fbSDaniel Baker the config file update procedure. 3152a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 316c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 317a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 31839943833SWarner Losh 319290f9ad8SWarner Losh20000620: 320290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 321290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 322290f9ad8SWarner Losh that workaround will no longer be required. 323290f9ad8SWarner Losh 32490fb6346SWarner Losh20000615: 32590fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 32690fb6346SWarner Losh ad driver. If you haven't done so already, you must update 32790fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 32890fb6346SWarner Losh devices. 32990fb6346SWarner Losh 330f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 331f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 332f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 333f75f65bbSWarner Losh may work). 334f75f65bbSWarner Losh 335ba26da8eSWarner Losh20000612: 336ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 337290f9ad8SWarner Losh on the topic before even thinking about updating. You will 338c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 339290f9ad8SWarner Losh to your config file to compile them in statically. The format 340f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 341f54a3542SWarner Losh NEWCARD for examples of the new format. 342290f9ad8SWarner Losh 343d65850ebSWarner Losh20000522: 344ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 345d65850ebSWarner Losh building a kernel after this point is advised that they need 346d65850ebSWarner Losh to rebuild their binutils (or better yet do a 347d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 348d65850ebSWarner Losh 349d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 350d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 351d9583a00SWarner Losh is recommended that you don't set this option until the problem 352d9583a00SWarner Losh is resolved. 353d9583a00SWarner Losh 3548039cedeSWarner Losh20000513: 3558039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 3568039cedeSWarner Losh 357d65850ebSWarner Losh20000510: 3588039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 3598039cedeSWarner Losh This will require some care in updating alphas. A new libstand 3608039cedeSWarner Losh is requires for the boot blocks to build properly. 3618039cedeSWarner Losh 3628039cedeSWarner Losh20000503: 3638039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 3648039cedeSWarner Losh is now available. 3658039cedeSWarner Losh 366d65850ebSWarner Losh20000502: 367d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 368d65850ebSWarner Losh connected to the kernel building instead. 369d65850ebSWarner Losh 370be149406SNik Clayton20000427: 3718039cedeSWarner Losh You may need to build gperf 3728039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 3738039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 3748039cedeSWarner Losh an option only in -current. 3758039cedeSWarner Losh 3762b8dd5f4SWarner Losh20000417: 3772b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 378f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 3792b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 3802b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 3812c021c6cSMark Ovens before you reboot, you'll need to issue: 3822b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 3832b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 3842b8dd5f4SWarner Losh 3858d9f1945SWarner Losh20000320: 3862b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 3872b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 3882b8dd5f4SWarner Losh cope if you have a problem combination is to add: 3898d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 3902b8dd5f4SWarner Losh to the start of /etc/rc.conf. 3918d9f1945SWarner Losh 392f8ab1dd6SWarner Losh20000319: 393f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 394f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 395f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 396f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 397f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 398f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 399f8ab1dd6SWarner Losh 40019cada77SWarner Losh20000318: 401f699bbbbSMark Ovens We've entered the traditional post release dumping party. 40219cada77SWarner Losh Large kernel changes are being committed and are in the 40319cada77SWarner Losh works. It is important to keep the systems' klds and kernel 40419cada77SWarner Losh in sync as kernel interfaces and structures are changing. 40519cada77SWarner Losh Before reporting kernel panics, make sure that all modules 40619cada77SWarner Losh that you are loading are up to date. 407ba228352SWarner Losh 40819cada77SWarner Losh20000315: 4096d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 4106d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 4116d23c382SWarner Losh will do the trick. This isn't critical until you remove your 4126d23c382SWarner Losh wd device entries in /dev, at which point your system will not 4136d23c382SWarner Losh boot. 4146d23c382SWarner Losh 4156d23c382SWarner Losh20000315: 41619cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 41719cada77SWarner Losh to upgrade to 4.0 from 3.x. 41857199806SWarner Losh 419dc0dbf5cSWarner LoshCOMMON ITEMS: 420dc0dbf5cSWarner Losh 421a24eff53SWarner Losh General Notes 422a24eff53SWarner Losh ------------- 423a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 424a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 425a24eff53SWarner Losh installworld. This is especially true when upgrading between 426a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 427a24eff53SWarner Losh or several minor releases, or when several months have passed 428a24eff53SWarner Losh on the -current branch). 429a24eff53SWarner Losh 430dc0dbf5cSWarner Losh To build a kernel 431dc0dbf5cSWarner Losh ----------------- 432ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 433f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 434ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 435ba01eb20SWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 436ba01eb20SWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 437dc0dbf5cSWarner Losh 438ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 439ba01eb20SWarner Losh -------------------------------------------------------------- 440ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 441ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 442ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 443ba01eb20SWarner Losh make depend 444ba01eb20SWarner Losh make 445ba01eb20SWarner Losh make install 446ba01eb20SWarner Losh 447ba01eb20SWarner Losh [1] If in doubt, -r might help here. 448ba01eb20SWarner Losh 449ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 450ba01eb20SWarner Losh 451ba01eb20SWarner Losh To rebuild everything and install it on the current system. 452ba01eb20SWarner Losh ----------------------------------------------------------- 453759f0aefSWarner Losh make world 454fdb9f54dSWarner Losh Build a new kernel, see above. 455759f0aefSWarner Losh 4561dece4a9SWarner Losh To upgrade from 4.x-stable to current 457ba26da8eSWarner Losh ------------------------------------- 458ba26da8eSWarner Losh make buildworld 459ba26da8eSWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 4609c1a7444SWarner Losh cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2] 461ba26da8eSWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 462ba26da8eSWarner Losh make installworld 463134d2e86SWarner Losh [1] 464ba26da8eSWarner Losh <reboot> 465ba26da8eSWarner Losh 466fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 467fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 468fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 469fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 470fdb9f54dSWarner Losh the UPDATING entries. 471ba26da8eSWarner Losh 4721dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 4731dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 4741dece4a9SWarner Losh your sources that you have read and understood all the recent 4751dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 4761dece4a9SWarner Losh much fewer pitfalls. 4771dece4a9SWarner Losh 478134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 479134d2e86SWarner Losh should disable them at this point so they don't crash your 480134d2e86SWarner Losh system on reboot. 481134d2e86SWarner Losh 4829c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 4839c1a7444SWarner Losh your own device.hints to reflect your unique hardware 4849c1a7444SWarner Losh configuration. 4859c1a7444SWarner Losh 486dc0dbf5cSWarner LoshFORMAT: 487dc0dbf5cSWarner Losh 488f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 4891fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 490f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 491f8ab1dd6SWarner Loshprevious releases if your system is older than this. 4921fc1a0dcSWarner Losh 4933645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 4943645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 495f8c77507SWarner Losh 49697d92980SPeter Wemm$FreeBSD$ 497