Tuesday, October 23, 2007

The Planet is Fine

Here is a link that I ran across that has alot of "Inconvenient" Truths, sorry Al.


To paraphrase, here is George Carlin laying it out for you.

Thursday, October 11, 2007

Insecure by Default

Guess what, I can walk up to your Ubuntu, PCLinuxOS, Debian, etc desktop installation and take complete control over it without needing a single password. Thats right, root access simply by sitting down at your computer. Why is it nearly every single distro by default leaves this gaping security hole open? Seriously, it is possible to fix the problem during installation, my personal favorite, Sabayon, asks if you want to password GRUB as part of the installation.

What am I talking about? One simple word 'single', thats it. You walk up to nearly every default desktop installation, reboot it then break the boot cycle when GRUB fires up. If GRUB is not passworded, and the default for almost all installations is that it isn't, you now have the option to grant yourself root access.

On single or multi boot systems, select the installation you want and instead of hitting enter to boot, enter 'e' to edit. Select the boot line with all the kernel options, typically the second, and hit 'e' again. Scroll all the way to the end of the line and add the word 'single'. Hit enter and press 'b' for boot.

The system will now start booting up in what appears to be normal fashion. With one exception, instead of dropping you into the GUI it will drop you into CLI with root access automagically granted. From that point on the system is mine. I can change passwords, add users, add background processes such as ftp access or ssh access for myself. Maybe add a hidden user account not so hidden if you know what you are looking for in /etc/passwd, but you have to know to look at it. In other words, anything.

So I ask again, why with security being such an assumed when running Linux is this hole left open? It is possible to close this after the fact, and it is not difficult at all. Directions on how to accomplish this simple security measure can be found:

(that one includes securing LILO as well)

Also if you happen to screw it up and need to recover from locking your GRUB you'll need a LiveCD and the directions here, or a little common sense.


So now, what is your excuse for not securing your bootloader from me? How often do you actually have to go in and mess with it or even look at it? Isn't five minutes of your time worth knowing that no one is going to access your system when your back is turned?

Oh did I mention that Sabayon gives you the option to do this as part of the install routine? I did, but this is a good place for a shameless plug for my distro of choice.


Friday, September 28, 2007

9/29 what a week

Been a really interesting week for me. So a quick recap:

1: I wont be doing any more opinion pieces on this blog. I have been offered and after a little discussion and thought, accepted a place to put my opinions. My next opinion piece which I am working on right now will be appearing at thenixedreport.com. I would like to thank the editor of that site for offering this position, especially considering the rocky start we got off to when I publicly called him on the carpet for one of the pieces he wrote.

It takes a great person to be able to take a person who has called you out and then turn around with no rancor at all and offer to give them a place to vent their views points. I am really looking forward to working with him and am grateful for the opportunity he has offered me. I may not be a journalist, but boy howdy do I have some opinions.

2: My old reliable laptop has finally started to give up the ghost. A Compaq Presario R3000, a AMD 3000+ (1600 Mhz) with 512 on board, 40 gig HD and a 32 meg video card. It has been my traveling companion for these last few years and has logged around 40,000 miles with me. The cooling fan died and I didn't notice. It is rather silent to start with and it was sitting next to my desktop which is anything but quiet.

Since I run Sabayon I tend to have to compile software that I use. This jams the CPU to 100% load and leaves it there, sometimes for a long stretch. It did in this case at a time when I started the job and walked away. Too late I checked on it's progress and noticed that the case was insanely hot. While I did manage to get it turned off in time, there was some noticeable damage done. If I lock the CPU down to around 800 Mhz it will function fine as long as I dont stress it too much, but it's days as a work horse are over.

Which brings me to my happy news. I had to get a new laptop. A sparkly HP dv6000t, which has for the first time since my P166 so many years ago, an Intel processor, dual core even. Hi Def wide screen, 2 Ghz, 2 Gig onboard, DVD R/W, and a 256 meg nVidia video card. All for less than $850.00 including shipping via 2nd day air. Too bad I am in bush Alaska and 2nd day air actually means sometime next week, with luck. So it is a race now, to see if the new laptop gets to me before I leave the state for 5 weeks. If not my wife has agreed to ship it to me in Kansas City, but being offline for more than a few days is pure hell for me. Just have to play it by ear I guess.

