February 08, 2010

First the Ady Gil… now the MV Bob Barker ???

Back in early January the Ady Gil was damaged and sunk by the Shonan Maru 2 in the Souther Ocean off Antarctica during protest action by the organisation Seashepherd and now the MV Bob Barker has suffered damage at the hands of the Japanese Illegal Whaling crew from the Yushin Maru 3. It is time that the international community takes action to put a stop to Japanese “Scientific Research” (AKA Whaling) and end this ruthless act…

Bob Barker Rammed by Illegal Whaler

At 1209 PM Fremantle, Australia time, the Yushin Maru 3 intentionally rammed the Sea Shepherd ship Bob Barker, penetrating it’s hull and endangering the lives of it¹s crew. The collision occurred at 65 degrees 21 South, 67 degrees 58 East, about 180 miles off Cape Darnley in the Australian Antarctic Territory.

The Bob Barker had been actively blocking the slipway of the Nisshin Maru, the Japanese whaling fleet’s factory ship when the collision occurred. Four harpoon ships, the Yushin Maru 1, 2, and 3 and Shonan Maru 2, were circling and making near passes to the stern and bow of the Sea Shepherd vessel. The Bob Barker did not move from its position. At which point, the Yushin Maru 3 intentionally rammed the Bob Barker, creating a 3-foot long 4-inch deep gash in the mid starboard side of the Sea Shepherd vessel above the waterline.

No crew was injured during the collision. The Bob Barker continues to block the slipway of the Nisshin Maru, preventing the transfer of slaughtered whales and effectively shutting down illegal whaling operations.

The incident demonstrates a continued escalation of violence by the illegal whalers in the Southern Ocean Whale Sanctuary.

Said Captain Paul Watson from the bridge of the Steve Irwin, currently en route to join the action, “Because the whalers got away basically scot-free with the outrageous sinking of the Ady Gil, they now apparently think they can do whatever they want and they appear to have no qualms about endangering Sea Shepherd crew. What we really need is for the governments of Australia and New Zealand to step up and start enforcing maritime laws in these waters, or who know what the whalers will do next. Australian and New Zealand lives are at risk every day in these waters.”

The crew of the Bob Barker noticed that the Yushin Maru 3 stopped moving in the water shortly after the impact, and appeared to be falling behind as the Bob Barker maintained its position on the stern of the Nisshin Maru. It’s possible the Yushin Maru 3 damaged itself in the collision.

The Japanese whalers are far more aggressive this year than in past campaigns.

Sourced from www.seashepherd.org

The Australian Government has let not only the people of Australia down by not sending a Naval Vessel to the area to ensure that no further aggression from the Japanese Whalers, but also that of the international community as well. What will it take to end this pointless practice? and should the scientific community be requesting proof of “Research” as claimed by the Japanese as their primary reason for such need to “cull” whales in the Southern Ocean.

In my opinion the only thing scientific here is the weight in tonnes of whale meat ending up on the tables of Japanese restaurants! see the following article from NewScientist Although this article is a little old, it still raises many valid questions into the practice.

© 2010, Scott Evans. All rights reserved.

February 07, 2010

Wayatinah Fires

On January 31 a fire was reported in central Tasmania. This fire is is located in some rather inaccessible terrain and also has some logging coups that if they go up in flames will make controlling the fire all the more difficult. So why am I mentioning this? well, there is a group of enthusiastic amateur radio operators that have assisted with helping the Tasmanian Fire Service (TFS) by providing their time to operate with the Incident Management Team (IMT) as radio operators. This is a job that not only requires great attention to detail, but also the ability to ensure that the information from the fire ground (where the fire is burning) to the relevant person in the IMT.

So far this fire has been burning for 8 days and I’ve been assisting with radio operations for 7 of these days! and as such I just wanted to make you aware of some of the on-line resources that the TFS have.

For a listing of all current bush fires you can get a summery from www.fire.tas.gov.au this listing is updated frequently from information received from the units attending the fires etc.  There is also RSS feeds that you can subscribe to as well thus keeping the page requests to a minimum! for example… when the smoke from the Wayatinah fire drifted over Hobart the TFS website did suffer from a lot of requests for current information as to where the smoke was coming from!

There are also KML Google Map Feeds for use with Google Earth to get a birds eye view of the area affected!

The current information for the Wayatinah fire is available from here

The current map showing the fire size & burnt out area is available from here

© 2010, Scott Evans. All rights reserved.

February 06, 2010

