I’ve been fiddling around the file system of the Nokia N9 lately. It’s not hard to do and actually quite fun to have shell on a linux device that fits in the palm of your hand.

First enable developer mode:

Settings > Security > Developer Mode

The phone will install an SSH server and also a Terminal to the home screen. Open the Terminal and you will be in BusyBox v1.19.0 shell.

Second, change the root password. Enter the following command to su to root:

devel-su

It will prompt for a password. The default is “rootme”. The prompt should change from “~ $” to “~ #”. Enter the following command to change the root password:

passwd

You will have to enter it twice. Then type “exit” to return to the user prompt.

If you type “gconftool-2 –help” at the prompt you should see a long list including a “s” option to set and sync a value and a “t” option with the values “int|bool|float|string|list|pair”

For example, use the following to install an image to the screen_lock screen.

gconftool-2 -t string -s /desktop/meego/screen_lock/low_power_mode/operator_logo /home/user/MyDocs/Pictures/filename.png

The image (filename.png) should be no more than 120×120 pixels and 1-bit (black and white). Space invaders comes to mind…

Or a flyingpenguin:

Maybe white is a little bright. The screen lock color can be modified by editing the following file:

/usr/share/themes/base/meegotouch/libsysuid-screenlock-nokia/style/libsysuid-screenlock-nokia.css

Easiest way to modify it is remotely over ssh. Open the SDK Connection app on the home screen. Select WLAN from the two buttons. It will show you the IP of the N9 and the password.

Once you’ve made a backup of the file, change the hex setting just below the line that reads LockScreen MLabelStyle#LockScreenLowPowerModeClockLabel. Red is #FF0000.

Chris Colotti has written detailed instructions on vCloud Director Disaster Recovery

Creating DR solutions for vCloud Director poses multiple challenges. These challenges all have a common theme. That is the automatic creation of objects by VMware vCloud Director such as resource pools, virtual machines, folders, and portgroups. vCloud Director and vCenter Server both heavily rely on management object reference identifiers (MoRef ID’s) for these objects. Any unplanned changes to these identifiers could, and often will, result in loss of functionality. vSphere Site Recovery Manager currently does not support protection of virtual machines managed by vCloud Director.

Michael Webster at Long White Virtual Clouds has a great post on changing the SSL certificates for the vCenter Server Virtual Appliance (VCVA):

…because the vCenter Server Virtual Appliance is Suse Linux Enterprise Server based you will have to be used to a Linux command line, using scp, and generally navigating around in order to successfully change your certificates. All operations will be done as root. The default password is vmware. Like in my previous articles regarding changing SSL Certificates I have included an example OpenSSL configuration file that you can use to generate your certificates.

The following directories on the VCVA contain SSL certificates in one form or another:

/opt/vmware/etc/lighttpd/

/etc/vmware-vpx/ssl

/usr/lib/vmware-vpx/inventoryservice/ssl

/usr/lib/vmware-vsphere-client/server/config

I will go through what needs to go where after I’ve given you what you need to create the certificates.