Install Slackware 13.37 as a VM on Citrix XenServer
Citrix XenServer doesn't offer a template out of the box for Slackware. This article will show you how to install the current Slackware 13.37 on XenServer assuming you have access to the XenCenter software.
Now, I'll have to admit that I probably haven't used/installed Slackware since around 1998/1999 (version 3.6 era). I couldn't tell you why - probably because I was using what I was working with at the time which was Red Hat derivatives. I could tell you, however, that I've always respected and admired Slackware and their user base - and have been wanting to install it again for some time.
So - let's install it on Citrix XenServer as a VPS...
You should have an ISO library for your XenServer installation. At this point you want to upload the iso file to that location so you can see it from XenCenter.
In XenCenter, start the new VM installation as you would any other..
Choose New VM from the menu...
Template: Other install media
Choose a name for it - let's pick "Rob's Slackware 13.37 VM" (Ok, you can put your name there too.. "Rob and ___'s Slackware 13.37 VM").
Next, use the drop down to pick the mini-install.iso as your install media.
Pick a XenServer instance to place it on
Specify the number of vCPUs and amount of memory (I chose 1 vCPU and 1024MB memory for this test)
Add storage (I chose 25GB from our MD1000)
Choose network device (Just hit next, you'll be fine)
Look over the values and click Finish (make sure 'Start the new VM automatically' is checked).
Installing Slackware! Hit enter at the boot prompt
Choose a fancy keyboard if you like..
Log in as root (It won't prompt you for a password)
At this point, we're going to skip ahead and add a nameserver to make our lives easier in a little while. Edit (or create, actually) the /etc/resolv.conf file and enter in some name server:
(Google's public nameserver)
Type fdisk -l to list the available drives (we'll use /dev/sda)
now use fdisk to create your partitions:
You will want to create at LEAST 2 partitions - one for swap, one for your installation. Ideally, you will have this mapped out on a piece of paper or something before hand - separating out things like /tmp, /var, /home, or whatever.. for this case however we'll just throw everything under /.
Make sure to toggle your swap partition as type '82' (Linux Swap). Write your changes and jump back out to your root prompt.
This will show you a nice little menu. Go through the list setting everything up: Keyboard, Swap space, target partition, etc..
when you choose your 'SOURCE' media, choose 'Install from FTP/HTTP server'
Set up your network: Type in your ftp source url: (We'll use the Oregon State University Open Source Lab ftp server)
Type in the proper directory (64 bit here)
At this point, the installer will look for the PACKAGES.TXT file. If it finds it, you're on your way to choose packages.
We chose all packages in this example.
When that is done, it will offer to create a usb rescue image - we'll skip that.
Next, it will install LILO. Here you can specify some options like adding extra parameters to be passed to the kernel at boot time. We're taking the default.
Next, it asks if we want to change the default text consoles from UTF-8 to something else.. we choose 'No'.
Next, it will ask where we want LILO installed. We want it in the MBR (Master Boot Record) which is the default answer.
Mouse config is next - we're accepting the default which is Microsoft PS/2.
We're going to go ahead and tell it to start GPM on boot next..
Configuring the network: Enter hostname: slack Domain name: iqnection.net IP: Static - 192.168.0.24 netmask: 255.255.255.0 Gateway: 192.168.0.1 nameserver: 192.168.0.9
It will show you what you picked - you can accept, edit or cancel.
Startup services: We're taking the defaults here - but here is where you can tell it to not bother starting cups, bind, httpd, etc.. by default.
Custom screen fonts: no thank you
Hardware clock set to UTC? Nah, let's use local time
Set root password: Don't choose 'password' or 'god' here. Choose something that you can remember but not something someone could guess. Mix it with Upper/Lowercase letters, numbers and symbols if you can. For example, maybe use: SW1972#ln (Remember it with: Slack Ware 1972 pound li nux)
After this, you will be presented with the familiar install menu. At this point you can choose the last option (EXIT) and drop out to a prompt.
THIS IS NOT YOUR NEW INSTALLATION YET...
You want to restart the VM to boot into your new installation.
Sending a ctrl-alt-del w/ the button will do this for you.. or just send PID 1 a kill signal:
kill -2 1
As it is rebooting, make sure to eject your iso image otherwise you'll keep booting from it. Another option is to change the boot options of the VM to boot off the hard drive first, but it's good practice to keep things ejected from there anyway.
Working within your new installation If all went correctly, you'll see this screen waiting for you to choose an image to boot. If you let it sit there, 2 minutes will count down and it will boot the default.
Once it comes up, log in as root by using your new fancy password. Here, we check to see which version of slackware we're running..
Next, let's add a regular user - as we don't want to go around as root all the time.
This will walk you through setting up your first user. You can fill out as much or as little as you like. Hit enter when not sure. Do choose a tough password for this user however.
Once you've added your user, log out and log back in as your new user and go to town!
You can see "Rob's" xsession is alive and well here (start X with the startx command as your regular user).
The next step is looking into whether or not we want to install the XenServer Tools. This part isn't so cut and dry so it's going to be a follow-up article to this one ;)
If you have questions/comments about this article or about Slackware in general, be sure to join our Linux Forum! Our commenting system on here isn't ready yet (but will be soon!).
Also, We're always on freenode's IRC network in #LinuxForum.com
Currently, the main Slackware.com website is having its ups/downs (hardware issues on an older server), but you should check out Slackware.com if you have a chance! Also, read up on our Slackware Distro page.