Installed sage under Ubuntu yesterday. Just for trying out. (Well, actually I tried it out a little bit already on their fantastic webservice)
The first thing I tried, however, gave me an error message!
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (805, 0))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (785, 0))
And then more blabla. Not very nice, I would say. Apparently, it is a conflict between certain versions of Sage and Maxima.
My solution: building Sage myself from source. Not hard to do, and you get the latest version fully installed. Disadvantage: it takes a couple of hours of compiling!
Without a doubt, the Views module is one of those Drupal modules without which Drupal wouldn’t be the same. With Drupal 6, Views got a major revision, and I must say I quite like the new interface. There was one thing that I couldn’t figure out immediately however: how to random sort the selection. I should have looked harder in the sort criteria – which is the most logical place to put it – but I was sort of expecting the possiblity to add randomness to any sort criterion I selected (e.g. node:type). Not so: in the list with all possible criteria, you have to select “global:random”.
Still not sure whether that is the most logical way of doing it. Personally, I would think adding “random” as a choice for each criterion (besides “ascending” and “descending”) would yield a much finer granularity and makes more sense. The fact that the random sort criterion is listed as “global:random asc” (asc for ascending) doesn’t really help changing this view either.
But probably there is a good reason for doing it this way. To paraphrase a French proverb: The programmer has his reasons that reason doesn’t know.
After a kernel upgrade, Virtualbox instructs you to run “/etc/init.d/vboxdrv setup” as root. When you try this on Arch, you get an error message, however:
bash: /etc/init.d/vboxdrv: No such file or directory
Turns out that on Arch, there’s a different path to follow. As root, do:
/usr/bin/vbox_build_module
Followed by:
modprobe -r vboxdrv
And you should be set! Still, if you’re not, please don’t hold me responsible. Everything you do as root is your own responsibility!
