Ubuntu is one of those polarising technologies; Its really easy to use on a recreational basis, or as part of a institution/business wide rollout, but heartbreakingly awkward to use ‘alone’ within an entrenched business setting.
I had an incident recently where the Windows 7 side of my laptop connected easily to an open AP, but the Ubuntu 10.04 (or 9.04, tried both) wouldn’t, with the Intel Iwlagn drivers reporting in syslog a deauth (reason=6), basically the card spoke too soon. I eventually found the solution.
Sick of having dozens of old kernels sitting under your /boot/ dir? Want a simpler boot-life? Well we’ve got the solution for you. (more…)
SEE, or, Stanford Engineering Everywhere, has turned out to be my favourite E-learning resource; I’ve dipped into it a few times over the past few years but in light of my recent investment into a CUDA enabled Graphics Card, I thought that it was coming high time to brush up on my C++ programming, which I’ve basically left stagnant for two years after advancing no further than function pointers, structures, and templates.
So, in the spirit of openness that SEE tries to foster, I’ll be blogging my work through their CS106B course, Programming Abstractions, the second of three programming courses. (I passed on CS106A, Programming Methodology, since I’ve had enough Java shoved down my throat to last a lifetime…).
Everyone and their dog has a walkthrough of adding @anywhere hovercards to your blog. But the default has a small failing that irked me when I was re-doing my Blogroll (check them out, they’re all great! I promise!), and that was that if you take a tweep, like @god for example, it’ll happily wrap the hovercard around it, but if you have a link to this great status that @god posted, @anywhere won’t pick this @god up.
So, as you can see the blog is sporting a new, cleaner look. Nothing better than experimenting! One of the nicer aspects of the new setup is the shaded headers (ie. <h1>/<h2> tags).
Its a problem that I’ve come across, and I’m not the only one, so heres what works for me to find those pesky files that start with a .
ls -a | egrep -i "^\."
This only works in the current working directory, which is the normal usage.
FYI the reason that this is problematic is that the ‘.’ symbol is a single character wildcard; most people are familiar with the asterisk ’*’ indicating ‘anything, however long’, whereas the ‘.’ means ‘any single character’.
The command works by looking only at the first character of the file (‘^’, thats called a caret) and then removing the special meaning of ‘.’ by escaping it with the slash.
Update:18/4/10
@stevebiscuit correctly pointed out that the -i flag is unnecessary.
-iinstructs egrep to ignore the case of any matches, so that ‘HeLlO’ matches if you egrep -i for ‘hello’. Since there is no case for the ‘.’ symbol, the -i is pointless.
Folks, we’re basically screwed; The Digital Economy Bill recieved Royal Accent on April 9th and is officially now Law.
So after barely three days of parliamentary ‘debate’ where only 20-ish MP’s actually spoke on the subject (but somehow 189 MP’s decided it was a good idea anyway), our civil rights have been sacrificed infront of the alter of copyright.
Just incase you forget how to fix this the easy way: Enable mod_rewrite for URL voodoo; (Or any module replacing the
rewrite
)
$sudo a2enmod rewrite $sudo service apache2 restart
Remember to fiddle with
/etc/apache2/sites-available.*< \pre> and change "AllowOverride none" to "all" in any places that you're having trouble with rewritten URL's
So, a while ago I started personal logbook and wanted a way to keep those posts off the main blog (while still appearing in the RSS and twitter feeds).
Long story short, Blog-in-blog gets a given category off the main blog, and with thinks to the wordpress.org support forum I was directed to the Page Links To plugin, which added the necessary navigational behaviour.
Job Done!
