<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debian on the bin</title><link>https://thebin.net/tags/debian/</link><description>Recent content in Debian on the bin</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 02 Mar 2011 00:00:00 +0000</lastBuildDate><atom:link href="https://thebin.net/tags/debian/index.xml" rel="self" type="application/rss+xml"/><item><title>KVM Guests: Using Virt-Install to Install Debian and Ubuntu Guests</title><link>https://thebin.net/2011/03/kvm-guests-using-virt-install-to-install-debian-and-ubuntu-guests/</link><pubDate>Wed, 02 Mar 2011 00:00:00 +0000</pubDate><guid>https://thebin.net/2011/03/kvm-guests-using-virt-install-to-install-debian-and-ubuntu-guests/</guid><description>&lt;p&gt;I like to be able to spin up a VM without looking for CD media so for a while now I have been using ISO images for all of my installs directly, however I found my self scurrying around “digitally” looking for the correct iso in much the same way I used to scurry about looking for physical CDs, except I was not physically moving.  So anyways the time was wasted either way, I figured it is time that I find a better (read: lazier) way to do this.  So the idea is that since the apt package manager contains all the packages and files needed to install and upgrade a system, we ought to be able to find a way to initiate the install over the wire.&lt;/p&gt;</description></item><item><title>Using Views with BIND 9</title><link>https://thebin.net/2011/02/using-views-with-bind-9/</link><pubDate>Thu, 24 Feb 2011 00:00:00 +0000</pubDate><guid>https://thebin.net/2011/02/using-views-with-bind-9/</guid><description>&lt;p&gt;In almost all organizations the network infrastructure needs to be designed in such a way as to allow both internal and external name resolution authoritatively.  In most organizations this has been accomplished by having separate internal and external servers.  Clearly this way is functional and simpler, however it is also wasteful considering how little resources DNS actually requires.  BIND 9 gives us a new method to manage these types of configurations.  The idea is that you can create a view which will reference specific zones based on the network location that you are coming from.&lt;/p&gt;</description></item><item><title>Hyper-V Guests: Compile Linux Kernel 2.6.32 on Debian</title><link>https://thebin.net/2009/12/hyper-v-guests-compile-linux-kernel-2-6-32-on-debian/</link><pubDate>Sat, 19 Dec 2009 00:00:00 +0000</pubDate><guid>https://thebin.net/2009/12/hyper-v-guests-compile-linux-kernel-2-6-32-on-debian/</guid><description>&lt;p&gt;In this post I will be detailing the steps needed to compile a new kernel in Debian Linux 5.  This particular case we are purpose building a kernel with the drivers necessary for Hyper-V Guests to take advantage of synthetic devices.  Additionally I plan on expanding this series with instructions for manual compiles of other distributions as well as some pre-compiled image based installs.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;DISCLAIMER:&lt;/strong&gt; These instructions are not provided with any guarantee of support.  Microsoft (company behind Hyper-V) does not acknowledge Debian as a supported guest operating system.&lt;/p&gt;</description></item><item><title>Hyper-V Guests: Linux Integration Components Ubuntu and Debian</title><link>https://thebin.net/2009/05/hyper-v-guests-linux-integration-components-ubuntu-and-debian/</link><pubDate>Tue, 12 May 2009 00:00:00 +0000</pubDate><guid>https://thebin.net/2009/05/hyper-v-guests-linux-integration-components-ubuntu-and-debian/</guid><description>&lt;p&gt;In this article I am documenting the process for installing the Hyper-V Integration Components within a Ubuntu or Debian VM. I am specifically writing this for Ubuntu 8.04.2 and Debian 5, however I have additionally confirmed that this process works on both Ubuntu 8.10 and Ubuntu 9.04. My environment consists of x64 VMs, I have not taken the time to test this process for x86 VMs, however it should hold true, as long as you update the package names to reflect the appropriate architecture.&lt;/p&gt;</description></item></channel></rss>