With today's (Monday) current, I'm seeing the following problems:

    uname(3) is broken - I've traced this down to the sysctl() for
    	KERN_VERSION failing with ENOMEM...the source for uname(3) 
    	looks good as best I can tell.  This of course breaks
    	uname(1).

    kernfs file sizes are broken - They show up like this:

nirvana::mark-21> ls -l /kern
total 0
-r--r--r--  1 root  wheel            -4294967195 May 17 01:24 copyright
-rw-r--r--  1 root  wheel            -4294967288 May 17 01:24 hostname
-r--r--r--  1 root  wheel            -4294967292 May 17 01:24 hz
-r--r--r--  1 root  wheel            -4294967276 May 17 01:24 loadavg
-r--r--r--  1 root  wheel            -4294967291 May 17 01:24 physmem
brw-r-----  1 root  operator    0,   0 Apr 20 01:41 rootdev
-r--r--r--  1 root  wheel            -4294967279 May 17 01:24 time
-r--r--r--  1 root  wheel            -4294967170 May 17 01:24 version
nirvana::mark-22> 

    Finally, escaping $ in sh seems to have busted.  The following 
line which used to work now tries to map to arg 6.  It may be a POSIX thing
but it works under bash.  It only shows up with double escapes and 
recursive shells.  This shows up in a script when trying to pass something
like foo=`awk " print { \\$6 }" `, but is easily illustrated with the
following example:

sh-6/15:

$ echo `echo $6`

$ echo `echo \$6`

$ echo `echo \\$6`

$

bash:

bash$ echo `echo $6`

bash$ echo `echo \$6`

bash$ echo `echo \\$6`
$6
bash$

If bash is wrong then I'd appreciate the "right" way to do this...
The kernfs and uname broke going from 5/6 current to 5/12 current and
stayed busted through today (everything else broken over the weekend
seems to have been gotten).  I'm not sure where sh broke since it
didn't build for sups over 5/12 and 5/13.

-Mark


------------------------------------------------------------------------------