<?xml version="1.0"?><rss version="2.0">
   <channel>
      <title>Chadone.com Blog</title>
      <link>http://www.chadone.com/blog/</link>
      <description>Description of my blog</description>
      <language>en-us</language>
      <generator>Chadone.com Custom Software</generator>
	  
	  <item>
         <title>Pepperoni and Sausage</title>
         <link>http://www.chadone.com/blog/posts/pepperoni_and_sausage/</link>
         <description><![CDATA[If I ever had two pets at the same time, they would be two weiner dogs, named Pepperoni and Sausage.  Oh sure, it would be a cute name and all, but the real reason would be at their death.  I would choose to memorialize them just so I can answer the question "What do you want on your tombstone?" with Pepperoni and Sausage.]]></description>
         <pubDate>Thu, 10 Jan 2013 21:38:48 -0600</pubDate>
         <guid isPermaLink="false">pepperoni_and_sausage</guid>
      </item>
	  	  
	  <item>
         <title>Meatloaf</title>
         <link>http://www.chadone.com/blog/posts/meatloaf/</link>
         <description><![CDATA[<p>I love a good meatloaf.  I made meatloaf just last night. Here's how it went together.</p>

<p>We bought some lovely, very tomato-ey BBQ sauce at the Spoon River Scenic Drive.  No idea who makes it, but it's not available in stores.</p>

<p>Here's what went in:</p>
<ul style="font-family: arial, helvetica, sans-serif"><li>One pound each of ground beef and ground pork</li>
<li>Two Eggs</li>
<li>1 Red Bell Pepper, diced</li>
<li>1/2 Green Bell Pepper, diced</li>
<li>1/2 onion, diced</li>
<li>Black pepper</li>
<li>Loads of Lea & Perrins Worcestershire</li>
<li>Panko, italian bread crumbs, and crushed saltines (had a lot of dry breads to rid myself of).</li>
<li>A small amount of a very tomatoey BBQ sauce (not store-bought)</li></ul>

<p>I topped it with a glaze made of that same BBQ sauce, loads of ketchup, honey, and worcestershire. I coated the meatloaf with the sauce and put it in the oven at 500 degrees for the first 10 minutes to dry on the sauce and brown the meat, then down to 375 for the next 45. After that, I put another layer of sauce and then some ketchup swirls, and back in the oven another 10 minutes.</p>

<p>Served with the rest of the sauce.</p>

<p>My only regret was not cutting the peppers/onions smaller, and/or sauteing them first.  They made it too crumbly, and it was hard to cut.  It was very good.</p>

<p>Yes, this post mostly exists because I haven't touched my blog in 2 years, 1 month.  But I love meatloaf, too. P.S. I also chopped up a strip of bacon to go in with the meat.</p>]]></description>
         <pubDate>Wed, 14 Nov 2012 15:23:06 -0600</pubDate>
         <guid isPermaLink="false">meatloaf</guid>
      </item>
	  	  
	  <item>
         <title>Happy 25th, Mario!</title>
         <link>http://www.chadone.com/blog/posts/happy_25th_mario/</link>
         <description><![CDATA[<p>My wife Rachel went yard sale shopping and found me a Nintendo (NES) for only $3.&nbsp; After some maintenance and cleaning, it looks as good as new and works just as well.&nbsp; What a great way to celebrate <a href="http://kotaku.com/5636283/happy-25th-birthday-super-mario-bros">Mario's 25th birthday</a>! It had a LOT of the original documentation.&nbsp; In fact, it had the original warranty form included.&nbsp; I wondered what the people at Nintendo would think if they received this.</p>
<p><img alt="Warranty booklet cover" src="http://www.chadone.com/blog/linkfiles/nintendo1.jpg" /></p>
<p><img alt="Warranty Registration Form" src="http://www.chadone.com/blog/linkfiles/nintendo2.jpg" /></p>
<p>As you can see, I've filled it out and I'm dropping it in the mail tomorrow.&nbsp; Afraid their business reply mail permit has changed or expired so I'm putting postage on this one.&nbsp;</p>
<p>I wonder how many Club Nintendo coins I might earn for this purchase.</p>
<p>If anyone has an old NES Control Deck lying around, and it doesn't read cartridges - try the <a href="http://classicgaming.gamespy.com/View.php?view=Articles.Detail&amp;id=256">instructions I used</a> to make mine as good as new.&nbsp; Well that, lots of Lysol cleaning wipes, and a Magic Eraser.</p>]]></description>
         <pubDate>Mon, 20 Sep 2010 00:06:57 -0500</pubDate>
         <guid isPermaLink="false">happy_25th_mario</guid>
      </item>
	  	  
	  <item>
         <title>And Now a Story About Bunny Poop</title>
         <link>http://www.chadone.com/blog/posts/and_now_a_story_about_bunny_poop/</link>
         <description><![CDATA[<p>I was working today on compiling a program that would help a company stream their webcam over the Internet.&nbsp; I decided to try out a program called Xuggler.</p>
<p>Anyone that's ever tried to compile software on Linux knows that ./configure pumps out hundreds of lines of checks in a few moments' time.</p>
<p>This time was different...</p>
<div style="background-color: black; color: rgb(136, 136, 136); margin: 10px; padding: 10px;">
<p class="nospacing" style="font-size: .8em; font-family: Menlo,Andale Mono,sans-serif;">checking for a BSD-compatible install... /usr/bin/install -c<br />
checking whether build environment is sane... yes<br />
checking for a thread-safe mkdir -p... /bin/mkdir -p<br />
checking for gawk... gawk<br />
checking whether make sets $(MAKE)... yes<br />
checking how to create a pax tar archive... gnutar<br />
checking whether to enable maintainer-specific portions of Makefiles... no<br />
checking whether to use captive versions of dependent libraries... yes<br />
checking whether to enable compiler optimizations... yes<br />
checking whether to regnerate java interfaces from swig... no<br />
checking build system type... i686-pc-linux-gnu<br />
checking host system type... i686-pc-linux-gnu<br />
<font color="#ffffff">checking whether we saw a bunny... no</font><br />
checking for gcc... gcc<br />
checking for C compiler default output file name... a.out<br />
checking whether the C compiler works... yes<br />
checking whether we are cross compiling... no<br />
checking for suffix of executables... <br />
checking for suffix of object files... o<br />
checking whether we are using the GNU C compiler... yes<br />
checking whether gcc accepts -g... yes<br />
checking for gcc option to accept ISO C89... none needed<br />
checking for a sed that does not truncate output... /usr/bin/sed<br />
checking for grep that handles long lines and -e... /usr/bin/grep<br />
checking for egrep... /usr/bin/grep -E<br />
checking for fgrep... /usr/bin/grep -F<br />
checking for ld used by gcc... /usr/i586-suse-linux/bin/ld<br />
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes<br />
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B<br />
checking the name lister (/usr/bin/nm -B) interface... BSD nm<br />
checking whether ln -s works... yes<br />
checking the maximum length of command line arguments... 1572864<br />
checking whether the shell understands some XSI constructs... yes<br />
checking whether the shell understands &quot;+=&quot;... yes<br />
checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r<br />
checking for objdump... objdump<br />
checking how to recognize dependent libraries... pass_all<br />
checking for ar... ar<br />
checking for strip... strip<br />
checking for ranlib... ranlib<br />
checking command to parse /usr/bin/nm -B output from gcc object... ok<br />
checking how to run the C preprocessor... gcc -E<br />
checking for ANSI C header files... yes<br />
checking for sys/types.h... yes<br />
checking for sys/stat.h... yes<br />
checking for stdlib.h... yes<br />
checking for string.h... yes<br />
checking for memory.h... yes<br />
checking for strings.h... yes<br />
checking for inttypes.h... yes<br />
checking for stdint.h... yes<br />
checking for unistd.h... yes<br />
checking for dlfcn.h... yes<br />
checking for objdir... .libs<br />
checking if gcc supports -fno-rtti -fno-exceptions... no<br />
checking for gcc option to produce PIC... -fPIC -DPIC<br />
checking if gcc PIC flag -fPIC -DPIC works... yes<br />
checking if gcc static flag -static works... yes<br />
checking if gcc supports -c -o file.o... yes<br />
checking if gcc supports -c -o file.o... (cached) yes<br />
checking whether the gcc linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes<br />
checking whether -lc should be explicitly linked in... no<br />
checking dynamic linker characteristics... GNU/Linux ld.so<br />
checking how to hardcode library paths into programs... immediate<br />
checking whether stripping libraries is possible... yes<br />
checking if libtool supports shared libraries... yes<br />
checking whether to build shared libraries... yes<br />
checking whether to build static libraries... no<br />
<font color="#ffffff">checking whether we smell bunny poop... no</font><br />
checking whether to build 64 bit version of package... no<br />
checking for gcc... (cached) gcc<br />
checking whether we are using the GNU C compiler... (cached) yes<br />
checking whether gcc accepts -g... (cached) yes&nbsp;</p>
</div>
<p>No, those lines weren't highlighted in bright white when I ran the command.  I happened to see them while it was scrolling by at 20 lines a second.</p>
<p>Reminds me of the Mozy backup service's Terms &amp; Conditions.&nbsp;&nbsp; A couple years ago, I decided for no apparent reason at all to skim through them, and it said.&nbsp; &quot;Furthermore, you agree to use Mozy <a href="http://www.hrwiki.org/wiki/some_kinda_robot">for good or for awesome</a>.&quot; They've since changed their terms, but I assure you that it was there. It's not so much that it's in there that's funny, it's that it's almost invisible and yet still people notice it.</p>]]></description>
         <pubDate>Fri, 16 Apr 2010 11:34:50 -0500</pubDate>
         <guid isPermaLink="false">and_now_a_story_about_bunny_poop</guid>
      </item>
	  	  
	  <item>
         <title>Don't Get Me Wrong - I Love the Bunny</title>
         <link>http://www.chadone.com/blog/posts/i_love_the_bunny/</link>
         <description><![CDATA[<p>I got a Russell Stover solid milk chocolate bunny to celebrate Easter with.&nbsp; As I was eating away on it, I saw a nice little letter on the back saying how they use only the finest ingredients.</p>
<p><img src="http://www.chadone.comhttp://www.chadone.com/blog/linkfiles/bunny.jpg" alt="" /></p>
<p>And then, of course, I had to read the ingredients.&nbsp; I'm very glad that they use cocoa butter for their chocolate.&nbsp; I can't stand &ldquo;chocolate&rdquo; made from palm kernel oil.&nbsp; But I noticed that they also use vanillin.&nbsp;</p>
<p>Why vanillin?&nbsp; There has to be what - one drop of vanilla flavoring in the whole thing.&nbsp; Why on earth would you cut corners there?&nbsp; For those that don't know, vanillin (imitation vanilla extract) is usually commercially extracted by soaking burnt wood or coal tar in alcohol.&nbsp; Yum!&nbsp;</p>]]></description>
         <pubDate>Sun, 11 Apr 2010 17:26:32 -0500</pubDate>
         <guid isPermaLink="false">i_love_the_bunny</guid>
      </item>
	  	  
	  <item>
         <title>New Google Maps Feature</title>
         <link>http://www.chadone.com/blog/posts/new_google_maps_feature/</link>
         <description><![CDATA[<p>Google Maps now automatically routes around roads closed for road construction.   I was trying to get to somewhere on I-64 on the west end of St. Louis.  When I asked Google Maps for help, it sent me all around the city, starting on I-64, then taking I-44 southwest, and then I-270 North to meet up with I-64 again.</p>
<p>I know that I-64 is closed from the Kingshighway exit to I-170 but I didn't think Google Maps knew that.  I tried to drag the route onto the closed section of I-64 and it wouldn't let me - it acted like there wasn't even a road to drive on.  Technically, there isn't at the moment.</p>
<p>So that was pretty exciting to me.  Although I wish Maps would at least tell me why it redirected me, so that I'd be sure that their route-planning isn't just getting dumber.</p>]]></description>
         <pubDate>Sat, 22 Aug 2009 11:33:24 -0500</pubDate>
         <guid isPermaLink="false">new_google_maps_feature</guid>
      </item>
	  	  
	  <item>
         <title>Overdrawn at the ... Bank</title>
         <link>http://www.chadone.com/blog/posts/overdrawn_at_the_bank/</link>
         <description><![CDATA[<p>I logged into our First Bank account, because I wanted to check on a couple things (we are moving to a new checking account this week.  When I got there, I saw that I was $45 overdrawn!!!  So after a nice, long panic I found check #2111 (not my check).  Ours are in the 600's.  Someone else's check for $57 posted to our account.  </p>

<img src="http://www.chadone.com/blog/linkfiles/check.gif" alt="Check Image">

<p>Their electronic check reader (or human) read the 229 as 559 and it posted to our account.</p>

<p>We're saved? I hope so. Otherwise, we'd be facing over $100 in overdraft fees, 75% of which would be for purchases under $7.00</p>

]]></description>
         <pubDate>Wed, 05 Aug 2009 17:19:15 -0500</pubDate>
         <guid isPermaLink="false">overdrawn_at_the_bank</guid>
      </item>
	     </channel>
</rss>
