<?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>DeckerD: Drew&#039;s Personal Corner of the Web &#187; Tips</title>
	<atom:link href="http://www.deckerd.com/tag/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.deckerd.com</link>
	<description></description>
	<lastBuildDate>Fri, 01 Jan 2010 20:22:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>VMWare: Unable to load the BIOS due to the VMWare Splash screen not showing</title>
		<link>http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/</link>
		<comments>http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/#comments</comments>
		<pubDate>Tue, 06 Jan 2009 10:47:46 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/?p=192</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">After upgrading my version of VMWare from VMWare 1.6 to VMWare 2.0, and then installing and updating the VMWare Infrastructure Client, I had a new issue; accessing the BIOS from the VMWare splash startup screen. Before the upgrade, VMWare would display the VMWare splash screen as it loaded the NVRAM (I believe), and had a section that said "Press F2 to enter setup"; it went by fast, but it was at least there. After fiddling around with VMWare for a few minutes, I found a way around this <a href="http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Record Cell Phone Calls with Drop.io Service (free)</title>
		<link>http://www.deckerd.com/core/record-cell-phone-calls-with-dropio-service-free/</link>
		<comments>http://www.deckerd.com/core/record-cell-phone-calls-with-dropio-service-free/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 09:00:03 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[audio]]></category>
		<category><![CDATA[drop.io]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/?p=118</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">This was a pretty cool find, that was merely an accident. I joined the Drop.io service due to trying to find a decent, free AJAX upload script, since I didn't have the time to write something basic myself. I never actually found one, however, I decided that Drop.io was the closest thing to a solution. Basically, I needed to upload a few files, quickly, so that I could download them on a remote system (without using rsync or scp). If you have a chance to check out Drop.io, please do, then <a href="http://www.deckerd.com/core/record-cell-phone-calls-with-dropio-service-free/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/record-cell-phone-calls-with-dropio-service-free/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Clearing (but not deleting) log files</title>
		<link>http://www.deckerd.com/core/clearing-but-not-deleting-log-files/</link>
		<comments>http://www.deckerd.com/core/clearing-but-not-deleting-log-files/#comments</comments>
		<pubDate>Mon, 23 Jul 2007 04:22:26 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Shell Scripting]]></category>
		<category><![CDATA[Sys Admin]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[UNIX/Linux]]></category>
		<category><![CDATA[Walkthrough]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/clearing-but-not-deleting-log-files/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Sometimes, as a Systems Administrator, or SysAdmin, there are times we need to clear out the log files, without actually deleting them. As a smart Sys Admin, you normally wouldn't need to do this, but as I am currently involved in supporting customers and their Linux machines, I run into some pretty neat stuff (neat as in special). I've had a few issues where someone actually runs out of disk space on / (root filesystem) due to the /var/log directory being full. First off, you might run the <a href="http://www.deckerd.com/core/clearing-but-not-deleting-log-files/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/clearing-but-not-deleting-log-files/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Windows Fix: &#8220;Insufficient system resources exist to complete the API&#8221;</title>
		<link>http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/</link>
		<comments>http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/#comments</comments>
		<pubDate>Sun, 22 Jul 2007 07:29:25 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Memory/RAM]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows XP]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/windows-fix-insufficient-system-resources-exist-to-complete-the-api/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Ugh. Another Windows error. Another Windows error that really doesn't tell you what is really wrong; some (most) people aren't nerds. Don't worry, I've got your fix right here. This has to do with memory on your Windows XP system. Have you tried Hibernating or putting your system into standby after upgrading your RAM? If you have, keep on reading. Alright, while this isn't a very descriptive error message to the average computer user, a simple Google search can have your answer in no <a href="http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>VMWare: &#8220;Failed to create named-pipe directory&#8221; error</title>
		<link>http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/</link>
		<comments>http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/#comments</comments>
		<pubDate>Wed, 30 May 2007 08:09:31 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Applications]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Sys Admin]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[UNIX/Linux]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/vmware-failed-to-create-named-pipe-directory-error/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Have you ever received the Failed to create named-pipe directory error message via the vmware-mui error log files, and not able to access the VMWare Management Interface? If so, here's the fix. The error message at hand is the following: /var/log/vmware-mui/error_log ModVmdb load: Address of ModVmdb_InitCore: 0xb7c745a0 Failed to create named-pipe directory: /var/run/vmware//httpd/3854: No such file or directory VMWARE PANIC: \nNOT_IMPLEMENTED F(4023):707 Panic: Could not <a href="http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Installing Habari 0.1.1 (finally)</title>
		<link>http://www.deckerd.com/core/installing-habari-0-0-1/</link>
		<comments>http://www.deckerd.com/core/installing-habari-0-0-1/#comments</comments>
		<pubDate>Wed, 11 Apr 2007 02:48:30 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Beta Testing]]></category>
		<category><![CDATA[Habari]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Web Apps]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/installing-habari-0-0-1/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Well, after the initial repository builds and a crappy 0.1 release, I have successfully been able to install Habari onto my server. Do I use it? No, but I do like to test out other software in my free time, heh. Seriously, though, installing Habari has been quite lame, and I'm happy to say that I have figured out how to get it installed on a server, with no error messages. Background Information First off, Habari is a new blogging software that is being highly-developed by former <a href="http://www.deckerd.com/core/installing-habari-0-0-1/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/installing-habari-0-0-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>/bin/rm: Argument list too long</title>
		<link>http://www.deckerd.com/core/rm-argument-list-too-long-fixed/</link>
		<comments>http://www.deckerd.com/core/rm-argument-list-too-long-fixed/#comments</comments>
		<pubDate>Sat, 06 Jan 2007 02:47:45 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Career]]></category>
		<category><![CDATA[File Systems]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Sys Admin]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[UNIX/Linux]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/rm-argument-list-too-long-fixed/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">While at work, I had a customer ask me how to, one time, delete all the mail in his /home//mail/cur directory. So, first off, I wanted him to just take a look at that directory, get to know it (figuratively speaking). So I had him run the du command on it; wow, you wouldn't imaging how much mail was in there! The actual command I had him run was: BASH cd /home//mail/cur du -h ./ The output was 1.3GB. Yes, that's right, he had 1.3GB of mail files. Some people are unaware <a href="http://www.deckerd.com/core/rm-argument-list-too-long-fixed/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/rm-argument-list-too-long-fixed/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>
