<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

  <title><![CDATA[f00bar.com]]></title>
  <link href="http://spheromak.github.com/atom.xml" rel="self"/>
  <link href="http://spheromak.github.com/"/>
  <updated>2011-12-11T16:35:27-08:00</updated>
  <id>http://spheromak.github.com/</id>
  <author>
    <name><![CDATA[Jesse Nelson]]></name>
    
  </author>
  <generator uri="http://octopress.org/">Octopress</generator>

  
  <entry>
    <title type="html"><![CDATA[Octopressed]]></title>
    <link href="http://spheromak.github.com/blog/2011/12/10/octopressed/"/>
    <updated>2011-12-10T17:43:00-08:00</updated>
    <id>http://spheromak.github.com/blog/2011/12/10/octopressed</id>
    <content type="html"><![CDATA[<p> Posterous just doesn&#8217;t support markdown very well, and every time I felt like writing a blog entry I would get frustrated. So after a couple people have expressed their pleasure with tools like <a href="http://jekyllrb.com/">jekyll</a> using github pages.  I decided to give it a go.</p>

<p>I love this setup. I tried jumping in with <a href="http://octopress.org/">octopress</a> without the rtfm. Having never setup github pages before i mucked up by creating a project site vs a user site, but once I fixed that (by creating a spheromak.github.com repo) everything clicked in.</p>

<p>Pulling old posterous posts down into <a href="http://jekyllrb.com/">jekyll</a> was simple, and now im off and running with real markdown blog. Backed by git, and I am happier for it.</p>

<p>So thanks <a href="http://github.com">github</a>, <a href="http://jekyllrb.com/">jekyll</a>,  and <a href="http://octopress.org/">octopress</a>  for cool software that works</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[XenServer and shadow passwords]]></title>
    <link href="http://spheromak.github.com/blog/2011/11/02/xenserver-and-shadow-passwords/"/>
    <updated>2011-11-02T00:00:00-07:00</updated>
    <id>http://spheromak.github.com/blog/2011/11/02/xenserver-and-shadow-passwords</id>
    <content type="html"><![CDATA[<p>Why doesn&#8217;t XenServer enable shadow passwords or authconfig.&nbsp; What year is this&nbsp; 1996 ? My guess is so that it can readd the hashed root without privs for things like xencenter to be able to edit the passwd via xapi. Tho i don&#8217;t see any password manipulation api hooks.&nbsp; I am really curious why this isnt set.</p>
<p>I have been manually (well chef does it)&nbsp; setting the dom0 passwords to shadow by detecting if its a xenserver and running pwconv. There hasn&#8217;t been any repercussions in the last 3 years.</p>
<p>Untill now.</p>
<p>Now moving up to xen6 in my test pool im running into all sortsa auth isues requireing me to single user my upgraded Hosts and pwconv and passwd them. Blargh.</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Hosts File LWRP for chef]]></title>
    <link href="http://spheromak.github.com/blog/2011/10/11/hosts-file-lwrp-for-chef/"/>
    <updated>2011-10-11T00:00:00-07:00</updated>
    <id>http://spheromak.github.com/blog/2011/10/11/hosts-file-lwrp-for-chef</id>
    <content type="html"><![CDATA[<p>Just finished making a simple LWRP for managing /etc/hosts with chef check it out on github: <a href="https://github.com/spheromak/cookbooks/tree/master/hosts">https://github.com/spheromak/cookbooks/tree/master/hosts</a></p>
<p>pretty simple/easy to use to manage individual entries in hosts files.&nbsp;</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Arch Linux Developer Vagrant Box]]></title>
    <link href="http://spheromak.github.com/blog/2011/09/21/arch-linux-developer-vagrant-box/"/>
    <updated>2011-09-21T00:00:00-07:00</updated>
    <id>http://spheromak.github.com/blog/2011/09/21/arch-linux-developer-vagrant-box</id>
    <content type="html"><![CDATA[<p><a href="http://vagrantup.com/" title="Vagrant">Vagrant</a> is sweet!, but there wasn&#8217;t a lot of <a href="http://archlinux.org/" title="Arch Linux">arch</a> boxes out there that i could find. So heres my <a href="http://pipe.f00bar.com/Vagrantfile" title="arch_dev Vagrant File">Vagrantfile</a>.</p>

<p>if you don&#8217;t already use <a href="http://vagrantup.com/" title="Vagrant">Vagrant</a> you should. If you are doing any dev you should use it! if your an ops person then you should use it, and tell your developers about it. If you are a nerd you should use <a href="http://vagrantup.com/" title="Vagrant">Vagrant</a>. Nuf said.</p>

<p><a href="http://archlinux.org/" title="Arch Linux">Arch</a> is also pretty sweet. <a href="http://archlinux.org/" title="Arch Linux">Arch Linux</a> has a system approach that rings totally right with me (I feel another post about arch in here someplace). Mainly Arch lets you do what you want how you want which is awesome!</p>

<p>Anyhow I have a little pet project that originally I was gonna do an LFS build up on, but realized arch already had a lot of what I needed. <a href="http://www.freedesktop.org/wiki/Software/systemd" title="ohai systemd">systemd</a> support, and an not ancient/screwed up ruby install.</p>

<ul>
<li><a href="http://pipe.f00bar.com/Vagrantfile" title="arch_dev Vagrant File">My build</a> deviates from base arch in these ways:

<ul>
<li>It&#8217;s running 3.0.4 Kernel</li>
<li>Using <a href="http://www.freedesktop.org/wiki/Software/systemd" title="ohai systemd">systemd</a> (with option to boot sysv)</li>
<li>full developer toolchain.</li>
<li><a href="" title="https://wiki.archlinux.org/index.php/Arch_Build_System">ABS</a> the source build system for Arch.</li>
<li>Its big! ~1.2GB for a base box is pretty big, but its cause of all the build crap + kernel source</li>
</ul>
</li>
</ul>


<p>Lastly heres the links to the <a href="http://pipe.f00bar.com/arch_dev-x86_64.box" title="arch_dev Base Box">base box</a> if you don&#8217;t want to get it via the vagrantfile.</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Simple robust OS detection in bash using $OSTYPE]]></title>
    <link href="http://spheromak.github.com/blog/2011/07/09/simple-robust-os-detection-in-bash-using-ostype/"/>
    <updated>2011-07-09T00:00:00-07:00</updated>
    <id>http://spheromak.github.com/blog/2011/07/09/simple-robust-os-detection-in-bash-using-ostype</id>
    <content type="html"><![CDATA[<p>I was using lazyweb to solve this problem. Google&rsquo;s results had solutions where people were calling all sorts of commands and parsing different files to detect system types. I didn&rsquo;t want to do a syscall. I wanted this solution to be as platform independant as possible. I only needed to know if it was linux/solaris/osx/bsd etc etc.  Not version or somehting special. SImple enough. 1 minute of RTFM&#8217;n the bash manual turned up $OSTYPE and $HOSTTYPE</p>

<p><script src="https://gist.github.com/1074195.js"></script></p>

<p>Man I love simple solutions!</p>

<p>P.S. First post!</p>

<p>P.P.S  posterious&rsquo;s syntax support sucks. took longer to figure out than this post did to write.</p>

<p>edit: converted to markdown  used gist for code highlight</p>
]]></content>
  </entry>
  
</feed>