My first Android App

 Well, here's my first Android App. Essentially it's a recreation of my Google Wave Robot - OpenAusBot, well at least the House of Reps member search.

Right now, it just does basic member searches based on Federal Seat, returning name, party and date elected. Still working on the ImageView.

Further plans are to build postcode search and geo-search.

What I don't have (yet) is a real android phone, so if anyone wants to download the apk attached to this post and make sure it works (it uses the Android 2.0 SDK), that would be great, thanks.

AttachmentSize
android_openaus.apk17.61 KB
android_openaus_16.apk17.61 KB

February 05, 2010

Howto Setup a Private Package Repository with reprepro with nginx

As the number of servers I am responsible for grows, I have been trying to eliminate all non packaged software in production. Although ubuntu and Debian have massive software repositories, there are some things which just aren't available yet or are internal meta packages. Once the packages are built they need to be deployed to servers. The simplest way to do this is to run a private apt repository. There are a few options for building an apt repository, but the most popular and simplest seems to be reprepro. I used Sander Marechal and Lionel Porcheron's reprepro howtos as a basis for getting my repository up and running.

nginx is a lightweight http server (and reverse proxy). It performs very well serving static files, which is perfect for a package repository. I also wanted to minimise the memory footprint of the server, which made nginx appealing.

To install the packages we need, run the following command:

$ sudo apt-get install reprepro nginx

Then it is time to configure reprepro. First we create our directory structure:

$ sudo mkdir -p /srv/reprepro/ubuntu/{conf,dists,incoming,indices,logs,pool,project,tmp}$ cd /srv/reprepro/ubuntu/$ sudo chown -R `whoami` /srv/reprepro/ubuntu/ # changes the repository owner to the current user

Now we need to create some configuration files.

/srv/reprepro/ubuntu/conf/distributions

Origin: Your NameLabel: Your repository nameCodename: karmicArchitectures: i386 amd64 sourceComponents: mainDescription: Description of repository you are creatingSignWith: YOUR-KEY-ID

/srv/reprepro/ubuntu/conf/options

ask-passphrasebasedir .

If you have a package ready to load, add it using the following command:

$ reprepro includedeb karmic /path/to/my-package_0.1-1.deb \# change /path/to/my-package_0.1-1.deb to the path to your package

Once reprepro is setup and you have some packages loaded, you need to make it so you can serve the files over http. I run an internal dns zone called "internal" and so the package server will be configured to respond to packages.internal. You may need to change the server_name value to match your own environment. Create a file called /etc/nginx/sites-available/vhost-packages.conf with the following content:

server { listen 80; server_name packages.internal; access_log /var/log/nginx/packages-error.log; error_log /var/log/nginx/packages-error.log; location / { root /srv/reprepro; index index.html; } location ~ /(.*)/conf { deny all; } location ~ /(.*)/db { deny all; }}

Next we need to increase the server_names_hash_bucket_size. Create a file called /etc/nginx/conf.d/server_names_hash_bucket_size.conf which should just contain the following line:

server_names_hash_bucket_size 64;

