Macify me is an attempt to document my first year as a Mac user. The idea is to try out some of the many myths and (mis?)conceptions around Apple, Mac and iEverything. I’ve decided to put myself in the role of the guinea pig and let all the good, the bad and the ugly of Apple Mac get into my life.
I guess you all know how search engines index the web. They send robots, or spiders, to surf the web and collect information about different pages. About a week ago I installed StatPress on my WordPress installation to collect some statistics about my visitors.
StatPress is a plug-in for WordPress which allows for real-time statistics about visitors. It reports most popular posts, browsers, search terms used to find your blog and also which search company visits your site most frequently.
In these 7 days I’ve had StatPress installed it has collected the following information about the search companies indexing my site. The results are in percentage of visitors recognized by StatPress as spiders:
The latter one I haven’t even heard about, but apparently they’re working on social media. Or in their own words:
“Radian6 created tools to help remove the barriers to effective social media monitoring and analysis.”
This list may not be 100% accurate since StatPress only lists spiders which is know to it. At least I think that’s what it does, because I have yet to see a single entry from any Norwegian search engine. But then again, maybe they’re not aggressive enough to get onto the list?
Found a nice tip for using VMwares Infrastructure Client to manage VMware Server, a product which is usually managed via web interface. The tip is to simply add the port number of the web interface after the server name or ip address in Infrastructure Client. I.e. “servername:8333”, where 8333 is the default port number for VMware Servers web interface.
The reason for this is most likely that VMware Server is installed as an application on top of an operating system. This underlying operating system might very well use the default SSL port number, 443, for its own web service already.
However; If you’re running VMware Server exclusively, it should be possible to change the port number of the web interface to 443, thus avoiding this issue all together. At least my guess is that this will work.
If you want a free hypervisor, but don’t want the trouble of maintaining an underlying operating system, I would recommend taking a look at VMware ESXi. I’ve written a blog post about it. The only reason, as I can see, to run VMware Server is the hardware support, since the operating system takes care of this. VMware ESXi has limited hardware support by default. But there are ways to get support for SATA controllers, among other things.
Also; You might want to check out Citrix XenServer, which also has been released for free. This is a bare-metal hypervisor, meaning you don’t need an underlying operating system. But I don’t have any experience with XenServer, so I can’t really give any advice or tips yet.
Apparantly the big money isn’t in the hypervisor anymore, but the technology to manage them. Giving away your product is the best way to get more customers.
Citrix says their hypervisor, XenServer, has a couple of features not available throught VMwares ESXi, at least not without opening your wallet. For instance, ESXi is a 32-bit bare-metal hypervisor, whereas XenServer is a 64-bit bear-metal hypervisor. XenServer can also handle up to 8 virtual CPUs, while ESXi only handles 4.