1.2.3 to 2.0 on VMware bombs

[jgreco]

An upgrade from 1.2.3 to 2.0 (i386) using the console upgrade tool bombed on one of our boxes, upgrading to BETA5.  It happened pretty much right after loading the vmware tools, so my guess is that maybe there's evil there and that old packages should be disabled as part of an upgrade.

Configuring CRON…done.
Starting OpenNTP time client...done.
Starting DHCP service...done.
Starting DNS forwarder...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting CRON... done.
Syncing packages: Open-VM-Tools
Syncing packages: done.
Executing rc.d items...
Starting /usr/local/etc/rc.d/vmware-guestd.sh...done.
Starting /usr/local/etc/rc.d/vmware-kmod.sh...done.
Bootup complete
panic: malloc_init: bad malloc type magic
cpuid = 0
Uptime: 29s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort

Annoyingly, even when chmod'd 000, those scripts are still executed; you have to actually move them out of the directory to get them to not run.  (Running scripts without an -x bit is almost certainly a separate bug)  After that it seems to work.

[jimp]

The most likely cause is the older vmware tools loading, leading to a panic.

I had thought we had a ticket open for that situation, but I don't see it. I just opened one:
http://redmine.pfsense.org/issues/1156