Hi Ken
Yep, the experiment could be expanded to other Moodle releases. Let's see how the 1.x takes off.
About the security at system level. No, I won't trust exposing very old systems to the Net. They have to be VMs, hidden behind an up-to-date host. Only the web server responding at a single port. The Moodle instance is a different story. Now you mention it, I might reset the whole Moodle instance regularly. (The original plan was to reset course-wise.) Either way, the whole "server" - it is just an energy saving mini server - hosts only sample web sites. So not an attractive target for hacking.
Yep, the experiment could be expanded to other Moodle releases. Let's see how the 1.x takes off.
About the security at system level. No, I won't trust exposing very old systems to the Net. They have to be VMs, hidden behind an up-to-date host. Only the web server responding at a single port. The Moodle instance is a different story. Now you mention it, I might reset the whole Moodle instance regularly. (The original plan was to reset course-wise.) Either way, the whole "server" - it is just an energy saving mini server - hosts only sample web sites. So not an attractive target for hacking.
Don't count on high uptimes though. Experimental rig means restarts are unavoidable. Even once frozen, future is not something determinable.
Edit. Release 1.6 also came up with zero problems!