我依然在使用 G2，已经两年半了，机器里跑的是基于 CM 6.1.0 裁减之后的版本，速度和稳定性都是能接受的。下表（Table 1）列出了修改细节：

Table 1. CyanogenMod ROM

你可以下载以上裁减之后的包：update-cm-6.1.0-DS-lite-signed.zip (48M)
如果你的手机是 G1 或者 G2 32B，直接刷这个包就行了。如果你的手机是 G2 32A (EBL1)，还需要刷一个 port 包。

（OPTIONAL）注意，以上 ROM 是不包含 Google Addons 的，如果你需要 Google 提供的一些功能，比如 Gtalk、电子市场等的，需要刷 gapps 包。当然，我们也可以做一些裁减。以下表格（Table 2）所列是对 gapps-mdpi-20110501 的修改：

Table 2. gapps

你可以下载以上裁减之后的 Google Addons 包：gapps-mdpi-20110501-lite-signed.zip (3M)

注：如果你自行修改了 ROM，一定要对新包进行签名，否则无法刷。android.com 上有指南：Signing Your Applications，就是使用 keytool、jarsigner 两个工具。

如此精简之后，你的“老旧”安卓手机应该也不会表现的太差，have fune ^o^

1. Install the necessary tools on your computer which runs a Linux as operating system. My ThinkPad runs Ubuntu 10.10:
$ sudo apt-get install mtools syslinux

2. Insert a USB stick into your computer, in most cases, your Linux should mount the USB disk automatically. If so, umount if firstly:
$ sudo umount /path/to/mount/point

3. Check the partitions information of the USB disk (assume the device is /dev/sdb):
$ sudo fdisk -l /dev/sdb

If the USB disk is never initialized and has no partition table, you need to create at least one partition on it.

4. Format (one partition is enough):
$ sudo mkdosfs /dev/sdb1

5. Install syslinux:
$ sudo syslinux /dev/sdb1

6. Mount the USB disk, and put necessary files into it:
$ sudo mount /dev/sdb1 /mnt
$ cd /mnt
$ sudo wget http://d-i.debian.org/daily-images/amd64/daily/hd-media/vmlinuz
$ sudo wget http://d-i.debian.org/daily-images/amd64/daily/hd-media/initrd.gz
$ sudo wget http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso

Notes: Of course, since downloading images is time-consuming, you can download them separately and copy into the USB disk.

7. Create configuration file syslinux.cfg
$ cd /mnt
$ sudo vi syslinux.cfg

default vmlinuz
append initrd=initrd.gz

Umount the USB disk, it’s ready for use then.

No CD/DVD, more green Have fun!

1. Prepare Virtual Disk Image

Xen supports to run VM on physical device or virtual disk image. Here I am going to use virtual disk image in raw format. The below creates a 8G virtual disk for root partition, and a 512M virtual disk for swap:

# dd if=/dev/zero of=centos6.img bs=4K count=0 seek=2048K
# dd if=/dev/zero of=centos6.swp bs=4K count=0 seek=128K

Or, you can use qemu-img utility to replace dd:

# qemu-img create -f raw centos6.img 8G
# qemu-img create -f raw centos6.swp 512M

2. Prepare Configuration for Xen VM installation

Xen needs three files to install a VM: kernel, ramdisk, and a configuration file.

You can always find appropriate kernel and ramdisk from your Linux distribution’s website, for example, CentOS 6.0:

# wget http://mirror.centos.org/centos/6.0/os/x86_64/isolinux/vmlinuz
# wget http://mirror.centos.org/centos/6.0/os/x86_64/isolinux/initrd.img

And create a Xen configuration file:

# vi centos6-x64-domu

kernel = "/data/vm/vmlinuz"
ramdisk = "/data/vm/initrd.img"
name = "xc6"
memory = "512"
disk = [ "file:/data/vm/centos6.img,xvda,w","file:/data/vm/centos6.swp,xvdb,w" ]
vif = [ "bridge=br0" ]
vcpus = 1
on_reboot = "destroy"
on_crash = "destroy"

Notes:

file: uses dom0 kernel page cache, and thus might give better performance than phy: or tap:aio:, but it’s also more insecure because of caching. tap:aio: uses direct IO, so it bypasses dom0 kernel cache, and works like phy: in that sense. Refer to blktap on Xen’s wiki to understand more.

