Skip to main content

Welcome Home, Brian!



I'm speechless and overwhelmed with the birth of my Son. Welcome home, Son!

Brian, born on 15:56 (GMT+1) hours, 17th Feb 2006.

PS: On another note. It's gotta be an auspicious day for VMware as they choose the same day (17th Feb) to send out invitations for Beta testers (ESX 3.0/VC2.0) finally.:-)

Comments

  1. I'm a bit confused as to where VM ends and Brian begins. Am I right in thinking he's not virtual?

    Hearty congratulations - DaPi.

    ReplyDelete
  2. David,

    Indeed, he's all flesh and blood.

    It's just that the long awaited ESX 3.x beta invitations too got sent out on the same date ;-)

    Thanks again.

    Tarry

    ReplyDelete
  3. Tarry --

    Congratulations! Start him virtualizing early! :-)

    John

    ReplyDelete
  4. Hey John,

    Thanks a lot!

    We're looking at the future CEO VMware here..heh heh

    ReplyDelete
  5. I can't believe I missed this post. Congratulations papa! Hope everyone is fine.

    All the best,
    Bill

    ReplyDelete
  6. That's OK Bill,

    Thanks a lot! :-) Everyone is doing fine indeed.

    ReplyDelete
  7. congratulations... Tarry.
    I was just browsing your blog & found this post.
    Nice blog. Keep on posting...

    ReplyDelete
  8. Thanks pran,

    Appreciate your kind words.

    ReplyDelete

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op