225. Sun GridEngine: commlib error: got select error (Connection refused)

The issue:
On doing qhost I get

error: commlib error: got select error (Connection refused)
error: unable to send message to qmaster using port 6444 on host "beryllium": got send error

Beryllium is my hostnode.

Same thing happens with qstat and any other imaginable SGE command.

The solution:
It's an obvious one -- just restart the services. I mean, it took me twenty minutes to re-remember that, but it should have been obvious. Most of the time, services are managed using scripts in /etc/init.d/ and that's the case here too. So, hanging my head in shame, here's the solution:

ls /etc/init.d/grid*

/etc/init.d/gridengine-exec  /etc/init.d/gridengine-master

sudo service gridengine-master restart

qhost should now slowly be populated

Done.

How I got there:


 ps aux|grep sge

sgeadmin  3173  0.0  0.0  56844  3428 ?        Sl   Aug20   6:29 /usr/lib/gridengine/sge_execd

 tree /var/spool/gridengine -L 4 -d
/var/spool/gridengine
|-- execd
|   `-- beryllium
|       |-- active_jobs
|       |-- jobs
|       `-- job_scripts
|-- qmaster
|   `-- job_scripts
`-- spooldb

Looking at /var/spool/gridengine/execd/beryllium/messages

08/20/2012 10:47:17|  main|beryllium|I|starting up GE 6.2u5 (lx26-amd64)
08/30/2012 15:06:57|  main|beryllium|E|commlib error: got read error (closing "beryllium/qmaster/1")
08/30/2012 15:06:58|  main|beryllium|W|can't register at qmaster "beryllium": abort qmaster registration due to communication errors

less /var/lib/gridengine/rupert/common/act_qmaster

beryllium

So looks ok.

Oddly, there's nothing funny in /tmp -- no execd_messages.* files.

 ps aux|grep sge

sgeadmin  3173  0.0  0.0  56844  3428 ?        Sl   Aug20   6:29 /usr/lib/gridengine/sge_execd

sudo kill 3173

start-stop-daemon --exec /usr/sbin/sge_execd --start --user sgeadmin

Which didn't seem to do anything.

start-stop-daemon --exec /usr/sbin/sge_qmaster --start --user sgeadmin

which doesn't seem to do anything either.

/usr/lib/gridengine/gethostname -aname

critical error: Please set the environment variable SGE_ROOT.

export SGE_ROOT=/var/lib/gridengine

/usr/lib/gridengine/gethostname -aname

beryllium

 service gridengine-master restart

