Skip to main content

VMware: A Classic from 2002



I'm a sucker of old nostalgic stuff. Just like that beautiful place in Japan (Kanokawa) which I visited in 1995. It always is such a pleasure to just run across some older versions and stories and visit the past (which held great promises of today, the future then).

This nice little explanation is one of those.

As for essence of imagination PC you expressed that there is the simultaneity. Other multiple boot technique never is not is quite the important function which cannot. When plural PC exist simultaneously, naturally as for exchanging the information of that PC that the problem which you say whether how it does happens. Because information interchange between each PC, it means that many of meaning of simultaneity are lost.

 If with VMware once it is the text data, it is possible to share between host OS, and each guest OS via the clipboard, but information interchange after all in earnest, probably there are no other things in network. Calling information interchange, because with special care plural PC can exist simultaneously, exceeding the dimension such as mere file sharing and data sharing, if you can verify network application and you can verify real client [sabashisutemu], how it probably is convenient.


While this might seem like "Hmmm..nice old times". I'm pretty sure many of you out there are running a lot older applications and OSs.( Heck, like I told you last, I found out myself of an old NT 4 sp5 servers running on a oldish PC in our production !, which was going to die quietly anytime). So get a free version of VMware and start testing today!

Read this nice article here (translated OR Japanese version)

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