<?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/"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
><channel><title>Muddled Ramblings and Half-Baked Ideas &#187; Rumblings from the Secret Labs</title> <atom:link href="http://muddledramblings.com/category/rumblings-from-the-secret-labs/feed/" rel="self" type="application/rss+xml" /><link>http://muddledramblings.com</link> <description>A blog about a geek trying to make a living as a writer</description> <lastBuildDate>Fri, 03 Feb 2012 04:13:58 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator><itunes:summary>A blog about a geek trying to make a living as a writer</itunes:summary> <itunes:author>Jerry Seeger</itunes:author> <itunes:explicit>no</itunes:explicit> <itunes:image href="http://s3.amazonaws.com/muddlebucket/wp-content/uploads/iTunes/iTunes_img.jpg" /> <itunes:owner> <itunes:name>Jerry Seeger</itunes:name> <itunes:email>vikingjs+tunes@mac.com</itunes:email> </itunes:owner> <managingEditor>vikingjs+tunes@mac.com (Jerry Seeger)</managingEditor> <itunes:subtitle>A blog about a geek trying to make a living as a writer</itunes:subtitle> <itunes:keywords>short story, spoken</itunes:keywords> <image><title>Muddled Ramblings and Half-Baked Ideas &#187; Rumblings from the Secret Labs</title> <url>http://muddledramblings.com/wp-content/plugins/powerpress/rss_default.jpg</url><link>http://muddledramblings.com/category/rumblings-from-the-secret-labs/</link> </image> <itunes:category text="Arts"> <itunes:category text="Literature" /> </itunes:category> <item><title>An Online Community that I can Get Behind</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/an-online-community-that-i-can-get-behind/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/an-online-community-that-i-can-get-behind/#comments</comments> <pubDate>Thu, 02 Feb 2012 08:28:14 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[geek]]></category> <category><![CDATA[Internet]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10920</guid> <description><![CDATA[Since there are others using my server now, I thought it would be a good idea to upgrade my backup practices. I looked around a bit, hoping for a solution that was free, butt-simple to set up, and automatic, so I would never have to think about it again. I don&#8217;t like thinking when I [...]]]></description> <content:encoded><![CDATA[<p>Since there are others using my server now, I thought it would be a good idea to upgrade my backup practices. I looked around a bit, hoping for a solution that was free, butt-simple to set up, and automatic, so I would never have to think about it again. I don&#8217;t like thinking when I don&#8217;t have to.</p><p>I came across CrashPlan, the backup solution my employer uses. Turns out their software is free to chumps like me; they make their cash providing a place for you to put that valuable information.</p><p>There are two parts to any backup plan: you must gather your data together and you must put it somewhere safe that you can get to later. The CrashPlan software handles the gathering part, making it easy, for instance, to save all my stuff to the external hard drive sitting on my desk, but if the house burns down that won&#8217;t do me much good.</p><p>Happily CrashPlan also makes it easy to talk to remote computers, provided they have the software installed. I put CrashPlan on my server in a bunker somewhere in Nevada, and now this site and a couple of others are saved automatically to my drive in California as well. Easy peasy! Any computer signed up under my account can make backups to any other.</p><p>But wait! There&#8217;s more! The cool idea CrashPlan came up with was letting friends back each other up. I give you a special code and you can put backups of your stuff on my system. I can&#8217;t see what you saved, it&#8217;s all encrypted. But unless both our houses burn down at the same time, there&#8217;s always a safe copy.</p><p>Sure, if you pay you get more features and they will store your stuff in a safe place where you don&#8217;t have to wait if I happen to be on vacation, but for free that&#8217;s not bad at all. The idea of friends getting together and forming a backup community appeals to me as well. It&#8217;s a great way for geeks to look out for one another.</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/an-online-community-that-i-can-get-behind/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Step-by-Step LAMP server from scratch with MacPorts</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/lamp-server-from-scratch-with-macports/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/lamp-server-from-scratch-with-macports/#comments</comments> <pubDate>Fri, 27 Jan 2012 02:39:13 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[geek]]></category> <category><![CDATA[Internet]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10823</guid> <description><![CDATA[A works-every-time guide to getting everything installed and configured.]]></description> <content:encoded><![CDATA[<p>Getting Apache, PHP, and MySQL installed and talking to each other is pretty simple — until something doesn&#8217;t come out right. This guide takes things one step at a time and checks each step along the way.</p><style type="text/css">
#page {
    width: 1170px;
}
#content.narrowcolumn {
    width: 790px;
}
.narrowcolumn .entry {
    line-height: inherit;
}
html > body .entry ul {
    text-indent: 0;
}
#tutorial .date-stamp {
    font-size: 80%;
    font-family: monospace;
}
#tutorial .date-stamp label {
    font-family: inherit;
}
	#tutorial p
	{
		margin-left: 4em;
	}
	#tutorial ol p
	{
		margin-left: 0;
	}
	#tutorial li {
		margin-top: 1em;
	}
	#tutorial ol ol li {
		list-style-type: upper-alpha;
	}
	#tutorial ol ol ol li {
		list-style-type: lower-roman;
	}
	#tutorial ol.code
	{
		list-style-type:none;
		margin: 1em 0;
		width: 580px;
		padding: 0.5em;
		font-size:90%;
	}
	#tutorial ol.code li
	{
		list-style-type:none;
	}
	#tutorial ul ol.code
	{
		width: 500px;
	}
	#tutorial ol ul li
	{
		list-style-type: circle;
	}
	#tutorial .example {
		padding: 0.1em 0.5em;
	}
	#tutorial ol.command,
	#tutorial .example.command
	{
		color:lightgreen;
		background-color:black;
	}
	#tutorial ol.text,
	#tutorial .example.code
	{
		color:black;
		background-color:lightgray;
	}
	#tutorial code.command:before
	{
		content:"$";
		padding-right:1ex;
	}
	#tutorial code.command.mysql:before
	{
		content:"mysql>";
		padding-right:1ex;
	}
	#tutorial ol.code li,
	#tutorial ol.text li
	{
		margin: 0;
	}
	#tutorial pre
	{
		margin: 0;
	}
	#tutorial li.note {
		background-color: lightyellow;
		list-style-type: none;
		/*text-indent:-42px;*/
		padding: 0.5em;
	}
	#tutorial li.note li {
		background-color: lightyellow;
		text-indent: 0;
	}
	#tutorial li.note ol {
		list-style-type: decimal;
	}
	#tutorial li.note:before {
		content: "Note:";
		margin-left: -42px;
		padding-right: 8px;
	}
	#tutorial li.before,
	#tutorial li.after
	{
		list-style-type: none;
	}
	#tutorial .filesystem
	{
		color: brown;
	}
	#tutorial table,
	#tutorial td
	{
		border: 1px solid black;
		border-collapse: collapse;
		vertical-align: top;
	}
	#tutorial td { padding: 0.3em 1em; }
	
	#tutorial .milestone span
	{
		color: purple;
	}
	#tutorial .quote { quotes: "\201c" "\201d"}
	#tutorial .quote:before { content: open-quote; }
	#tutorial .quote:after { content: close-quote; }
	#tutorial .remove { color: red; }
	#tutorial .add { color: green; }
