Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

===================================================================
RCS file: /ftp/cvs/cvsroot/src/UPDATING,v
rcsdiff: /ftp/cvs/cvsroot/src/UPDATING,v: warning: Unknown phrases like `commitid ...;' are present.
retrieving revision 1.127
retrieving revision 1.141
diff -u -p -r1.127 -r1.141
--- src/UPDATING	2004/10/01 15:29:23	1.127
+++ src/UPDATING	2005/07/01 09:55:37	1.141
@@ -1,4 +1,4 @@
-$NetBSD: UPDATING,v 1.127 2004/10/01 15:29:23 christos Exp $
+$NetBSD: UPDATING,v 1.141 2005/07/01 09:55:37 augustss Exp $
 
 This file (UPDATING) is intended to be a brief reference to recent
 changes that might cause problems in the build process, and a guide for
@@ -16,12 +16,71 @@ See also: BUILDING, build.sh, Makefile.
 Recent changes:
 ^^^^^^^^^^^^^^^
 
+20050531:
+	genassym.sh(8) was moved to genassym(1). You need to either build
+	tools first or install the version of genassym from /usr/bin before
+	you can build a kernel again.
+
+20050520:
+	Because a kernfs bug which xentools relies on was fixed,
+	xentools up to xentools20-2.0.3nb4 won't work with new kernel.
+
+20050417:
+	postinstall(8) was moved from /etc to /usr/sbin and made part
+	of the "base" set, to make it easier to invoke after an
+	upgrade.
+
+20050325:
+	pcppi(4) was separated in two devices, adding attimer(4).  Be sure
+	to add a config line for an attimer(4) device in your kernel
+	configuration, or you won't be able to set the pitch of the beep
+	with wsconsctl.  Depending on the default value for the pitch, you
+	might even not hear any more beep.  Also, it is advised to attach both
+	devices the same way (i.e., both on isa or both on acpi) or the
+	pcppi(4) device may fail to find the attimer(4) one.
+
+20050211:
+	Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in
+	some of the cross tools to fail if they use configure. Some configure's
+	cache the environment passed in and notice the new environment is
+	different and abort. Doing a clean in tools/ should be enough to
+	make a build continue.
+
+20050109:
+	Since su is using pam by default now, make sure that you have
+	/etc/pam.d populated (postinstall will do that automatically
+	for you). Otherwise su will fail open (i.e. will not require
+	a password).
+
+20041229:
+	Make had a path resolution bug that manifested itself as not
+	being able to install openpam.3. This bug has been fixed, but
+	you might need to rebuild make manually first to get through
+	the build.
+
+20041201:
+	Userland programs have been changed to use /dev/bpf instead of
+	/dev/bpfX. You need to create that device by installing a new
+	MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]*
+
+20041006:
+
+	A bug was introduced into /bin/sh (var.c rev 1.35) which causes
+	variables to not export correctly to subshells in all cases. This
+	will cause builds to break if that version of /bin/sh is installed
+	on the system. The proper version of /bin/sh can be verified with:
+
+        ident /bin/sh | grep var
+
+	Any /bin/sh w. version 1.35 will not work and needs to be updated
+	before attempting a build.
+	
 20041001:
 	The ipfilter kernel sources moved from sys/netinet to
 	dist/sys/ipf/netinet. Due to the move some Makefile
 	dependencies are now dangling requiring a make cleandir
-	before they work again (kdump, ktruss, rescue, ipf are
-	amongst the victims).
+	before they work again (kdump, ktruss, rescue, ipf, and
+	ftp-proxy are the victims).
 
 20040715:
 	The rc.d/sendmail script now uses a heuristic to determine
@@ -637,7 +696,7 @@ Recent changes:
 Hints for a more successful build:
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     Use build.sh, but do not use its "expert mode":
-	This will will automatically build the tools in the
+	This will automatically build the tools in the
 	   correct order, and it will keep the tools and the
 	   new build products from interfering with the running
 	   system.  This will allow you to ignore most of the