Did I mention that the thing is being shipped with Vista on it? So for the first time ever I get to try my hand at getting the Windows Tax Refund. That should be interesting and different, however I have my Sabayon install disc all set and ready for it the day I get it. More on that experiance later. Until then ...

Have Fun

Thursday, September 20, 2007

Have been AFK

I have been AFK for awhile. Not because of the responses received from my previous article, just that real life managed to catch up with me. Lots of work and travel to remote villages in Alaska, and when I was home I was spending as much time as I could with my family.

I have in mind several pieces to write. Many of them would probably be considered inflammatory by some, this as evidenced previously doesn't phase me a whole lot. So perhaps over the next few weeks I'll get around to writing them, at this point though even all the notes I have for them are locked away in the mostly unused space between my ears.

Whats else has been going on? Removed PCLOS from both of my laptops, one got Ubuntu just for ease and simplicity in maintenance. The other got Sabayon, and is anxiously awaiting the Sabayon 3.4 mini which as of this writting is still being worked on.

I will be in Kansas City Missouri for 5 weeks starting Oct 10th for a radar equipment school, then home for a week before taking off to Oklahoma City for two weeks for training on a different system, home for christmas, then back to OKC for yet another systems class. I'm really going to rack up the air miles over the next few months going back and forth from Alaska.

On a side note, I had to put up a copyright notice for the site. After I wrote my last article I found it in all kinds of places, and in a few of them mangled fairly well. It was an opinion piece and you will notice the "I" in the title. It was and is my opinion, it does not necessarily mean that I think you should share it. Discuss it to death for all I care, agree, disagree, flame me all you want, but pulling it apart and using pieces out of context is disingenious at best and outright lying at its worst. So thanks to a few who have few if any morals, I feel forced to put certain restrictions upon any opinion pieces that I right.

Have fun

Sunday, August 19, 2007

Why I refuse to call it GNU/Linux

When listening to others talk about GNU/Linux it always strikes me as odd the argument that is used. That the Linux kernel was made usable by the marriage of the GNU tool set to it so therefor it should be called GNU/Linux as it is a blending of the two and Linux is only the kernel. On the face of it this argument makes sense ... if one doesn't think about it too deeply.

There are however a few things I would like to point out. The GNU tools are released under the GPL, which does not carry a branding clause. This means in effect I can take those tools, do nothing at all to them, and rename them. Henceforth I can call them the 'Azerthoth Tool set and Compiling modules' and there is not a thing that can be done about it legally. Making that change stick in the eyes of the public, odds probably arent that good. As long as I don't change the license though, all I really have to worry about are the purists and Stallmanites flaming me into oblivion.

The next reason, and in my mind the compelling reason I refuse the GNU/Linux name, my car. Did that stop you for a second making you ask yourself where THAT connection came from? Let me explain then. Lets take my Mercury Cougar for example. Thats easy, Mercury makes a car that I bought, and the model name for that car is Cougar. I have never, and neither have you called it a John/Cougar, even though John might be the name of the guy who designed it. How about a Delco/Cougar because I have a Delco alternator in it that supplies power for the electrical system. A Chevron/Cougar because of the gas I use to give it motive force? Do you see what I am getting at? All of these things are part of a complex and integrated system, however they are NEVER named specifically. The same holds true with nearly every item you have ever acquired.

But, but, but, the GPL is what makes Linux ... well ... Linux, shouldn't we acknowledge that? Um, NO, we should not have to, nor should we be forced to tolerate those who would make us think so. If contribution to the underlying abilities of Linux made that sort of branding logical then should we not also be correct in calling it Morton/Linux or Tridgell/Linux perhaps Ingo/Linux or Stallman/Linux. It is all about a whole bunch of complex pieces coming together in one place at one time to make something that just works. All the pieces are needed to make it happen, and picking out just one single piece to give additional credit to in the complex amalgam that is otherwise known as Linux is just plain silly. Kind of like Frankenstein's monster, a bit from here and a bit from there and a bit from somewhere else. Stuff it into a case, apply electricity, and viola.

