Utilize free RAM as RAM drive for temp files and swap

RAM drive utility: ImDisk - http://www.ltr-data.se/opencode.html/#ImDisk

Create for instance a 2GB RAM drive, mounting it as R:

  • Chrome - Add --disk-cache-dir="R:\ChromeCache" --media-cache-dir=R:\ChromeCache to the Chrome icon's Target to change temp internet files
  • Internet Explore - Internet Options, Browsing History, Settings, Move Folder - Select the root of R:\
SWAP - Disable swap on a normal disk and set a 1GB swap file on R:

Verified on Windows 8, and should support all Windows NT based systems, including x64 :)

A forum post on how to do this with scheduled tasks when booting. Also it is not recommended to use RAM for pagefile. Get more RAM instead, it's cheap these days.
Updated 2: Added info about 'media-cache-dir' option for Chrome.


Reclaim disk space, disable hibernation (hiberfil.sys)

If you just found a gigantic c:\hiberfil.sys, it's your hibernation save file. If you don't use hibernation, turn it off and reclaim the space. On my new rig, I have a sweet 32GB of RAM, and my hibernation file at this point was 26GB. That's a lot of wasted space on an SSD drive when I don't use hibernation.

To disable hibernation and remove this file in Windows Vista, Windows 7 and Windows 8, open a command prompt as administrator and type:

powercfg -h off

This should turn of hibernation and delete the big file automatically :)

For Windows XP, just go to Control Panel > Power Options > Hibernate tab.


WHATS NEW in VMware vSphere 5.1

I found a nice blog article listing new features in vSphere 5.1. The main stuff (taken from the article) was:
  1. vRAM has been killed. vSphere is again licensed per CPU just as it was before vSphere 5.0. The licensing whitepaper is here.
  2. Enhanced vMotion allows you to combine a vMotion and Storage vMotion into a single operation, without shared storage.
  3. vSphere replication has been decoupled from SRM, and released as an available feature of every vSphere license from Essentials Plus through Enterprise Plus
  4. New VMware vSphere Storage Appliance 5.1 for SMBs
  5. New backup solution named vSphere Data Protection replacing VDR.
You'll find the entire article over at the VMware VCP blog


Nice overview of the new VMware vSphere Web Client

Read a good overview article about the new VMware vSphere Web Client at vladan.fr -

Looks like the WebClient is the way VMware is heading, stating that "the thick client won’t get further enhancements after the 5.1 release".


Create icon (.ico) online wit X-Icon Editor

I was looking for a way to convert an image into an icon (.ico), and luckily I found an online tool for that :)
Meet X-Icon Editor --> http://www.xiconeditor.com/


eth0+N headache in linux with virtual templates

If you keep getting eth1 instead of eth0 as your main ethernet interface on a (newer) linux template/clone in a virtualized environment it's most likely because your udev rules is in affect and creates a new eth1 since eth0 is already defined and bound to the clone/template source's MAC address.

This can be fixed in a couple of ways (in your template/clone source image):

1) You can delete the 'SUBSYSTEM' line in your /etc/udev/rules.d/70-persistent-net.rules:

Edit the rules files
  vi /etc/udev/rules.d/70-persistent-net.rules

Delete the SUBSYSTEM line(s), feel free to also delete the comment about PCI device just above:

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:4b:05:e0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

2) A more dirty hack would just be to delete the /etc/udev/rules.d/70-persistent-net.rules file and create a directory named as the file. This tip is taken from six degrees of fredom blog (link):

  rm /etc/udev/rules.d/70-persistent-net.rules
  mkdir /etc/udev/rules.d/70-persistent-net.rules


Hyper-V and Virtualbox is a 'no go' together on a Windows 8 PC

I just tried to run VirtualBox on my Windows 8 computer where I already had activated Hyper-V. That was a 'no go' - it borked out with missing VT-x support:

You simply can't run Hyper-V and VirtualBox simultaneously, as any application that uses the virtualization-specific instruction sets on the CPU (Intel VT-x in my case) does so alone and therefore locks other programs out of using them.

Too bad, but probably security-wisely good. 


iproute2 cheatsheet (updated)

A decent cheatsheet about iprout2 can be found at http://whodat.be/iproute2-cheatsheet-and-reference-guide/ (link dead)

Update: New links for others:
  • http://www.bde.enseeiht.fr/clubs/net7/supportFormations/reseaux/networksheet.pdf
  • http://www.guyrutenberg.com/2010/12/29/iproute2-cheatsheet/


Difference between Windows Storage Server 2012 Workgroup and Standard

Microsoft Technet has an overview of the difference between Windows Storage Server 2012 Workgroup and Windows Storage Server 2012 Standard.

For starters, workgroup does not support dedup, dhcp/dns/wins, failover clustering, runs on only 1 cpu-socket with max 32GB RAM..

Read all at Technet: http://technet.microsoft.com/en-us/library/jj643303.aspx



Use BackInfo to set a servers wallpaper with hostname and other useful info. I used to use bginfo, but backinfo is simpler and that is what I want. Keep it simple!