Am I the only one lucky enough to be getting the
	"size > 0"
panic in 2.0?  (On alpha, if it matters).

uvm_map.c says:
	/*
         * zero-sized mapping doesn't make any sense.
         */
        KASSERT(size > 0);

Booted 2.0 twice today.  Got this panic both times, only a minute
or so into multiuser, not much going on.

Also, am I the only one lucky enough to have it print "syncing disks"
and then hang? (requiring a push of the reset switch).  I've gotten
this hang with both 1.6.2 and 2.0.