Please be aware:
1, your dom0 must have loaded blktap modules before you can use tap:aio:. Not every Linux distribution has built everything in.
2, if your blktap is version 2 (i.e., blktap2), for example, Debian Wheezy, you need to use tap2:tapdisk:aio: etc.

3. Start Installing

Now it’s time to create the VM and start installing CentOS 6.0 in it:

# xm create centos6-x64-domu

Then you can connect to the virtual console, and do regular OS installation:

# xm console xc6

4. Change Configuration for Xen VM Normal Operation

After the OS is installed, the VM is destroyed. You need to edit the configuration from Xen VM installation to normal operation.

# vi centos6-x64-domu

name = "xc6"
memory = "512"
disk = [ "file:/data/vm/centos6.img,xvda,w","file:/data/vm/centos6.swp,xvdb,w" ]
vif = [ "bridge=br0" ]
bootloader = "/usr/lib/xen-4.1/bin/pygrub"
vcpus = 1
on_reboot = "restart"
on_crash = "destroy"

The new configuration uses pygrub as a bootloader that acts grub and uses grub.conf from inside the VM. Of course, you can continue using the separated kernel and ramdisk, but this means you need to maitain them by yourselves.

Then you can start your VM by typing:

# xm create centos6-x64-domu

Have fun!

1. Remove AppArmor

$ sudo invoke-rc.d apparmor stop
$ sudo update-rc.d -f apparmor remove
$ sudo apt-get autoremove --purge apparmor
$ sudo reboot

After the machine is rebooted, you can check if there are configurations or data folders not deleted automatically, if yes, you can delete them safely, for example:

$ cd /etc
$ sudo rm -fr apparmor*

2. Configure Bridge (optional)

This step is only required when you want to provide ethernet bridging for VMs.

First of all, bridging tool needs to be installed:

$ sudo apt-get install bridge-utils

By default, Ubuntu uses NetworkManager to configure network devices automatically. But here we need to edit the configuration file manually to add bridging settings:

$ sudo vi /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto br0
iface br0 inet static
address 192.168.96.88
netmask 255.255.255.0
network 192.168.96.0
broadcast 192.168.96.255
gateway 192.168.96.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

If your machine is using DHCP for IP configuration, change the third section (device br0) to:

auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

Save your configuration file, and restart network to take effect:

$ sudo invoke-rc.d networking stop
$ sudo invoke-rc.d networking start

Or, if you are working remotely, stopping network will disconnect you to the machine, just do reboot machine alternatively.

After restarted network or rebooted machine, use ifconfig and brctl show to check if ethernet briding works as expected.

$ brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.5c63bf86e499	no		eth0

3. Install KVM and SPICE packages

The qemu-kvm version in Oneiric is 0.14, but Ubuntu’s compilation does not include SPICE support. We have to use another repository which has compiled qemu-kvm with SPICE support.

$ sudo apt-add-repository ppa:bderzhavets/qemu-git
$ sudo apt-get update

I don’t know if there are the other repositories better than the above found in Ubuntu wiki. But at least it works.

Install:

$ sudo apt-get install qemu-kvm virt-manager spice libspice-server

After installed the packages, your Oneiric is ready to run VM with SPICE support. Refer to another post to learn how to install guest with SPICE support.

Stop and remove UFW:

$ sudo invoke-rc.d ufw remove
$ sudo update-rc.d -f ufw remove
$ sudo apt-get autoremove --purge ufw

Then install a utility for loading iptables rules at boot-time:

$ sudo apt-get install iptables-persistent

By default the iptables rules are stored in /etc/iptables/rules.v4.

Sample 1: configure a dual-NIC Linux box as a NAT gateway. Let’s assume eth0 be connected with external network, eth1 be connected with internal network, and the internal network is 192.168.96.0/24.

Use editor to open the above file, and add the following line under POSTROUTING ACCEPT chain of nat table:

-A POSTROUTING -s 192.168.96.0/24 ! -d 192.168.96.0/24 -o eth0 -j MASQUERADE

Sample 2: Open ports. Assume needs to open TCP ports 22, 53, 80, and 5900-5920.

