Upgraded to WordPress 3.0

It seems to have gone completely cleanly, at least at first glance.  I do of course have a database backup and a file backup from just before the upgrade.

I haven’t looked into what new features I might want to exploit in my custom theme yet; nor have I looked at maybe using any of the standard themes.  There are certainly infelicities in my own theme that I’d like to get rid of.

Server Upgrade Chronicles IIa

Didn’t find any useful information.  Asked today online, and found t/3 of what I need at least, so I can revisit the install and upgrade tomorrow (got better things to do tonight). I need to resolve the uncertainties about update before considering doing it to the real server. Maybe I should just wait for the next stable release, due in March and expected in April.

Meanwhile, yesterday the new SAS disk controller arrived. I’ve now got all the hardware to install into the box, and I can do that without changing anything associated with the current boot or data disks, so I probably will. Try things out on the new hardware and new disks, before cutting over.

Meanwhile, not sure why WordPress is displaying the time in UTC.

ETA: Okay, install log is fairly clean.  There’s “device pciclass,030000@3(display#0) keeps up device sd@0,0(sd#0), but the latter is not power managed” and “/usr/lib/powerd: [ID387247 daemon.error] Able to open /dev/srn” and “SUNW_piclmemcfg init mc failed!”

Added Emacs.  Going to shutdown, snapshot, and start update from there.

ETA: On boot, several popup errors, and this in the logs:

Feb  5 07:47:08 osol-play-002 nwamd[37]: [ID 116842 daemon.error] sysevent_bind_handle: Permission denied
Feb  5 07:47:11 osol-play-002 genunix: [ID 127566 kern.info] device pciclass,030000@2(display#0) keeps up device sd@0,0(sd#0), but the former is not power managed
Feb  5 07:47:11 osol-play-002 /usr/lib/power/powerd: [ID 387247 daemon.error] Able to open /dev/srn
Feb  5 07:48:53 osol-play-002 inetd[6089]: [ID 702911 daemon.error] Failed to update state of instance svc:/application/x11/xfs:default in repository: entity not found
Feb  5 07:48:53 osol-play-002 inetd[6089]: [ID 702911 daemon.error] Failed to get instance for svc:/application/x11/xfs:default
Feb  5 07:48:53 osol-play-002 inetd[6089]: [ID 702911 daemon.error] Failed to update state of instance svc:/application/x11/xfs:default in repository: No such file or directory
Feb  5 07:48:53 osol-play-002 inetd[6089]: [ID 702911 daemon.error] Failed to update state of instance svc:/application/x11/xfs:default in repository: entity not found
Feb  5 07:48:53 osol-play-002 inetd[6089]: [ID 702911 daemon.error] Failed to get instance for svc:/application/x11/xfs:default
Feb  5 07:48:53 osol-play-002 inetd[6089]: [ID 702911 daemon.error] Failed to update state of instance svc:/application/x11/xfs:default in repository: No such file or directory
Feb  5 07:49:01 osol-play-002 ip: [ID 224711 kern.warning] WARNING: Memory pressure: TCP defensive mode on

But, unlike the previous attempt, the system did boot. I halted and snapshotted it immediately after the boot.