As part of getting ready to actually getting restarted on my GUI tool, I decided to build a VM to run DS2 so that I can easily manage a DS2 setup via my Windows machine.
Anyway it got me thinking that it might be a good idea to create a VM image for all public lp mudlibs. I use VM images a lot at work and they can be very handy from everything to developing, testing, playing and even live usage.
I would like to briefly outline what I have in mind :-
VM creation tool:-Virtualbox 1.6.4 OSE. Not sure of implication of using and distributing non OSE version. The non OSE version ships as a binary, I am assuming my OSE VM will work on both versions of VirtualBox.
Virtualbox allows VMs to make outbound connections be default so intermud would work, but nobody could connect to the mud, unless a route was setup between the host and the VM.
Consider VMWARE at a later date, if enough demand.
I will publish how I built the VM so that people can verify there is no back doors etc.
Linux Version:-Ubuntu server LTS support until 2013, vast selection of s/w. Ubuntu now happens to be my favoured *nix. Unless IBM ever release openAIX

There is no X front end with this release ie Gnome etc, but can be added by the user fairly easily.
Will include nano/pico for users that have not used vi/emacs.
VMSize:-The current VM I am working should be less than 300MB when compacted
LPMUDS:-Any that are listed on the downloads section of lpmuds.net
Client(s):Tiny Fugue
As Ubuntu server does not ship with X/Gnome/KDE I plan to write a basic Ncurses front end that will list all muds available, as well as the comments about them from the lpmuds site. Connections to chosen mud could be made via ncurses front end as it would invoke tf to connect to the mud on the correct port. As stated earlier it would not be possible to connect to VM via a remote client, unless end user specifically allowed it.
If anyone has any comments/views on this then please let me know.
I hope to have an alpha release available in the next couple of days.
Saquivor