Is Local ColdFusion development practical?
I used to develop entirely on development servers. This was fine until I started working 100% remotely about 5 years ago. At first I still used Homesite+ via RDP and continued to write code on the dev servers. Then I started using Eclipse/CFeclipse for my IDE. I have no regrets making that switch, but I was then limited to using Windows mapped drives to connect via a slow VPN connection (No RDP for CF5). Not Good! Eclipse was really-really slow doing anything over this connection. Somewhere in that time-frame I also started using Subversion and if I installed Subclipe it would literally kill Eclipse while it refreshed a project.
I now use various virtual machines running in VMWare Workstation. This is a terrific way to program locally on your PC, but still have the flexibility to configure just about anything that you want for a development setup. I typically use a much smaller database in the this dev scenario, as moving 10-20 GB of data over that same slow VPN connection is not any fun.
Well, today it bit me.
Network trouble with Ubuntu 8.04 Hardy when cloning VMWare
I'm still fairly new in the Linux world and still find things that make me scratch my head. I use Kubuntu 8.04 on my PC and I'm working with Ubuntu 8.04 Server in VMWare Workstation.
When cloning or copying a VMWare image, a new MAC address is created for the new image, which means that the first time that you boot up the clone, guess what? No networking! This is stupid simple with Windows, as it would simply detect the new network adapter and continue booting with network support working just fine. It's a different story with Linux, of course! I knew it was an adapter issue and Ubuntu simply wasn't recognizing the new adapter.
This guy found the solution, so he gets all the credit.
Delete this file:
Reboot
VMware unable to open network mapping library
When starting a VM, I received this error:
This started when I moved back to VMware Workstation 6 after trying Server 2.0 Beta.
This thread got me to thinking, but didn't fix the problem.
I looked further into the .vmx file and found more entries that Server 2.0 beta had added. The removal of these 4 lines fixed the issue and the VM now starts fine in Workstation.
ethernet0.networkName = "Bridged"
ethernet0.allowGuestConnectionControl = "FALSE"
ethernet0.wakeOnPcktRcv = "FALSE"
