Updating all the timezone stuff one needs on a LAMP environment: (necessary in Australia because they changed the daylight savings start date once again). I haven't yet been able to convince my hosting provider to go through all this hassle; and the tables are outdated - so Aussie visitors may see an incorrect time on some of my websites for the next week. 

Test:

# zdump -c 2009 -v Australia/Sydney | grep 2008
Australia/Sydney  Sat Apr  5 15:59:59 2008 UTC = Sun Apr  6 02:59:59 2008 EST isdst=1 gmtoff=39600
Australia/Sydney  Sat Apr  5 16:00:00 2008 UTC = Sun Apr  6 02:00:00 2008 EST isdst=0 gmtoff=36000
Australia/Sydney  Sat Oct  4 15:59:59 2008 UTC = Sun Oct  5 01:59:59 2008 EST isdst=0 gmtoff=36000
Australia/Sydney  Sat Oct  4 16:00:00 2008 UTC = Sun Oct  5 03:00:00 2008 EST isdst=1 gmtoff=39600

(If the first two lines contain 'Mar' instead of 'Apr' you've got old tables). e.g. this is what an unpatched system would report:

# zdump -c 2009 -v Australia/Sydney | grep 2008
Australia/Sydney  Sat Mar 29 15:59:59 2008 UTC = Sun Mar 30 02:59:59 2008 EST isdst=1 gmtoff=39600
Australia/Sydney  Sat Mar 29 16:00:00 2008 UTC = Sun Mar 30 02:00:00 2008 EST isdst=0 gmtoff=36000
Australia/Sydney  Sat Oct 25 15:59:59 2008 UTC = Sun Oct 26 01:59:59 2008 EST isdst=0 gmtoff=36000
Australia/Sydney  Sat Oct 25 16:00:00 2008 UTC = Sun Oct 26 03:00:00 2008 EST isdst=1 gmtoff=39600

Debian:

# apt-get update 

# apt-get install tzdata

PHP5.x

# apt-get install php5-dev 

[fetch and save] http://pecl.php.net/get/timezonedb

# tar zxvf timezonedb-xxxxxxx.tgz

# cd timezonedb-xxxxxxx

# phpize

# ./configure

# make

# make install

# echo "extension=timezonedb.so"  > /etc/php5/conf.d/timezonedb.ini

# /etc/init.d/apache2 restart

MySQL:

# mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql -p

(ignore all the errors from Riyadh{NN}, iso3166.tab, and zone.tab) 

Those two or three people who actually visit this website may have noticed that I haven't done much with it lately. I think it's time to declare it over and done with - though I'll leave the archives here indefinitely should anybody wish to see the timeline of happenings. 

Blogging is so 2002. Social nets are so 2004. I'm tired of it all. Seems the world has tired of my writings as well (or more accurately it's just another channel of stuff amongst the 200+ million channels of stuff to choose from on the web). Thanks to the RSS fiasco and a host of other factors (e.g. search behaviour, PageRank changes, my use of a 'non-standard' community platform, etc.), traffic has plummeted way beyond rock bottom. We're now down to 3 visitors a day on average, down from 100,000 back in October and even the 20-30,000 around Christmas.

There's no point anymore writing into space - as I mentioned a few weeks back. The photo albums for friends and family are largely unseen. Except for two of you, friends and family are too intimidated by online spaces to touch the place.

The community site has been a dismal failure - a lot of hard work wasted. 

It's coming up on one year since I arrived in Australia, and so much has changed. Work and family consumes my time, as it should (at least family). Work is what it is. Blogging and social nets are a thing of the past, and tremendous time-wasters at that.

It was fun. Now onto the next chapter - of a book which probably won't be written online.

I'm pretty much ranted out.

The school start of session turned out to be a non-event thanks to all the preparatory work we've done in the last few weeks. Yawn. Whew!

Gas prices in San Francisco hit $3.35/gallon. Which infers that peninsula prices are probably closing in on $3.50. Whatever. Don't whine. We pay a bit over $5 here. 

The U.S. shoots down its errant Keyhole satellite. Seems that a load of hydrazine fuel may or may not be the hazardous substance they were warning us about - if indeed there was one. Likely this had something to do with posturing vis-a-vis China who shot a satellite to smithereens (actually large chunks) recently. If the thing smashed up over a major city it wouldn't really matter if it had a full tank or not. The death toll would be about the same either way. The real motive is probably that it was headed for a crash somewhere that the US couldn't get to and lock down the site. 