Restarting Sun Grid Engine Master Scheduler: sge_qmasterrm: cannot remove `/var/run/gridengine/qmaster.pid': Permission denied
.

cat /var/run/gridengine/qmaster.pid

3198

ps aux|grep 3198

yields nothing

sudo rm  /var/run/gridengine/qmaster.pid

sudo service gridengine-master restart

Restarting Sun Grid Engine Master Scheduler: sge_qmaster.

ps aux|grep sge

sgeadmin 32178  2.5  0.0  69004  6112 ?        Sl   09:40   0:00 /usr/lib/gridengine/sge_qmaster

qstat

job-ID  prior   name       user         state submit/start at     queue                          slots ja-task-ID 

-----------------------------------------------------------------------------------------------------------------

    715 0.75000 submit__la me         r     08/22/2012 08:10:32 six.q@boron                        6        

    720 0.25194 submit__63 me         r     08/22/2012 11:15:02 four.q@tantalum                    4        

    716 0.74817 submit__la me         qw    08/22/2012 08:11:28                                    6        

    719 0.70429 submit__la me         qw    08/22/2012 08:38:17                                    6        

    721 0.25071 submit__63 me         qw    08/22/2012 11:15:35                                    4        

    722 0.25000 submit__32 me         qw    08/22/2012 11:16:01                                    4    

 qhost

HOSTNAME                ARCH         NCPU  LOAD  MEMTOT  MEMUSE  SWAPTO  SWAPUS

-------------------------------------------------------------------------------

global                  -               -     -       -       -       -       -

beryllium               lx26-amd64      3     -    7.8G       -   14.9G       -

boron                   lx26-amd64      6  6.10    7.6G    1.4G   14.9G  240.8M

tantalum                lx26-amd64      4  4.01    7.7G    1.6G   14.9G     0.0

sudo service gridengine-exec restart

Restarting Sun Grid Engine Execution Daemon: sge_execd.

qhost

HOSTNAME                ARCH         NCPU  LOAD  MEMTOT  MEMUSE  SWAPTO  SWAPUS

-------------------------------------------------------------------------------

global                  -               -     -       -       -       -       -

beryllium               lx26-amd64      3  0.22    7.8G    3.0G   14.9G  141.3M

boron                   lx26-amd64      6  6.09    7.6G    1.4G   14.9G  240.8M

tantalum                lx26-amd64      4  4.01    7.7G    1.6G   14.9G     0.0

224. Disabling tracker-miner-fs

Yes, yes, I shouldn't have a full desktop install on a computational node, but the nodes serve as instant replacement desktops if something goes awry with my main desktop, and occasionally visitors get to use them to access the internet in order to avoid getting bored.

Anyway, tracker-miner-fs is eating up 26% of my 8 Gb RAM on one of my nodes running KDE, and I really don't need it. I mean, I don't know if it's useful to most people running a full DE, but on my node I most certainly, definitely don't need it.

Given the number of posts online with questions about tracker ('What is it?", "Why is it using up all my resources?" etc.) I think that there's a bit of a PR problem. If it's a program that is noticeable because it makes demands on your computer system, the users should be allowed to know why putting up with this extra drain on resources is desirable -- or not.

Anyway.

aptitude show tracker says:
"Tracker is an advanced framework for first class objects with associated metadata and tags. It provides a one stop solution for all metadata, tags, shared object databases, search tools and indexing."

...which means what exactly in practical terms?

man tracker-miner-fs 

NAME
       tracker-miner-fs - Used to crawl the file system to mine data.

man tracker-store

NAME
       tracker-store - database indexer and query daemon

My guess would be that tracker-miner is basically indexing files for faster search, but I really don't know. It's one daemon I'm happy to expel.

There's a standard place for stuff that's supposed to be brought up with x:

ls /etc/xdg/autostart/

-rw-r--r-- 1 root root   306 May  3 09:42 at-spi-dbus-bus.desktop
-rw-r--r-- 1 root root  6216 Jun 20 06:58 evolution-alarm-notify.desktop
-rw-r--r-- 1 root root  7404 Oct 14  2011 gdu-notification-daemon.desktop
-rw-r--r-- 1 root root  5340 May 24 08:46 gnome-keyring-gpg.desktop
-rw-r--r-- 1 root root  6711 May 24 08:46 gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root  6282 May 24 08:46 gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root  5138 May 24 08:46 gnome-keyring-ssh.desktop
-rw-r--r-- 1 root root  6681 May 30 21:02 gnome-sound-applet.desktop
-rw-r--r-- 1 root root  7018 Apr 28 09:27 gsettings-data-convert.desktop
-rw-r--r-- 1 root root   460 Oct 21  2011 guake.desktop
-rw-r--r-- 1 root root   301 Jun 24 16:52 hplip-systray.desktop
-rw-r--r-- 1 root root   238 Dec  2  2011 kerneloops-applet.desktop
-rw-r--r-- 1 root root  4673 Mar 25 08:49 nm-applet.desktop
-rw-r--r-- 1 root root   250 Sep 10  2011 notification-daemon.desktop
-rw-r--r-- 1 root root  4651 Nov 12  2011 polkit-gnome-authentication-agent-1.desktop
-rw-r--r-- 1 root root  7112 Dec 23  2011 print-applet.desktop
-rw-r--r-- 1 root root  3864 Oct  1  2011 pulseaudio.desktop
-rw-r--r-- 1 root root   633 May 20 06:08 pulseaudio-kde.desktop
-rw-r--r-- 1 root root  3288 Aug 12 12:05 tracker-miner-fs.desktop
-rw-r--r-- 1 root root  3004 Aug 12 12:05 tracker-store.desktop
-rw-r--r-- 1 root root 11041 Apr  4 22:02 user-dirs-update-gtk.desktop
-rw-r--r-- 1 root root   433 Nov  3  2011 wicd-tray.desktop
-rw-r--r-- 1 root root   150 Feb  8  2012 xfce4-settings-helper-autostart.desktop
-rw-r--r-- 1 root root   357 Aug  1  2011 xfce4-volumed.desktop

Incidentally, the folder on that particular node betrays a history of previously installed desktop environments...

To stop and remove the tracker-miner processes, do

tracker-control -r 

It removes the databases it has created as well.


To disable:
Launch tracker-preferences from the KDE menu. Uncheck all options under 'Semantics'. Uncheck all places under locations. Clicking apply doesn't seem to have any effect, but if you open tracker-preferences again you'll probably find that it worked.

To disable tracker-miner-fs and tracker-store from the terminal you can probably edit:

tracker-miner-fs.desktop:

51 Icon=

 52 Exec=/usr/lib/tracker/tracker-miner-fs

 53 Terminal=false

 54 Type=Application

 55 Categories=Utility;

 56 X-GNOME-Autostart-enabled=false

 57 X-KDE-autostart-enabled=false

 58 X-KDE-StartupNotify=false

 59 X-KDE-UniqueApplet=true

 60 NoDisplay=true

tracker-store.desktop

54 Icon=

 55 Exec=/usr/lib/tracker/tracker-store

 56 Terminal=false

 57 Type=Application

 58 Categories=Utility;

 59 X-GNOME-Autostart-enabled=false

 60 X-KDE-autostart-enabled=false

 61 X-KDE-StartupNotify=false

 62 X-KDE-UniqueApplet=true

 63 NoDisplay=true

 64 OnlyShowIn=GNOME;KDE;XFCE;

Reasons why we don't simply uninstall it:

apt-cache rdepends tracker

         tracker
Reverse Depends:
  tracker-miner-fs
  tracker-gui
  tracker-gui
  tracker-gui
  nautilus
  tracker-miner-evolution
  tracker-utils
  tracker-extract
  brasero
  shared-mime-info
  tracker-utils
  tracker-miner-fs
  tracker-miner-evolution
  tracker-gui
  tracker-gui
  tracker-gui
  tracker-extract
  tracker-explorer
  tracker-dbg
  shared-mime-info
  rygel-tracker
  nautilus (twice?)
  catfish

223. Moving disks, devices from one box to another -- issues with network interfaces

Long story short: edit /etc/udev/rules.d/70-persistent-net.rules

Long story:
I have a very small beowulf cluster keeping my office warm in these antipodean winter months. For some silly reason I was using the front node, a six core + 8 Gb box, as my daily desktop. That of course meant I wasn't really using it for computations. In addition to the front node I have a four core i5-somethingorother with 8 Gb RAM (fast!) and a slovenly AMD X3 /4 Gb to actually run the jobs. They are connected via a gigabit switch (192.168.1.0/24) for nfs exports and a 10/100 router (192.168.2.0/24) for WAN access.

I finally decided that 1) I didn't need a six-core box to prepare latex documents, run octave jobs and make pretty gnuplot plots and that 2) having a slow 3-core AMD box to run heavy nwchem jobs was not fast enough. On the other hand, I didn't want to set up/reinstall/move all my stuff from one harddrive to another.

Linux is wonderful in that it's often just a case of ripping out a harddrive and moving it to a different physical. Windows will scream bloody murder, but linux normally does it pretty well. Same here.

The main issue was the three network cards that I wanted to set up (three separate subnets) and which I configure via /etc/network/interfaces. I simply couldn't call the networks cards what I wanted.

Well, as is obvious in hindsight, you should pay a visit to /etc/udev, and more specifically, /etc/udev/rules.d/70-persistent-net.rules

It looks something like this:

# This file was automatically generated by the /lib/udev/write_net_rules# program, run by the persistent-net-generator.rules rules file.## You can modify it, as long as you keep each rule on a single# line, and change only the value of the NAME= key.
# PCI device 0x10ec:0x8168 (r8169)SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:YY:XX:96:XX:32", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:XX:YY:83:0a:48", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:XX:YY:64:0b:46", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
# PCI device 0x1814:0x3062 (rt2860)SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:YY:XX:cf:1f:5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="ra*", NAME="ra0"
# USB device 0x:0x (rt2800usb)SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:YY:XX:c8:91:e6", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

Basically, make sure you can figure out the mac addresses of the different network cards (ip addr helped me more than ifconfig) you can simply go in and edit the ATTR{address}=="" statements and the NAME="" variables. Make sure that there are no conflicts, obviously.

After that, everything should be fine.

If you are using network-manager (i.e. stock GNOME setup) then you will want to pay attention to the /etc/NetworkManager/system-connections/ as well -- open and edit suspiciously named files like e.g. eth0.

They'll look like this:

[802-3-ethernet]
duplex=full
mac-address=00:YY:XX:96:93:32
[connection]
id=eth0
uuid=fa5YYYY-XXXX-43a3-8502-f8ba2d28ZZZZ
type=802-3-ethernet
timestamp=1326324509
[ipv6]
method=auto
[ipv4]
method=auto

222. Fighting and, eventually, installing HP laserjet P1102w on debian.

This printer is great when it works. It's just always a pain to set up, and it seems to be down to the way the install scripts are written. Setting up the printer was easy in the end -- but getting there? Not so much. Obviously, part of the reason is my own stupidity. Summary: it works on linux, but you'll need a bit of time and patience.

Update: here's an interesting post on the same topic: http://downfromthetrees.com/linux-installing-a-proprietrary-hp-printer-driver.html The only thing I would add is that instead of using sudo as described in that post you may have to use gksu in order to avoid the Magic Cookie error.

The short guide:
You NEED a binary plugin. It blows, but you do. Blowing harder: there's a lot of references to letting hp-setup download it for you -- but I'm willing to bet that it will fail for you.

Anyway, do this:
wget http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.12.6-plugin.run
chmod +x hplip-3.12.6-plugin.run
gksudo ./hplip-3.12.6-plugin.run

Hopefully that's good enough to take you through to system-config-printer and/or hp-setup. I did a lot of things, but it was the gksudo ./hplip-3.12.6-plugin.run that did it in the end.

And don't forget to add yourself to the lpadmin and perhaps lp groups:

cat /etc/group|grep lp

lp:x:7:verahill
lpadmin:x:111:verahill

I don't know how necessary it is, but heck, why not?

Here's the full, painful (and probably embarrassing) route I took:
It should not be this difficult to get a bloody printer to work. With older printer models it's been quick and easy, without having to download any 'binary plugins'. This is just effing ridiculous. Guess who's not buying another HP printer...

I reorganised my office, and as part of that decided to move my printer from my desktop to one of my networked boxes to free up some space on my desk. My desktop is running GNOME, while the target box is running KDE.

If you install the hplip packages in debian you end up with a very helpful script called hp-setup. You can run that as a user, but try running it as root via sudo, and you get

Invalid MIT-MAGIC-COOKIE-1 keyhp-setup: cannot connect to X server :0

OK, so you can run it as user. Everything looks great, BUT...you'll find that in this case the install will fail at the step of downloading the magical, mythological 'binary plugin'.

Also, as a user you're unlikely to be able to be able to put files in the places where they belong anyway, so there's that (see e.g. the first comment below).

You then do a bit of googling for hplip-3.12.6-plugin.run, and end up here: https://aur.archlinux.org/packages.php?ID=44646

You do

wget http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.12.6-plugin.run
chmod +x hplip-3.12.6-plugin.run
./hplip-3.12.6-plugin.run

This opens a gui where you get to accept the T&C. Not much seems to happen beyond that though. Oh, and you can't do the sudo-thingy because, well, you get the magic cookie error.

OK, take a step back.

sudo lpstat -a

global-mfp accepting requests since Mon 20 Aug 2012 10:46:48 EST
HP-LaserJet-Professional-P1102w-2 accepting requests since Mon 20 Aug 2012 13:49:19 EST

lpoptions -d HP-LaserJet-Professional-P1102w-2

lpq

HP-LaserJet-Professional-P1102w-2 is ready

Test it:
lp /etc/fstab

request id is HP-LaserJet-Professional-P1102w-2-1 (1 file(s))

 lpq

HP-LaserJet-Professional-P1102w-2 is ready and printing
Rank    Owner   Job     File(s)                         Total Size
active  (null)  1       untitled                        2048 bytes

Printing my foot it is.

Hmm...
cat /etc/group|grep lpadmin

lpadmin:x:114:

OK, edit /etc/group and add myself to lpadmin.

I can open system-config-printer, but I can't 1) delete any printers (which would've been nice) or 2) start it with sudo.

I can use http://localhost:631, but as a user I'm somehow not allowed to remove printers, and I use sudo -- there's no 'root' password.

At this point I was getting frustrated and nuked all printers clear of my system.

sudo lpadmin -x HP-LaserJet-Professional-P1102w-2

sudo apt-get install system-config-printer-kde

Now I had both 'printing' (= vanilla CUPS system-config-printer) and 'Printer Configuration' in the KDE menu.

Still no dice.

OK, another step back.
mkdir hp
./hplip-3.12.6-plugin.run --target hp
cd hp/
sudo cp 86-hpmud-sysfs_hp_laserjet_professional_p1102w.rules /etc/udev/rules.d

Still no effing luck.

Tried one last desperate thing:
gksudo ./hplip-3.12.6-plugin.run
Clicked the agreement. Said done.
Hit 'print test page' and...it printed!

So...you need to be root...but the MIT magic cookie issue combined with the requirement to have a friggin' gui (why???) made that painful. Well, I guess that's why we're told to use gksu whend oing graphical stuff...

OK, only things remaining: network sharing. Should be simple. Opened up all ports on print-host box to accept traffic from my desktop (and desktop only). No luck.

gksu system-config-printer
Click on server, settings -> check Publish shared printers connected to this system.

On my desktop it was then just add a matter of adding the printer in GNOME (ipp://192.168.1.101:631/printers/HP-LaserJet-Professional-P1102w)

Sweet.

SOLVED.

221. First steps with Moodle (the .deb version) in Debian

This is a very brief, very basic outline.

Looking online the general recommendation seems to be to install moodle yourself and avoid the debian package version. While not a stranger to rolling my own, I just want to play with moodle for learning purposes because that's what my uni uses.

Anyway, do
sudo apt-get install moodle

Once it's installed, look at
ls /etc/apache2/sites-enabled

If there's nothing moodly, then do
sudo cp /etc/moodle/apache2.conf /etc/apache2/sites-enabled/moodle.conf
sudo service apache2 restart

Navigate to http://localhost/moodle

The actual installation takes ages, so go get yourself a cup of tea/coffee to prevent your mouse finger from getting itchy. In other words, just wait until you get a list showing that all steps have completed and that you may continue.

You need to allow cookies.

Fill out the admin stuff - country, password, city etc etc.

At this point you can log in, create a class and start exploring. Have fun.

220. My first few lectures in Australia...and the importance of thermodynamics

I'm not an expert on anything. It's not a matter of false modesty, but an observation based on the fact that I come across new things on a regular basis, even within my field of research. When I do, I try to learn.

But to learn new things I need a toolbox - a set of skills that I rely on to put anything new into context. The toolbox for a chemist is basically thermodynamics. Simple, applied thermodynamics. As a chemist you can get away with memorising the expression for Gibbs free energy and the general expression for rate laws, and you can do a whole lot of fun/damage.

I'm only at the beginning of my current class, and I'm an inexperienced lecturer, but I had a bit of a shock today discovering that my class -- second semester of the second year at a 'good' university -- don't feel comfortable dealing with free energies and standard potentials.

The origin lies in the idea of students as clients here -- universities want pass rates in excess of 70-80%, while most of the faculty likely experienced a first year as undergraduates where the Gen Chem class (which did thermodynamics until you eyes were bleeding) had a failure rate of 60% or above.

We might have thought it was harsh to fail that many students at the very beginning, but the result was that the more inspired/motivated students made it through, and the ones who weren't willing to dedicate the effort necessary to become professionals got a kick in the pants to look for majors that actually interested and inspired them.

If something interests you it  becomes 'easy' -- either because you instinctually  understand it, or more likely, because you simply put in that extra effort to teach yourself.

Instead, the impetus to pass as many students as possible -- and to get 'good' student feedback which will help your promotion -- means that the students are never challenged. 'Difficult' topics are avoided and taught late in the course or ,increasingly, not at all.

Rumour has it that one of the reasons why some Australian universities are adopting a Bologna-inspired model is because they can use the masters section of the education to cover the things the students should have learned as undergraduates --- and thus still produce graduates with the skills that their chosen major indicates that they should have.

It's pretty damning.

The consequence is dire -- some scary example of PROFESSORS -- that is: professionals entrusted with teaching the next generation of scientists and engineers -- in the STEM fields who don't appear to understand basic thermodynamics or more specifically: entropy and the distinction between open and closed systems based on their use of thermodynamics to 'disprove' Evolution. They may be appearing to be capable professionals in every other sense and may well do 'good' research. The individuals may be appearing to do capable research in every other aspect and may be wonderful people, but their use of the 2nd law of thermodynamics as an argument against evolution is just misguided.

Andrew McIntosh -- Professor of Thermodynamics(!) and Combustion Theory at Leeds. Website.
Stuart Burgess -- Professor, Department of Engineering at Bristol. Website

In fact, the list here would presumably include mostly people of a similar persuasion. While I've seen Andrew's and Stuart's writings, I feel comfortable commenting on their opinions, but since I am not as confident about the rest of the people on the list, let's just highlight the fact that it include people from (the universities of) Sheffield, Cambridge, Liverpool and Cardiff.

Or what about this letter: http://www.bcseweb.org.uk/index.php/Main/EstelleMorris
The fact that the signatories mention their affiliations is an obvious way of trying ot use those affiliations to attach significance to their views.

Anyway, here's MC Hawking's take on it: http://www.mchawking.com/includes/lyrics/entropy_lyrics.php

219. Seeing animals in metropolitan Melbourne

As a foreigner in Melbourne one of my first questions to my local pals was where I could see typical Aussie animals. The answer was 'The Zoo', which just doesn't cut it.

Well, it would've helped if I had asked the more outdoorsy types, because you can actually be fairly sure to catch glimpses of kangaroos, wallabies, bandicoots, corellas, rosellas, cockatoos and kookaburras without having to travel too far. This is biased towards the eastern suburbs, since that's where I roam.

I (almost) always see...

Kangaroos: As it turns out,  the most iconic animal of Australia is very easy to find around Melbourne. Sure, it's Grey Kangaroo and not the perhaps more famous Red Kangaroo, but they are everywhere if you know where to look, and in many places they are used to humans.

This is one kangaroo that isn't bothered by human presence. Lysterfield Lake Park on Tramline track.

On the best places is along Tram Line Track in Lysterfield Lake Park:

Lysterfield Lake Park

Tram line track is where the action's at

The walking's easy for the most part. Some of the tracks get soggy and muddy due to bikes and horses ruining them.

For the most part, the park's flat.

If you go on the smaller trails and keep quiet you may spot the odd Swamp Wallaby -- they are much smaller, solitary and tend to leg it whenever they see humans. Apart from their difference in size and fuzzier fur, you can recognise them by 1. they are (almost) always alone, 2. their tail is white-tipped and 3. their stance when hopping is different from that of kangaroos (lean forward more).

Other safe places to spot kangaroos would be Churchill national park, the area around Police Paddocks, and Cardinia Lake Park -- but Cardinia Reservoir Park tends to get really busy with people playing games and bbq:ing which tends to ruin the experience.

 Lysterfield Park north of Wellington road also has a lot of Kangaroos, but they aren't always easy to spot.

Wallabies: The Swamp Wallaby is quite common around Melbourne, but is much more shy than Kangaroos. It's also solitary -- if you spot a kangaroo you know that there are others around, but not so with wallabies.

The picture is heavily overexposed to show the wallaby hiding in the shade off of Possum Gully track in Cranbourne

The best place to spot wallabies seems to be the park surrounding the Botanical Park in Cranbourne. If you're quiet and attentive you will spot Wallabies in the sandier parts of the park before they run away. If you bring binoculars you're like to see wallabies hiding in the stands of ferns abutting the forests or in the middle of the fields. Again, they take a bit more patience to spot.

Cranbourne Botanic Gardens

Sometimes you can spot Wallabies among the fern in the more open part of the park

Otherwise, carefully walk on the sandier tracks among the scrub -- and be aware that any wallaby that sees you will either leg it, or stand absolutely still in the shade. So you need keen eyes.

I've seen wallabies up by Lysterfield Lake Park every time I go there, but you'll have to find the smaller tracks/breaks to spot them.

Crimson Rosellas: This is a typical forest parrot. Dandenong Ranges is a great place to see them, and because of their crimson red colour they aren't that difficult to spot. The young are green and tend to form flocks towards the end of summer. You sometimes see a single green young and its two parents as well earlier in the summer.

Just outside Churchill national park

The best places to spot them  is in shaded and wooded areas right at the edge of the woods. Rock track next to the golf course outside Olinda tends to be good, but in general, these birds are fairly common in the area. Typically you'd see a pair, but the young do flock at times.

A flock of crimson rosellas

Rock track

The lookout on Chalet road is a good place to park your car and start walking.

Another safe place is Grant's Picnic Ground north of Belgrave. There's an area where you can feed the parrots, and it's mostly cockatoos and rosellas. Just be warned -- they bring in bus-loads of tourists, so if you're looking for a 'wild' experience it can be a bit disappointing. The parrots are wild and free alright, but they are certainly used to the presence of humans.

Grant's picnic ground. It has some nice tracks as well.

There's a visitor centre where you can buy birdseed.

Sulphur-crested Cockatoos:

A cockatoo grazing on a football field in the morning sun

Apart from Grant's Picnic Ground (see Crimson Rosellas) where you are more or less guaranteed to find them, the area around Shepherd's bush in the Dandenong Valley area is pretty good. It also has the advantage of being easy to get to.

Eastern Rosellas: Probably the prettiest parrot I've seen. It's not always that easy to find, but it tends to be in more open areas than the Crimson Rosella. Also, it tend to forage on the ground. Normally, using your ears is the way to know where to look Rosellas have a much more melodic call than the other parrots and are easy to distinguish based on that alone.

They are small and fairly shy. The red head gives it away though.  Police Paddocks.

The best area so far seems to be Police paddocks just east of Stud Road in the city's far east, where there's a bit of open forest. You're likely to spot Kangaroos there as well.

Southern Brown Bandicoot: 
I've seen them two out of three time when visiting Cranbourne botanic gardens (See Wallabies above). They are normally around the visitor centre and the BBQ area. If you walk into the park you might see them cross the road. Going on the smaller tracks along the fence tends to be rewarding as well. Basically think of them as big rats in terms of what you're looking for -- they are less paranoid than rats, but you should still walk softly.

A large bandicoot over by the playground behind Cranbourne botanic gardens

Rainbow Lorikeets: You see them everywhere in the eastern suburbs. If you want to see them up close, look for e.g. flowering bottle brush and you might get lucky.

A rainbow lorikeet in our garden.

Kookaburras: Kookaburras aren't rare, but can be tricky to locate. The only place which has always  produced consistent sightings is Lysterfield Lake Park -- again on tramline track. Otherwise, the more open patches of forest (mountain ash) up in Dandenong ranges can yield lots of sightings depending on season. If you go along trig track up by the sky high observatory in the Dandong ranges you may spot lots of kookaburras and crimson rosellas. Otherwise, rock track over by Olinda occasionally has the odd kookaburra laughing away.

Laughing kookaburra at Cardinia Reservoir.

I have once seen...

Echidnas: I've seen one on a track in Cardinia Reservoir Park, and one next to the road (alive and digging) in the area surrounding the Cranbourne Botanic Gardens. You're unlikely to spot them. Instead, use your ears -- you'll hear them digging in the grass/leaves.

Normally Echidnas are camera shy, but this guy was happy to pose.

Emu: I've only seem one once, and that was just east of Cardinia Reservoir Park, while driving on Red Hill road. The emu was in the fenced off area belong to Melbourne Water.

A lone emu near Cardinia.

Corellas: from time to time I see lots of them -- they seem to be very common in the area around Monash University, but they aren't always there when I visit. Especially the corner of Blackburn road and Wellington road occasionally has flocks of them.

Little Corellas hanging out in a town along Great Ocean Road.

218. The end of Gnome in Debian?

Update 12/11/2012: And we're back to gnome: http://www.phoronix.com/scan.php?page=news_item&px=MTIyNTM

This is a bit of a bombshell: http://www.phoronix.com/scan.php?page=news_item&px=MTE1NTk

Also reported here: http://www.h-online.com/open/news/item/Debian-to-use-Xfce-as-its-standard-desktop-1663868.html
and here: http://www.neowin.net/news/debian-drops-gnome-chooses-xfce-as-default-desktop
and here: http://linux.slashdot.org/story/12/08/08/1455243/debian-changes-default-desktop-from-gnome-to-xfce

UPDATE: No, I don't have any more information. However, I've been thinking a little bit about this. Debian is not a targeted distro like Ubuntu, Red Hat, SUSE or Mint. I'm not sure how the discussions among the debian package maintainers go, but I'm suspecting that it's more of a matter of ironing out reported bugs, than to focus on providing a 'user experience'. SID and Testing are rolling releases, after all. So 'dumping' gnome really won't affect anything at all very much in the short to medium term. Those who like KDE will use KDE. Those who like Gnome will use Gnome. And so on. In the long term, enough people may encounter XFCE as their first DE via Debian that it starts to change the balance in the user bases of the different DEs, but given that a great majority of both current and future debian users come to debian via other distros  -- from red hat/fedora/knoppix back in the days, then ubuntu in the late 2000s, and now perhaps mint -- many users probably both have both experience in how to set up different DEs and preferences as to which one they want to use.

So yeah. Sorry about the hyperbole in the title.

Original post:
Basically, Debian is thinking about dropping Gnome as the default desktop and replacing it with XFCE when Wheezy goes stable. The official reason is (CD ROM) space, not that there's any issues with GNOME 3.

I wouldn't be surprised if the rumoured difficulties in communicating with the Gnome crowd may have played a role, in addition to the (a bit hysterical at times) general dissatisfaction with GNOME 3.

Having 'grown up' with gnome (Baby Duck Syndrome) I think it's sad news -- gnome is pretty, functional and makes linux just different enough to give it a distinct look.

[Btw, this article about the Baby Duck Syndrome is a nice read: http://www.ibm.com/developerworks/web/library/wa-cranky50/index.html ]

XFCE, LXDE and KDE are all capable desktops, and I've played with LXDE and KDE recently. Not being that familiar with XFCE -- or even LXDE really -- it does appear to me that what really sets KDE and GNOME apart is that they come with a complete package -- KDE and GNOME all have their awkwardly named software applications: epiphany vs konqueror, evolution vs kmail etc.

Apart from lxterminal and lxmusic for lxde, and thunar for xfce, similar DE specific apps appear to be thin on the ground for LXDE and XFCE. That's not necessarily a big issue, but we've all had issues with GTK vs QT and how pieces of software using either framework look in different environments. It's hardly a disaster, but just enough to be noticeable.

It would also be interesting if the netinstall and business-card isos would ask about which specific DE to install, rather than just ask about whether a desktop is to be installed , in particular if debian is interested in experimenting.

Offering more choice would really not be that bad of an idea. Personally, and for my own biased reasons, I'm  much more interested in LXDE than XFCE, and more interested in GNOME than KDE. XFCE, the way it's implemented in Debian Squeeze, looks a bit dated -- basically like GNOME 2. While I'm not really into that, given the uproar during the past year a lot of people seem to prefer the old gnome 2 look. Besides, the strength of the old desktops is that you can theme and modify them to the point of no recognition.

And if we're talking about slim installs of debian, we really should take a look at Crunchbang (#!) as well, which uses openbox.

Finally, what about Jessie? Will GNOME be back or is this the defining moment for XFCE?