Skip to main content

Minimal Debian Lenny install on VirtualBox

Pre-requisite:
- internet connection
- Virtual Box installed on host machine. This exercise will be using Vista as host.

As of this writing, Debian Lenny is still at testing stage. For this exercise we will use RC1, visit http://www.debian.org/releases/testing/ for the netinstall iso. Once download is done, create a new virtual machine using Virtual Box, use the following configuration: 512 MB Memory, 120 GB HD, use Intel PRO/1000T server for the network card. For the VirtualBox networking I am using host network configuration. Once VirtualBox guest configuration is set, start the guest machine and then mount the CD-ROM image. In installer boot menu, select Graphical Install. For "Chose the Language" screen, select English or your language of choice. For the country, select whichever you are currently in. In my case, I will be using Philippines. In "Keymap to use" select "American English" or whichever is much appropriate for your system. After this screen, the system should now start detecting your hardware and configures the system for installation. Few seconds later, it should present you with "Configure your network" screen, in my case I am gonna be using "deb5." Since I am using Vista and Internet Connection Sharing, I have mshome.net as the default domain. Accept this default. This should not matter that much if you are using your system inside a guest machine. In "Partition disks", use Guided - use entire disk. You may use other option if you are confident with playing around with disk partitioning in Linux. Select first HD in your Virtual Box, then select "All files in one partition (recommended for new users)." Then accept the changes to write the partition layout to your HD. Wait while the installation sequence is partitioning your hard drive and installs the base system. In Philippines, one of the nearest mirror sites is Hongkong. We have two mirrors from Hongkong and I will be using ftp.hk.debian.org. In the Http proxy window, you can leave this blank if you are not using HTTP proxy to access outside world. Thus say, if you are using DSL, Cable, WIFI or Wireless connection like HSDPA or the like, leave it blank. After this, the system will pull up installation software from our mirror site. This may take a while depending on the connection speed. Since this is only the few cases where I can help the Debian community, I opted to join the "package survey." I too encourage everyone to participate this survey. Since we want this to be a minimal system, deselect all packaged options. This leaves us with the bare minimum to run our Debian Lenny Linux system. Since this is running of VirtualBox guest, we are sure enough that it is safe to put GRUB boot loader in master boot record. So go ahead, and say Yes. In few moments, installation should complete. Congratulations, you have just installed a minimal Debian Lenny Linux in VirtualBox!!!

Let us now install a minimal GNOME in top of our minimal system. Before we do the installation of desktop environment, it is a good practice to do the ff:
hostname:/# aptitude update hostname:/# aptitude safe-upgrade
But since we have just used netinstall installation, our system should be up to date. Now, let us get our system configured with X, do:
hostname:/# aptitude install less hostname:/# aptitude install xorg gnome-core gdm gdm-themes
The above command install xorg, GNOME and gdm (GNOME Display Manager) and associated gdm themes. Wait and relax as this may pull archives of around 250 MB. After the installation, do a reboot to login to GNOME Display Manager. You will notice here that your graphical login screen maybe bigger than your monitor. This can be fixed by installing virtual additions but we can also work around this one by modifying /etc/X11/xorg.conf as root, like so:
Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" SubSection "Display" Modes "1024x680" "800x600" EndSubSection EndSection
Let us now install VirtualBox guest additions:
hostname:/# su hostname:/# aptitude install build-essential hostname:/# aptitude install linux-headers-`uname -r` hostname:/# mount /media/cdrom hostname:/# sh VBoxLinuxAdditions-x86.run
After reboot, you should now have a nicely integrated Debian Lenny with VirtualBox. Now, to make guest machine auto-adjust with the size of main VirtualBox window, update /etc/X11/xorg.conf with:
Section "Device" Identifier "Configured Video Device" Driver "vboxvideo" EndSection
Enjoy!

~ts

Comments

Anonymous said…
Thanks, this just saved me a headache. :)

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.