Elsevier Boycott Over Price, Business Practice and SOPA

While complaints about the commercialization of scholarly research publication have been common to academics and librarians (for generations), Elsevier’s recent support for U.S. SOPA, PIPA and Research Works Act legislation has crystallized some of the opposition that has otherwise been circulating around the internet since at least 1997.  In short, the boycott is on.

It’s good to see researchers actively seeking open publication and distribution models.  The more libraries can do to provide institutional support for open repositories and platforms, the more likely these are to succeed.  What is interesting to me is seeing how the complaints about journal cost were really just one aspect of a larger struggle over control of access, researchers inherently wanting the most open terms and commercial publishers building increasingly restrictive ones.  If you think “academic publishers have become the enemies of science,” well, you’re not alone.

Nods to slashdot and Peter Murray for their links.

Posted in News | Comments Off on Elsevier Boycott Over Price, Business Practice and SOPA

Top 11 Fastest CPAN Mirrors for EC2

If you’re finding yourself more frequently developing, testing or deploying infrastructure in EC2, and if perl is part of your stack, as it tends to be for library applications, then you’ve probably had occasion to ask “what CPAN hosts should I use?”  Even a well scripted installation process will encounter that question unless CPAN has been configured, and unlike their internal RPM repository, Amazon doesn’t have their own CPAN mirror exposed or even a default target for their system images.

So you have to decide for yourself.  And while you probably know your favorite hosts to use from your LAN, or from your old server room, the context has changed.  Rather than pick randomly, I went ahead and measured speeds for downloading a small module.  Here’s the 11 fastest mirrors with average response time:

0.080s http://ftp.wayne.edu/cpan/
0.908s ftp://mirror.cogentco.com/pub/CPAN/
1.193s http://mirror.cogentco.com/pub/CPAN/
1.712s ftp://mirror.cc.columbia.edu/pub/software/cpan/
1.727s http://mirror.metrocast.net/cpan/
1.943s http://cpan.dagolden.com/
2.453s ftp://cpan.mirrors.tds.net/pub/CPAN/
2.657s http://mirror.team-cymru.org/CPAN/
2.844s http://cpan.ezarticleinformation.com/
2.880s http://cpan.mirrors.tds.net/
3.232s http://httpupdate.cpanel.net/CPAN/

That’s for the US East (Virginia) region, ymmv.

Should I update it? – Try using apt-listchanges

As a linux system administrator, I often find myself dealing with numerous new “updates” on the command line when I run my usual “sudo apt-get update ; sudo apt-get upgrade” every other day.  Often, I don’t know what’s included with the updates, so I’ll just cross my fingers and hope that good things will come with installing the updates.  And yet there may be hidden issues or strange defaults that come with changes.

For Debian/Ubuntu, I just recently discovered a program out there that’ll help with putting together the missing pieces for me and it’s called “apt-listchanges”.

To install it on one of your servers, go with something like:

sudo apt-get install apt-listchanges

Then configure with:

sudo dpkg-reconfigure apt-listchanges

The software explains itself pretty nicely, apparently it hooks into apt-get update to put together a nicer list of changelog data and other important news information.  There are also options to email a copy of the changes to yourself, for easier reading out of the command line prompts.  From a description for the program (http://packages.debian.org/stable/utils/apt-listchanges):

The tool apt-listchanges can compare a new version of a package with the one currently installed and show what has been changed, by extracting the relevant entries from the Debian changelog and NEWS files.

It can be run on several .deb archives at a time to get a list of all changes that would be caused by installing or upgrading a group of packages. When configured as an APT plugin it will do this automatically during upgrades.

What other ways do you know of to keep track of what you’re really updating on your Linux servers whilst in command-line?