KDE4 aqua theme

Latest Code from SVN

You can allways get the bleeding-edge fresh new experimental code from svn.
Most Linux distributions install svn by default, every brings it on disc or via online update.

You can also obtain it from svn.tigris.org (especially if you use Windows).

Getting the code is easy.

• First open a terminal (konsole, xterm, windows users call “cmd”)
• Now checkout the sources
  

  svn co https://cloudcity.svn.sourceforge.net/svnroot/cloudcity

• This will create a directory “cloudcity” in the path wherever you are
  (usually $HOME, make sure you have write permissions here)
• For instructions how to compile the code, see the tarball section.

Tarballs

Source tarballs can be downloaded from SourceForge

How to compile
Download the tarball, open a terminal (konsole) and navigate to the directory where you downloaded the tarball, e.g.:

cd ~/downloads

Next, untar the tarball (x.y.z are just placeholders…)

tar -xjf bespin-x.y.z.tar.bz2

Enter the just created bespin directory

cd cloudcity

---

Configure

./configure

The configure script can detect a valid Qt4/KDE4 environment.

If your system lacks such, there will be error reports.
In case you can pass the Qt4 and KDE4 paths (along some other options, try)

./configure help

---

If anything went right, you can start compilation

make

---

No compile errors? Install the libraries / config dialog

make install

NOTICE: You need proper rights on the QT4 / KDE4 paths to perform this
If it fails, try

sudo make install

(You’ll need your administrator password here)

usefull linux commands – xprop

xprop – used to view the class

type: What kind of window is it? A menu, a dialog, a tooltip, or something else?

Command: xprop _NET_WM_WINDOW_TYPE | cut -d_ -f10

role: What is the window’s role? (Only useful for some programs. Usually blank.)

Command: xprop WM_WINDOW_ROLE | cut -d\” -f2

name: What is the window’s class name?

Command: xprop WM_CLASS | cut -d\” -f2

class: What is the window’s class?

Command: xprop WM_CLASS | cut -d\” -f4

title: What is written in the window’s title bar?

Command: xprop WM_NAME | cut -d\” -f2

xid: What is the window’s XID? (Only useful for identifying a window that’s already open.)

Command: xprop WM_CLIENT_LEADER | cut -d’ ‘ -f5

state: Is the window maximised, staying on top, sticky, or something else?

Choose one: modal, sticky, maxvert, maxhorz, shaded, skiptaskbar, skippager, hidden, fullscreen, above, below, or demandsattention

Reccomended Service Console Partitions and Sizes

Reccomended Service Console Partitions and Sizes for Each ESX Server Host

Mount Point		Partition Type		Size		Description
/dev/sda (Primary)
/boot	ext3		250 MB		Change for additional space for upgrades
N/A	swap		1600 MB		Change for maximum service console swap size
/	ext3		5120 MB		Change for additional space in root
/dev/sda (Extended)
/var	ext3		4096 MB		Create partition to avoid overfilling root with log files
/tmp	ext3		1024 MB		Create partition to avoid overfilling root with temporary files
/opt	ext3		2048 MB		Create partition to avoid overfilling root with VMware HA log files
/home	ext3		1024 MB		Create partition to avoid overfilling root with agent / user files
	vmkcore		100 MB		Pre-configured
	Free Space		(Optional) Auto-configured and used for local VMFS-3 volume (needed for virtual machines running Microsoft’s Clustering Software.

from http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/

ssh tunneling

using openssh it is possible to tunnel to a remote network over an encrypted port and tunnel any protocol over that.

sudo ssh -L local port:endpoint ip:port on endpoint user@ssh server

where local port is the port on your machine, endpoint ip is the server you want to connect to, port on endpoint is the service port on the endpoint and user@ssh server is the user and the ssh server you are proxing through.

for example:

sudo ssh -L 33890:192.168.0.10:3389 root@1.2.3.4

will map the port 33890 on your local PC through to 192.168.0.10 from the remote ssh server 1.2.3.4.

this means you can connect to 127.0.0.1:33890 and you will connect to 3389 on the 192.168.0.10 server.

the main advantage of this is you dont need to be able to route to the 192.168.0.10 address – only the ssh proxy needs to.

converting .pfk certificates to .pem

Some applications require that the certificate you are using is in the .pem (Privacy Enhanced Mail) Base64 encoded DER certificate format. If you have the certifiacte as a .pfx you can convert it using openssl like this…

openssl pkcs12 -in yourcert.pfx -out yourcert.pem -nodes