I have said my piece on the matter, coherently I hope. All that remains now is to bid you all ado for the moment and await the flaming that I am sure is coming. I did knowingly and willingly step on Saint Stallman, and in the community that surrounds Linux, that is one of the “Shall Not's”. Let's hope that my new asbestos undies are up to the challenge.

have fun till next time.

Monday, August 13, 2007

Sabayon x86_64

Did I say that I had started a new love affair with Sabayon? Let me tell you what I went on an install binge this weekend, Bluewhite64, Slackware 12, and Sabayon x86_64. I was terminally unimpressed with either of the first two, although I'm going to give Bluewhite64 which is a Slack derivative a little more time and play before I pass final judgment on it. Sabayon 64 bit ... All I can say is WOW!!!.

Finally a 64 bit OS that works like I want it to. No tinkering with this that or the other to get some 32 bit app working correctly (Flash). I want to run Warcraft, which has a permanent home on its own partition ... well that did take a tinker just as it did with the 32 bit version. For some reason it didn't ship with opengl compiled in, so you have to re-emerge it with opengl support. Other than that though whammo Warcrack was up and running inside a few minutes.

Here is what I do to any new Linux install within minutes of having it running for the first time.
Visit youtube and see if everything works out of the box (it does for Sabayon 32 and 64 bit)
Drop in a movie and see if I can watch it. (yes again for both versions)
Warcraft (no for both, but it was a really fast fix, and got me the latest wine release to boot)
3D desktop (yes for both 32 and 64 bit) Not that I use it Compiz and Beryl have issues about locking up pretty much any system I have tried them on with I ctrl|alt|F1 to terminal and then try to go back to the desktop. But I like having it available, and I know how to shut them down.

Almost every distro I have ever tried has failed in these tests, which I consider my daily uses. I haven't tried Linux Mint lately, which is from what I hear should pass these simple tests however I have an aversion to most things Ubuntu. I know that Ian Murdock has said Ubuntu is Debian done right, but if I wanted a 6 month old snapshot of Debian Sid I can do that and without the bugs that the Ubuntu folks induce. Dont flame me for the truth here folks, Ubuntu has done wonderful things for Linux, its just that it is a far cry from the end all be all it could be if they would just pay a little more attention to what they were doing, and what their users should EXPECT to see out of the box.

All in all I just made another switch, from 32 bit Sabayon to 64 bit Sabayon. I just get happier and happier the more I use this Distribution. It says alot for them and for the Gentoo community and developers that desktop Linux can be this easy.

Sunday, August 5, 2007

Sabayon 3.4a x86

Just a quick update. I had initially installed Sabayon on my desktop using the 3.3 mini LiveCD. While I was away in Oklahoma for training I downloaded the 3.4a DVD in both x86 and x86_64 as well as a few others that looked interesting such as Bluewhite64. So far the only one I have had time to play with is the 32 bit version of Sabayon.

First up I tried the upgrade (not 6th sense) and that took way too long. I did let it finish and do everything it wanted to, however it did not fix some of the problems I had induced into my system, such as not being able to start the 3D desktop environment any longer. I waited something like 6 hours to find that the update pretty much spent 6 hours giving me a new kernel and left me with a partially broken system. Not that I couldnt fix it if I had wanted to, I knew where the error was I just dont need the compiz fusion beryl stuff active except for showing people that Linux outshines any other OS for eye candy.

Next I went ahead and did a fresh install using the same DVD. Folks if you are smart enough to back up the stuff you want to keep onto a seperate partition, this is the way to go. In less than an hour I had a sparkly new install vs 6+ hours for a partially broken upgrade. This is by far the fastest and easiest way to use the DVD to update your system. Of course you can still use emerge to upgrade as you go along if you choose and now that I have learned more how Sabayon/Gentoo works, thats probably the path I will continue to use. Not that I have figured out all the gotcha's yet, but I'm learning *grin*.

