Windows 10 is definitely better than Windows 8 and 8.1 in terms of usability. I find myself using my labtop a lot more after upgrade from the factory installed 8.0. Compared with Windows 7, however, I don’t see much difference and that is why I haven’t taken advantage of the free upgrade from Microsoft on my desktop.
I just spent quite some time helping a friend to recover a corrupted virtual machine in VMware Fusion. It’s indeed a long and interesting (sometimes frustrating too) process that I learned quite some that I would never otherwise. I think you might find it useful as well. Hopefully, you don’t get a corrupted virtual machine, but in case you do, I am sure the post will help you.
Once in a while, I got into issues that my build failed because the IDE could not clean certain folder or file. The root cause was that they were opened by another application/process. If the application is known, just closed it and the build worked well. Some times I had no clue which application held the file. To find out quickly without guessing, right tools are needed.
On Linux, it’s quite easy with a command called lsof as follows:
While writing technical blogs, it’s always nice to include commands and scripts that readers can try on their own. I find it a bit challenging to accurately document these in steps while intensively testing or debugging something by myself.
There are actually commands that faithfully list all the commands you typed. You can then clean them up for your posts. In the following, I introduce how to do these on Linux, Windows.
I got an interesting request from one of the enterprises which uses vijava in their product. Although there are downloads for binary and source packages on the sourceforge Web site, they still would like me to create the checksum as I am the trustable source for that. As I was told, the checksum is required by their build team. I don’t know how is exactly used, but I decided to help out anyway.
In my previous article, I introduced the Remote Desktop Connection Manager. It’s highly recommended to use it over the virtual machine console which all goes through the ESXi management IP therefore is not good for performance especially when there are many concurrent connections to virtual machines running on a same physical host.
Even if you are convinced on connecting to virtual machines directly, you will find it’s not convenient to add many virtual machines to the Remote Desktop Connection Manager. That is why I decided to write a small tool to automate it.
I think most of us have used Microsoft Remote Desktop Connection (mstsc.exe), which is used to connect to a remote server using RDP protocol. If you have more than several remote servers to connect, it can be very inconvenient to navigator through them. Microsoft knew that and created a new tool called Remote Desktop Connection Manager. You can download it for free at Microsoft site here.
Even if you haven’t heard about BusyBox, you may have used it. It runs in every ESXi, which doesn’t have a full OS as console like classic ESX. Still, you need an easy way to interact the hypervisor directly. So the ESXi includes a tiny console that uses BusyBox (reduced version) due to its small size.
The BusyBox has been ported to Windows as well. You can download the 600+K executable here. It’s really a simple exe file and you can place it anywhere.