Note: Many sites advocate sticking this value in the http section of the /etc/nginx/nginx.conf config file, but in Debian and Ubuntu /etc/nginx/conf.d/*.conf is included in the http section. I think my method is cleaner for upgrading and clearly delineates the stock and custom configuration.

To enable and activate the new virtual host run the following commands:

$ cd /etc/nginx/sites-enabled$ sudo ln -s ../sites-available/packages.internal.conf .$ sudo service nginx reload

You should get some output that looks like this

Reloading nginx configuration: the configuration file /etc/nginx/nginx.conf syntax is okconfiguration file /etc/nginx/nginx.conf test is successfulnginx.

Now you can add the new repository to your machines. I recommend creating a file called /etc/apt/sources.list.d/packages.internal.list and put the following line in the file:

deb http://packages.internal/ubuntu/ karmic main

To make the machine aware of the new repository and associated packages, simply run:

$ sudo apt-get update

That's it. Now you have a lightweight package repository with a lightweight webserver - perfect for running in a virtual machine. Depending on your setup you could probably get away with using 256Mb of RAM and a few gig of disk.

February 03, 2010

Packaging Drush and Dependencies for Debian

Lately I have been trying to avoid non packaged software being installed on production servers. The main reason for this is to make it easier to apply updates. It also makes it easier to deploy new servers with meta packages when everything is pre packaged.

One tool which I am using a lot on production servers is Drupal's command line tool - drush. Drush is awesome it makes managing drupal sites so much easier, especially when it comes to applying updates. Drush is packaged for Debian testing, unstable and lenny backports by Antoine Beaupré (aka anarcat) and will be available in universe for ubuntu lucid. Drush depends on PEAR's Console_Table module and includes some code which automagically installs the dependency from PEAR CVS. The Debianised package includes the PEAR class in the package, which is handy, but if you are building your own debs from CVS or the nightly tarballs, the dependency isn't included. The auto installer only works if it can write to /path/to/drush/includes, which in these cases means calling drush as root, otherwise it spews a few errors about not being able to write the file then dies.

A more packaging friendly approach would be to build a debian package for PEAR Console_Table and have that as a dependency of the drush package in Debian. The problem with this approach is that drush currently only looks in /path/to/drush/includes for the PEAR class. I have submitted a patch which first checks if Table_Console has been installed via the PEAR installer (or other package management tool). Combine this with the Debian source package I have created for Table_Console (see the file attached at the bottom of the post), you can have a modular and apt managed instance of drush, without having to duplicate code.

I have discussed this approach with anarcat, he is supportive and hopefully it will be the approach adopted for drush 3.0.

Update The drush patch has been committed and should be included in 3.0alpha2.

International Women’s Day Competition

There’s only something like 2 and half weeks left for the women of all ages in all parts our community to tell us how they discovered Ubuntu for the International Women’s Day Competition.

That means that you really ought to get a move on!

The process is easy:

  1. Women and girls email us (address and rules in announcement) a description of how they discovered Ubuntu. Whether it was at school, work, from a partner or because they were sleep-computing and woke up to the sound of drums — whatever!
  2. In just over 2 weeks time, we put up the stories and let the community vote for their favourite
  3. On March 8th, the favourite is declared, and we make Jono earn his keep by announcing it and drawing the second surprise winner from a hat on his ustream channel or vidcast or whatever it is kids call that funky video stuff these days.
  4. Two lucky ladies get a share of this loot:

Bags, tshirts, magazines, books and other fun stuff

Amber describes the prize packs thusly:

    ***Prize packages are being sponsored by: Canonical, Linux Pro Magazine and Ubuntu-User Magazine. Package includes but not limited to: Ubuntu backpack, Ladies T-shirt, Ubuntu Key Chain, 1 year digital subscription to Linux Pro Magazine or a 1 year print subscription to Ubuntu User Magazine, and a copy of The Art of Community. Thank you all so much for your gracious support and sponsorship.

    Help spread the word by telling all the women you know who use Ubuntu and by hitting up digg and /.

    February 01, 2010

    In process we trust

    Folks who follow my various social networking instances have probably figured by now that I am in somewhat of a peeved state currently, and mostly due to the way various things have been handled by the Ubuntu Community Council (as an institution, not any individual counsellor) over recent times. I’ve been involved in the Ubuntu Community for the past 4 years, and my motivation for staying has dwindled rapidly in the past 4 months.

    This post is as much me getting stuff off my chest as it is about providing my perspective on what is wrong with the system. I’m going to work through all this in reverse order, as I think it will make more sense to others this way.

    The appointment (it was not an election irrespective of what the process was called) of the UW Leader was the final straw. Seriously, please don’t get me wrong — my grievance is 101% with the CC here. Amber is a smart and wonderful person and will try her best and probably do an ok job of it, and we’re working on some really cool things together. However, I’m worried about the detriment of latency that a newcomer leading the team will bring about. I have been around the group for years in a passenger-seat role but my experience but was overlooked. I’m really quite terrified that despite working alongside Amber, it won’t be enough.

    Approximately a month earlier saw the eventual (after months of inaction by the CC) appointment of a renewed IRC Council. There are now no original IRC Councillors remaining. I was one of the 2 remaining who put their hands up for another term, and after the CC decided they were unsatisfied with the applicants and staged another call, neither of us was appointed. This Council now lacks the benefit of prompt historical insight in to the evolution of the Ubuntu IRC-scape, the relationship with Freenode, and (in a big way) many troublesome chatters. I’m already seeing cracks showing thanks to this.

    And this brings me to the final point. I was discussing all this with another individual on Tuesday following the realisation that the Asia/Oceania Regional Membership Board is nearing “election” time. After musing whether I’ll be permitted to continue with that role since (I feel that) I’ve been pushed from the other roles, and explaining my discontent with recent behaviour of the CC (as a whole, not individual members), the individual asked me “But if you’re unhappy with the CC, why weren’t you on this list: http://www.cs.cornell.edu/w8/~andru/cgi-perl/civs/results.pl?id=E_f802a7d79840b58a“. After responding that actually, I had been nominated, but had been silently dropped in the cut down to 12, the response I got was “I’d rather have public nominations, and then have the incumbent CC select the new CC than the mess you expose.”.

    I think that last exchange this week summarises my discontent rather neatly.

    My opinion in criticism of the CC is, as far as some folk are concerned, moot. If you don’t run, you don’t get to criticise, right? Sure, fair enough. Except that since few people know I was nominated for and willing to hold a seat on the CC, this is the response I’m getting. That hurts. There was a lack of transparency from the CC, and it’s making my word worthless.

    The IRCC went through a fightclub-esque appointment process because folks FUDwashed the CC, convincing them that the IRCC is corrupt and needs supervision. UW got similar treatment because dudes have been petitioning that the group is hostile because there’s not enough good stuff to outweigh the bad stuff.

    Validation for non-elections for both groups has been given as a lack of definition of voting group and that is quite frankly, IMHO, nothing more than a convenience. Voting groups could have been defined (and funnily enough one has been defined for the UW scope vote), but in both cases doing so was refused for the leadership appointment processes.

    I mean, people are aware that folks need to and do talk theories and things through privately. In all groups, especially governance groups like the IRCC. And that this is essential to the functionality of these groups, right? Right? At least, I’d hope so. Privacy doesn’t kill transparency — trying to eliminate privacy does.

    And here is the clincher.

    Who knows how the CC (as a whole) came to their decisions on these things? I don’t. It was private. I can only theorise (or ask and still theorise about the response). And to be perfectly honest, I can and do accept that at face value when I can trust the group.

    What I cannot accept is that concurrently similar privacy within the IRCC and different (but not unique, see other unlogged social channels such as #ubuntu-offtopic and various LoCo channels) privacy in UW isn’t acceptable. And this privacy within the IRCC and UW are part of why these non-democratic faux-meritocratic appointment processes were so closed, and exist to begin with in the case of the latter. I cannot accept that hypocrisy, and it alters how I (and others) theorise this stuff. Drastically.

    It kills my trust in the CC.

    Most importantly. It kills my motivation.

    I’m still on the Asia/Oceania Membership Board for another few months (and will be seeking re-whatevering), and I have a few things to do within Ubuntu Women still. Once those things are over with, I really don’t know where I’m going to end up. I do know that if the current trend follows, it is unlikely to be with Ubuntu.

    January 28, 2010

    “Control” will the end-user be recognised?

    Well the campaign against mandatory ISP filtering by internetblackout.com.au has certainly been causing a stir both in the media & on-line forums. Some statistics are always good viewing!

    • 500+ verified participating sites
    • 296,000+ unique visitors to the campaign site
    • 438,000+ views of the blackout info popup

    Here is some information provided by Jonathan Barnett (via facebook) detailing the history of the proposed bill…

    Internet Filtering Policy

    Stuart Fenech

    28 January 2010

    The Internet filtering policy has changed around six times since it was an election policy back in 2007. The office of Brett Raguse MP has constantly raised concerns of constituents in this area since the 2007 election. This document aims to provide an overview of the current state of the policy.

    Overview

    The Internet filtering policy, originally a 2007 election policy, has evolved as a result of industry and community feedback. The current policy proposes two levels of Internet filtering:

    1. Mandatory Internet filtering of Refused Classification (RC) material.

    RC material includes child sex abuse, bestiality, sexual violence and similar material. The Australian Communications and Media Authority (ACMA) already orders his material to be ‘taken down’ if is hosted in Australia. There is a credible debate about what this may mean on the edges and public consultation is taking place on this subject.

    This system is proposed to block a list of Internet sites called a blacklist. This relatively simple technology is quick and used in many countries. I am advised by Information Technology professionals that this system will have a negligible impact on Internet connection performance.

    The policy in this area was originally that there would be a mandatory blocking of ‘offensive material’. This was narrowed to the ‘ACMA blacklist’ and has now been narrowed further to RC. This is a far more limited scope than that used in countries such as China and is similar to the systems in the UK, Norway, Denmark and Sweden.

    2. Optional Internet filtering of broader ‘offensive material’.

    The second level of Internet filtering is the one that has attracted the most controversy. This is an optional higher level of Internet filtering to be offered by some Internet Service Providers (ISP’s). Individuals will only have this ‘clean feed’ on their service if they request it. ISP’s do not have to offer this ‘clean feed’ but may access Federal Government grants for providing this service.

    Originally, it was planned for this level of Internet filtering to be mandatory for individuals and ISP’s, with an ‘opt out’ option for individuals. This has been sensibly altered to the current policy, where individuals have to ‘opt in’ if they want a ‘clean feed’ and ISP’s are not forced to offer such a service.

    Current technologies for this level of censorship present technical issues including overblocking, underblocking and performance impacts. There are also critical social issues relating to the role of government in censorship. As technical barriers are inevitably eventually overcome, the social issues will become of more importance than the technical issues in the long term.

    Policy

    The following issues have been overcome:

    The policies as proposed will not slow down the Internet unless people deliberately choose a censored connection.

    Scope of censorship issues have been largely resolved – RC for all Internet connections, and higher levels only for people who want it.

    Cost issues have been reasonably contained by limiting the scope and not forcing Internet Service Provider’s (ISP’s) to offer censorship beyond RC.

    ISP competition issues have been resolved by assistance to implement the blacklist filter and not forcing them to implement higher levels of censorship.

    The following issues remain:

    The Internet filtering technology is likely to be overcome by technical experts.

    The optional higher level of Internet censorship will still have overblocking, underblocking, effectiveness and speed issues, but this will not affect most people.

    Oversight of sites to be blocked, though a discussion paper has been released by Minister Conroy on this subject.

    Risks of scope creep in censorship.

    There is a technical issue relating to the boundary between RC and illegal material.

    So will you just sit and watch as your internet freedom is taken from you (like you are a child) or will you make a stand and voice your opinion to your local MP? The decision is yours to make, but do nothing… and well you just may not be able to view my blog as who knows it may get “FILTERED” …

    © 2010, Scott Evans. All rights reserved.

    Upcoming Book Reviews

    Packt Publishing seem to have liked my review of Drupal 6 Javascript and jQuery, so much so they have asked me to review another title. On my return from linux.conf.au and Drupal South in New Zealand, a copy of the second edition of AJAX and PHP was waiting for me at the post office. I'll be reading and reviewing the book during February.

    I will cover LCA and Drupal South in other blog posts once I have some time to sit down and reflect on the events. For now I will just gloat about winning a spot prize at Drupal South. I walked away with Emma Jane Hogbin and Konstantin Käfer's book, Front End Drupal. I've wanted to buy this title for a while, but shipping from the US made it a bit too pricey even with the strong Australian Dollar. I hope to start reading it in a few weeks, with a review to follow shortly after.

    Got a book for me to review? I only read books in dead tree format as I mostly read when I want to get away from the screen. Feel free to contact me to discuss it further.

    January 25, 2010

    Take “Control” of your Internet…

    Have your say against internet censorship

    Who will be the one to decide what you will be “allowed” to do & see? and do you want Australia to be blacklisted as a rouge state?

    It’s time to act…  Say No to Internet censorship!


    What’s the problem?

    The Federal Government is pushing forward with a plan to force Internet Service Providers to censor the Internet for all Australians. This plan will waste millions of dollars and won’t make anyone safer.

    1. It won’t protect children: The filter isn’t a “cyber safety” measure to stop kids seeing inappropriate content such as R and X rated websites. It is not even designed to prevent the spread of illegal material where it is most often found (chat rooms, peer-to-peer file sharing).
    2. We will all pay for this ineffective solution: Under this policy, ISPs will be forced to charge more for consumer and business broadband. Several hundred thousand dollars has already been spent to test the filter – without considering high-speed services such as the National Broadband Network!
    3. A dangerous precedent: We stand to join a small club of countries which impose centralised Internet censorship such as China, Iran and Saudi Arabia. The secret blacklist may be limited to “Refused Classification” content for now, but what might a future Australian Government choose to block?

    Help turn the lights out on the proposed Internet filter by joining the Great Australian Internet Blackout.

    [source:  http://www.internetblackout.com.au/]

    I have implemented the internet blackout on my Home page, Blog and Profile avatars…

    © 2010, Scott Evans. All rights reserved.

    Planet Ubuntu Australia

    Planet Ubuntu Australia is a window into the world, work and lives of Australian Ubuntu developers and contributors.

    Updated on February 08, 2010 11:56 PM UTC. Entries are normalised to UTC time.

    Subscribe