Skip to main content

My views on the upcoming VI3 book (based on the samples)

This will be updated by the time I am done reading all the 110 pages on the sample chapter, a good learning experience for me since I too am working on writing my own book out there:

  • Language: Guys, you need to reword this, I wouldn't use words like "Butt" in a hardcopy.
One thing about being in IT (that no one ever mentioned when I got into it), is
that licensing, not to mention the legalities of it, is one of the biggest pain in the
butt issues I deal with all the time. Every time a vendor comes out with a
feature, you get a new price and a new license model.


I should be done in a week (I know , I know, but I am way too busy to just go through the book only). Keep watching this space!!!

Thanks!

Tarry

Comments

  1. I also believe that their definitions of the VI3 versions are wrong. With the starter edition it comes with a license to use with VirtualCenter.

    I echo the comments about 'butt', etc. Granted this document is from some very well respected professionals in the field and they're allowed to write it any way they want. It just makes it sound a little rough around the edges.

    Hopefully the entire book will be available before VMworld.

    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

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!