Skip to main content

Thin's back!

Another multi-part series coming up here:

Phil Osborne has been with Citrix in Australia for the last ten years, and he's watched the market for thinness growing. "So I really came in at the start of the whole concept of thin client computing. I think even the word thin client, which I guess we're stuck with now because it's the start of the whole revolution, is a little bit of a misnomer because today thin client really refers to the thinness of the connection between the end point and the data centre," says Osborne. "So that's what thin client today really means as opposed to the actual hardware that many people use."

Indeed, you don't have to have thin client hardware to run a thin client model. "In fact many people are using fat PCs in what we call a hybrid mode," says Osborne. "I have a laptop because I travel a lot and I use that both as a fully functional fat PC but I also use it in conjunction with, if you like, a thinness of connection for some of our back-office applications. I often say to people when they're trying to get their head around this, I say think of two things, where do you want the applications to run and where do you want the data to reside?

Read on...

Comments

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!