157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh 4e72fd46aSWarner Losh<imp@village.org>. Please send new entries directly to him. See end 5e72fd46aSWarner Loshof file for further details. For commonly done items, please see the 6e72fd46aSWarner LoshCOMMON ITEMS: section later in the file. 7e72fd46aSWarner Losh 8*4b676ec1SWarner Losh20011126: 9*4b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 10*4b676ec1SWarner Losh after this date. 11*4b676ec1SWarner Losh 12d961e462SWarner Losh20011103: 13d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 14d961e462SWarner Losh edges may be left, but for the most part things should be 15*4b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 16d961e462SWarner Losh 17d961e462SWarner Losh20011030: 18d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 19d961e462SWarner Losh choppy waves in the upgrade process. 20d961e462SWarner Losh 211fe003b6SWarner Losh20011030: 22a4b6fda0SWarner Losh The asr driver problem has been resolved. 231fe003b6SWarner Losh 241fe003b6SWarner Losh20011027: 251fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 261fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 271fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 281fe003b6SWarner Losh try to use from this date forward. 291fe003b6SWarner Losh 301fe003b6SWarner Losh20011025: 311fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 321fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 331fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 341fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 351fe003b6SWarner Losh TARGET_ARCH=i386. 361fe003b6SWarner Losh 37d05f9643SWarner Losh20011001: 38d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 39d05f9643SWarner Losh You must recompile both the kernel and userland applications 40d05f9643SWarner Losh at the same time. 41d05f9643SWarner Losh 4258970f85SWarner Losh20010929: 4358970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 4458970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 4558970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 4658970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 4758970f85SWarner Losh (eg, you can build pc98 on a i386 machine and vice versa). 4858970f85SWarner Losh 4958970f85SWarner Losh20010927: 5058970f85SWarner Losh Some weird problems result from using ACPI on some machines. 5158970f85SWarner Losh To disable ACPI you can add 52378f4486SAlfred Perlstein hint.acpi.0.disable="1" 5358970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 5458970f85SWarner Losh loader "ok" prompt). 5558970f85SWarner Losh 5658970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 5758970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 5858970f85SWarner Losh file and not list acpi in that list. 59378f4486SAlfred Perlstein 605119d237SWarner Losh20010924: 615119d237SWarner Losh The buildworld has been fixed. You may need to install 625119d237SWarner Losh the 4.x compatibility libraries for some old binaries 6358970f85SWarner Losh to work. 6458970f85SWarner Losh cd src/lib/compat/compat4x.i386 6558970f85SWarner Losh make all install 665119d237SWarner Losh 673c293725SWarner Losh20010919: 683c293725SWarner Losh There's a bug in the world build process. The cross-tools 693c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 703c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 71772730c7SWarner Losh workaround is to add 723c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 733c293725SWarner Losh before building world when upgrading from 4.x to current. This 743c293725SWarner Losh can be removed afterwards. 753c293725SWarner Losh 763c293725SWarner Losh A proper fix to the buildworld target is needed. 773c293725SWarner Losh 783c293725SWarner Losh20010918: 793c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 803c293725SWarner Losh NFS may be unstable after this date. 813c293725SWarner Losh 823c293725SWarner Losh20010912: 833c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 843c293725SWarner Losh the kernel. While a few problems were introduced in the 853c293725SWarner Losh initial commit, most of the major ones have been found and 863c293725SWarner Losh corrected. 873c293725SWarner Losh 883c293725SWarner Losh20010901: 893c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 903c293725SWarner Losh arounds described in the 20010604 entry are now no longer 913c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 923c293725SWarner Losh have been rectified around this date. 933c293725SWarner Losh 9498b17b95SWarner Losh20010823: 9598b17b95SWarner Losh named now runs as user bind and group bind rather than as 9698b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 9798b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 9898b17b95SWarner Losh and that group bind is available in /etc/group. Also make 9998b17b95SWarner Losh sure that user or group bind has read (and not write) 10098b17b95SWarner Losh permission for your name server configuration and that it 10198b17b95SWarner Losh has read and write permission for your slave zone files and 10298b17b95SWarner Losh directory. 10398b17b95SWarner Losh 10498b17b95SWarner Losh If you wish to continue to run named as root (a less secure 10598b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 10698b17b95SWarner Losh 10798b17b95SWarner Losh named_flags= 10898b17b95SWarner Losh 1097b9786edSMark Murray20010709: 1107b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 1117b9786edSMark Murray the ability of the shared library major number to handle. 1127b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 1137b9786edSMark Murray solution is to rebuild those ports. 1147b9786edSMark Murray 1151d28950eSWarner Losh20010628: 1161d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 1171d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 1181d28950eSWarner Losh 119e72fd46aSWarner Losh20010625: 12098b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 12198b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 12298b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 12398b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 12498b17b95SWarner Losh IRQ configuration needs more safety belts. 12516de1a07SWarner Losh 1260d415dffSWarner Losh20010617: 127e72fd46aSWarner Losh Softupdates problems have been corrected. 1280d415dffSWarner Losh 1290d415dffSWarner Losh20010614: 1300d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 1310d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 1320d415dffSWarner Losh kernel building methods. 1330d415dffSWarner Losh 1348b9959adSWarner Losh20010613: 1358b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 1368b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 137e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 138e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 1398b9959adSWarner Losh 140e72fd46aSWarner Losh20010613: 1418b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 142e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 143e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 1448b9959adSWarner Losh 1450d415dffSWarner Losh20010612: 1460d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 1470d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 1480d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 1490d415dffSWarner Losh work around this issue, please use only one or the other mechanism 1500d415dffSWarner Losh until this bug is fixed. 1510d415dffSWarner Losh 152e72fd46aSWarner Losh Please note that a feature of config is that if you have config 153e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 154e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 155e72fd46aSWarner Losh 1560d415dffSWarner Losh20010610: 1570d415dffSWarner Losh Locale names have changed to match other systems better. 1580d415dffSWarner Losh 1596ccdb5e4SWarner Losh20010604: 1606ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 1616ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 1626ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 1633590182eSWarner Losh Interrupt storms look a lot like a hang. 1643590182eSWarner Losh 1653590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 1663590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 1673590182eSWarner Losh it is). 1683590182eSWarner Losh 1693590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 1703590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 1713590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 1723590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 1736ccdb5e4SWarner Losh 1740bc62786SWarner Losh20010530: 1750bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 1760bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 1770bc62786SWarner Losh a limited time. If you see 1780bc62786SWarner Losh 1790bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 1800bc62786SWarner Losh 1810bc62786SWarner Losh in your makeworld, then you need to migrate towards using 1820bc62786SWarner Losh COPY=-C. 1830bc62786SWarner Losh 18468a38c6cSWarner Losh20010525: 185b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 186c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 187c4f4a728SWarner Losh definitely is in bad shape. 18868a38c6cSWarner Losh 189ed0f29caSWarner Losh20010521: 190f10d3145SWarner Losh Minor repo damange has happened. This may cause problems 191ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 192ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 193ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 194ed0f29caSWarner Losh is 195ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 196ed0f29caSWarner Losh 19780c16af9SWarner Losh20010520: 19868a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 19980c16af9SWarner Losh 20080c16af9SWarner Losh20010519: 20180c16af9SWarner Losh pccard has had much reorganizational work done to it over 20280c16af9SWarner Losh the past few days. Everything should still work, but if 20380c16af9SWarner Losh not, please contact imp@freebsd.org. 20480c16af9SWarner Losh 205a45f2d05SWarner Losh20010517: 206a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 207a45f2d05SWarner Losh userland at the same time. 208a45f2d05SWarner Losh 209a45f2d05SWarner Losh20010517: 210a45f2d05SWarner Losh New ncurses imported. 211a45f2d05SWarner Losh 2122988afcaSWarner Losh20010512: 2132988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 2142988afcaSWarner Losh will be the only way to go starting July 1. 2152988afcaSWarner Losh 21609946a51SWarner Losh20010502: 21709946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 21809946a51SWarner Losh 21909946a51SWarner Losh20010501: 22009946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 22109946a51SWarner Losh 22209946a51SWarner Losh20010430: 223a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 22409946a51SWarner Losh go back in the water. 22509946a51SWarner Losh 22609946a51SWarner Losh20010429: 22709946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 22809946a51SWarner Losh this date, but before the correction date. 22909946a51SWarner Losh 23091dd3b53SWarner Losh20010423: 23191dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 23291dd3b53SWarner Losh 23391dd3b53SWarner Losh20010411: 23491dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 23591dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 23691dd3b53SWarner Losh Update only if you understand that you must not use the old 23791dd3b53SWarner Losh fsck with the new kernel ever. 23891dd3b53SWarner Losh 239933b3269SWarner Losh20010330: 240933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 241c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 242933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 243933b3269SWarner Losh 244933b3269SWarner Losh20010319: 245933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 246933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 247933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 248f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 24909946a51SWarner Losh 25009946a51SWarner Losh20010315: 25109946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 25209946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 25309946a51SWarner Losh been replaced by tunables. See ata.4 for details. 254933b3269SWarner Losh 255933b3269SWarner Losh20010312: 256933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 257933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 258933b3269SWarner Losh 259933b3269SWarner Losh20010312: 260933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 261933b3269SWarner Losh instead of ad-hoc. 262933b3269SWarner Losh 263933b3269SWarner Losh20010310: 264f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 265933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 266933b3269SWarner Losh ssh might not work if you don't. 267933b3269SWarner Losh 26862353691SWarner Losh20010303: 26962353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 27062353691SWarner Losh which means that you must include the miibus in your kernel if 27162353691SWarner Losh you use the ed driver. 27262353691SWarner Losh 273d325cf65SWarner Losh20010220: 274d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 275d325cf65SWarner Losh safe to go back into the water. 276d325cf65SWarner Losh 277024daae6SWarner Losh20010211: 278024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 279024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 280024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 281024daae6SWarner Losh that before upgrading would be a good time to do a level 0 282024daae6SWarner Losh dump of your system. No, really, I mean it this time. 283024daae6SWarner Losh 284024daae6SWarner Losh To get to the new system, you'll need to use the following 285024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 286024daae6SWarner Losh don't have to move this to the updating section. 287024daae6SWarner Losh 288024daae6SWarner Losh To get around the installworld problem, do: 289024daae6SWarner Losh # cd /usr/src/usr.bin/sed 290024daae6SWarner Losh # make install 291024daae6SWarner Losh # cd /usr/src 292024daae6SWarner Losh # make installworld 293024daae6SWarner Losh If that doesn't work, then try: 294024daae6SWarner Losh # make -k installworld 295024daae6SWarner Losh # make installworld 296024daae6SWarner Losh 297024daae6SWarner Losh20010207: 298024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 299024daae6SWarner Losh do not include devfs in your kernel as problems result. 300024daae6SWarner Losh 301024daae6SWarner Losh20010205: 3027595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 303024daae6SWarner Losh Remove them from your config. 304024daae6SWarner Losh 3051e159248SWarner Losh20010122: 3061e159248SWarner Losh ****************************** WARNING ****************************** 3071e159248SWarner Losh buildkernel has been changed slightly 3081e159248SWarner Losh ****************************** WARNING ****************************** 3091e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 3101e159248SWarner Losh should update your scripts and make.conf accordingly. 3111e159248SWarner Losh 3121e159248SWarner Losh20010119: 3131e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 3141e159248SWarner Losh This requires a new config to build correctly. 3151e159248SWarner Losh 316aac7dfeaSWarner Losh20010116: 317aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 318aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 319aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 320aac7dfeaSWarner Losh 321aac7dfeaSWarner Losh20010110: 322aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 323aac7dfeaSWarner Losh 324aac7dfeaSWarner Losh20010102: 325aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 326aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 327aac7dfeaSWarner Losh 32863c90c9eSWarner Losh20010101: 32963c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 33063c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 3315fd2a895SWarner Losh dump while building termcap. You can work around this problem 33263c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 33363c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 33463c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 33563c90c9eSWarner Losh might have been ignored by the -k option. 33663c90c9eSWarner Losh 3375fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 3385fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 3395fd2a895SWarner Losh of this working. 3405fd2a895SWarner Losh 341aac7dfeaSWarner Losh20001228: 342aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 343aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 344aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 345aac7dfeaSWarner Losh 346de2bcc63SWarner Losh20001218: 347de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 348de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 349de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 350de2bcc63SWarner Losh cards will not be recognized without it. 351de2bcc63SWarner Losh 352960773f7SWarner Losh20001205: 353960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 354960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 355960773f7SWarner Losh adding the following in pam.conf: 356960773f7SWarner Losh 357960773f7SWarner Losh sshd auth sufficient pam_skey.so 358960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 359960773f7SWarner Losh sshd session required pam_permit.so 360960773f7SWarner Losh 3610acc635eSWarner Losh20001031: 3620acc635eSWarner Losh cvs updated to 1.11. 3630acc635eSWarner Losh 3640acc635eSWarner Losh20001020: 3650acc635eSWarner Losh The random device needs more entropy, so you need to make sure 3660acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 3670acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 3680acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 3690acc635eSWarner Losh workaround. 3700acc635eSWarner Losh 3710acc635eSWarner Losh20001010: 3720acc635eSWarner Losh ****************************** WARNING ****************************** 3730acc635eSWarner Losh Sendmail has been updated. 3740acc635eSWarner Losh ****************************** WARNING ****************************** 3750acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 3760acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 3770acc635eSWarner Losh is set. 3780acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 3790acc635eSWarner Losh commands. 3800acc635eSWarner Losh o Now using sendmail's version of vacation(1). 3810acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 3820acc635eSWarner Losh in /usr/share/sendmail/cf. 3830acc635eSWarner Losh o sendmail.cw changed to local-host-names 3840acc635eSWarner Losh 3850acc635eSWarner Losh More details can be found at 3860acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 3870acc635eSWarner Losh 3886e98a146SWarner Losh20001009: 3896e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 3906e98a146SWarner Losh your entire ports tree, or you will have problems. 3916e98a146SWarner Losh 3926e98a146SWarner Losh20001006: 393685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 3946e98a146SWarner Losh the installed miniperl. It is recommended that you delete 3956e98a146SWarner Losh /usr/bin/miniperl. 3966e98a146SWarner Losh 397073113a4SWarner Losh20001005: 398073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 399685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 400073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 401073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 402073113a4SWarner Losh tree for anything to work. 403073113a4SWarner Losh 4040acc635eSWarner Losh20000928: 4050acc635eSWarner Losh There was a change in the passwd format. Need more information. 4060acc635eSWarner Losh 407be3885b3SWarner Losh20000916: 408be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 409be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 410be3885b3SWarner Losh same time as your kernel. 411be3885b3SWarner Losh 41276ec9675SWarner Losh20000914: 41376ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 41476ec9675SWarner Losh include the device will cause suspended laptops losing time 41576ec9675SWarner Losh when they resume. Include 41676ec9675SWarner Losh device pmtimer 41776ec9675SWarner Losh in your config file and 41801b9a434SWarner Losh hint.pmtimer.0.at="isa" 41976ec9675SWarner Losh to your /boot/device.hints file. 42076ec9675SWarner Losh 421f4865386SMark Murray20000911: 422f4865386SMark Murray The random device has been turned into a (pseudo-)device, 423f4865386SMark Murray rather than an option. The supplied kernel config files have 424f4865386SMark Murray been updated. You will need to do something similar in your 425f4865386SMark Murray own kernel config file. 426f4865386SMark Murray Remove: 427f4865386SMark Murray options RANDOMDEV 428f4865386SMark Murray Add: 429f4865386SMark Murray device random 430f4865386SMark Murray If you prefer to load the loadable module, you need to do 431f4865386SMark Murray nothing. 432f4865386SMark Murray 433d594498fSWarner Losh20000909: 434d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 435d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 436d594498fSWarner Losh reflect this if you load this module at boot time. 437d594498fSWarner Losh The line should read: 438d594498fSWarner Losh random_load="YES" 439d594498fSWarner Losh 4400deb7ddcSWarner Losh20000907: 4410deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 44216eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 44316eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 44416eb772dSWarner Losh sure you don't have model loading problems which might at 44516eb772dSWarner Losh first blush appear related to SMP. 44652bf24e7SWarner Losh 4475a01880bSWarner Losh20000906: 4485a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 4495a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 4505a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 4515a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 4525a01880bSWarner Losh don't have one, and you have host.conf. 4535a01880bSWarner Losh 4542b41163cSWarner Losh20000905: 45538d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 45638d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 45738d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 45838d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 45938d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 46038d6ecd2SWarner Losh 46138d6ecd2SWarner Losh20000905: 4628aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 4638aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 4648aab4bc7SWarner Losh is /boot/kernel. 4658aab4bc7SWarner Losh 4668aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 46738d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 46838d6ecd2SWarner Losh installkernel/installworld dance. 4692b41163cSWarner Losh 470d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 471d594498fSWarner Losh before booting the new kernel, since kldload will find stale 472d594498fSWarner Losh modules in that directory instead of finding them in the correct 473d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 474d594498fSWarner Losh is that the linux module crashes your machine after the update. 475d594498fSWarner Losh 476d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 477d594498fSWarner Losh mv /modules.old /boot/kernel.old 478d594498fSWarner Losh chflags noschg /kernel.old 479d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 480d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 481d594498fSWarner Losh fi 482d594498fSWarner Losh 483c22a309cSWarner Losh20000904: 484c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 485c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 486c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 487c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 488c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 489c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 490c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 491c22a309cSWarner Losh is not likely to be generated. 492c22a309cSWarner Losh 493fdb9f54dSWarner Losh20000825: 494fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 4959c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 4969c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 4979c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 4989c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 4999c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 5009c1a7444SWarner Losh messages will appear after the boot loader tries to start the 5019c1a7444SWarner Losh kernel. 5029c1a7444SWarner Losh 5039c1a7444SWarner Losh20000821: 5049c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 5059c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 5069c1a7444SWarner Losh /boot/loader.conf. 507fdb9f54dSWarner Losh 5088f250aa7SWarner Losh20000812: 5095da0d091SWarner Losh suidperl is now always built and installed on the system, but 5105da0d091SWarner Losh with permissions of 511. If you have applications that use 5115da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 5125da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 5135da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 5145da0d091SWarner Losh will fix this until the next build. 5155da0d091SWarner Losh 5165da0d091SWarner Losh20000812: 5178f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 5188f250aa7SWarner Losh visible changes that may immediately affect your configuration 5198f250aa7SWarner Losh include: 5208f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 5218f250aa7SWarner Losh - newaliases limited to root and trusted users 5228f250aa7SWarner Losh - MSA port (587) turned on by default 5238f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 5248f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 5258f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 5268f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 5278f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 5288f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 5298f250aa7SWarner Losh 53071c38472SWarner Losh20000810: 53171c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 53271c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 53371c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 53471c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 53571c38472SWarner Losh specific use for it. 53671c38472SWarner Losh 53771c38472SWarner Losh20000729: 53871c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 53971c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 54071c38472SWarner Losh /etc/rc.conf if they want to have the same setup 54171c38472SWarner Losh afterwards (unless the variables already are set, of course): 54271c38472SWarner Losh # Enable network daemons for user convenience. 54371c38472SWarner Losh inetd_enable="YES" 54471c38472SWarner Losh portmap_enable="YES" 54571c38472SWarner Losh sendmail_enable="YES" 54671c38472SWarner Losh 54771c38472SWarner Losh20000728: 54871c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 54971c38472SWarner Losh will need to change that to nullfs_load="YES". 55071c38472SWarner Losh 5511dece4a9SWarner Losh20000728: 5521dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 5531dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 5541dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 5551dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 5561dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 5571dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 5581dece4a9SWarner Losh to /MYKERNEL. 5591dece4a9SWarner Losh 560409e887cSWarner Losh20000711: 561409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 562409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 563409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 564409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 565409e887cSWarner Losh for details on potential problems that you might have and how 566409e887cSWarner Losh to get around them. 567409e887cSWarner Losh 568409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 569409e887cSWarner Losh clauses above, you needn't worry. 570409e887cSWarner Losh 571409e887cSWarner Losh20000711: 572409e887cSWarner Losh /etc/security has been updated to print the inode number of 573409e887cSWarner Losh setuid programs that have changed. You will see a large spike 574409e887cSWarner Losh in the number of changed programs the first time when you run 575409e887cSWarner Losh mergemaster to get a new /etc/security. 576409e887cSWarner Losh 577673d13f2SWarner Losh20000710: 578673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 579673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 580673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 581673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 582673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 583673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 584673d13f2SWarner Losh errors. (see below, 20000624). 585673d13f2SWarner Losh 586bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 5871dece4a9SWarner Losh 588673d13f2SWarner Losh20000709: 589c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 590c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 591c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 592673d13f2SWarner Losh ln -s aj /etc/malloc.conf 593673d13f2SWarner Losh 594e98e26cdSWarner Losh20000706: 595e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 596e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 597e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 598f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 599e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 6002c021c6cSMark Ovens interim if needed. 601e98e26cdSWarner Losh 602e98e26cdSWarner Losh20000705: 603e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 604e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 605e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 606e98e26cdSWarner Losh details. 607e98e26cdSWarner Losh 608c373950eSWarner Losh20000704: 6092f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 6102f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 6112f961bc8SWarner Losh 6122f961bc8SWarner Losh20000704: 613c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 614c373950eSWarner Losh or stop. This may cause some harmless warnings from older 615c373950eSWarner Losh rc.d scripts that haven't been updated. 616c373950eSWarner Losh 61727dc3a2bSWarner Losh20000630: 61827dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 61927dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 62027dc3a2bSWarner Losh which should be reported to des@freebsd.org. 62127dc3a2bSWarner Losh 622b8c215acSWarner Losh20000625: 623b8c215acSWarner Losh From approximately this date forward, one must have the crypto 62427dc3a2bSWarner Losh system installed in order to build the system and kernel. 62527dc3a2bSWarner Losh While not technically strictly true, one should treat it as 62627dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 62727dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 62827dc3a2bSWarner Losh were required. You should check with the latest collections 62927dc3a2bSWarner Losh to make sure that these haven't changed. 630b8c215acSWarner Losh 6317b990719SWarner Losh20000624: 6327b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 6337b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 6347b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 6357b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 6367b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 6377b990719SWarner Losh openssh and openssl should not be used to generate keys from this 6387b990719SWarner Losh date to the completion of the work. 6397b990719SWarner Losh 64027dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 64127dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 64227dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 64327dc3a2bSWarner Losh recreate the random and urandom devices. 64427dc3a2bSWarner Losh 64581e54c50SWarner Losh20000622: 64681e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 64781e54c50SWarner Losh BSD license. You may need to remove your symbolic links 64881e54c50SWarner Losh that used to be required when updating. 64981e54c50SWarner Losh 65039943833SWarner Losh20000621: 6512c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 6522a2f33fbSDaniel Baker the config file update procedure. 6532a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 654c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 655a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 65639943833SWarner Losh 657290f9ad8SWarner Losh20000620: 658290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 659290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 660290f9ad8SWarner Losh that workaround will no longer be required. 661290f9ad8SWarner Losh 66290fb6346SWarner Losh20000615: 66390fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 66490fb6346SWarner Losh ad driver. If you haven't done so already, you must update 66590fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 66690fb6346SWarner Losh devices. 66790fb6346SWarner Losh 668f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 669f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 670f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 671f75f65bbSWarner Losh may work). 672f75f65bbSWarner Losh 673ba26da8eSWarner Losh20000612: 674ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 675290f9ad8SWarner Losh on the topic before even thinking about updating. You will 676c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 677290f9ad8SWarner Losh to your config file to compile them in statically. The format 678f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 679f54a3542SWarner Losh NEWCARD for examples of the new format. 680290f9ad8SWarner Losh 681d65850ebSWarner Losh20000522: 682ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 683d65850ebSWarner Losh building a kernel after this point is advised that they need 684d65850ebSWarner Losh to rebuild their binutils (or better yet do a 685d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 686d65850ebSWarner Losh 687d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 688d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 689d9583a00SWarner Losh is recommended that you don't set this option until the problem 690d9583a00SWarner Losh is resolved. 691d9583a00SWarner Losh 6928039cedeSWarner Losh20000513: 6938039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 6948039cedeSWarner Losh 695d65850ebSWarner Losh20000510: 6968039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 6978039cedeSWarner Losh This will require some care in updating alphas. A new libstand 6988039cedeSWarner Losh is requires for the boot blocks to build properly. 6998039cedeSWarner Losh 7008039cedeSWarner Losh20000503: 7018039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 7028039cedeSWarner Losh is now available. 7038039cedeSWarner Losh 704d65850ebSWarner Losh20000502: 705d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 706d65850ebSWarner Losh connected to the kernel building instead. 707d65850ebSWarner Losh 708be149406SNik Clayton20000427: 7098039cedeSWarner Losh You may need to build gperf 7108039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 7118039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 7128039cedeSWarner Losh an option only in -current. 7138039cedeSWarner Losh 7142b8dd5f4SWarner Losh20000417: 7152b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 716f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 7172b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 7182b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 7192c021c6cSMark Ovens before you reboot, you'll need to issue: 7202b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 7212b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 7222b8dd5f4SWarner Losh 7238d9f1945SWarner Losh20000320: 7242b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 7252b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 7262b8dd5f4SWarner Losh cope if you have a problem combination is to add: 7278d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 7282b8dd5f4SWarner Losh to the start of /etc/rc.conf. 7298d9f1945SWarner Losh 730f8ab1dd6SWarner Losh20000319: 731f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 732f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 733f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 734f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 735f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 736f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 737f8ab1dd6SWarner Losh 73819cada77SWarner Losh20000318: 739f699bbbbSMark Ovens We've entered the traditional post release dumping party. 74019cada77SWarner Losh Large kernel changes are being committed and are in the 74119cada77SWarner Losh works. It is important to keep the systems' klds and kernel 74219cada77SWarner Losh in sync as kernel interfaces and structures are changing. 74319cada77SWarner Losh Before reporting kernel panics, make sure that all modules 74419cada77SWarner Losh that you are loading are up to date. 745ba228352SWarner Losh 74619cada77SWarner Losh20000315: 7476d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 7486d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 7496d23c382SWarner Losh will do the trick. This isn't critical until you remove your 7506d23c382SWarner Losh wd device entries in /dev, at which point your system will not 7516d23c382SWarner Losh boot. 7526d23c382SWarner Losh 7536d23c382SWarner Losh20000315: 75419cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 75519cada77SWarner Losh to upgrade to 4.0 from 3.x. 75657199806SWarner Losh 757dc0dbf5cSWarner LoshCOMMON ITEMS: 758dc0dbf5cSWarner Losh 759a24eff53SWarner Losh General Notes 760a24eff53SWarner Losh ------------- 761a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 762a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 763a24eff53SWarner Losh installworld. This is especially true when upgrading between 764a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 765a24eff53SWarner Losh or several minor releases, or when several months have passed 766a24eff53SWarner Losh on the -current branch). 767a24eff53SWarner Losh 768dc0dbf5cSWarner Losh To build a kernel 769dc0dbf5cSWarner Losh ----------------- 770ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 771f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 772ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 7731e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 7741e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 775dc0dbf5cSWarner Losh 776ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 777ba01eb20SWarner Losh -------------------------------------------------------------- 778ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 779ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 780ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 781ba01eb20SWarner Losh make depend 782ba01eb20SWarner Losh make 783ba01eb20SWarner Losh make install 784ba01eb20SWarner Losh 785ba01eb20SWarner Losh [1] If in doubt, -r might help here. 786ba01eb20SWarner Losh 787ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 788ba01eb20SWarner Losh 789ba01eb20SWarner Losh To rebuild everything and install it on the current system. 790ba01eb20SWarner Losh ----------------------------------------------------------- 791759f0aefSWarner Losh make world 792fdb9f54dSWarner Losh Build a new kernel, see above. 793759f0aefSWarner Losh 7941dece4a9SWarner Losh To upgrade from 4.x-stable to current 795ba26da8eSWarner Losh ------------------------------------- 796ba26da8eSWarner Losh make buildworld 7971e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 7987595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 7991e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 800ee6e1fc3SWarner Losh reboot in single user [3] 801ba26da8eSWarner Losh make installworld 802a6cd4f9dSWarner Losh mergemaster [4] 803134d2e86SWarner Losh [1] 804ba26da8eSWarner Losh <reboot> 805ba26da8eSWarner Losh 806fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 807fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 808fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 809fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 810fdb9f54dSWarner Losh the UPDATING entries. 811ba26da8eSWarner Losh 8121dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 8131dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 8141dece4a9SWarner Losh your sources that you have read and understood all the recent 8151dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 8161dece4a9SWarner Losh much fewer pitfalls. 8171dece4a9SWarner Losh 818134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 819134d2e86SWarner Losh should disable them at this point so they don't crash your 820134d2e86SWarner Losh system on reboot. 821134d2e86SWarner Losh 8229c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 8239c1a7444SWarner Losh your own device.hints to reflect your unique hardware 8249c1a7444SWarner Losh configuration. 8259c1a7444SWarner Losh 826ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 827ee6e1fc3SWarner Losh fsck -p 828ee6e1fc3SWarner Losh mount -u / 829ee6e1fc3SWarner Losh mount -a 830ee6e1fc3SWarner Losh cd /usr/src 831ee6e1fc3SWarner Losh adjkerntz -i # if COMS is wall time 832ee6e1fc3SWarner Losh 833a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 834a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 835a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 836a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 837a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 838a6cd4f9dSWarner Losh for potential gotchas. 839a6cd4f9dSWarner Losh 840dc0dbf5cSWarner LoshFORMAT: 841dc0dbf5cSWarner Losh 842f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 8431fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 844f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 845f8ab1dd6SWarner Loshprevious releases if your system is older than this. 8461fc1a0dcSWarner Losh 8473645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 8483645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 849f8c77507SWarner Losh 850e72fd46aSWarner LoshCopyright information: 851e72fd46aSWarner Losh 852e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh. All Rights Reserved. 853e72fd46aSWarner Losh 854772730c7SWarner LoshRedistribution, publication, translation and use, with or without 855772730c7SWarner Loshmodification, in full or in part, in any form or format of this 856772730c7SWarner Loshdocument are permitted. 857e72fd46aSWarner Losh 858e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 859e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 860e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 861e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 862e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 863e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 864e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 865e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 866e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 867e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 868e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 869e72fd46aSWarner Losh 870e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 871e72fd46aSWarner Loshauthor a beer. 872e72fd46aSWarner Losh 87322306abcSWarner LoshContact Warner Losh if you have any questions about your use of 874772730c7SWarner Loshthis document. 875772730c7SWarner Losh 87697d92980SPeter Wemm$FreeBSD$ 877