There are many reasons why this is bad. First, the ability to type in a decent speed may be necessary to program fast (not necessarily to program well, mind you), at least in non-static type languages where IDE can't do autocomplete well. That means languages Java, VB, .NET (with compile time type checking) with extensive autocomplete support, doesn't need much typing speed because the autocomplete will do most of the fast typing for you. Even then, you don't usually bottleneck your productivity at your typing speed unless you are writing a lot of linear non repeating code. But in any environment where such code is necessary, typing speed will be the least of your concern. What's important is the ability to type without conscious effort so that your programming effort can be concentrated on actual programming. Assumes existing programmers in that company are competent: If typing speed limits the productivity of programmers, any framework the existing programmer...
Information on setting xen with NAT in debian lenny is scattered over the internet. One resource mention about patching some files. This guide is for people who want to do the setup with the most minimal change to debian default setup. 1. In /etc/xen/xen-config.sxp, comment (put # in front of) the "(network-script network-dummy)" and "(vif-script vif-bridge)". Comment out (erase # in front of) the "(network-script network-nat)" and "(vif-script vif-nat)". 2. Put "brctl addbr $2" after the line saying "echo $*". Then put "ifconfig $2 xxx.xxx.xxx.xxx" at the end of the file, where xxx.xxx.xxx.xxx is a local static IP address. 3. Set up your dhcp server accordingly by have it listen to the interface, the default is xenbr0. The ip of xenbr0 will be automatically set to xxx.xxx.xxx.xxx from step 2 above. Restart your dhcp server if necessary. 4. Run your xen image. 5. Then restart ipmasq by running /etc/init.d/ipmasq...