Adding the below line under INPUT ACCEPT chain of filter table:

-A INPUT -p tcp -m multiport ‐-dports 5900:5920 -j ACCEPT
-A INPUT -p tcp -m multiport ‐-dports 22,53,80 -j ACCEPT

<EOF>

• ICA – Citrix XenDesktop supports it
• PCoIP – VMWare View supports it
• RDP – Microsoft supports it
• SPICE – Red Hat (RHEV) supports it
• … …

The last one, SPICE, really rocks, especially in multimedia and WAN! The user experience is really great.

SPICE (Simple Protocol for Independent Computing Environments) is an open standard. Red Hat got SPICE and KVM when it acquired Qumranet in 2008, and opened them. SPICE support was added to upstream Qemu in April 2010, that means, if your Qemu is released after April 2010, you can play with SPICE easily with the following steps.

This experiment uses Fedora 15 x86_64 as the host machine OS, SPICE server doesn’t support 32-bit system due to its reliance to 64-bit atomic operation, and uses Windows XP as the guest machine OS, because Windows still dominates the personal desktop area.

1. Create a VM and install Windows XP:

Prepare a virtual disk:

$ sudo qemu-img create -f raw winxp.img 10G

Install VM:

$ sudo virt-install --connect=qemu:///system \
                    --name=richdesk --ram=1024 --vcpus=1 \
                    --os-type=windows --os-variant=winxp \
                    --hvm --virt-type kvm \
                    --cdrom=/path/to/winxp_install.iso \
                    --disk path=/path/to/winxp.img \
                    -w network=default \
                    --graphics spice,port=5901,listen=0.0.0.0 \
                    --video qxl --channel spicevmc \
                    --soundhw default \
                    --accelerate

Notes:

• The above command uses NAT for network, if you prefer bridge mode, change network option to --network bridge=br0. Of course, you need to configure a bridge device br0 firstly.
• The above command uses 5901 as SPICE server port, you can change it to any valid port. Please make sure the port is opened on the host machine if it has firewall enabled.

After installed the basic Windows XP, shutdown the VM.

2. Install SPICE guest packages for Windows

Download the latest Windows binaries packages from SPICE website:

$ wget http://spice-space.org/download/binaries/qxl-win-0.1010-20110308-d9eb3203bd.zip
$ wget http://spice-space.org/download/binaries/virtio-serial_20110725.zip
$ wget http://spice-space.org/download/binaries/vdagent-win32_20110801.zip

Copy qxl, virtio-serial, vdagent packages into the images:

$ sudo virt-copy-in -a winxp.img *.zip 'win:c:\'

Then start VM, and install the drivers qxl and virtio-serial.

Unzip vdagent package to any place, for example, C:\opt, and register it as a Windows service:

C:\opt\vdagent-win-x86> vdservice install

Reboot this Windows VM.

3. Connect to VM via SPICE protocol

There are several client tools which support SPICE protocol, for example, Vinagre, spicec, virt-manager, etc. My favourite is Vinagre. Also you can buy a thin client hardware whose firmware supports SPICE protocol.

By default the SPICE plugin of Vinagre is disabled, you can enable it through Edit -> Plugins. Then you can connect to host:5901.

Now you have gotten a Windows guest with SPICE support, then enjoy the great quanlity and smooth operation experience brought to you by SPICE! Is it all? Yes if you mean SPICE. But if you want to improve the performance of your virtual desktop more, recommend to use virtio drivers for hard disk and network card. I’m not going to cover virtio in this post.

Have fun ^o^

The following describes how to compile and install a SPICE client from source code on Ubuntu 10.10 (Maverick) 32bit. The procedure for the other Ubuntu releases or Debian distributions should be similar.

1. Install the standard tools for compilation
$ sudo apt-get install build-essential autoconf git-core libtool

2. Install dependencies existing in repository
$ sudo apt-get install libavcodec-dev libssl-dev libasound-dev libpng12-dev libfreetype6-dev libogg-dev libxrandr-dev libgcrypt-dev libsdl-dev libnss3-dev libpixman-1-dev libxfixes-dev libjpeg8-dev libsasl2-dev

3. Install dependencies not existing in repository