Anyway, Sabayon 3.4 is a very polished and functional system. If you have moved beyond the newbie distro's (and honestly Sabayon is almost capable of being a newbie distro ... almost) and are looking for something to start ecking out the most horsepower out of your system, Sabayon is a great place to start. Especially since so many things are already included and configured for you, more than in the various *buntu's or PCLinuxOS. Not to knock PCLOS, I still use that on my laptop and keep a few CD's handy to pass out to folks who are just starting out, its just that Sabayon is so much more, if not exactly as newbie friendly as PCLOS.

Good job on the latest release, I look forward to a long and fruitful affair with this great project.

Tuesday, July 24, 2007

Debian Etch: Custom Install

The following is a how-to that was on my original blog and also posted at www.debian-administration.org. It is the first I ever did, and as such has a few rough edges.

As a not completely new Linux user I have been frustrated over and over again at all the extra bloat and apps that I will never use that gets loaded onto my system when I do an install. Debian was the second distro that I tried and have used many others since, but I keep coming back.
With Etch I finally decided to get my system MY WAY(tm). No excess junk and no excess apps. After I had played for a little while I came up with the way to do it, and since I had found very little in the way of easily human understandable documentation I thought I would share the process.

Now understand that what we are going to do is start from where I changed the installation.

1: netinst CD and an internet connection.

2: start the normal install process and proceed all the way to where it asks if you want to use a network mirror.

3: select NO for network mirror (we will change this in a minute)

4: reboot and log in root

5: edit the sources.list

nano /etc/apt/sources.list

add these lines

deb http://ftp.debian.org/debian etch main contrib non-free
deb-src http://ftp.debian.org/debian etch main contrib non-free

Then make sure to comment out the line with the CD in it with a # otherwise it will drive you nuts asking for that blasted CD that has nothing of anymore use on it.

Close and save the file (double check your spelling and make sure you didnt fat finger any keys like I constantly do)

6: type in the command

apt-get update

7: type in

apt-get install xserver-xorg-core xorg

There will be a few questions at the end, for now just go with the defaults.

