I just setup a new Debian OpenVZ container on a commercial VPS. It was installed as Lenny, but since I want to install a newer version of Varnish, I upgraded to Squeeze.
uh-oh::/var/cache/apt/archives# dpkg -i dpkg_1.14.26_i386.deb
(Reading database ... 12216 files and directories currently installed.)
Preparing to replace dpkg 1.14.26 (using dpkg_1.14.26_i386.deb) ...
Unpacking replacement dpkg ...
Replaced by files in installed package base-files ...
Setting up dpkg (1.14.26) ...
touch: setting times of `/var/log/dpkg.log': Bad address
Oh-no! A little digging reveals that there is a conflict between the newer version of coreutils and the kernel that is running on the openvz host. I’m surprised as I have an openvz host which is running 2.6.18 with squeeze containers… I think. I’ll have to check that.
A recent run of powertop discovered that the webcam in my Acer Extensa 5620Z was causing a significant amount of wakeups. I never use it, in fact its covered up with a sticker.
[ 6.888500] usb 1-1: Product: Acer CrystalEye webcam
[ 15.287631] uvcvideo: Found UVC 1.00 device Acer CrystalEye webcam (064e:a101)
[ 15.288506] input: Acer CrystalEye webcam as /class/input/input6
zzillezz.net turned a similar webcam off with “blacklist gspca”. I’m using “blacklist uvcvideo”.
While I was at it, I also blacklisted a few other modules to save RAM as my laptop recently lost 2GB of RAM. 
I’m realizing that by using web server proxies to servers which run inside virtual machines, its much safer to hack up code and libraries. If something gets messed up, its much easier to recover, or avoid a failure altogether. That’s nice.
As it so happens, I’m currently messing around with a bunch of libraries trying to get the perl web::svn package working. Its an awesome package but the libraries behind it seem all out of sorts.
What’s this mean specifically? I’m going to setup a Genoo container!
I’ve used OCF linux before and it is very cool, however its BSD license taints the linux kernel.
http://www.logix.cz/michal/devel/cryptodev/index.xp?show_selected=1&msgid=4534
Of course this patch is for 2.6.8 and I’m using 2.6.26, and am getting this error:
crypto/cryptodev.c:74: error: ‘CRYPTO_TFM_MODE_ECB’ undeclared here (not in a function)
crypto/cryptodev.c:74: error: array index in initializer not of integer type
crypto/cryptodev.c:74: error: (near initialization for ‘crypto_cipher_modes’)
crypto/cryptodev.c:75: error: ‘CRYPTO_TFM_MODE_CBC’ undeclared here (not in a function)
crypto/cryptodev.c:75: error: array index in initializer not of integer type
crypto/cryptodev.c:75: error: (near initialization for ‘crypto_cipher_modes’)
crypto/cryptodev.c:76: error: ‘CRYPTO_TFM_MODE_CFB’ undeclared here (not in a function)
crypto/cryptodev.c:76: error: array index in initializer not of integer type
crypto/cryptodev.c:76: error: (near initialization for ‘crypto_cipher_modes’)
crypto/cryptodev.c:77: error: ‘CRYPTO_TFM_MODE_CTR’ undeclared here (not in a function)
crypto/cryptodev.c:77: error: array index in initializer not of integer type
crypto/cryptodev.c:77: error: (near initialization for ‘crypto_cipher_modes’)
Obviously a lot has changed in the kernel from 2.6.8. I’m not sure how to proceed - maybe I should look at the 2.6.8 code, or I should just start editing the cryptodev.c / cryptodev.h.
There might be a chance that Michal’s code gets adopted into the kernel. That would be awesome. More info: http://www.docunext.com/wiki/Michal_Ludvig_Cryptodev