3.1. libcacard

This library is what SPICE uses to emulate smart cards and smart card readers.

$ git clone git://anongit.freedesktop.org/~alon/libcacard
$ cd libcacard
$ ./autogen.sh
$ make
$ sudo make install

3.2. celt051

There is newer celt packages in Maverick’s repository, the version is 0.7.1. But SPICE client requires a specific version – 0.5.1, so we have to install this required version manually.

Get the below two packages from launchpad then install:

$ sudo dpkg -i libcelt051_0.5.1.3-2_i386.deb
$ sudo dpkg -i libcelt051-dev_0.5.1.3-2_i386.deb

3.3. SPICE protocol

$ wget http://spice-space.org/download/releases/spice-protocol-0.8.1.tar.bz2
$ tar jxvf spice-protocol-0.8.1.tar.bz2
$ cd spice-protocol-0.8.1
$ ./configure --prefix=/usr
$ make
$ sudo make install
$ cd /usr/include
$ sudo ln -s spice-1/spice .

4. Finally we are ready to compile and install SPICE client

$ wget http://spice-space.org/download/releases/spice-0.8.2.tar.bz2
$ tar jxvf spice-0.8.2.tar.bz2
$ cd spice-0.8.2
$ ./configure --enable-smartcard
$ make
$ sudo make install

That’s it. Now you can connect to your VM with spicec, for example:

$ spicec --host SPICE_SERVER --port 5300

Enjoy the speed and performance of SPICE!

<EOF>

ppa:libreoffice/ppa
ppa:chromium-daily/stable
ppa:mozillateam/firefox-stable
ppa:pidgin-developers/ppa

If you need QQ support in Pidgin, you can install a protocol plugin: libqq-pidgin. You can compile its source code and install it, of course, there is a PPA usable:

ppa:lainme/libqq

<EOF>

Fedora:

$ sudo yum install NetworkManager-openvpn

Debian/Ubuntu:

$ sudo apt-get install network-manager-openvpn

以下步骤是在 Fedora 15 中配置 GNOME Network Manager 连接至 HLYY OpenVPN 服务，其他 Linux 分发版应该都是一样一样滴：

1. 下载 HLYY OpenVPN CA 证书：
$ wget http://vpn.yunsong.net/hlyy-ca.crt

2. 打开 系统设置 -> 网络，点击左下角的加号（图1），在出现的对话框中选择创建一个 VPN 连接、并选择 OpenVPN 类型。

图1

3. 如下图2配置 OpenVPN 客户端

图2

网关：vpn.yunsong.net
认证类型：密码
用户名：your_username
密码：your_password
CA 证书：选择在第一步中下载的 hlyy-ca.crt 文件

并点击“高级…”按钮，在弹出的新对话框（图3）中做如下配置：

图3

选中“使用自定义网关端口”，并指定端口为 11194
选中“使用 LZO 压缩”

OK，这就完成了配置。

需要注意的是，当你在 Network Manager 中启用了这个 OpenVPN 连接后，所有你的计算机的网络流量都得经过这个 VPN 线路，这对于访问那些墙内资源就不合适了。这时你需要考虑分流，即只有墙外资源走 VPN 线路，Google Code 上有一个很好的项目 chnroutes 可以帮助你。

$ cd /etc/yum.repo.d
$ sudo wget http://pokgsa.ibm.com/projects/o/openclient/lotus/notes/beta/8.5.3/notes-8.5.3-ea.repo
$ sudo yum clean all
$ sudo yum update
$ sudo yum install ibm_lotus_notes

This is going to install Lotus Notes 8.5.3 and dependencies in your Linux. After installed, you can launch Lotus Notes to configure it, then you can see Lotus Notes launched with a blank main frame. Well, that’s a bug, don’t worry, shutdown Notes, and do the following workaround:

$ cd /opt/ibm/lotus/notes
$ sudo wget http://linux-aha.de/wordpress/wp-content/uploads/2009/10/notes_libs_karmic.tgz

There are 4 .so files in the package, extract it, and make sure they are owned by root and executable.

$ sudo chown root.root libg?k*
$ sudo chmod 755 libg?k*

OK now, you can start Lotus Notes again, the blank is gone.