Another release of Wordpress another potentially PITA upgrade to complete, but it isn’t thanks too patch. I quickly ran a diff of the Subversion repository like so:
$ svn diff http://svn.automattic.com/wordpress/tags/2.1.2 http://svn.automattic.com/wordpress/tags/2.1.3
Piped it to a file and applied it to Wordpress using patch, no drama no mess no effort. Just the way I like it 
I have upgraded the version of Wordpres my blog runs, for me this is a pain in the ass due to custom modifications. So, this time I decided to use their subversion repository to create a patch and use that, guess what it worked first time.
To patch:
$ patch -i ./wordpress-2.1_2.1.2.diff -d /path/to/wordpress -p0
Its hard to deny that phpMyAdmin is a little slow (being generous) this annoys me when I just want to make a quick change to something in a configuration table and I have to wait 30 seconds for it to output the page. I have found the solution in the form of MySQL Quick Admin, it is very fast, lean and clean. It has so far not failed to impress, it doesn’t have the power of phpMyAdmin but it is far cleaner and quicker to output pages.
As I said earlier I have upgraded my blog here to Wordpress 2.1, codenamed ‘Ella’, and I am impressed by the improvements. The categories hierarchy makes sense, I have added a few more categories in to neaten it out a bit which makes it more manageable, and look better on the index. The draft saving feature has not saved me yet, but it does appear to be saving, lousy pun I know!
Very Pleased 
I will be performing some administration tasks which will means killing the RAID array which serves most of my data, temporarily, so, expect evident breakage.
Well I was trying to play around with some groovy new features in OpenSSH, namely its ability to create a secure VPN connection between two points. Its a fairly new feature so howto’s are thin on the ground, anyway I was persisting to make it work. I had multiple remote sessions open up on my server and a few to my PC here at uni, and anyway. I wrote out a command to alter the routing tables to hopefully allow me to connect, it was totally wrong, but I sent it to the wrong machine, the remote one.
Pop …
… my server disappeared off the internet, I had told it to route all traffic bound for external addresses down the SSH tunnel which had also died. I managed to solve the problem by divulging my password and SSH keys to my brother at home who ran the appropriate command to fix the routing table.
I think I am just gonna stick with local port forwarding over SSH, I could really do with another host running at home. You learn the hard way I guess.
I spent a goodly while reconfiguring my email services on Friday and Saturday, then to find the script I wrote Saturday night went bye bye in the powercut I had all of Sunday 
Anyhow.
I know have this sorta layout for my incoming mail:
|--> Sieve Rules -->|
| |
Postfix (SMTP, MTA) => Dovecot Deliver (LDA) => Maildir (storage) => Dovecot (IMAP & IMAPs)
The new bit is the Sieve Rules and Dovecot Deliver as my LDA, the motivation behind this was my dependance on Thunderbird rules which are of course client side. So, when I read my mail in webmail it was not sorted for me Postfix’s LDA had to go and in came Dovecot’s which interfaced with sieve using some experimental code *quivers*. But it works and I am dead happy The script I mentioned was a walk around to a problem in the experimental code where the from address is not passed correctly to sendmail, my script fixes this (if anyone wants it post a comment).
I could not have accomplised this without help from the following resources:
Also dead handy for the SQL adjustments I made to my postfix table, also used the MySQL string reference a lot.
All content on this site are my own thoughts and opinions not those of my employer or projects I contribute to.
You are currently browsing the archives for the Site category.
Chris is excited new Metallica single and album soon :D. (Yesterday)
Previously:
It is currently Fri Aug 22, 2008 12:26 am BST