Skip to main content

Virtuaization with QEMU

A nice walk through with some print screens.

Why should you virtualize at all? There are several good reasons for that, I’ll list a few here:

  • My wife and me do web design. No, not for a living, just for fun. And tho we nowadays keep most of our stuff in out-of-the-box blog systems like Wordpress, we still like to tweak around with our themes and templates and all that stuff, and of course we have to test them with different browsers from time to time. So this time, I wanted to see our stuff with Internet Explorer on Windows again, and compare the views to those of Iceweasel, Epiphany, or Konqueror.
  • All of our computers here run Debian these days, and that means: Debian ’stable’, also known as ‘Etch’. But hey, just like my close-to-perfect Honda motorbike, a perfect, well-functioning Linux distribution like Etch gets boring after a while, and I’m the guy who writes ‘thedebianuser.org’, so I want to keep track of newer versions of Debian like ‘testing’ (at the time of this writing also known as ‘Lenny’), or even ‘unstable’ (also known as ‘Sid’). If you run these in virtual machines, you can explore tomorrow’s software today, without the risk of doing something chaotic to your stable setup, which simply keeps running, well, stable.
  • Maybe you are a so-called ‘distro-hopper’, or just want to see the latest and greatest Ubuntu/Fedora/you-name-it-here? Save yourself the hassle of swapping or wiping hard disks, and do it all in virtual machines. If you don’t make them too big, you can save them onto a DVD, or even a USB memory stick, and carry them with you to show them to your friends.


This is consumerism.

Read the rest.
Labels:

Comments

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
Post a Comment
Read more

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
Post a Comment
Read more