So, official Drupal.org policy is no support for more than one version back. Many Drupal developers/shops have the same policy as Drupal.org itself - no services, development, or maintenance for legacy Drupal versions.
In a perfect world free of money and time limitations, the benefits of staying with the most current version of Drupal make enough sense. However, the reality is that there are practical reasons to try and stick it out with an older site sometimes. These reasons can include (but are probably not limited to):
Older sites which are merrily chugging along. For these sites "upgrading" or "migrating" simply translates into having to paying big money just to have the same exact site they have now, only with a newer Drupal version number next to it.
Older Drupal sites of such customization, scope, and/or scale that upgrading them would be unmanageable in the near term. I worked on such a site for 4 years. With over 30+ custom coded modules (not just downloaded modules from Drupal.org), upgrading to a new version of Drupal would have taken hundreds if not thousands of hours.
Drupal project lead, Dries Buytaert, recently called for more developers to go after niches within the Drupal ecosphere. I believe serving users of older Drupal sites could be a valuable one to some Drupal users, as well as to the Drupal project itself.
As a fan of older Drupal versions and as someone who has spent a lot of time working with them (and yes, plenty of time working with newer Drupal versions), I'm throwing my hat into the ring to try and assist these particular Drupal users. If you have an older Drupal site (or know someone with one) which needs development, support, maintenance, or server administration drop me a line.
Despite wishing "Drupal and the White House nothing but happiness" at the outset, Chris Wilson quickly moves to scare the beejezus out of you about Drupal and make sure everyone understands that the thousands of people coming together to provide really awesome free software are actually all user-hating Nazis and that Drupal is a REALLY. BAD. THING.
Unfortunately, the thing about misinformation is that it often does cause a stir. As one can see from this comment left on another article about Whitehouse.gov, a well known and curious Joomla developer is linking to the propaganda piece and referring to it as a "very different view". So misinformation success, it's now a 'point of view' whether Drupal folk are all user-hating nazis or not.
The software world is not generally the hack-political world where all one needs is an implication and a "reliable source" to start a false "debate" on whether something is true or not. But the slate article, and reactions to it, does demonstrate the point that the Drupal community needs to be prepared to address misinformation. This is a (large) annoyance, of course (more time fighting propaganda ='s less time coding or helping newcomers), but as a great person once said, "With great power comes great responsibility".
Word is out that Whitehouse.gov is now powered by Drupal. The Washington Post has the details of this big win for Drupal and Open Source:
"The online-savvy administration on Saturday switched to open-source code for http://www.whitehouse.gov meaning the programming language is written in public view, available for public use and able for people to edit.
"We now have a technology platform to get more and more voices on the site," White House new media director Macon Phillips told The Associated Press hours before the new site went live on Saturday. "This is state-of-the-art technology and the government is a participant in it.
Under the open-source model, thousands of people pick it apart simultaneously and increase security. It comes more cheaply than computer coding designed for a single client, such as the Executive Office of the President. It gives programmers around the world a chance to offer upgrades, additions or tweaks to existing programs that the White House could - or could not - include in daily updates.
Yet the system - known as Drupal - alone won't make it more secure on its own, cautioned Ari Schwartz of the Center for Democracy and Technology.
"The platform that they're moving to is just something to hang other things on," he said. "They need to keep up-to-date with the latest security patches."
UPDATE: More coverage of this choice along with information on who worked on the site here.
UPDATE II: Dries (Drupal founder and project lead) blogs about it UPDATE III: MSNBC has an article about Whitehouse.gov. Slightly misleading title to it though.
After looking around for how to make an alias for Mac OS X's terminal/shell I ended up cobbling together my solution from a variety of different (mostly unixy-linuxy) places. So in the name of good documentation, here is the magic formula for the next time I need to set up an alias for happier command line hacking:
First we edit/create a profile. For a normal user do: pico /etc/profle ...or for root/superuser do: pico ~/.profile
Add your alias like so to the file: alias aliasname='mycommand /path/path' (notice no space between equal sign and ')
Save your changes and close the file
Load/reload your profile with: . /etc/profile ...or for root/superuser do: . ~/.profile
This article assumes you have NFS and portmap installed on your server already. I think a lot of distros come that way, but some of the links below the instructions mention installation steps if you need it. If you need to install for Redhat or Centos just do: yum install nfs-utils nfs4-acl-tools portmap
I. First, setup the NFS server
(note: in the steps below 192.168.0.2 is the nfs client, and 192.168.0.3 is the nfs server)
1. mkdir /home/fileshare
2. Add this to /etc/exports on NFS server:
3. Add this to /etc/hosts.allow on NSF server
4. Check to make sure portmap is running correctly by doing:
/sbin/service portmap status
...check /var/log/messages for any error that might occur
5. Start nfs and portmap:
6. Make entry for the ip gets added to APF or else connection will timeout:
apf -a 192.168.0.2
7. Make sure services start on boot:
chkconfig nfs on
chkconfig portmap on
SPECIAL NOTES 1. If portsentry is on the server, make sure that it doesn't get in the way when trying to start portmap. If this an issue, comment out everywhere where '111' appears in /etc/portsentry/portsentry.conf (111 is the port that portmap uses) and stop and stop portsentry to reload (/etc/init.d/portsentry stop, /etc/init.d/portsentry start)
2. add ip of client server to /etc/portsentry/portsentry.ignore
II. Second, setup NFS client
1. Make shared directory on client
2. Add to /etc/fstab on client so will get mounted on reboot
192.168.0.3:/home/fileshare /home/fileshare nfs rw,hard,intr 0 0
3. Start portmap:
4. Make entry for the ip gets added to APF or else connection will timeout:
apf -a 192.168.0.3
5. Mount with:
6. Make sure portmap starts on boot:
chkconfig portmap on
Other articles http://linuxwave.blogspot.com/2008/08/nfs-howto-for-centos-5.html