First off, to everybody who reads this via an aggregator or feed reader, my apologies. Here’s why:Last night I did both a LiveUpgrade to snv_56 and a `Roller`_ upgrade to 3.0-incubating. The Roller upgrade had the effect of re-publishing (via rss) all my previous blog entries as new. I noticed this early (way early!) this morning when I checked Google Reader and saw that my feed (yes, I’ve subscribed to my feed) was full of entries which I’d already marked as read.Yay for that.The LiveUpgrade mostly went ok, once I’d remembered that my mirror disk had to have its fdisk partition marked as active, and that I needed to run /sbin/bootadm update-archive as well as /usr/sbin/luactivate.Gah. Took me a few hours to work that bit out, because I hadn’t fully read the doco and when you’re at the non-gui console root prompt, the output from luactivate is more than 24 lines.One point of note though – since I run this webserver, `roller`_ and an internal dns in a non-global zone on zfs, I had to backup the contents of the zone first (took a zfs snapshot and then the extra precaution of physically copying the data somewhere else
.. image:: /images/smilies/icon_smile.gif
System Message: ERROR/3 (<string>, line 4)
Unexpected indentation.
- alt
-
:-)
), then destroyed the zone before running the lu. I’m pretty sure that particular bug has been fixed, but I couldn’t figure out even after extensive googling whether I had to be on a new release than snv_49 to do an ordinary lu. Hopefully for the next lu it won’t be an issue.I’m not sure whether I’ll bother to use svm to re-mirror my root device. At the moment I’ve got two lu BEs – “d0″ (with snv_49) and “snv” (with snv_56). If anybody has comments on goodness/badness of re-mirroring, please let me know. Since my data is mirrored with zfs, I’m not too worried about root. Maybe I should check out the zfs best practices sometime soon.Anyway…. once I’d gotten the new BE booted, I added the Simplified Chinese locale with localeadm, kicked fc-cache to re-run, then realised that I needed to do some futzing around to get roller to work. The templates and macros have changed, my roller resources directory (for photos and other uploads) was in the wrong place, and the roller.conf file’s docBase variable (under $CATALINA_HOME/conf/Catalina/www.jmcp.homeunix.com) was pointing to the wrong filesystem location for the webapp. With that all figured out, I now have to get my page layout and css back to an un-broken state then figure out the “front page” concept. Yes, I did read the release notes. Not sure how much of it stuck, though!
System Message: WARNING/2 (<string>, line 12); backlink
Duplicate explicit target name: "roller".
Docutils System Messages
System Message: ERROR/3 (<string>, line 2); backlink
Duplicate target name, cannot be used as a unique reference: "roller".
System Message: ERROR/3 (<string>, line 2); backlink
Duplicate target name, cannot be used as a unique reference: "roller".
