The File::Find::Rule::VCS module excludes certain directories, artifacts from version control systems, from your File::Find::Rule queries. While it’s aware of the big two (subversion and CVS) today I needed a version that was aware - and can ignore - RCS directories. So I hacked the module and tada, we now have a File::Find::Rule::VCS RCS support patch. I’ve sent a copy to the module author but I’m putting it here as well in case it gets rejected.
The work is done, the script is written and from this Sunday night my RSS aggregator will kill any post that’s from before noon on Saturday. This is all part of my (proably pointless) attempt to prevent backlogs and pile ups of unread things. I’m not going to release any of the (very hacky) scripts as they all assume lots about their running environment but I thought I’d mention it in case I can inspire anyone (Lee) to clear out their queues every now and again. Read on →
Amazon sent me one of the more amusing recommendations I’ve ever had: Greetings from Amazon.co.uk, We've noticed that customers who have purchased books by Rael Dornfest have also ordered "Adolf Hitler: A Portrait" by Michael Fitzgerald. I know O’Reilly are not the most popular of companies since the web 2.0 incident but I didn’t think they’d fallen that far… :)
When it comes to host-based intrusion detection I’m most familiar with the Tripwire OpenSource Edition, while shopping around for a HIDS to deploy on a play box I decided to try AIDE. And got stopped at one of the first hurdles. Tripwire has an interactive update mechanism, it runs a scan (based on your config file) and then prompts you to except, reject or mark changes as pending - within one operation. Read on →
Due to some other, recently appearing, demands on my spare (and not so spare) time I’ve had to drastically cut back on the amount of time I spend working with different Free and Open groups. One of the biggest casualties of this has been the UKUUG. I no longer have the time available to make any meaningful contributions so I’ve stepped down from the UKUUG council. As a group they’re doing a lot of interesting work, and some great conferences, so it’s worth looking at their site every now and again.
I saw a description of Brick when I was looking for the X-Men 3 release date and it grabbed my attention pretty quickly. “A modern day film noir sit in a high-school” seemed very Whedon. And now that he’s got nothing on the air I’m finding it harder to get my regular dose of Joss. The film itself was great, very stylishly shot, featured a solid performance from the “hero” and had great dialogue. Read on →
I’m not a lawyer, so this is based on my uneducated understanding, but from what I can gather, if you use the phrase Web 2.0 in the name of a conference then O’Reilly and CMP are within their rights to send you a Cease and Desist. Even if it’s a non-profit Web 2.0 conference like IT@Cork. Who now have coverage of their event I’d kill for :) I think what’s annoyed a lot of people is that they’ve been dupped in to promoting a clumsy, easy to mock, phrase that’s never been more than a marketing term. Read on →
I’ve seen two posts today, each of them about technical events, that caught my interest and deserve a comment. The Farm on the Rails Seminar Admissions Test is something I’ve thought about in the past and never come to a conclusion about; how do you do an advanced event without pissing people off? The Pragmatic Studio’s Advanced Rails Studio approach is to ask for demonstration code, a site or a decent write up of previous experience. Read on →
If you say, “I need this by the end of today. At the absolute latest!” (or some close variation) which of these do you think is most likely outcome? I admire your spontaneous creativity and willingness to “motivate” people in to achieving your goals or I think you can’t plan for shit and have no ability to manage your time or projects? Want a hint?
Booty Call: “Booty calls can be used by one partner of an ended relationship to obtain sex from the ex-partner, due to lingering emotions and feelings of a need for continued physical connection.” This one’s pretty obvious, it’s a replay attack. You’ve already gone through the authorisation and authentication processes and now you’re reusing previously obtained credentials to obtain access to a resource.