<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ali Aboosaidi &#187; Debian</title>
	<atom:link href="http://insanelabs.com/category/debian/feed/" rel="self" type="application/rss+xml" />
	<link>http://insanelabs.com</link>
	<description>Umm... Unorthodox?</description>
	<lastBuildDate>Mon, 19 Jul 2010 19:02:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Debian: dmesg output contains &#8220;Error: Driver &#8216;pcspkr&#8217; is already registered, aborting&#8230;”</title>
		<link>http://insanelabs.com/debian/debian-dmesg-output-contains-error-driver-pcspkr-is-already-registered-aborting-%e2%80%9d/</link>
		<comments>http://insanelabs.com/debian/debian-dmesg-output-contains-error-driver-pcspkr-is-already-registered-aborting-%e2%80%9d/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 05:07:47 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[pcspkr]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=700</guid>
		<description><![CDATA[Here is what&#8217;s transpiring: the boot sequence attempts to load two different drivers for the integrated PC speaker. To solve the problem install alsa-base package: aptitude install alsa-base And then execute the following command: echo blacklist snd-pcsp &#62;&#62; /etc/modprobe.d/alsa-base-blacklist Related posts:Debian: NIC bonding (teaming) 32/64 bit OS Debian: Setup is unable to find the &#8220;killall&#8221; [...]


Related posts:<ol><li><a href="http://insanelabs.com/debian/linux-nic-bonding-teaming-debian-3264/" rel='bookmark' title='Permanent Link: Debian: NIC bonding (teaming) 32/64 bit OS' class="liinternal">Debian: NIC bonding (teaming) 32/64 bit OS</a></li>
<li><a href="http://insanelabs.com/debian/debian-setup-is-unable-to-find-the-killall-program-error-when-installing-vmware-tools/" rel='bookmark' title='Permanent Link: Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools' class="liinternal">Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools</a></li>
<li><a href="http://insanelabs.com/debian/debian-upgrade-etch-to-lenny-and-error-message-there-is-no-public-key-available-for-the-following-key-ids-xxxxxxxxxxxxxxxx/" rel='bookmark' title='Permanent Link: Debian: Upgrade Etch to Lenny, and error message &#8220;There is no public key available for the following key IDs: xxxxxxxxxxxxxxxx&#8221;' class="liinternal">Debian: Upgrade Etch to Lenny, and error message &#8220;There is no public key available for the following key IDs: xxxxxxxxxxxxxxxx&#8221;</a></li>
</ol>]]></description>
		<wfw:commentRss>http://insanelabs.com/debian/debian-dmesg-output-contains-error-driver-pcspkr-is-already-registered-aborting-%e2%80%9d/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Debian: open-iscsi, use iSCSI initiator to connect to a SAN</title>
		<link>http://insanelabs.com/linux/debian-open-iscsi-use-iscsi-initiator-to-connect-to-a-san/</link>
		<comments>http://insanelabs.com/linux/debian-open-iscsi-use-iscsi-initiator-to-connect-to-a-san/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 20:41:03 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[iscsi]]></category>
		<category><![CDATA[san]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=687</guid>
		<description><![CDATA[It is actually quite easy as long as your kernel is 2.6.16 or newer. Debian supports fibre channel out of the box, and for iSCSI you only need to install the open-iscsi package (you can easily taylor this to your distro): aptitude install open-iscsi Once the package is installed restart the initiator: /etc/init.d/open-iscsi restart To [...]


Related posts:<ol><li><a href="http://insanelabs.com/linux/linux-mount-remote-windows-shares-with-smbfs/" rel='bookmark' title='Permanent Link: Linux: Mount remote Windows shares with smbfs' class="liinternal">Linux: Mount remote Windows shares with smbfs</a></li>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Permanent Link: Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/linux/debian-ssh-authentication-key-instead-of-password-rsa-key-pairs/" rel='bookmark' title='Permanent Link: Debian: ssh authentication key instead of password &#8211; RSA key pairs' class="liinternal">Debian: ssh authentication key instead of password &#8211; RSA key pairs</a></li>
</ol>]]></description>
		<wfw:commentRss>http://insanelabs.com/linux/debian-open-iscsi-use-iscsi-initiator-to-connect-to-a-san/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install</title>
		<link>http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/</link>
		<comments>http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 16:58:22 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Debian]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=479</guid>
		<description><![CDATA[If you have a Dell server, dump it, or keep reading Well&#8230; to me it sounds like some copyright crap Broadcom is pulling, or perhaps Debian is trying to be more compliant with restricted drivers. Three ways I can think of to work around this: Download the deb package from http://packages.debian.org/etch/firmware-bnx2, copy it to a [...]


Related posts:<ol><li><a href="http://insanelabs.com/linux/debian-debian-5-lenny-has-been-released/" rel='bookmark' title='Permanent Link: Debian: Debian 5 (Lenny) has been released!' class="liinternal">Debian: Debian 5 (Lenny) has been released!</a></li>
<li><a href="http://insanelabs.com/debian/debian-upgrade-etch-to-lenny-and-error-message-there-is-no-public-key-available-for-the-following-key-ids-xxxxxxxxxxxxxxxx/" rel='bookmark' title='Permanent Link: Debian: Upgrade Etch to Lenny, and error message &#8220;There is no public key available for the following key IDs: xxxxxxxxxxxxxxxx&#8221;' class="liinternal">Debian: Upgrade Etch to Lenny, and error message &#8220;There is no public key available for the following key IDs: xxxxxxxxxxxxxxxx&#8221;</a></li>
<li><a href="http://insanelabs.com/vmware/vmware-install-intel-et-82575-and-82576-drivers-on-esx-4-vsphere/" rel='bookmark' title='Permanent Link: VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere' class="liinternal">VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere</a></li>
</ol>]]></description>
		<wfw:commentRss>http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/feed/</wfw:commentRss>
		<slash:comments>36</slash:comments>
		</item>
		<item>
		<title>Debian: Upgrade Etch to Lenny, and error message &#8220;There is no public key available for the following key IDs: xxxxxxxxxxxxxxxx&#8221;</title>
		<link>http://insanelabs.com/debian/debian-upgrade-etch-to-lenny-and-error-message-there-is-no-public-key-available-for-the-following-key-ids-xxxxxxxxxxxxxxxx/</link>
		<comments>http://insanelabs.com/debian/debian-upgrade-etch-to-lenny-and-error-message-there-is-no-public-key-available-for-the-following-key-ids-xxxxxxxxxxxxxxxx/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 03:33:19 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[gpg]]></category>
		<category><![CDATA[Lenny]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=472</guid>
		<description><![CDATA[It’s pretty easy to upgrade your Etch to Lenny. Open your repo list and replace all references to “etch” with “lenny”. To edit your sources.list: nano /etc/apt/sources.list Then update your repositories: aptitude update and proceed to upgrade: aptitude dist-upgrade I ran into an error when I was updating my repositories: “There is no public key [...]


Related posts:<ol><li><a href="http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/" rel='bookmark' title='Permanent Link: Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install' class="liinternal">Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install</a></li>
<li><a href="http://insanelabs.com/debian/debian-vmware-server-1x-and-debian-etch/" rel='bookmark' title='Permanent Link: Debian: VMware Server 1.x and Debian Etch' class="liinternal">Debian: VMware Server 1.x and Debian Etch</a></li>
<li><a href="http://insanelabs.com/debian/linux-symantec-backup-exec-12-and-debian-etch-3264/" rel='bookmark' title='Permanent Link: Debian: Symantec Backup Exec 12 and Debian Etch 32/64' class="liinternal">Debian: Symantec Backup Exec 12 and Debian Etch 32/64</a></li>
</ol>]]></description>
		<wfw:commentRss>http://insanelabs.com/debian/debian-upgrade-etch-to-lenny-and-error-message-there-is-no-public-key-available-for-the-following-key-ids-xxxxxxxxxxxxxxxx/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Debian: Debian 5 (Lenny) has been released!</title>
		<link>http://insanelabs.com/linux/debian-debian-5-lenny-has-been-released/</link>
		<comments>http://insanelabs.com/linux/debian-debian-5-lenny-has-been-released/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 17:59:52 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=469</guid>
		<description><![CDATA[http://www.debian.com/News/2009/20090214 Happy Valentine&#8217;s day! Related posts:Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install


Related posts:<ol><li><a href="http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/" rel='bookmark' title='Permanent Link: Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install' class="liinternal">Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install</a></li>
</ol>]]></description>
		<wfw:commentRss>http://insanelabs.com/linux/debian-debian-5-lenny-has-been-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
