Barputer-Next

From VoidWarranties - Hackerspace Antwerp, Belgium
(Difference between revisions)
Jump to: navigation, search
Line 33: Line 33:
  
 
=What should still be done?=
 
=What should still be done?=
 +
* Make it work on the physical barputer
 +
** Make Touchscreen input work again.
 +
* Install the barputer application (should be a primary objective when (re)creating the barputer, amirite?)
 +
* Solve last minute issues, which are currently unknown.
  
 
=Notes=
 
=Notes=
 +
* username/password is the same as the old one. (ask in the space, posting them on the wiki is not a good idea)
 +
* it's a Debian, sudo won't work like it does in Ubuntu. Use <code>su -</code> for now to become root, return to normal privileges with ctrl+d/logout, untill I fix it.
 +
* IP is 10.98.254.144, should be accessible by VPN and inside the network.
 +
* X2go settings: Gnome, FullScreen, ADSL Speed (or whatever suits the connection),... Leave most things in the default state, except KDE->GNOME and Desktop 800x600->FullScreen.

Revision as of 10:07, 8 February 2012


Barputer-Next
What:
Rebuilding the barputer, with a touch of cloudlyness.
Cloud.jpg
Participants:
Yvanj
Category:
Art
Locations:
Den Bunker


Contents

Outline

Concept

Since the barputer lives in a pretty harsh environment, a backup strategy is required. The last one left us at a moment whe didn't expect it to fail, and accounting is an issue for those who pay their drinks monthly. My idea was to put the barputer and related software in a VM (without Apache <= 2.2.19, or even without Apache at all), and access it remotely. I recently starded exploring x2go. X2go is somewhat like a RDP alternative for linux, a free/OSS version of NXServer.

The advantages of x2go/NX are:

The disadvantages are:

What has been done?


What should still be done?

Notes

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Content Creation
Belgian Spaces