Roy's musings

Ever since I tried Java back in 2000, I have felt a little uncomfortable about the not-so-powerful and not-so-intuitive set of tools accompanying JDKs. That was one of the reasons why I didn't pursue my interests seriously in programming in Java. But the notions are changing and I mean it. From the hoopla going on about Java SE 6, I was tempted to try that. Hence you might be seeing some Java SE 6 specific posts in future too. There are a lot of powerful tools (jhat and jmap for instance) that are bundled in this SE for the pleasure of the system programmer. I came across this excellent list of tutorials when I was browsing through Mandy Chung's blog . She is the person leading the Java Management & Monitoring Tools API (java.lang.management) effort. You would find this list of tutorials extremely useful. Though most of them are specific to Java SE 6, I guess some of them should be applicable to earlier JSEs too.

I faced a very weird problem while I was trying to find log, check out or update files from the CVS repository. The following error message was flashed on the screen: [myuserid@localhost java]$ cvs log . myuserid@mycvshost's password: cvs-1.11.17_p2 log: Logging . : No such file or directoryopen directory /cvsroot/my/repository cvs-1.11.17_p2 log: skipping directory myuserid@mycvshost's password: " but pserver says "/cvsroot/my/repository"/my/repository I could sense that this might be related to some CRLF (Carriage Return-Line Feed) issue, as all the error lines seem to be starting with what look like end of string delimiters (":" or "\""). So to further clarify my doubt I redirected the output to a file and this is the exact error message I was getting: cvs-1.11.17_p2 log: Logging . cvs-1.11.17_p2 log: cannot open directory /cvsroot/my/repository^M: No such file or directory cvs-1.11.17_p2 log: skipping directory Protocol error: Root s...

I came across Java Platform Performance book while I was searching for something else. Thought this would be an interesting reading.

We had a heated discussion in our team today. One of my teammates was complaining that the existing 8 GB disk (the .vmdk file) that he had attached to his VMWare Player was running out of space. Hence he needed a work around for that. Remember that all of us only have a VMWare Player, not a VMWare Workstation using which you can create a hard disk image. I suggested him a hack. Copy the existing .vmdk file. Give it a new name. Add that file as the next SCSI drive in your VWWare configuration file (.vmx file). You can do it easily by editing your .vmx file in notepad. Start your virtual OS. In his case it was RH Linux. Format the newly added disk. (mke2fs /dev/sdb). You are done. You have another 8 GB of storage. But still I was not happy about this hack. What in case he exhausts all this 8 GB soon. So I was searching the Internet. My objective is simple: I have an up and running VMWare virtual OS where I would like to add a new SCSI drive of whatever size I want. Well! Forever For Now ...