8: while apt is doing its thing we need to make a decision.
Which login manager do you want to use? Unless you want to run as root all the time ( #1 bad idea by the way) we need a login manager. Here are the 3 I have used and comments on them.


smallest and works well to get you going on your way. Highly configurable.


easily configurable and adds libraries you need if you want to use the synaptic package manager. (also contains alot of the extra functions of xdm)


largest and bloated, I list it only because I know a few people who like it. (my opinion)

It honestly makes no differance to us which you pick. For ease of configuration I'd suggest gdm, if your just setting up a single user machine and will never change your desktop interface xdm might be the way to go. Your choice (thats what Linux is about right?)It doesnt matter which desktop environment you are going to use, any of them will fire up what ever you happen to have

So we

apt-get install xdm/gdm/kdm

9: Next decision, what desktop package to put in?


If you want Gnome you have just wasted time reading this, thats what you would have gotten if you had continued on with the installation normally.


very much like the operating system that comes from redmond, and nearly as bloated with worthless junk. I have this installed only because my wife likes it.


This is the one I use. Very small, fast, and configurable. Its a low frills let our programs use system resources instead of having the desktop environment hog it approach. Nor will this one load your system up with oddbits like Gnome or KDE, however both are integrated with it. So if you install your favorite Gnome app or KDE app it automagicly appears in your menu in fluxbox.

There are others you can use as well, if you have one you like instead, use it.

So we

apt-get install fluxbox/gnome/kde

9A: If you went with fluxbox because like me you wanted to control what apps are on your system instead of letting someone else decide what is right for you. Remember this, fluxbox doesnt ship with proggies AT ALL. so at the very least you will want to add a web browser.

apt-get install firefox

(my choice, again use what you like)

10: reboot and poof you should be up and running.

For those who are wondering this worked equally well on my desktop as it did my laptop. I hope this helps someone else who like me is still learning all the wonderful things that can be done with Linux, but needs a few pointers because face it, we arent all programmers and everyone has to start the process of understanding somewhere.

Since originally writing this how-to I have changed my minimal install technique, however since at this point I have stopped using Debian or Debian derived distros completely I doubt that a new how-to will be forthcoming any time soon.

Saturday, July 14, 2007

Off Topic: New Gun

OK, so this isn't about Linux, but this is too cool for words. I finally bought the gun I have wanted since I first heard of it. After first reading about this gun I went and found one to see how it felt and was surprised in that for a small cannon it felt like it was made for my hand. It fit perfectly. I'm talking about nothing other than the Smith and Wesson 500, a .50 caliber magnum handgun which has roughly three times the stopping power of a .44 magnum. Here are 2 pictures of this monster with a quarter in the picture for scale.

Sunday, July 8, 2007

Breaking Sabayon

OK, the learning curve is not as steep as I thought it would be, or its my ignorance talking. However I did a "world" update of the install I did from the 3.3 mini LiveCD and then immediately ran into a problem. This update basically brought everything in the system up to "testing" which I guess is a lot more testing than stable then I'm used to coming from Debian.

I wanted to back a few files off to DVD for later use. Namely all the files and updates to install World of Warcraft and Burning Crusade. This was so I could save myself some time later on if I had to reinstall, which I did and am doing as I write this. To do this backup though I fired up k3b, which I nearly always use and the system immediately hard locked and boy do I mean hard.

This is when I discovered that the system had been upgraded to the testing level. OK, can I downgrade my packages? Sure can, you can mix and match so easily its no even funny. you find out the package you want:
emerge -s *package name*

That will spit out available packages plus the one you have installed. The stable one is listed, usually the one thats available with a lower version number. To install that one instead all you have to do is:
emerge =*package name-version number*

Whammo your all fixed up.

OK I may be getting excited over nothing, but fixing and downgrading is something new and different for me. Who said Sabayon/Gentoo were for uber geeks? oh, wait I have, repeatedly. Its so much easier to reconfigure and/or fix screw ups its not even funny.

Anyway, More on the adventures of moving to Sabayon later.

till the have fun

Tuesday, July 3, 2007

Making the switch to Sabayon

For those readers who had read my old blog, or from elsewhere on the net you know that I am a huge fan of Debian. However I have become more and more disenchanted with it as time goes on. It started when I was doing a laptop installation and finished with a recent battle with my desktop.

Laptop issue:
Cpu frequency scaling (also an issue with my desktop). Its not enabled by default even if I selected laptop during the install. Come on guys every other distro out there enables scaling by default, and even when its not fully supported it defaults to the highest cpu speed not the lowest. Hell, even the Ubuntoids got that part right.

Desktop issues:
1: AM2 64x2 4600+ with either a abit AN9 32X or a Gigabyte M61P-S3 motherboard. CPU scaling AGAIN!!! With either board. Trying to get scaling to work on multiple installs fell on its face. Why you ask? It needs sysfs loaded, guess what didnt get loaded because my processor was misdetected on every install with either mobo and the wrong damn kernel got installed ... even using expert install.

2: CPU detection and kernel installation. Even though supposedly Debian now releases all the kernels with SMP support every time I install I get no SMP, I have to go and pick the kernel I want out of synaptic. Up to and including the testing (Lenny) net install as of 2 days ago.

These are things that arent just an annoyance for a desktop user, its a show stopper for anyone even thinking of deploying a server. If you cant get what every other distro in the world can get then your useless, wait let me say that again, useless, worthless, self absorbed, prissy prima donas. Debian used to have the reputation of being the best, you dont keep a reputation like that guys, you work at keeping it, and right now your loosing it.

PCLinuxOS, I love you guys even if you have a jerk or two doing forum moderation. Dig through my posts at LXer for that story. This is the distro that I have on my laptop, I installed on my 58 year old mothers laptop, and that I keep a couple of LiveCD's kicking around to hand out to people. Good job and well done. However there are things that I want to do that I cant with it. The documentation is SOOO wonderful that it took me 2 days to manage to get wine to compile from source correctly.

Back to the desktop, I ruled out Debian as the distro to go into it. So I went with Ubuntu 7.04, 6.10 worked well for me when I used it so what the heck I'll spin up the new one. That lasted less than 2 days, I cant even begin to describe just how clunky it felt. The speed wasnt there, the configuration options are worse not better. It just felt and acted wrong and after several lockups where I couldnt even 'ctrl alt f1' to get to a terminal to find and kill the offending culprit I decided it was as stable as a fart in high winds.

Enter Sabayon, a Gentoo derivative. Gentoo is NOT newbie friendly, I have tried it a couple of times and wandered off muttering "I'm not that big a geek". However when I first heard of Sabayon I went out and snagged the LiveCD and was suitably impressed. I liked its look and feel, as well as the overall approach to things. First off it loaded the nVidia drivers from the CD and also brought my wireless networking up (bcm4306) so all I had to do was enter the hex code I use for my router. Thats 2 really big pluses for it right there.

That test was a few months ago, so I decided to give their 3.3 livecd a look. On top of both the other pluses it came right up with KDE and Beryl working flawlessly (except I usually use fluxbox, so neither KDE or Beryl mean much to me. Except I hadnt seen Beryl work right out of the box before). I poked and prodded a bit (checked for cpu scaling) the decided to take the plunge. I knew just enough about source based distro's to know that I just entered into another steep learning curve. However 2 days later and the curve isnt as steep as I thought it would be. No real gotcha's so far ... well one, the user accounts I created during the live CD install never created the home folders so I had a little fixing to do once I figured out what happened.

All I can say is that 2 days in and Sabayon is fast, has taken my every little tweak without so much a cough, and blows the doors off of any other distro I have used before. I hope that it continues to do so, I'll get back later on that though. For the time being PCLOS is still staying on my laptop and will continue to be my newbie recomendation of choice.


Sunday, July 1, 2007

QEMU/KVM,and a trick

Ever wanted to play with a new distro without having to burn and then reboot into a liveCD or do an install into a spare partition that you may or may not have? QEMU has been an option for awhile, but lets face it, its slow. There are several options available to run up a virtual machine, i.e. a second operating system running inside and seperate from your already running operating system. Here we will be focusing on kqemu and kvm.

If your kernel is already 2.6.20 or higher you can run kvm, if its under then you will be using kqemu.

kvm is in sid/unstable so you will have to add that to your apt sources.
go root
nano /etc/apt/sources.list

deb http://ftp.debian.org/debian unstable

apt-get update
aptitude install kvm

After kvm and associated packages are installed it would be best to edit your sources.list again and comment out the line where you added in unstable with a # at the beginning of the line.

kqemu, which is technically a qemu accelerator instead of kernel level virtualization like kvm is available in Debian stable and there for as easy to install as:

aptitude install kqemu

You should have noticed if it wasn't already installed that qemu was installed regardless of whether you went with kvm or kqemu. Thats because both packages use qemu. So no worries, we need the qemu tools anyway.

OK so now we need to set a few things up.

If you installed kqemu then we need to load that module when we boot. I use nano, you can use what ever other editor you want.

Go root, then

nano /etc/modules

and add at the bottom of whatever list might be there


For kvm you need to know something beforehand, whether you have an Intel or an AMD processor. It makes a difference in the module we are going to load on boot.

Go root, then

nano /etc/modules

If you have an Intel processor you will add at the end of the list


If you have an AMD processor you will add at the end of the list


Now that we have the modules ready to load, we need to make them accessible to you as a user.

adduser $USER kvm
adduser $USER kqemu

depending on which you installed.

Congratulations, right now you should have everything just about ready to go. The problem is, even if you modprobe the modules active right now they still wont be usable to you, they need to be loaded against the kernel when you boot, so bookmark this page and reboot your computer, I'll wait here while you do.

OK so now we need to create a virtual drive to install our test distro to. I'll explain the parts of it after. From here on out everything is applicable to QEMU, Kqemu, and KVM. It is done as a normal user, so no more need to be root.

qemu-img create debian.img -f qcow 5G

The first bit is self explanatory, create an image (virtual drive) named debian.img. The next bit -f qcow tells it to format it in an inflatable structure. The 5G means a maximum physical size of 5 gig real hard drive space. The nice thing about this format is, if your VM installed only takes up 2.5 gig, then the virtual drive only takes up 2.5 gig of space on your real hard drive.

I guess the next thing that you'll be wanting to do is actually spin this up and try it out. I should note that I have had problems on occasion with KVM locking up during the install process, if this should happen to you drop back and use qemu with the same command line arguments. If you are using kqemu instead of kvm use qemu in the command line instead of kvm, kqemu is a module called by qemu when it starts. I'll be using kvm for the command line, you use what works for you.

I'm not ready yet to tell you how to start. A few things first if you don't mind. I usually make a seperate directory for my VM's because there are usually one or two files other than just the .img file. Such as an overlay file or two, which I will cover shortly and a script that simplifies launching the VM after its made. There are tons of command line arguments that can be added to the basic ones I am using here to get you started, the script is a huge time saver.

There are two basic ways to start this off, either with an .iso image or a CD/DVD. Lets start with an .iso image, the debian net-inst image in this case. We will assume for the sake of argument that the .iso is in the same folder as the virtual drive that you created is, and that it is also our working directory.

kvm -cdrom net-inst.iso -hda debian.img -m 512 -boot d

First this calls kvm and tells it that the .iso image is actually a cd drive, then the -hda debian.img is its hard drive. The -m 512 tells it that its a computer with 512 meg of memory. Careful here because this is the amount of physical memory that its going to block out for itself. Rule of thumb is no more than ½ of your actual physical memory. The final bit is -boot d, it tells it to boot from the cdrom drive.

kvm -cdrom /dev/cdrom -hda debian.img -m 512 -boot d

The only difference here is that your pointing it to your real cd drive here. If /dev/cdrom doesn't work for you then you can cat /etc/fstab and look there to see what you cdrom drive really is.

Now I mentioned that you might have problems doing an install using kvm, if this happens you have to explicitly tell qemu to not use the kvm module in the command line like this:

qemu -no-kvm -cdrom /dev/cdrom -hda debian.img -m 512 -boot d

Lets move on with the thought that you have installed your new virtual operating system. Your going to want to get in and play with it. The command for this is simply:

kvm -hda debian.img -m 512

With that you will be up and running in your new OS running inside your existing. However there is another trick that is really handy that will let you do whatever you want without permanently breaking this new creation, overlay files. Which basically takes a snapshot of your virtual drive and then run it from the overlay instead of the virtual drive. Really handy if you want to have several versions accessible but only have to do the install process once. Say like having a version of stable a version of testing and a version of unstable all available from the same install. To do this its as simple as:

qemu-img create -b debian.img -f qcow stable.ovl

To boot into this you just change the command line a little bit and tell it to use the overlay file you just made.

kvm -hda stable.ovl -m 512

As you can see the easy way to run multiple versions off the same install would be to do a base install of stable and then make your overlay file for it. Next you would make an overlay file named something like testing.ovl and another for unstable.ovl all from the debian.img that we made to start.

Then simply fire each up in turn via the overlay files, edit your /etc/sources.list to what ever you want and update yourself into debian nirvana.

My thanks to Scott Ruecker over at lxer.com for asking the question that started the process for this how-to. As I said though there are tons of switches that will add functionality to your virtual machine. More than I can adequately explain as I haven't managed to figure them all out yet either. This how to was written with the whole intent to get someone armed and dangerous before kicking them out the door and isn't intended to be all inclusive.

For more information on this topic you can start at qemu's authors site at:

Have fun.

Starting Out

OK, I just deleted my last blog, all posts and comments are mostly gone. There does exist a bit here and there that found itself posted on other sites on the net. I will move those back here as soon as feasible. For the most part though all this blog will be about will be my adventures in the lands of Linux.