Well we were sitting down eating pizza, and watching the kids down below “losing” their balloons, after an hour or so there was a pretty large collection of them sitting around the roof. Now question is whether someone went up there to bring them down, or did they just wait a few days for the helium to leak out?
Unfortunately, only had my phone with me – so not as nice a picture as it could’ve been – still, and interesting view.
so one shiny nokia e65, and a bit of frustration, later; have found the following recipe for getting the phone to sync correctly with iSync.
Firstly download the plugin from Nokia
Then install and if you get a rather cryptic error like this:
[Nokia E65] Device is not available or synchronization was cancelled. Close dialogs and applications on the phone and try again. Device “Nokia E65″ synchronization failed Looks like the Nokia installer drops the plugin into a strange location (originally it allowed isync to work once and then I got the error message
Configure the zone you want, this is just a basic configuration (suited to a name server - that inherits the global zones /var/named)
# zonecfg -z solzone solzone: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:solzone> create zonecfg:solzone> set zonepath=/u01/zones/solzone zonecfg:solzone> set autoboot=true zonecfg:solzone> add net zonecfg:solzone:net> set address=10.10.10.20/24 zonecfg:solzone:net> set physical=bge0 zonecfg:solzone:net> end zonecfg:solzone> add fs zonecfg:solzone:fs> set type=lofs zonecfg:solzone:fs> set special=/u01/zonedata/solzone zonecfg:solzone:fs> set dir=/u01 zonecfg:solzone:fs> end zonecfg:solzone> add inherit-pkg-dir zonecfg:solzone:inherit-pkg-dir> set dir=/var/named zonecfg:solzone:inherit-pkg-dir> end zonecfg:solzone> add attr zonecfg:solzone:attr> set name=comment zonecfg:solzone:attr> set type=string zonecfg:solzone:attr> set value="test solaris zone" zonecfg:solzone:attr> end zonecfg:solzone> verify zonecfg:solzone> commit zonecfg:solzone> exit And now install and boot the zone
Hmm, nice little error when trying to start db2 on solaris 10, stating that it was unable to start up the database and i should check my SHM settings!
Arrgh!
prctl reported correct project settings, so tried truss:-
# truss -f db2start truss: cannot trace set-id or unreadable object file: db2start Cue alarm bells, proven by trusty “ls”:
# truss -f db2start -rwsr-xr-x 1 root root 238584 Jul 10 12:28 db2start Add root to the user.
Found this written by Frank Hofmann, very interestly little history lesson about the x86 chipset. (he also talks about how HOSTID is generated on solaris x86 - which shows how important it is to keep track of your /kernel/misc/sysinfo file for hostid locked software :D