Difference between revisions of "Mumd"

From SkullSpace Wiki
Jump to navigation Jump to search
(external access now via vm server host)
 
(3 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
==Claim your account==
 
==Claim your account==
  
Visit http://192.168.1.28/ from the Skullspace LAN.
+
Visit http://claimid.vmsrv.skullspace.ca from the Skullspace LAN and follow the link to MUMD. This is unavailable outside of Skullspace.
  
 
Accounts are for members only and will be verified. Please include information in the claim process to help us verify you.
 
Accounts are for members only and will be verified. Please include information in the claim process to help us verify you.
  
 
==MUMD hosts open to all users==
 
==MUMD hosts open to all users==
* Latest Ubuntu (12.04) -- 192.168.1.29
+
* Latest Ubuntu LTS (12.04) -- 192.168.1.29
 
 
Coming soon, Arch
 
  
 
== Log in ==
 
== Log in ==
Line 23: Line 21:
 
* [[wikipedia:XDMCP | XDMCP]] e.g. X -query 192.168.1.29, Xephyr -query 192.168.1.29, Xnest -query 192.168.1.29
 
* [[wikipedia:XDMCP | XDMCP]] e.g. X -query 192.168.1.29, Xephyr -query 192.168.1.29, Xnest -query 192.168.1.29
  
The Latest Ubuntu container can also be reached on port 22 (ssh) and 3389 (RDP) from outside Skullspace via external.mumd.markjenkins.ca
+
The Latest Ubuntu container can also be reached on port 2288 (ssh) and 23389 (RDP) from outside Skullspace via vmsrv.skullspace.ca
  
 
== Desktop Environments ==
 
== Desktop Environments ==
Line 36: Line 34:
 
We'll try and take some LVM snapshots from time to time and copy off site. Don't count on it, backup your stuff, distributed version control in particular is very nice.
 
We'll try and take some LVM snapshots from time to time and copy off site. Don't count on it, backup your stuff, distributed version control in particular is very nice.
  
== Future plans ==
+
==Intense Resource Usage==
 +
As a server running under the vmsrv Please see the vm server page on [[vmsrv#intense%20resource%20usage |intense resource usage]]
  
 
[[Category:Projects]]
 
[[Category:Projects]]

Latest revision as of 05:21, 6 May 2013

A multi-user computer system hosted on the virtual machine service with Linux containers (LXC).

This system aspires to be a multi-user, multi-desktop/distro (MUMD) system -- a place where multiple users can access thousands of pre-installed useful gui, terminal-based, and line-based applications. A "shell" server for the modern age.

LDAP is being used to allow you to have one account that works for logging into multiple MUMD services. Your MUMD account also allows you to log on to the Skullspace virtual machine service.

Claim your account

Visit http://claimid.vmsrv.skullspace.ca from the Skullspace LAN and follow the link to MUMD. This is unavailable outside of Skullspace.

Accounts are for members only and will be verified. Please include information in the claim process to help us verify you.

MUMD hosts open to all users

  • Latest Ubuntu LTS (12.04) -- 192.168.1.29

Log in

Three ways to log in to each MUMD host from the skullspace LAN using the internal ip addresses listed above (192.168.1.29).

  • SSH (port 22)
  • RDP (port 3389)
  • XDMCP e.g. X -query 192.168.1.29, Xephyr -query 192.168.1.29, Xnest -query 192.168.1.29

The Latest Ubuntu container can also be reached on port 2288 (ssh) and 23389 (RDP) from outside Skullspace via vmsrv.skullspace.ca

Desktop Environments

Default desktop environment on RDP login is LXDE. A different login session can be specified in ~/.xsession .

Security challenge

Non-disruptive attempts to discover security flaws are welcome if disclosed on discovery. A possible fruitful area to look at is the claimid system, as it accesses a private file with the master LDAP password in order to add the accounts. (somebody bug Mark to post code to Skullspace github group)

Backups

We'll try and take some LVM snapshots from time to time and copy off site. Don't count on it, backup your stuff, distributed version control in particular is very nice.

Intense Resource Usage

As a server running under the vmsrv Please see the vm server page on intense resource usage