Nader jumps into the presidential race. Why now?  OK, better question - why at all?  The media never took him seriously enough to do their routine mudslinging probes. Let's quickly figure out what skeletons are in his closet and get rid of him before he screws up yet another election. 

Yesterday around lunchtime an entire subnet at the school went 'dark'. This is not good. The session ('semester' for my  friends in the northern hemisphere) starts on Monday. This is the absolute busiest time of year for faculty and staff because we've got a lot of stuff to prepare for next week when the hammer falls.

The curious thing is that the subnet that went 'dark' was only one subnet, and another subnet which traverses the same wire continues to work fine. So only a random smattering of machines was affected. This made it very difficult to even track down what happened because it appeared as a random cluster of machines that suddenly could not route packets. As it turns out they're all related by having an equal third byte of the IP address. What made it even more difficult to troubleshoot is that two of these machines which went dark are the primary DNS servers, so when they vanished, nobody could see anything 'by name' until we patched a couple of machines over to an alternate.

Trying to get anything done by IP number is a minefield, because even if you don't use any hostnames directly, you might accidentally touch a server or service which does - and you're screwed; waiting for it to time out (if you're lucky).  Some services just hang until you get tired of looking at the hourglass icon and then you have to go find another already logged-in session somewhere else to work. Can't start any new sessions because they mount home directories, which touch name servers and will hang.  

So I'm chugging the morning coffee and heading off to work an hour early this morning to try and recover from this disaster. Spent half the night awake formulating a plan after spending the entire evening determining for certain where the problem was. The problem is a router that's locked in a closet, and only the main campus IT folks have keys. Coincidentally, they made some configuration changes in that closet yesterday. Around lunchtime.

Gentlemen, get over here right now and unlock that door.

Unfortunately it isn't that easy, as there are layers of bureaucracy to contend with. My backup plan is to move two of our absolutely critical machines out of the darkness and into the light. One of them I can unplug and carry away. The other is a virtual machine living on two networks (which can run elsewhere) but I've got to find a wire in another room/building that can talk to both subnets. Oh and a cooperative host with enough disk and memory, that won't mind being loaded up with an alien machine.   

I've got this Minarik Goddess Special Edition guitar that I picked up to sell a few years back, and it never sold. So I kept it. It's really an awesome guitar, but I could never quite figure out why I didn't like it. It's 'meaty' (the best way to describe it). Not a speed demon. Should be great for jazz, rhythm, or chordings like heavy metal or ACDC. Beautiful to look at, exceptional tone quality. But it sounded like shit. I didn't do anything with it until recently because of this, and the fact that it was best left as-is as a collectible to hopefully sell some day. (Serial # 000025).

But finally I figured that it wasn't much good to anybody if it sat in the case year after year. So I put some decent strings on it, changed the neckstrap button to play it backward, and then did a setup (to match the new strings to the scale length). That improved things quite a bit. It no longer sounded horrible. But it was still lacking sustain. Curious because being so meaty you'd think that is where it would shine. The problem was the frets - big meaty badass frets that had been hand shaped. And therein lies the problem. The hand shaping left them a bit rough. It took a few weeks of playing for the strings to 'polish' both the frets and the intricate inlays and smooth them out. Now it sings like a bird. I can add it to the list of 'perfect' guitars that I've acquired over a lifetime of searching. It doesn't matter that it's 'meaty' because that's a quality that makes it suited for particular uses. No guitar is perfect for all uses. They all have their special qualities which makes them best suited for one thing or another.

Looks pretty much like this one,  except hers is left-handed. Mine is right-handed but I play it backward (left-handed). Don't ask. The answer will make your brain hurt. 

Coincidentally, my Phoenix acoustic (which is currently showing in the main macgirvin.com website banner) also has improved recently - although it was already near perfect. This was from a batch of guitars I bought a few years back that were all awesome except they all cracked and split. I've spoken about this previously. This one didn't actually split, but developed two hairline cracks on the backside (that didn't affect the sound or beauty). Anyway, I'm pleased to report that with relocating to a more humid environment,  the hairline cracks completely vanished! It's perfect once again, and as far as I know, the only surviving specimen of this incredible line of guitars.

Getting ready for the start of session next week so my postings have been and may be irregular for a while. Imaging lab machines, importing accounts, installing software for lecturers, that kind of thing. As soon as the students hit it'll be flat out for another few weeks as they all need to know how to set proxies and set up their mail accounts and every other system question that they come up with. 

But just so y'all don't feel totally neglected, here's a public service announcement from the anti-fur society. 

Remember folks, wearing animal fur is bad and makes you look ugly. See what I mean?   

Some notes to save somebody some grief:

Installing the Oracle libraries and access module into an existing PHP5 installation on Debian...

First grab the Linux instantclient from oracle.com - you'll also need the client SDK kit. Here I'm using instantclient 11.1

create a directory for these such as /home/oracle and unpack both of them to that directory.

Go into the oracle directory (and into the instantclient_11_1 directory) and create a symlink:

$ ln -s libclntsh.so.11.1 libclntsh.so

Grab the oci8 PECL package and unpack it somewhere (~/oci).

Make sure you have the following packages (in addition to php5, php5-cli, apache2, etc).

  php5-dev

  libaio1

Go to the oci8 directory (~/oci/oci8-1.3.0). Forget about 'pecl build' - which won't work. Well it will, but it will quietly and quickly remove all the built packages before you can save them or install them. Yargghh. I wasted half a day trying to fix this one. 

Better to just build by hand:

$ ./configure --with-oci8=instantclient,/home/oracle/instantclient_11_1 

$ make

Fix any errors/warnings before continuing

Don't make install, which won't work.

$ cp ./modules/oci8.so /usr/lib/php5/20060613+lfs

Replace 20060613+lfs with whatever module directory has been setup for you in /usr/lib/php5

Create /etc/php5/conf.d/oci8.ini:

----

extension=oci8.so

----

Now run the php cmdline in verbose mode (php -v) and see if everything loaded. Fix it if it didn't.

You may need some env variables setup in your /etc/init.d/apache2 file to make everything work and actually execute queries, but a phpinfo() at this point should show your oci8 extension. See the php.net Oracle pages if you need help with the env variables.

Today the Australian government officially apologized to the aborigines for taking their children away a few decades back 'to give them better lives'. 

However I don't think we're going to hear an apology any time soon for taking their continent away... 

via itnews: 

Terrorists may be using virtual worlds such as Second Life to meet and exchange ideas, security experts warned today..

...

The CIA already has a presence in Second Life which it uses it for meetings and training.

-----

Careful, the person you have virtual sex with might be either a terrorist or spook. Maybe they'll implant you with a virtual bug. Maybe they'll blow up your virtual house or suicide bomb your virtual store front. The mind reels....

I mentioned in an earlier rant that CNN is now figuring out where you are in the world, and expressed some concern that they would eventually use this to limit or control what news you view based on where you came from.

That day arrived. If you're outside the U.S. and now go to CNN.com you are now redirected to 'edition.cnn.com', which is titled 'CNN.com international'. You see something totally different from the default U.S. page - which if you're looking for it, can now be found at 'us.cnn.com'.

...Though one could legitimately question whether either site will have newsworthy content, regardless of where you're at. 

We went to the city today (Sydney) to visit the Viking furniture warehouse. You know the place. Large warehouse, all the products have Nordic names.

I started thinking about the modern Vikings and their contributions to the world. Ikea, Linux, Nokia. They're pretty impressive warriors in the modern world just as they were in the past.  

As I ponder the Microsoft/Yahoo! issue a bit more, what strikes me is Microsoft's arrogance. No, that's nothing new. But it's the corporate mindset that says 'We have to dominate online search'. Why? Why does Microsoft feel they have to dominate every software category that has ever existed, online and off? Why is it that nobody else can make a profit in the tech industry, without Microsoft threatening to take the ball away from them?

Google may make bold statements, the same way Netscape once made bold statements, but the fact of the matter is that Google is doing nothing to threaten Microsoft's business. McSoft's worst enemy is themselves and their arrogance. Get rid of that, and a tech industry could flourish - one where everybody can make new products and create markets and grow the industry as a whole. As it is today, you live in constant fear of being successful, because if you actually make money, you'll be in McSoft's laser sights and they'll stop at nothing to wipe you off the face of the earth. It's difficult for anybody to thrive under that kind of pressure.  

Super Bowl Sunday is here! Yay!

Oh wait a minute. The game doesn't start for another 24 hours. Roughly 8AM tomorrow (Monday) morning, about the time I'm chugging some coffee and driving down the cliff. Bummer.

Oh well, I haven't really been that big on the Super Bowl since back when Joe Montana and the Niners showed us how the game is meant to be played.  

Microsoft is making a bid to buy Yahoo!. Surprise, shock... What words could describe my emotion on hearing this?

I can see the motivation and the reasoning behind it. They want to put a stop to Google ("I'd like to buy a noun, please."). Still I believe this is the wrong way to do it. The only way for them to stop Google is to buy Google. Don't laugh. They are ideologically more closely aligned than you might realize. I don't believe that they've thought through the consequences of this decision - or maybe they have but just don't care. It is a culture clash of epic proportions that will result pretty much in the destruction of Yahoo! and all they've ever done - and do nothing to harm Google. I suspect many of the employees will quit outright, and there's not much place for them to go in Silicon Valley except to side with the enemy (Google), the largest employer in the valley that's still adding significant headcount.

But I also believe that this move can't be stopped, so it doesn't really matter what I think about it. I would however like to share with you the exact image that popped into my brain on hearing this.

Mardi Gras/Carnival is getting close, and the Brazilian government wants to make sure they don't end up with the typical swarm of unwanted pregnancies afterward. (I guess what happens in Rio tends to stay in Rio.) They are handing out 20 million condoms and an unspecified number of RU-486 pills this week. This has gotten them in a bit of trouble with the Catholic church.

But what you may not have heard is that last year, they purchased 1 Billion (with a B) condoms. What's to become of the other 980 million rubbers?

Something else you may or may not know is that condoms have a shelf life. They start to deteriorate after a couple of years - even with the best of modern packaging. You might only know this if you kept one in your wallet for 'emergencies' and found that it fell apart when put to use, or kept a stash in a drawer next to the bed and found they all crumbled when you reached for them.

So not only does the Brazilian government have a whole lot of protection to hand out, it also has a limited time in which to do it. This should be interesting. 

Sometime later this month "Diary and Other Rantings" (i.e. my weblog) will turn 7 years old, and I'll start my eighth year doing this activity called 'blogging'. Perhaps I'll mark the day, perhaps not. We'll see. Maybe I'll just stop doing it altogether. Maybe not. We'll see.

This all started in early 2001. I was at AOL making lots and lots of money from my Netscape stock options. I had a Netscape employee home page that was visited hundreds of thousands of times a day, but this was slowing. AOL no longer linked to it. I had started running a new server in the spare bedroom in 1998-1999, and later moved it to the garage. It took almost two years to get a working DSL link so that I could actually run a public website off of it. High-speed internet to the home was still an experimental technology. DSL wasn't yet ready for prime time and ISDN had other issues which plagued it. Leased-line required somebody to sell you an end-point on the public net and nobody was doing this, besides being limited to 56k which was now the speed of most modems. Web 'hosting' in those days was mostly for big business and costed big money. I could certainly afford it, but decided to spend my cash on more important things (like buying  a music store a year later).

Running a Linux box with an internet link isn't very expensive in the overall scheme of things. So once the DSL was finally working I made a new home page and started improving it.

I think it was Cindy at 'Off the Beaten Path' (now at 'dustingmybrain.com' ) who first introduced me to the concept of a rambling page. Instead of replacing your 'Current Interests' web page every week, you just keep adding to it. Drop in a date. Write what's happening. I started doing this. I was writing HTML in emacs. I called it an online diary. I didn't have titles, categories, RSS feeds, etc. These would come much later. I wasn't writing 'articles', I was just rambling. Why do you need a title for it? That makes it look so structured. The only important thing is the date, so somebody knows when it was that you thought this way. This was important. After several years of living on Netscape time, I firmly believed that one didn't think the same way for very long, and technology was always changing - so information had to have a date.

The other thing that I did was to take a cue from some of the large online news sites, which were the best model available for presenting information that had timestamps. I started writing in reverse chronological order (recent first). This was born of necessity, since nobody wanted to load a large page and scroll to the end to find recent stuff; which was how we did things previously (logfile format).  

In fact I maintained this format for a few years until it became unmanageable. Then I looked for ways of automating my monthly (or whenever) process of moving the current entries to an archive page and starting fresh. So after looking to see what programs were available and trying a few of them, I instead wrote a program to do it myself. Over time that evolved from a simple diary 'archiver' to the thing that you see today - a mega social portal that does everything but make coffee. (I miss this incidentally, I had my computer turn on the coffee pot from an online request in the early 1980s using my first homebrew social portal).  

I still wonder whether anybody reads these pages. Does anybody care? I don't subscribe to the current notions of SEO and affiliate marketing and trackware and all the other ways to improve one's blog ranking. Most notable these days are the pages and pages of 'widgets' attached to every blog, selling everything from online communities to soap. Why bother? Your only visitors will be other bloggers that are all trying to get you to visit their own blog. They aren't really reading what you have to say, they're too busy 'selling' their own wares. Still even after the RSS fiasco a few months back, I manage to pull in a few thousand humans a week. They come and read a page and leave again. This is the state of the modern internet.

It may be of some interest that I've managed to serve up a few hundred million pages since this all started - mostly to crawlers and robots; however last year activity peaked with about 100,000 daily hits (30,000 human visitors) and we've had six or seven days with over a million hits. I've written close to 1500 articles and there have been about 6600 total articles at one time or another from various feeds - before I was forced to nuke them for legal reasons. Only about 250 comments total, which I attribute to my decision a couple years back to do away with the daily spam cleanup and only allow website members to post comments. [I've since revised this policy.]

The 'community portal' (which I started writing a couple of years ago) doesn't have much community and I don't know if that will ever change. Community folks like big parties and unless you have one, you're late to the party. Bloggers only like communities where they can sell their blog.  I don't know how to convince them that a long-running website with several thousand non-blogging human visitors a week is actually a good place to drop a link. Yeah, I could put you on my blogroll, but I read thousands of blogs. It would quickly grow to be unmanageable and you'd be lost in the noise. 

But you can add your own link and profile page and whatever - you don't need me to do it. Hint, hint.  

Anyway - we'll see if this lasts or whether I just decide that there are better things to do. Write into space everyday and maybe a couple of people will read it. Maybe not.

That's what it's all about.

Don't ask yourself if it is actually relevant or important or whether anybody cares. You might not like to hear the true answer. It's one blog amongst hundreds of millions, all trying to be visited. All thinking they should be relevant to somebody. It's like asking if one star in the entire universe is relevant. Maybe one is relevant to somebody. But the big question looms, is it yours? Unless it's the sun and brings life to this planet, it's likely just another star in the vastness of space.  

In fact, nobody really cares whether you blog or not when all is said and done. Well maybe one or two folks. In my case those are the same one or two folks that cared back in 2001. Everybody else is just passing through on their way to somewhere else.

Still every day (sometimes two) I go to my website and ramble about what's on my mind. I tweak the software to make it better. Even knowing that it is all an exercise in futility. Strange.  

The school's weather station webpage seems to have stuffed it sometime around Thanksgiving. Today somebody finally noticed and alerted the support staff.

My boss asks "where's the documentation?".

Right.  There is none. This system has been in place for ten years or more and fails occasionally.  When that happens we go in and fix it.

Start with the webpage that actually displays the data. It's pulling the data from a file that is supposed to be automagically updated. Except we don't believe in magic. The file didn't get updated. Now to find out why.

Since this is a scheduled event, cron has to be involved. Let's have a look at the crontab file. Hmmm. It's pulling the changes from another file that is supposed to be automagically updated. That one hasn't been changing either. What changes that file? It isn't cron. Or is it? That file is symlinked to a file on another computer. Let's go have a look at the other computer. Ah, I see. There's a crontab running there which generates the contents of the update file from a data file via a collection of python scripts. Let's have a look at those. 

As I suspected, they are pulling data from yet another file that is automagically updated. Right. It hasn't changed since November either. What changes this file? Time to scan the logs. Nothing.

OK, it's time to start from the other direction. The weather station is connected to a PC in the corner of a lab. Let's have a look there. It's hung and totally unresponsive. OK, maybe that's the problem. I reboot it. Then go back to the webpage. Nope. Nothing has changed.

OK, somehow the data has to get from the weather station computer to the other computer where the python scripts can munge it. Let's have a look at the logs.

The logs say everything is fine, but it isn't fine. Nothing. It's not happening. Well this is interesting. I check connectivity and network connections. They're OK. We've got an IP addess and pings work just fine. A closer look reveals that there's a Windows task scheduler which occasionally FTP's the weather files across the net to the second Unix box. The logs don't show any errors. Hmmm. The files aren't being FTP'd though. They aren't making it. Then I see a notice at the bottom of the screen. Updates were applied some time since the computer was last powered on - six months ago. OK, what updates? Windows firewall. Right. So I have a look, and sure enough the computer's FTP connection has been firewalled because of an automatic update. The FTP's are silently failing - and indicating success. This is pure evil. After several minutes I'm able to get in with an administrator account that can fix the firewall and do so. 

Then have another look. Still nothing happening. What could be the problem now? Ah, on reboot FTP is automatically disabled on the weather station software - again without any warnings. The logs again say everything is working and files are being transferred. More evil. What's the use of having log files if they lie to you? I turn on the FTP. Bingo - now the files get through. Now back to the second computer to manually process the files and dump them into the directory where the third computer can pick them up. Then back to the third computer to manually update the processed files.

Yay! It works.

Back to the documentation. How would somebody document stuff like this? There's just too much that can go wrong. I could use up a tree or two writing it all down. This is why we've got systems folks. 

Still trying to figure out cricket. It's not as easy as one might let you think. For instance, here's the intro on wikipedia:

--- 

The bowler, a player from the fielding team, bowls a hard, fist-sized cricket ball from the vicinity of one wicket towards the other. The ball usually bounces once before reaching the batsman, a player from the opposing team. In defence of the wicket, the batsman plays the ball with a wooden cricket bat. Meanwhile, the other members of the bowler's team stand in various positions around the field as fielders, players who retrieve the ball in an effort to stop the batsman scoring runs, and if possible to get him or her out. The batsman — if he or she does not get out — may run between the wickets, exchanging ends with a second batsman (the "non-striker"), who has been waiting near the bowler's wicket. Each completed exchange of ends scores one run. Runs are also scored if the batsman hits the ball to the boundary of the playing area. The match is won by the team that scores more runs.

---

Sounds pretty easy doesn't it? Well keep reading:

---

The aim of the bowler's team is to get each batsman out (this is called a "taking a wicket", or a "dismissal").^[3] Dismissals are achieved in a variety of ways. The most direct way is for the bowler to bowl the ball so that the batsman misses it and it hits the stumps, dislodging a bail. While the batsmen are attempting a run, the fielders may dismiss either batsman by using the ball to knock the bails off the set of stumps to which the batsman is closest before he has grounded himself or his bat in the crease. Other ways for the fielding side to dismiss a batsman include catching the ball off the bat before it touches the ground, or having the batsman adjudged "leg before wicket" (abbreviated "L.B.W." or "lbw") if the ball strikes the batsman's body and would have gone on to hit the wicket.^[4] Once the batsmen are not attempting to score any more runs, the ball is "dead", and is bowled again (each attempt at bowling the ball is referred to as a "ball" or a "delivery").^[5]

The game is divided into overs of six (legal) balls. At the end of an over another bowler from the fielding side bowls from the opposite end of the pitch. The two umpires also change positions between overs (the umpire previously at square-leg becomes the bowler's umpire at what is now the bowling end, and vice versa). The fielders also usually change positions between overs.

Once out, a batsman is replaced by the next batsman in the team's line-up. (The batting side can reorder their line-up at any time, but no batsman may bat twice in one innings.) The innings (singular) of the batting team ends when the tenth batsman is given out, leaving one batsman not out but without a partner. When this happens, the team is said to be "all out". (In limited overs cricket the innings ends either when the batting team is all out or a predetermined number of overs has been bowled.) At the end of an innings, the two teams exchange roles, and the side that has been fielding bats.

A team's score is reported in terms of the number of runs scored and the number of batsmen that have been dismissed. For example, if five batsmen are out and the team has scored 224 runs, they are said to have scored 224 for the loss of 5 wickets (commonly shortened to "224 for five" and written 224/5 or, in Australia, "five for 224" and 5/224).

---