</style><div
id="tutorial"><div
class="date-stamp"><label>last updated:</label> January 14, 2011</div><div
class="date-stamp"><label>last executed:</label> January 14, 2011</div><p><h2>Using MacPorts to build a LAMP server from scratch</h2></p><h4>About this tutorial:</h4><p>There are other step-by-step guides out there, and some of them are pretty dang good. But I’ve never found one that I could go through and reach the promised land without a hitch. (Usually the hitches happen around MySQL.) Occasionally key points are glossed over, but I think mostly there are things that have changed, and the tutorials haven’t updated. Now however I’ve done this enough times that there are no hitches anymore for me. Since MacPorts occasionally changes things, I’ll put up at the top of this page the last time this recipe was last used exactly as written here.</p><p>This guide breaks things down into very small steps, but each step is simple. I include tests for each stage of the installation, so problems can be spotted while they're easy to trace. We get each piece working before moving on to the next. I spend a little time telling you what it is you accomplish with each step, because a little understanding can really help when it’s time to troubleshoot, and if things are slightly different you have a better chance of working through them.</p><p><strong>Audience:</strong> This guide is designed to be useful to people with only a passing familiarity with the terminal. More sophisticated techno-geeks may just want to go through the sequence of commands, and read the surrounding material only when something doesn't make sense to them. The goal: follow these steps and it will work every damn time.</p><p><strong>MacOS X versions:</strong> Tiger, Leopard, Snow Leopard, Lion. Maybe others, too. The beauty of this method is it doesn’t really matter which OS X version you have.</p><h4>The advantages of this approach</h4><p>There are multiple options for setting up a Mac running OS X to be a Web server. Many of the necessary tools are even built right in. Using the built-in stuff might be the way for you to go, but there are problems: It’s difficult to customize (Search on <span
class="quote">install apc Mac</span> and you’ll see what I mean), you don’t control the versions of the software you install, and when you upgrade MacOS versions things could change out from under you.</p><p>Also simple to set up is MAMP, which is great for developing but not so much for deployment. For simple Web development on your local machine, it’s hard to beat.</p><p>But when it comes right down to it, for a production server you want control and you want predictability. For that, it’s best to install all the parts yourself in a known, well-documented configuration, that runs close to the metal. That’s where MacPorts comes in. Suddenly installing stuff gets a lot easier, and there’s plenty of documentation.</p><p>Holy schnikies! A new timing exploit on OpenSSL! It may be months before Apple's release fixes it. I want it sooner!</p><h4>What you lose:</h4><p>If you’re running OS X Server (suddenly an affordable option), you get some slick remote management tools. You’ll be saying goodbye to them if you take this route. In fact, you’ll be saying goodbye to all your friendly windows and checkboxes.</p><p>Also, I have never, ever, succeeded in setting up a mail server, MacPorts or otherwise, and I’ve tried a few different ways (all on the same box, so problems left over from one may have torpedoed the next), and no one I've ever met, even sophisticated IT guys, likes this chore. If serving mail is a requirement, then OS X Server is probably worth the loss of control. Just don’t ever upgrade your server to the next major version. (<span
class="quote">Where’s MySQL!?! Ahhhhhh!</span> I hear frustrated sys admins shout.)</p><p>So, here we go!</p><h3>Document conventions</h3><p>There are commands you type, lines of code you put in files, and other code-like things. I've tried to make it all clear with text styles.</p><table><tbody><tr><td
style="width: 400px;"><code
class="example command">This is something you type into the terminal</code></td><td>Do <strong>not</strong> type the <code
class="example command"></code>; it's just to represent the prompt in your own terminal window. Once you've typed the text (or pasted it in from here), hit return.</td></tr><tr><td><code
class="example code">This is a line of code in a file.</code></td><td>Either you will be looking for a line like this, or adding a line like this.</td></tr><tr><td><span
class="filesystem">This is a reference to a file or a path.</td><td></td></tr></tbody></table><div
class="major-section"><h3>Prepare the Box</h3><ol><li>Turn off unneeded services on the server box. Open System Preferences and select <span
class="quote">Sharing</span>.<ul><li
style="margin:0">turn on remote login<li
style="margin:0">(optional) turn on Screen Sharing<li
style="margin:0">Turn off everything else - <em>especially</em> Web Sharing and File Sharing</li></ul></li><li>Install XCode. This provides tools that MacPorts uses to build the programs for your machine. You can get XCode for free from the app store. It’s a huge download. Note that after you download it, you have to run the installer. It may launch XCode when the install is done, but you can just Quit out of it.</li><li>Install MacPorts. You can download the installer from <a
href="http://www.MacPorts.org/install.php">http://www.MacPorts.org/install.php</a> (make sure you choose the .dmg that matches the version of MacOS you are running). Run the installer and get ready to start typing.</li><li>Now it’s time to make sure MacPorts itself is up-to-date. Open terminal and type<ol
class="code command"><li><code
class="command">sudo port selfupdate</code></li><li><code
class="prompt">password: &lt;enter your admin password&gt;</code></li></ol> MacPorts will contact the mother ship and update itself.</li><ul><li
class="note">If you're not familiar with <a
href="http://xkcd.com/149/"><code>sudo</code></a>, you will be soon. It gives you temporary permission to act as the root user for this machine. Every once in a while during this process you will need to type your admin password again.</li></ul><li>May as well get into the habit of updating the installed software while we’re at it. Type<ol
class="code command"><li><code
class="command">sudo port upgrade outdated</code></li></ol> and you will most likely see a message that looks like an error but really says that there was nothing to upgrade. No biggie.<ul><li
class="note">Make a habit of running these commands regularly. One of the reasons you're doing this whole thing is to make sure your server stays up-to-date. This is how you do it.</li></ul></li></ol></div><div
class="major-section"><h3>Install Apache</h3><ol><li>Now it’s time to get down to business. All the stuff we’ve installed so far is just setting up the tools to make the rest of the job easier. Let’s start with Apache!<ol
class="code command"><li><code
class="command">sudo port install apache2</code></li></ol><ul><li
class="note">This may take a little while. It’s actually downloading code and compiling a version of the server tailored to your system. First it figures out all the other little pieces Apache needs and makes sure they’re all installed correctly. Hop up and grab a sandwich, or, if you're really motivated, do something else productive while you wait.</li></ul></li><li>When the install is done, you will see a prompt to execute a command that will make Apache start up automatically when the computer is rebooted. Usually you will want to do this. The command has changed in the past, so be sure to check for the message in your terminal window. <strong>As of this writing</strong>, the command is:<ol
class="code command"><li><code
class="command">sudo port load Apache2</code></li></ol></li><li>Create an alias to the correct apachectl. apachectl is a utility that allows you to do things like restart Apache after you make changes. The thing is, the built-in Apache has its own apachectl. To avoid confusion, you can either type the full path to the new apachectl every time, or you can set up an alias. Aliases are commands you define. In this case you will define a new command that executes the proper apachectl.<ol><li>In your home directory (<span
class="filesystem">~/</span>) you will find a file called <span
class="filesystem">.profile</span> - if you didn’t have one before, MacPorts made one for you. Note the dot at the start. That makes the file invisible; Finder will not show it. In terminal you can see it by typing<ol
class="code command"><li><code
class="command">ls -a ~/</code></li></ol> You will get back a list of all the files in your home directory, including the <span
class="quote">hidden</span> ones that start with <span
class="quote">.</span>.</li><li>Edit <span
class="filesystem">~/.profile</span> and add the following line:<ol
class="code text"><li><code
class="console">alias apache2ctl='sudo /opt/local/apache2/bin/apachectl'</code></li></ol><ul><li
class="note">Edit <em>how</em>? See <a
href="#ap2">below</a> for a brief discussion about editing text files and dealing with file permissions.</li><li
class="note">~/.profile isn't the only place you can put the alias, but it works.</li></ul></li><li>You need to reload the profile info for it to take effect in this terminal session.<ol
class="code command"><li><code
class="command">source ~/.profile</code></li></ol></li><li>Now anywhere in the docs it says to use apachectl, just type apache2ctl instead, and you will be sure to be working on the correct server.</li></ol><li>Start Apache:<ol
class="code command"><li><code
class="command">apache2ctl start</code></li></ol> You might see a warning or two, probably a notification about the server's name. That's fine.</li><li>Test the Apache installation. At this point, you should be able to go to <a
href="http://127.0.0.1/">http://127.0.0.1/</a> and see a simple message: “It works!”</li><li
class="milestone"><span>MILESTONE</span> - Apache is up and running!</li></ol></div><div
class="major-section"><h3>Install PHP</h3><ol><li> Use MacPorts to build PHP 5:<ol
class="code command"><li><code
class="command">sudo port install php5 +pear</code></li></ol><ul><li
class="note">You could install the MySQL extensions to PHP now (<code>sudo port install php5-mysql</code>), but that will cause MySQL to be installed as well. It’s no biggie, but I like to make sure each piece is working before moving on to the next. It makes problem-solving a lot easier. So, let’s hold off on that.</li><li
class="note"><code>+pear</code> adds an industry-standard way to load other PHP addons later.</li></ul></li><li>Choose your php.ini file. There are a couple of different options that trade off security for convenience (error reporting and whatnot). As of this writing there is <span
class="filesystem">php.ini-development</span> (more debugging information, less secure) and <span
class="filesystem">php.ini-production</span>. Copy the one you want to use and name it <span
class="filesystem">php.ini</span>:<ol
class="code command" style="width: 620px;"><li><code
class="command">sudo cp /opt/local/etc/php5/php.ini-development /opt/local/etc/php5/php.ini</code></li></ol> You will be editing this file a little bit later, but mostly it’s just a bunch of settings you’ll never need to understand.</li><li>Test the PHP install<ol><li>On the command line, type<ol
class="code command"><li><code
class="command">php -i</code></li></ol></li><li>A bunch of information will dump out. Hooray!</li></ol></li><li>Now it’s time to get Apache and PHP talking to each other. Apache needs to know that PHP is there, and when to use it. There’s a lot of less-than-ideal advice out there about how to do this.<ol><li>httpd.conf is the heart of the Apache configuration. Mess this up, Apache won’t run. It’s important, therefore, that you MAKE A BACKUP (there’s actually a spare copy in the install, but you never rely on that, do you?)<ol
class="code command"><li><code
class="command">cd /opt/local/apache2/conf</code></li><li><code
class="command">sudo cp httpd.conf httpd.conf.backup</code></li></ol></li><li>First run a little utility installed with Apache that supposedly sets things up for you, but actually doesn’t do the whole job:<ol
class="code command"><li><code
class="command">cd /opt/local/apache2/modules</code></li><li><code
class="command">sudo /opt/local/apache2/bin/apxs -a -e -n "php5" libphp5.so</code></li></ol><li>The utility added the line in the Apache config file that tells it that the PHP module is available. It does <strong>not</strong> tell Apache when to use it. There is an extra little config file for that job, but it’s not loaded (as far as I can tell), and it’s not really right anyway. Let's take matters into our own hands.<ul><li
class="note"><em>It won't let me save!</em> See <a
href="#ap2">below</a> for a brief discussion about editing text files and dealing with permissions.</li></ul><li>Time to edit! Open <span
class="filesystem">/opt/local/apache2/conf/httpd.conf</span> with permission to edit it. We need to add three lines; one to tell it that PHP files are text files (not strictly necessary but let’s be rigorous here), and two lines to tell it what to do when it encounters a PHP file.<ol><li>Search for the phrase <span
class="quote">AddType</span> in the file. After the comments (lines that start with #) add:<ol
class="code text" style="width:450px;"><li><code>AddType text/html   .php</code></li></ol></li><li>Search for AddHandler (it’s just a few lines down) and add:<ol
class="code text" style="width:450px;"><li><code>AddHandler application/x-httpd-php         .php</code></li><li><code>AddHandler application/x-httpd-php-source  .phps</code></li></ol> The second of those is just to let you display PHP source code in a Web page without actually running it.</li><li>Finally, we need to tell Apache that index.php is every bit as good as index.html. Search in the config file for <span
class="quote">index.html</span> and you should fine a line that says <code>DirectoryIndex index.html</code>. Right after the html file put <span
class="quote">index.php</span>:<ul><li
class="before">Before:<ol
class="code text"><li><code>DirectoryIndex index.html</code></li></ol></li><li
class="after">After:<ol
class="code text"><li><code>DirectoryIndex index.html <span
class="add">index.php</span></code></li></ol></li></ul></li><li>(Optional) As long as we’re in here, let’s make one more change for improved security. Search for the line that specifies the default options for Apache and remove <span
class="quote">Indexes</span>:<ul><li
class="before">Before:<ol
class="code text"><li><code>Options <span
class="remove">Indexes</span> FollowSymLinks</code></li></ol></li><li
class="after">After:<ol
class="code text"><li><code>Options FollowSymLinks</code></li></ol></li></ul> This prevents outsiders from seeing a list of everything in a directory that has no index file.</li><li>Save the file.</li></ol></li><li>Check the init file syntax by typing<ol
class="code command"><li><code
class="command">/opt/local/apache2/bin/httpd -t</code></li></ol> You will probably get a warning about the server’s name again, but that’s OK, as long as you see the magical <code
class="out">Syntax OK</code> message. If there is an error, the file and line number should be listed.</li><li>Restart Apache:<ol
class="code command"><li><code
class="command">apache2ctl restart</code></li></ol></li></ol></li><li>Test whether PHP and Apache can be friends. We will modify the “It Works!” file to dump out a bunch of info about your PHP installation.<ol><li>Currently the default Apache directory is <span
class="filesystem">/opt/local/apache2/htdocs</span></li><li>Start by renaming <span
class="filesystem">index.html</span> to <span
class="filesystem">index.php</span>:<ol
class="code command"><li><code
class="command">cd /opt/local/apache2/htdocs</code></li><li><code
class="command">sudo mv index.html index.php</code></li></ol></li><li>Edit the file, and after the It Works! bit add a PHP call so the result looks like this:<ol
class="code text"><li><pre><code class="code">&lt;html></code></pre></li><li><pre><code class="code">    &lt;body></code></pre></li><li><pre><code class="code">        &lt;h1>It works!&lt;/h1></code></pre></li><li><pre><code class="code">        &lt;?php echo phpinfo(); ?></code></pre></li><li><pre><code class="code">    &lt;/body></code></pre></li><li><pre><code class="code">&lt;/html></code></pre></li></ol></li><li>Save the file</li><li>Go to <a
href="http://127.0.0.1">http://127.0.0.1</a> - you should see a huge dump of everything you wanted to know about your PHP but were afraid to ask.</li></ol></li><li
class="milestone"><span>MILESTONE</span> - Apache and PHP are installed and talking nice to each other.</li></ol></div><div
class="major-section"><h3>Install and configure MySQL</h3><ol><li>Use MacPorts to install MySQL database and server and start it automatically when the machine boots:<ol
class="code command"><li><code
class="command">sudo port install mysql5-server</code></li><li><code
class="command">sudo port load mysql5-server</code></li></ol></li><li>Now we get to the trickiest part of the whole operation. There's nothing here that's difficult, but I've spent hours going in circles before, and I'm here so you won't find yourself in that boat as well. MySQL requires some configuration before it can run at all, and it can be a huge bother figuring out what’s going on if it doesn’t work the first time. We start by running a little init script:<ol
class="code command"><li><code
class="command">sudo -u _mysql mysql_install_db5</code></li></ol></li><li> As with Apache, you can create a set of aliases to simplify working with MySQL. There are some commands you will run frequently; things get easier if you don’t have to type the full path to the command every time. Open up <span
class="filesystem">~/.profile</span> again and add the following three lines:<ol
class="code text"><li><code
class="code">alias mysqlstart='sudo /opt/local/share/mysql5/mysql/mysql.server start'</code></li><li><code
class="code">alias mysql='/opt/local/lib/mysql5/bin/mysql'</code></li><li><code
class="code">alias mysqladmin='/opt/local/lib/mysql5/bin/mysqladmin'</code></li></ol> When you're done, save and<ol
class="code command"><li><code
class="command">source ~/.profile</code></li></ol></li><li>Start MySQL server:<ol
class="code command"><li><code
class="command">mysqlstart</code></li></ol></li><li>Next we need to deal with making the database secure and setting the first all-important password. The most complete way to do this is running another utility that takes you through the decisions.<ol
class="code command"><li><code
class="command">/opt/local/lib/mysql5/bin/mysql_secure_installation</code></li></ol> The script offers to delete some test users and databases that in my experience are totally useless anyway. Take the advice offered and get rid of all that junk. <br
/> <strong>Remember the password you set for the root user!</strong><ul><li
class="note">You now have a MySQL account named <span
class="quote">root</span> which is not the same as the root user for the machine itself. When using sudo you will use the machine root password (as you have been all along), but when invoking mysql or mysqladmin you will enter the password for the database root account.</li></ul></li><li>As with PHP above, MySQL has example config files for you to choose from. The config file can be placed in a bunch of different places, and depending on where you put it, it will override settings in other config files. If you follow this install procedure, you don’t actually need to do anything with the config files; we’ll just be using the factory defaults. But things will work better down the road if you choose a config that roughly matches the way the database will be used.<ol><li>Find where the basedir is. As of this writing it’s <span
class="filesystem">/opt/local</span>, and that’s not likely to change anytime soon, but why take that for granted when we can find out for sure? Let's make a habit of finding facts when they're available instead of relying on recipes like this one.<ol
class="code command"><li><code
class="command">mysqladmin -u root -p variables</code></li><li><code
class="prompt">password: &lt;enter MySQL root user's password&gt;</code></li></ol> A bunch of info will spew across your screen. At this moment, there are two interesting nuggets: basedir and socket. Make a note of them for later.</li><li>Now it’s time to choose which example config file you want to start with. The examples are in <span
class="filesystem">/opt/local/share/mysql5/mysql/</span>, and each has a brief explanation at the top that says what circumstances it’s optimized for. You can read those, or just choose one based on the name. If you have no idea how big your database is going to be, medium sounds nice. You can always swap it out later.</li><ol
class="code command"><li><code
class="command">sudo cp /opt/local/share/mysql5/mysql/my-medium.cnf &lt;basedir&gt;/my.cnf</code></li></ol> Fill in &lt;basedir&gt; with the basedir you learned in the previous step.</li></ol></li><li>Test MySQL<ol><li>On the command line, type<ol
class="code command"><li><code
class="command">mysql -u root -p</code></li><li><code
class="prompt">password: &lt;enter MySQL root user's password&gt;</code></li></ol> and enter the MySQL root user password when prompted. No errors? Cool. We’re done here. Type<ol
class="code command"><li><code
class="command mysql">exit</code></li></ol> at the prompt.</li></ol></li><li
class="milestone"><span>MILESTONE</span> - MySQL server is running and happily talking to itself.</li></ol></div><div
class="major-section"><h3>Teach PHP where to find MySQL</h3><ol><li><p>The database is up and running; now we need to give PHP the info it needs to access it. There's a thing called a socket that the two use to talk to each other. Like a lot of things in UNIX the socket looks like a file.</p><p>The default MySQL location for the socket is in <span
class="filesystem">/tmp</span>, but MacPorts doesn’t play that way. There are a couple of reasons that <span
class="filesystem">/tmp</span> is not an ideal place for the socket anyway, so we’ll do things the MacPorts way and tell PHP that the socket is not at the default location. To do this we edit <span
class="filesystem">/opt/local/etc/php5/php.ini</span>.</p><p>There are three places where sockets are specified, and they all need to point to the correct place. Remember when you saved the socket variable from MySQL before? Copy that line and then search in your php.ini file for three places where is says <code>default_socket</code>:</p><ol
class="code text"><li><code
class="code">pdo_mysql.default_socket = &lt;paste here></code></li><li><code
class="code">.  .  .</code></li><li><code
class="code">mysql.default_socket = &lt;paste here></code></li><li><code
class="code">.  .  .</code></li><li><code
class="code">mysqli.default_socket = &lt;paste here></code></li></ol><p>In each case the <code>whatever =</code> part will already be in the ini file; you just need to find each line and paste in the correct path.</p></li><li>While we’re editing the file, you may want to <a
href="http://php.net/manual/en/datetime.configuration.php">set a default time zone</a>. This will alleviate hassles with date functions later.</li><li>Finally, we need to install the PHP module that provides PHP with the code to operate on MySQL databases.<ol
class="code command"><li><code
class="command">sudo port install php5-mysql</code></li></ol></li><li>Restart Apache:<ol
class="code command"><li><code
class="command">apache2ctl restart</code></li></ol></li><li>Test the connection.<ol><li>Typing<ol
class="code command"><li><code
class="command">php -i | grep -i 'mysql'</code></li></ol> Should get you a list of a few mysterious lines of stuff.</li><li>Second test: The whole bag of marbles. You ready for this?<br
/><ol><li>In the Apache’s document root (where the index.php file you made before lives), create a new file named testmysql.php</li><li>In the file, paste the following: <br
/><ol
class="code text" style="width:450px;"><li><pre><code class="code">&lt;?php</code></pre></li><li><pre><code class="code">$dbhost = 'localhost';</code></pre></li><li><pre><code class="code">$dbuser = 'root';</code></pre></li><li><pre><code class="code">$dbpass = 'MYSQL_ROOT_PASSWRD';</code></pre></li><li><pre><code class="code">$conn = mysql_connect($dbhost, $dbuser, $dbpass);</code></pre></li><li><pre><code class="code">if ($conn) {</code></pre></li><li><pre><code class="code">    echo 'CONNECT OK';</code></pre></li><li><pre><code class="code">} else {</code></pre></li><li><pre><code class="code">    die ('Error connecting to mysql');</code></pre></li><li><pre><code class="code">}</code></pre></li><li><pre><code class="code">$dbname = 'mysql';</code></pre></li><li><pre><code class="code">mysql_select_db($dbname);</code></pre></li></ol></li><li>Edit the file to replace MYSQL_ROOT_PASSWRD with the password you set for the root database user.</li><li>Save the file.</li></ol><li>In your browser, go to <a
href="http://127.0.0.1/testmysql.php">http://127.0.0.1/testmysql.php</a></li><li>You should see a message saying “Connection OK”</li></ol></li><li
class="milestone"><span>MILESTONE</span> - Apache, PHP, and MySQL are all working together. High-five yourself, bud! You are an IT God!</li></ol></div><div
class="major-section"><h3>Set up virtual hosts.</h3><p>Finally, we will set up virtual hosts. This allows your server to handle more than one domain name. Even if you don't think you need more than one domain, it's a safe bet that before long you'll be glad you took care of this ahead of time.</p><p>We will create a file that tells Apache how to decide which directory to use for what request. There is an example file already waiting for us, so it gets pretty easy.</p><ol><li>Tell Apache to use the vhosts file. To do this we make one last edit to httpd.conf. After this, all our tweaks will be in a separate file so we don’t have to risk accidentally messing something up in the master file.<ol><li>In <span
class="filesystem">/opt/local/apache2/config/httpd.conf</span>, find the line that says<ol
class="code text"><li><code
class="code">#Include conf/extra/httpd-vhosts.conf</code></li></ol> and remove the #.</li><li>The # told Apache to ignore the include command. Take a look at all those other files it doesn’t include by default. Some of them might come in handy someday...</li><li>Save the file and restart Apache</li><li>Test by going to your old friend <a
href="http://127.0.0.1">http://127.0.0.1</a></li><li>Forbidden! What the heck!?! Right now, that's actually OK. The vhosts file is pointing to a folder that doesn't exist and even if it did it would be off-limits. All we have to do is modify the vhosts file to point to a directory that actually does exist, and tell Apache it's OK to load files from there.</li></ol></li><li>Before going further, it's probably a good idea to figure out where you plan to put the files for your Web sites. I've taken to putting them in <span
class="filesystem">/opt/local/www/domain.com/public/</span> - not through any particular plan, but <span
class="filesystem">/opt/local/www</span> is the default location for phpMyAdmin and I just went with it. The <span
class="quote">public</span> part is so you can have other files associated with the site that are not reachable from the outside.</li><li>Set up the default host directory<ol><li>Open <span
class="filesystem">/opt/local/apache2/conf/extra/httpd-vhosts.conf</span> for editing.</li><li><p>You will see two example blocks for two different domains. Important to note that if Apache can’t match any of the domains listed, it will default to the first in the list. This may be an important consideration for thwarting mischief.</p><p>The examples provided in the file accomplish one of the two things we need to get done — they tell Apache what directory to use for each domain, but they do nothing to address what permissions Apache has in those directories. A lot of people put the permissions stuff in the main httpd.conf, but why not keep it all in one place and simplify maintenance while we reduce risk?</p><p>Here's an example:</p><ol
class="code text"><li><pre><code class="code">&lt;VirtualHost *:80></code></pre></li><li><pre><code class="code">    ServerAdmin you@your.email.com</code></pre></li><li><pre><code class="code">    DocumentRoot "/opt/local/www/mydomain.com/public"</code></pre></li><li><pre><code class="code">    ServerName mydomain.com</code></pre></li><li><pre><code class="code">    ServerAlias www.mydomain.com</code></pre></li><li><pre><code class="code">    ErrorLog "logs/mydomain.com-error_log"</code></pre></li><li><pre><code class="code">    CustomLog "logs/mydomain.com-access_log" common</code></pre></li><li><pre><code class="code">    &lt;Directory "/opt/local/www/mydomain.com/public"></code></pre></li><li><pre><code class="code">        Options FollowSymLinks</code></pre></li><li><pre><code class="code">        AllowOverride None</code></pre></li><li><pre><code class="code">        Order allow,deny</code></pre></li><li><pre><code class="code">        Allow from all</code></pre></li><li><pre><code class="code">    &lt;/Directory></code></pre></li><li><pre><code class="code">&lt;/VirtualHost></code></pre></li></ol><p>You can see where it sets what directory to go to, where it says to treat www.mydomain.com the same as mydomain.com, and then in the Directory block it sets permissions. The actual permissions instructions are pretty arcane. The most important thing to note is the line<ol
class="code text"><li><code
class="code">AllowOverride none</code></li></ol> <strong>This is not typical</strong>, but it's better, as long as you don't forget you did it.</p><p>Here's the skinny: A lot of web apps like WordPress and Drupal need to set special rules about how certain requests are handled. They use a file called .htaccess to set those rules. By setting <code>AllowOverride none</code> you're telling Apache to ignore those files. Instead, you can put those rules right in the &lt;Directory> blocks in your vhosts file. It saves Apache the trouble of searching for .htaccess files on every request, and it's a more difficult target for hackers. .htaccess is for people who don't control the server. You do control the server, so you can do better.</p><ol
class="note"><li
class="note">If others will be putting sites on the server and you don't want them fiddling with the config files, you can allow .htaccess to override specific parameters. Read up in the Apache docs to learn more.</li><li
class="note">If you are using SSL, you also need to set up a VirtualHost entry for port 443. That entry will also include the locations of the SSL certificates.</li></ol></li><li>Add further blocks that match the domains you will be hosting.</li><li>Restart Apache and test your setup. <a
href="http://127.0.0.1">http://127.0.0.1</a> should go to your default directory. Testing the domains is trickier if you don’t have any DNS entries set up for that server. I’ll write up a separate document about using /etc/hosts to create local domains for this sort of test.</li></ol></li><li
class="milestone"><span>MILESTONE</span> - You have done it. A fully operational LAMP environment on your Mac, suitable for professional Web hosting.</li></ol></div><div
class="major-section"><h3>(Optional) Install phpMyAdmin</h3><p>phpMyAdmin makes some database operations much easier. There have been security issues in the past, so you might reconsider on a production machine, but on a development server it can be a real time saver.</p><ol><li><ol
class="code command"><li><code
class="command">sudo port install phpMyAdmin</code></li></ol></li><li>Update your Virtual Hosts with the domain you want to use to access phpMyAdmin, which is by default at <span
class="filesystem">/opt/local/www/phpmyadmin/</span></li><li>test - log in as root.</li><li>Configure - configuring phpMyAdmin fills me with a rage hotter than a thousand suns. It just never goes smoothly for me, whether I use their helper scripts or hand-roll it while poring over the docs. Maybe if I do it a few more times I’ll be ready to write a cookie-cutter guide for that, too. In the meantime, you’re better off getting advice on that one elsewhere.</li></ol></div><div
class="major-section"><h3>Wrapping Up</h3><p>I hope this guide was useful to you. I'm he kind of guy who learns by doing, and I've made plenty of mistakes in the past getting this stuff working. Funny thing is, when it goes smoothly, you wonder what the big deal was. Hopefully you're wondering that now.</p><p>If you find errors in this guide, please let me know. Things change and move, and I'd like this page to change and move with them.</p><p><strong>Keep up to date:</strong> One of the big advantages of this install method is that updates to key software packages get to your server faster. <strong>Use that power.</strong> Run the update commands listed in step one regularly.<ol
class="note"><li
class="note">The script that tests the PHP-MySQL connection is based on one I found at <a
href="http://www.pinoytux.com/linux/tip-testing-your-phpmysql-connection">http://www.pinoytux.com/linux/tip-testing-your-phpmysql-connection</a></li></ol></div><div
class="major-section"><h3>Appendices</h3><h4>Appendix 1: A brief explanation of sudo</h4><p>In the UNIX world, access to every little thing is carefully controlled. There's only one user who can change anything they want, and that user is named root.</p><p>When you log in on a Mac, you're not root, and good thing, too. But as an administrator, you can temporarily assume the root role. You do this by preceding your command with <code>sudo</code>. (That's an oversimplification, and you will have earned another Geek Point when you understand why. In the meantime, just go with it. <code>sudo</code> gives you power.)</p><p>When you use sudo, you type your password and if the system recognizes you as an administrator it will let you be root for that command.</p><p>For convenience, you only have to type your password every five minutes, but you do need to repeat 'sudo' for each command.</p><p>Just remember, as root you can really mess things up.</p><a
name="ap2"><h4>Appendix 2: On editing text files and permissions</h4></a><p><span
class="quote">Jerry told me to edit the file,</span> you lament, <span
class="quote">but he didn't say <em>how</em>.</span> Kind of strange, considering the minute detail of the rest of the guide. The thing is, there's not one easy answer.</p><p>Let's start with the two kinds of text editors. There are editors like vim and pico that run right in terminal. They are powerful, really useful for editing files on a remote box, and if you know how to use them you're not reading this footnote. The other option is a windowed plain-text editor. TextEdit is <strong>NOT</strong> a plain-text editor. There are a lot of plain-text editors out there, and they all have their claims to fame. You can use any of them to edit these files.</p><p>Whoops! That brings us to the gotcha: <em>permissions</em>. In UNIX, who can change what is tightly controlled. Many of the files we need to edit are owned by root, the God of the Machine, so we need to get special permission to save our changes. Many of the plain-text editors out there will let you open the file, but when it comes time to save... they can't. You don't have permission.</p><p>Some editors handle this gracefully, however, and let you type your admin password and carry on. BBEdit and its (free) little brother TextWrangler give you a chance to type your password and save the file. I'm sure there are plenty of others that do as well.</p><p>BBEdit and TextWrangler also allow you to launch the editor from the command line, so where I say above <span
class="quote">edit ~/.profile</span>, you can actually type <code
class="example command">edit&nbsp;~/.profile</code> and if you have TextWrangler installed, it will fire right up and you'll have taken care of the permissions issue. (If you decided to pay for BBEdit, the command is <code
class="example command">bbedit&nbsp;~/.profile</code>.) I'm sure there are plenty of other editors that do that too.</p><p>I'm really not endorsing BBEdit and TextWragler here; they just happen to be the tools I picked up first. Over time I have become comfortable with their (let's call them) quirks. Alas, finding your text editing answer is up to you. If you're starting down this path, it's only a matter of time before you pick up rudimentary vim or pico skills; eventually you'll be using your phone to tweak files while you're on the road. It's pretty empowering. But is now the time to start learning that stuff? Maybe not. It's your call.</p></div></div> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/lamp-server-from-scratch-with-macports/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>I Just Slid Wikipedia a Couple of Bucks</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/i-just-slid-wikipedia-a-couple-of-bucks/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/i-just-slid-wikipedia-a-couple-of-bucks/#comments</comments> <pubDate>Thu, 15 Dec 2011 05:59:42 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10701</guid> <description><![CDATA[Because it's useful to me.]]></description> <content:encoded><![CDATA[<p>I use Wikipedia regularly, and apparently it&#8217;s costing them a bundle to keep the servers going. While I have on occasion had issues with the way they run things, overall this is shaping up to be a humanity-changing effort. So I slid them a couple of bucks. If you use Wikipedia a few times a week, you should too. They&#8217;re looking for big donations, but if everyone voluntarily pays just a little we get closer to the utopian ideal.</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/i-just-slid-wikipedia-a-couple-of-bucks/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>They ARE Watching You</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/they-are-watching-you/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/they-are-watching-you/#comments</comments> <pubDate>Mon, 21 Nov 2011 23:34:18 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[privacy]]></category> <category><![CDATA[security]]></category> <category><![CDATA[suck]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10539</guid> <description><![CDATA[I'm late to the party with this particular hand-wringing, but it seems the tempest blew over without much discussion of the actual problem.]]></description> <content:encoded><![CDATA[<p>Near the beginning of the novel 1984, Winston Smith is in his apartment, doing his state-mandated exercises in front of the TV. Suddenly a voice blares from the speaker and reprimands him for not making more of an effort. We learn at that moment that the telescreen is a two-way device; it watches you as you&#8217;re watching it.</p><p>Now we call that machine Kinect for XBOX Live.</p><p>Some of this is old news in privacy circles; it was more than a year ago that Microsoft first <a
href="http://www.engadget.com/2010/11/15/microsoft-exec-caught-in-privacy-snafu-says-kinect-might-tailor/">bragged to investors</a> that the Kinect platform could be used to gather data on people using their product &#8212; what people are wearing, and things like that. This is what happens when you have a Web-cam in the house that&#8217;s always connected to the Internet, and someone you don&#8217;t know is on the other end.</p><p>Well, as you might expect, these revelations raised quite a kerfuffle. Microsoft very quickly and very loudly <strong>promised</strong> not to use data gathered through the camera in your home for targeted advertising. In the articles I read, journalists took two approaches:</p><ol><li><em>Whew! I&#8217;m sure glad Microsoft promised not to be evil!</em></li><li><em>You know, targeted advertising isn&#8217;t as bad a people keep claiming. Relax and get information tailored to you.</em></li></ol><p>The commentary, and Microsoft&#8217;s reassurances, miss the point entirely. With the government pulling flagrant rights violations like <a
href="http://en.wikipedia.org/wiki/National_Security_Letter">National Security Letters</a>, how long before the video feed in your living room is handed over to the FBI? Hell, it might have happened already. Microsoft would be legally barred from telling anyone it even happened. This is the state of our constitution these days.</p><p>(If the government really thinks this is all cool and the public wouldn&#8217;t mind, why do they work so hard to keep it secret?)</p><p>There are ways to prevent the video feed from reaching the outside world, but as I understand it, the default is always on. Not only can it report what game (or political convention) you&#8217;re watching, it can report when you cheer. Better think twice about that Che Guevara poster on the far wall from the TV. My video-game playing, dope-smoking neighbors may not be too concerned about privacy anyway (judging by the clouds drifting through the neighborhood), but I doubt they&#8217;d feel great about knowing they have a live video feed that any government monkey with a frightening letter will be able to watch.</p><p>Let me repeat that just so I&#8217;m clear: Any government monkey with a frightening letter will have access to a live video feed from your living room, as well as every email you&#8217;ve ever sent and what you checked out at the library. Things are bad enough without handing them the most invasive tool yet to pry into your lives.</p><p>I would LOVE to see a big company like Microsoft stand up to the government and publish a policy that states that they will not surrender the feed without a legal warrant signed by a judge. The chances of that actually happening are zero &#8212; unless Microsoft thinks it&#8217;s losing a very large amount of business due to those privacy concerns. That&#8217;s not an indictment of Microsoft, I doubt any major US corporation is ready to go to the mat with the Feds on this one.</p><p>Microsoft once more finds itself in the very familiar position of creating something that sounds really cool without considering all the consequences, much like when they put into Microsoft Office a system specifically tailored for adding executable code to Office documents. Office automation, they called it. A great time-saver. &#8220;Capital idea!&#8221; shouted the virus writers with glee. Now once more Microsoft has come up with something that is almost magic in how it works (e.g., parental controls based on the metrics of the people in the room), but those things require the camera to be on, even when you&#8217;re just watching TV.</p><p>If someone gave me a free Kinect and XBOX, I&#8217;d probably use it. But I&#8217;d be very, very careful about when the Internet connection is active. And, while exercising I&#8217;ll be sure to give it my all.</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/they-are-watching-you/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>Class A, Baby!</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/class-a-baby/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/class-a-baby/#comments</comments> <pubDate>Sun, 06 Nov 2011 20:15:32 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[Internet]]></category> <category><![CDATA[technology]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10472</guid> <description><![CDATA[Where have all the numbers gone?]]></description> <content:encoded><![CDATA[<p>Usually I blame the Chinese for every shortage or surfeit, and while they are definitely participating in this particular drought, it would be difficult to pin the blame wholly on them. Much of the problem lies closer to home.</p><p>You see, the world is running out of IP addresses. An IP address is like a computer&#8217;s phone number on the Internet. When you type muddledramblings.com, you start a complicated series of interactions (&#8220;I don&#8217;t know where that is, but I know who to ask&#8230;&#8221;) out there in the Interwebs and eventually it is resolved that what you&#8217;re looking for is computer 173.245.60.121. You get the same answer for JersSoftwareHut.com and jerryseeger.com. (That&#8217;s actually an IP owned by CloudFlare, who sends things on to the actual IP of 66.116.108.197. But that&#8217;s not what matters here&#8230;)</p><p>At the time of this writing, jer.is-a-geek.com resolves to 98.210.116.58, the IP of my home router. The actual number may change, but there will always be an ip address used up by the router. (Don&#8217;t bother going there; there&#8217;s nothing to see unless you use ssh and already have a key installed on your computer. (The key file itself is locked with a password I may have forgotten.))</p><p>Anyway, the IP address is a finite number, and so there is a limit to the total number of computers connected directly to the Internet. This is a very, very big number, but when they came up with the number they didn&#8217;t think people&#8217;s toasters (and telephones, and cars) would be connected to the Internet. (In your house, most likely your computers and other gadgets go through a router or a modem. That router has to have a unique ID, but the rest of your network uses a special range of IP&#8217;s reserved for internal networks. So, your household only eats up one of the limited supply.)</p><p>We are starting to reach the limits of the IP system, just as in the US there was a shortage of telephone numbers. (Some of the reasons we ran out of phone numbers are similar as well, as I&#8217;ll mention in a bit.)</p><p>With phone numbers they split areas into smaller chunks, and created new area codes. While there was the inconvenience of people&#8217;s area codes changing, everything still worked.</p><p>The Techno-Wizards who run the Internet saw the IP problem coming some time ago, and set out to solve it. What they came up with was IPv6 (currently we are using IPv4). The only problem: the two systems are not compatible. So now a new network based on IPv6 is being deployed, and the people on it can&#8217;t look at Web sites that have IPv4 addresses without some sort of middleman. Sucks to be one of those guys. (Muddled Ramblings is now visible on the IPv6 network thanks to CloudFlare.)</p><p>Meanwhile, at work, my team needed an IP address for one of our servers. We were advised by a coworker to just go ahead and grab a block of 256 addresses, so we&#8217;d have them if we needed them. Really? When IP addresses are running out?</p><p>Yep. It turns out that long ago, organizations who were on the ball could buy up huge blocks of IP addresses on the cheap. MIT bought a Class A* block, as did Stanford (who has given it back, I believe), the Army National Guard, IBM, HP (they have DEC&#8217;s block now, too, I think), and Apple. Each Class A block has almost 17 million IP addresses, and represents a significant chunk of all the IP addresses available.</p><p>The US military has several blocks, and the British military has some as well.</p><p>Oh, and Amateur Radio Digital Communications has a Class A, along with Prudential Securities. Ford and Daimler. Three or four pharmaceutical companies. (I imagine Merck or whoever bought one, and their competitors followed suit out of habit.)</p><p>I think you might now be getting a glimpse of a core problem. The huge blocks of IP addresses were allotted to whoever <em>asked</em> for them, with no requirement that the organization actually show that they <em>needed</em> them or would not hoard them. Does Ely Lilly have a side business as a data center?</p><p>A possibly-apocryphal story I was told the other day: Back when IPs were up for grabs, someone at Apple proposed that they snag a Class A. The powers that be decided against the move, so he got the purchase of the block wedged into the budget for something completely unrelated. It turns out to have been a pretty savvy move. Now every IP address that starts <i>17.</i> belongs to Apple.</p><p>Of the companies on that list, I&#8217;d certainly say Apple has more business owning a Class A block than many of the others. Whether the US Military really needs all those huge blocks I&#8217;m not qualified to argue. But the fact remains that while we would be running out of IP addresses eventually anyway, the careless and haphazard way they were originally handed out exacerbated the problem mightily.</p><p>I mean, does the Department of Social Security in the UK <em>really</em> need 16.7 million IP addresses? Really?</p><p>* The term &#8216;Class A&#8217; is a little out of date, but reads better than &#8216;/8 block&#8217;</p><p><strong>Note 1:</strong> I got my information here and there on the Internet, then found it all <a
href="http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_address_blocks">here</a>.</p><p><strong>Note 2:</strong> This episode contains a lot of parenthetical comments, part of my crusade to address the global overabundance of parentheses. I encourage you to use a few extras as well, until supply is back in balance with demand. (As usual, I blame the Chinese for the surfeit.)</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/class-a-baby/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Science</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/science/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/science/#comments</comments> <pubDate>Tue, 25 Oct 2011 23:47:17 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[science]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10429</guid> <description><![CDATA[It's not the answer to everything. Real scientists know that. Fake scientists don't even know what that means.]]></description> <content:encoded><![CDATA[<p>A few years ago I was at a party, and I was talking to a guy I&#8217;d met a few times before. &#8220;I don&#8217;t believe in X,&#8221; he said (I have no recollection what X was), just like I don&#8217;t believe in relativity.&#8221;</p><p>I was young, and perhaps naïve, but I didn&#8217;t think relativity was a candidate to be part of a belief system. &#8220;What do you mean, you don&#8217;t believe in relativity?&#8221; I asked. Here was a chance, I thought, to explain the principle to someone who didn&#8217;t understand it.</p><p>I failed. I failed and got very frustrated, angry at myself for not explaining things better. Angry that I had not even put doubt into the non-believer. It went like this: He explained something he called &#8220;the inertia problem.&#8221; I assumed he&#8217;d picked it up from a book by some &#8216;rogue&#8217; physicist (more on them later). He described the inertia problem. It was nonsensical and even if you helped it along a bit with incorrect terminology, it still had <em>absolutely nothing to do with relativity</em>.</p><p>In retrospect, I enumerated a few options how to proceed:</p><ul><li>Ask, &#8220;What does that have to do with relativity?&#8221; and address the incorrect linkages specifically.</li><li>Say, &#8220;Look, relativity has been <em>measured</em> over and over, in different ways, from the orbit of Mercury to clocks in the Apollo capsules. The work my own father does would simply <em>break</em> without it.&#8221;</li><li>Ask &#8220;Do you believe in gravity? Because that&#8217;s a hell of a lot more mysterious than relativity.&#8221;</li><li>Say, &#8220;Fortunately, relativity doesn&#8217;t need your faith to work.&#8221;</li><li>I could treat the &#8220;inertia problem&#8221; as a credible theory, work my ass of to recast it in terms that actually meant something, then demonstrate that my construct was, in fact, not in disagreement with relativity.</li></ul><p>I think you can guess which course I took. Perhaps all of the above would have failed (more on that later, too), but just mentioning personal experience and giving a taste of the enormous pile of things that have verified relativity in the past century might have provided enough skepticism that at least the Unbeliever would not spread his Unfaith as fervently. (I wonder if he uses a GPS now? I wonder if he knows he&#8217;s using relativity?)</p><p>This guy thought of himself as a skeptic, as someone who didn&#8217;t just believe what everyone else did. In fact, he was not a skeptic at all. He was Rogue wanna-be. The way to convince him of something was to start with, &#8220;The establishment doesn&#8217;t want me to say&#8230;&#8221; and then say something that implies special knowledge that no one else has. Some idiot whose concept of physics is mired in the 1850&#8242;s writes a book saying that relativity is bogus, and members of the Rebel Dalliance hoist him on their shoulders. Stick it to the man! Believe a quack for no other reason than he says the establishment is wrong!</p><p>There&#8217;s never been a moon landing! Never mind that the junk is up there, in plain sight. For some reason Russia and China continue to cooperate with the US to perpetuate a hoax forty years later. Why do people believe that? Because it&#8217;s fun to style oneself as a rogue. As long as you only talk to other members of the Rebel Dalliance, you don&#8217;t have to discover that you&#8217;re an idiot.</p><p>Which brings me to evolution. Lots of people in this country don&#8217;t believe in it. As I could have said to the guy who didn&#8217;t believe in relativity, evolution doesn&#8217;t require their faith to work. The part that sticks in my craw is the large number of anti-evolution salesmen who claim that there are other scientifically-viable theories. Intelligent design and whatnot. A handful of &#8216;rogue&#8217; scientists have done well for themselves proposing plausible-sounding stories and selling them as science. People will pay you to tell them what they want to hear.</p><p>Those theories are not science. In fact, they&#8217;re not even theories. A better name for &#8216;rogue scientist&#8217; is &#8216;salesman&#8217;. Anyone who claims to be a scientist must always be ready to listen to more evidence and modify or scrap his favorite theory. It happens. But in science, even the guys who are wrong are improving the process, bringing up proposals and, most importantly, new tests to challenge the status quo. Sometimes (well, often) pride gets tangled up in things, but even then they are not rogues, they are stubborn scientists.</p><p>Science is about letting go. People who say science is messed up because people used to believe one thing but now believe something else are in fact demonstrating the strength of science. We learn. We grow. We change.</p><p>&#8220;I believe God made Adam from clay,&#8221; is perfectly all right with me. I have no difficulty with faith; it&#8217;s about the unknowable, about the places science can&#8217;t reach. Just don&#8217;t try to clothe faith in science and wedge it into the science curriculum at my local school.</p><p>If your theory can&#8217;t be tested, it&#8217;s not science. This is currently a hot topic at the most esoteric level of physics. The math works, but it&#8217;s hard to test without exploding suns to get the energy required. There are a lot of folks, promoters and skeptics alike, searching for planet-earth size experiments to test the math.</p><p>So, scientific theories have to be testable. Even that&#8217;s not enough, though. How many times have you started a sentence with &#8220;A study showed that&#8230;?&#8221; A bunch of times, right? Me, too. And I will again. Some of those studies are pretty crazy. But while you do it, remember this: <em>A study has never shown anything.</em> Ever. A single study is so vulnerable to mistakes and misinterpretation that you can never draw broad conclusions. The study has to be replicated, by someone else, using methods that answer questions raised by outsiders about the first study.</p><p>Remember cold fusion? Some guys were so excited about the result of their experiment that they bypassed normal science channels and went mainstream. The economic implications of their study were so world-changing that the entire scientific community dropped what they were doing to try to replicate that experiment in a hundred different ways. Turns out, the original experiment was flawed. (Somewhere, there&#8217;s a ROGUE SCIENTIST selling books telling of the coverup of cold fusion.)</p><p>Scientific evidence has to be repeatable. <em>Predictably</em> repeatable. Every measurement has to have an estimate of the likelihood that it&#8217;s wrong.</p><p>The biggest problem with teaching creationism alongside evolution in schools is that it clouds what science even <em>is</em>. Creationism as an &#8216;alternate theory&#8217; totally confuses the definition of &#8216;theory&#8217;. When discussing science, creationism is most certainly <em>not</em> a theory. It can&#8217;t be tested. I don&#8217;t care what you think about dinosaurs; you could leave them out of the curriculum and I wouldn&#8217;t mind that much (the kids will supplement their own education on that score), but please, please, teach what science is, and even more importantly, what it isn&#8217;t.</p><p>Sooner or later our government will be filled with people who don&#8217;t even understand the nature of science, its strengths and weaknesses, yet they will be making critical decisions based on science. Ah, shit. That&#8217;s happened already.</p><p>If we all knew what science was, then when some oil-company-funded pundit comes on TV to &#8216;debunk&#8217; global warming with feel-good talk about economic growth, the token scientist in studio to rebut could simply say, &#8220;that&#8217;s not science,&#8221; and the nation would nod and disregard the previous bloviations. &#8220;Now,&#8221; the anchor will say, &#8220;We can get to the real debate: what to do about it.&#8221;</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/science/feed/</wfw:commentRss> <slash:comments>4</slash:comments> </item> <item><title>The Rise and Fall of Adobe Flash</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/the-rise-and-fall-of-adobe-flash/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/the-rise-and-fall-of-adobe-flash/#comments</comments> <pubDate>Mon, 10 Oct 2011 18:12:15 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[Edge]]></category> <category><![CDATA[Flash]]></category> <category><![CDATA[Internet]]></category> <category><![CDATA[technology]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10390</guid> <description><![CDATA[The next generation has arrived.]]></description> <content:encoded><![CDATA[<p>A long, long time ago, I wanted to make lava lamp buttons for my Web site. I wanted the shape of the lava blobs to be random and mathematically controlled, and it had to be done with vector graphics &#8211; animated gifs would have been huge to provide something that even remotely felt random, and back in those days most people connected with dialup modems.</p><p>I searched high and low for a vector animation tool and couldn&#8217;t find one. There was Macromedia Director, which I used extensively back then, which put out files for Web play in a format called Shockwave, but it wasn&#8217;t a true vector-based program. Not the right tool for lava lamp buttons, that was for sure. I&#8217;d started playing with a java applet to draw my buttons, but it seemed like vector animation was something the Web really needed. I mentioned this to a friend of mine, and he said, &#8220;Oh I know some guys with the tool you&#8217;re looking for.&#8221; At the time it was called FutureSplash.</p><p>I mentioned FutureSplash to my boss. It was going to be huge, I predicted. His response: &#8220;Maybe we should buy them.&#8221; (Ah, those dot-com boom days, how I miss them.) Three days later Macromedia announced that <em>they</em> had bought FutureSplash (for a <em>lot</em> more than we could have paid) and contracted the name to Flash.</p><p>The rest is history &#8212; until the present.</p><p>There was even a time when I imagined that a lot of the Web would end up as Flash. Or at least it <em>should</em>. Flash had a lot of things right that HTML had managed to screw up. You could do a lot more, and with Flash the Web experience began to approach the quality of experience people had in other parts of their computing lives.</p><p>Macromedia and later Adobe seemed to go out of their way to prevent Flash from taking over the Web. Creating Flash became ever more complex and ever more expensive. Nowhere was the simple &#8220;baby Flash&#8221; that Joe Amateur could use to build a nice site without first getting extensive training and shelling out a few hundred bucks for tools.</p><p>Meanwhile, Flash designers didn&#8217;t help in those early years, either. So much Flash became &#8220;look what I can do&#8221; rather than &#8220;look how I can make your visit to my Web site better&#8221; that Jane Surfer started resenting Flash. &#8220;I waited 60 seconds to download <em>this?</em>&#8221; A good example of that sort of waste is at the top of this page, in fact. There are a couple of fun things in the banner, but they don&#8217;t enhance the Muddled Experience very much.</p><p>Now, the world is shifting again. If you&#8217;re reading this site from your iPad, you don&#8217;t see the banner at all. No Flash in iOS. This is something the other tablet manufacturers have made a big deal of—but maybe not for very much longer. Microsoft&#8217;s next tablet OS won&#8217;t support Flash, either.</p><p>HTML, the platform I get paid to dislike, is becoming HTML, the platform I get paid to deal with. HTML5, CSS3, full SVG support, and robust JavaScript libraries make possible just about everything Flash can do, without Flash. That&#8217;s a lot of things to learn and manage to get a job done, however. Before, a designer could just master Flash and be confident that their work would look right wherever the Flash plugin was installed.</p><p>What&#8217;s needed is a tool like Flash that, after you&#8217;re done designing, outputs your masterpiece in Web-standard format, with HTML, CSS, and JavaScript. When something like that comes out, the handwriting will be on the wall for Flash.</p><p>And here it is. Adobe, makers of Flash, have announced Edge, the animation tool that will eventually replace Flash. It looks pretty good. It doesn&#8217;t do anything remotely close to what Flash does (no mention of audio that I&#8217;ve found, for instance, so my banner would have to forego the theme song, and interactivity will have to be handled outside the tool as well, as far as my first glance tells me), but it does a great deal, and when you&#8217;re done the product will work in all modern browsers, including mobile ones. Adobe has applied their long, long experience making animation tools to make the user interface slick and clean (though you will want a really big monitor).</p><p>Flash will be around a long, long time yet; it still lets a developer build Web-based user interfaces that would be a pain in the butt to create from HTML and the rest of the alphabet soup. That gap is narrowing, however, and as Edge gains in features (and, alas, complexity), the marginalization of Flash will accelerate. I&#8217;m impressed that Adobe said, &#8220;If Flash dies, we&#8217;ll be the ones to kill it.&#8221; They really are the right people for the job. Now all we need is &#8220;baby Edge.&#8221;</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/the-rise-and-fall-of-adobe-flash/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Seven? Really?</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/seven-really/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/seven-really/#comments</comments> <pubDate>Fri, 07 Oct 2011 22:38:02 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[Internet]]></category> <category><![CDATA[technology]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10374</guid> <description><![CDATA[The truth behind the number surge.]]></description> <content:encoded><![CDATA[<p>A few days ago the Firefox team let forth a new major release. 7.0.1. Seven. That&#8217;s a lot of progress since earlier this year when they floated Firefox 4.</p><p>Most software companies would have labeled this release 4.3. The Firefox team has eschewed the first dot and has decided to make any release with a feature change a new major release. There is no n.1; the first decimal digit is entirely vestigial. There was no 4.1. There was no 5.1 or 6.1 There will be no 7.1, just 7.0.1. This might sound stupid, unless you have Inside Information. Which I have, thanks to Wikipedia.</p><p>The Internet Explorer team at Microsoft, sworn rivals of Firefox, are nonetheless ok guys who want to make this whole Web thing work. Back in the day when the Firefox team kicked the ass of the web world and released a browser that not only defined standards but provided the tools to help Web developers code to those standards, team FF were the guys to beat. On the release of FF3, the boys at Microsoft sent the team a cake. Firefox 4 was similarly honored. And FF5. And so on.</p><p>And now we see the real reason behind the accelerated numbering. Each major release gets a cake. If I was in charge, there&#8217;d be a new major version every Thursday.</p><p>* The firefox team joked about sending a cake to Microsoft to honor IE 8 (or 7 or 9 and you shouldn&#8217;t ask me to remember shit like that), but they would send the cake along with the recipe. Open-source cake. But (as far as history records) they didn&#8217;t. Would&#8217;a been funny. There&#8217;s talk and there&#8217;s action, and seriously you don&#8217;t want to be on the losing side of that with Microsoft.</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/seven-really/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Then there&#8217;s Incapsula</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/then-theres-incapsula/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/then-theres-incapsula/#comments</comments> <pubDate>Sun, 25 Sep 2011 01:38:52 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[CloudFlare]]></category> <category><![CDATA[Incapsula]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10361</guid> <description><![CDATA[I&#8217;ve written about CloudFlare in the past. I think it&#8217;s a no-brainer for small-time bloggers like me who control their own domain name registry. My writing has attracted the attention of another company, Incapsula, who offer a similar service. Incapsula would love for me to give them a try, so I can write about them, [...]]]></description> <content:encoded><![CDATA[<p>I&#8217;ve written about CloudFlare in the past. I think it&#8217;s a no-brainer for small-time bloggers like me who control their own domain name registry. My writing has attracted the attention of another company, Incapsula, who offer a similar service.</p><p>Incapsula would love for me to give them a try, so I can write about them, too. They&#8217;re under the impression that I have some sort of influence in the world. Ha! They&#8217;ve even offered me a free upgrade to the &#8216;pro&#8217; level of the service. One really cool thing about the upgrade: out-of-the-box SSL, which means you don&#8217;t have to get your own certificate to handle commerce. Certificates can be a real hassle, and a considerable expense.</p><p>The thing is, I&#8217;m pretty happy with CloudFlare. As of today, people on IPv6 can read these words. (Much like telephone numbers in some areas, the world is running out of IP addresses.) I&#8217;ve worked out <a
href="http://muddledramblings.com/rumblings-from-the-secret-labs/bad-behavior-cloudflare-and-google-bot">one kink</a> with the system and things are running smoothly. Does Incapsula have code to install on the server to make it play well with others? I don&#8217;t know.</p><p>Also, I don&#8217;t really <em>need</em> any of the advanced services of either system. I don&#8217;t do e-commerce, which could be a compelling reason to switch and grab my free upgrade.</p><p>I have a couple of terrifically minor quibbles about CloudFlare&#8217;s user interface and flexibility blocking IP ranges, but nothing worth even mentioning here. Logically, I should just stick with CloudFlare and leave it at that.</p><p>Except&#8230;</p><p>That guy they think I am? The one whose words can shift the balance of power in an emerging new market? I&#8217;m not that guy. I&#8217;ll never be that guy unless I devote myself to the task, and I&#8217;ve got other things to write about that are probably more interesting to most of you. But still I <em>want</em> to be the guy they think I am. I want to write the CloudFlare vs. Incapsula smackdown article to which all the pundits refer.</p><p>To do something like that, I&#8217;d have to set up a site to use Incapsula, but I don&#8217;t want to rock the Muddled Boat. I have jerryseeger.com, but what sort of test do I get out of a site that no one ever visits? It&#8217;s a site where acceleration hardly matters because the whole thing is so simple, and there&#8217;s no sign of e-commerce on the horizon. The thing barely even gets spammed.</p><p>Still, I have to think of something&#8230; the public demands it!</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/then-theres-incapsula/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Your Most Important Password</title><link>http://muddledramblings.com/rumblings-from-the-secret-labs/your-most-important-password/</link> <comments>http://muddledramblings.com/rumblings-from-the-secret-labs/your-most-important-password/#comments</comments> <pubDate>Fri, 16 Sep 2011 22:23:50 +0000</pubDate> <dc:creator>Jerry</dc:creator> <category><![CDATA[Rumblings from the Secret Labs]]></category> <category><![CDATA[Internet]]></category> <category><![CDATA[security]]></category><guid
isPermaLink="false">http://muddledramblings.com/?p=10314</guid> <description><![CDATA[I&#8217;ve mentioned passwords before, but today I&#8217;d like to tell you about the most important password in your possession, the single password that keeps the hordes at bay. Take a moment to think about the passwords you use for your various secret stuff. If you&#8217;re like me, you have your ordinary password for unimportant stuff, [...]]]></description> <content:encoded><![CDATA[<p>I&#8217;ve mentioned passwords before, but today I&#8217;d like to tell you about the most important password in your possession, the single password that keeps the hordes at bay.</p><p>Take a moment to think about the passwords you use for your various secret stuff. If you&#8217;re like me, you have your ordinary password for unimportant stuff, then you ratchet up the entropy for sites that involve money. For a long time I had two passwords, my &#8216;secure&#8217; one and my &#8216;other&#8217; one. Now I&#8217;ve started taking my passwords a lot more seriously, which means keeping a file of all my passwords, itself protected with massive encryption and the most awesome passphrase ever. No one&#8217;s getting into that file.</p><p>But here&#8217;s the thing: they don&#8217;t have to. There&#8217;s another password I have that&#8217;s just as powerful and easier for a bad guy to use. My primary email password.</p><p>How does that password drop my trousers universally? Simple: if someone had access to my email, they could click &#8220;I forgot my password&#8221; on every site in the world and harvest the responses. If the evil robot cleared out the emails before I read them, I&#8217;d be none the wiser. And I&#8217;d be fucked.</p><p>You might think your online banking password is the one you must protect most diligently, but your email password will hand them your bank account along with everything else. This is the password to protect and change regularly.</p><p>As an aside, you can make things a little tougher for bad guys by modifying your email address when you register for stuff. For instance, if I register at xyz.com, I might use vikingjs+abc@mac.com for my email address. The cool thing about &#8216;+&#8217; is that it doesn&#8217;t change the delivery (the above will go to vikingjs@mac.com) but you can sort your email based on the suffix, and you can track who gave your email address away. Most significantly, if some wrongdoer has your email password, they still have to guess the +suffix part for each site before they can use the &#8220;I forgot my password&#8221; feature. If your email password gets out, that second line of defense could really save your ass.*</p><p>Also, know that if your email provider gets hacked, you could be hosed. There is one major company (rhymes with achoo!**) that seems to have a hard time keeping the wrong guys out of your account (although I think it&#8217;s the address book that has been compromised, and not direct access to your emails). There are likely others that do a better job keeping their names out of the press when they spill your information.</p><p>So, to flog the horse: If bad guys gets access to your email, they own you. Protect that password diligently. Change it fairly often. Use email+suffix@whatever.com when you sign up for stuff. In databases around the globe, your email is quite literally your entire identity.</p><p>* I read somewhere that hotmail and some others don&#8217;t support the + in emails. I haven&#8217;t tested personally, but if your provider is one of those, drop them immediately and find a better service.</p><p>** I&#8217;m pretty sure I have stock in a company that ends oo!, so I&#8217;m not just slinging mud here.</p> ]]></content:encoded> <wfw:commentRss>http://muddledramblings.com/rumblings-from-the-secret-labs/your-most-important-password/feed/</wfw:commentRss> <slash:comments>6</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Content Delivery Network via Amazon Web Services: S3: muddlebucket.s3.amazonaws.com

Served from: muddledramblings.com @ 2012-02-03 22:39:09 -->
