Translate

Archives

Install VirtualBox Guest Additions in Debian Wheezy (7.0 and 7.1)

Either of the following two methods will install and configure the VirtualBox Guest Additions on Debian Wheezy (7.0 or 7.1) – assuming you have clicked on “Install Guest Additions” option on the VM Menu. # apt-get update # apt-get install build-essential module-assistant # m-a prepare # mount /media/cdrom # bash /media/cdrom/VBoxLinuxAdditions.run or # apt-get update # apt-get install gcc make # apt-get install linux-headers-$(uname -r) # mount /media/cdrom # bash /media/cdrom/VBoxLinuxAdditions.run Contrary to what some people have experienced, I had no trouble invoking the GNOME 3 Shell in Debian 7.0 or 7.1 when running in VirtualBox 4.2.16 under Microsoft Windows

Multiarch

Multiarch is a general solution for installing libraries of more than one architecture on a system. It was first proposed in 2004. It solves the problem which was created when Linux distributions standardized on the /lib and /lib64 directories for libaries. The core concept is to put libraries for each architecture into architecture-specif ic paths. For example, /usr/lib/libfoo (amd64) —> /usr/lib/x86_64-linux-gnu/libfoo /usr/lib/libfoo (armel) —> /usr/lib/arm-linux-gnueabi/libfoo /usr/lib/libfoo (i386) —> /usr/lib/i386-linux-gnu/libfoo GNU triplets are used for architecture paths, with some adjustment for historical cruft. While I do not particularly like the proposed names for the architecture specific directories, the general idea has

Building VirtualBox Guest Additions on Debian 5

Here is what you need to do to successfully build and install the Oracle VirtualBox Guest Additions on Debian 5. First mount the VirualBox guest additions (Extensions Pack) media (Host-D). Then either mount your Debian 5 installation media or configure your Debian 5 package manager to download the necessary packages from a suitable repository. # apt-get update # apt-get install gcc make # apt-get install linux-headers-$(uname -r) # cd /media/cdrom # bash VBoxLinuxAdditions.run Then reboot your appliance and check that you can auto-resize the guest display. If not, check the build logs which are available under /var/log.