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

<channel>
	<title>Phil Hunter &#187; Linux</title>
	<atom:link href="http://blog.philhunter.com/category/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.philhunter.com</link>
	<description>Mac, Linux and everthing else!</description>
	<lastBuildDate>Tue, 01 Jun 2010 20:22:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Samba and OS X permission solution</title>
		<link>http://blog.philhunter.com/2010/06/01/samba-and-os-x-permission-solution/</link>
		<comments>http://blog.philhunter.com/2010/06/01/samba-and-os-x-permission-solution/#comments</comments>
		<pubDate>Tue, 01 Jun 2010 20:21:54 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mac]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=53</guid>
		<description><![CDATA[To avoid permission problems when accessing a SAMBA file share from OS X add the following to the [global] section of your samba configuration /etc/samba/smb.conf
unix extensions = no
]]></description>
			<content:encoded><![CDATA[<p>To avoid permission problems when accessing a SAMBA file share from OS X add the following to the [global] section of your samba configuration /etc/samba/smb.conf</p>
<p><code>unix extensions = no</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2010/06/01/samba-and-os-x-permission-solution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Howto update to an old version of Fedora</title>
		<link>http://blog.philhunter.com/2010/02/24/howto-update-to-an-old-version-of-fedora/</link>
		<comments>http://blog.philhunter.com/2010/02/24/howto-update-to-an-old-version-of-fedora/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 15:53:11 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=43</guid>
		<description><![CDATA[I recently needed access to an older version Fedora and discovered that neither updates or the core packages would download and install using YUM.
To fix this (based on Fedora Core 5) I made the following modifications to these files:
File: /etc/yum.repos.d/fedora-core.repo
[core]
baseurl=http://archives.fedoraproject.org/pub/archive/fedora/linux/core/5/i386/os/
File: /etc/yum.repos.d/fedora-extras.repo
[extras]
enabled=0
File: /etc/yum.repos.d/fedora-updates.repo
[updates]
baseurl=http://archives.fedoraproject.org/pub/archive/fedora/linux/core/updates/5/i386/
Now when I execute &#8220;yum update&#8221; I get the last set of updates to [...]]]></description>
			<content:encoded><![CDATA[<p>I recently needed access to an older version Fedora and discovered that neither updates or the core packages would download and install using YUM.</p>
<p>To fix this (based on Fedora Core 5) I made the following modifications to these files:</p>
<p><strong>File: /etc/yum.repos.d/fedora-core.repo</strong></p>
<p><code>[core]<br />
baseurl=http://archives.fedoraproject.org/pub/archive/fedora/linux/core/5/i386/os/</code></p>
<p><strong>File: /etc/yum.repos.d/fedora-extras.repo</strong></p>
<p><code>[extras]<br />
enabled=0</code></p>
<p><strong>File: /etc/yum.repos.d/fedora-updates.repo</strong></p>
<p><code>[updates]<br />
baseurl=http://archives.fedoraproject.org/pub/archive/fedora/linux/core/updates/5/i386/</code></p>
<p>Now when I execute &#8220;yum update&#8221; I get the last set of updates to be released for that particular version of Fedora and likewise I can use yum to also install new software packages.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2010/02/24/howto-update-to-an-old-version-of-fedora/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Windows Clip Art on a Mac</title>
		<link>http://blog.philhunter.com/2008/08/20/using-windows-clip-art-on-a-mac/</link>
		<comments>http://blog.philhunter.com/2008/08/20/using-windows-clip-art-on-a-mac/#comments</comments>
		<pubDate>Wed, 20 Aug 2008 16:20:38 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[PICT]]></category>
		<category><![CDATA[WMF]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=12</guid>
		<description><![CDATA[Having recently convinced my wife that she needed to make the switch to Mac OS X I was horrified to find that the Mac would not open WMF files.  Over the years I have accumulated a large collection of clip art files in the WMF (Windows Metafile) file format and didn&#8217;t really want to start [...]]]></description>
			<content:encoded><![CDATA[<p>Having recently convinced my wife that she needed to make the switch to Mac OS X I was horrified to find that the Mac would not open WMF files.  Over the years I have accumulated a large collection of clip art files in the WMF (<a title="Windows Metafile" href="http://en.wikipedia.org/wiki/Windows_Metafile">Windows Metafile</a>) file format and didn&#8217;t really want to start again.</p>
<p>I found the quickest way to resolve this was to convert all of my existing WMF file into the PICT file format.  Using one of my Linux servers I ran the following shell command against my picture library:</p>
<p><code>find /home/user/clipart/ *.WMF -print0 | while IFS= read -rd $'\0' f;<br />
do echo "[$f]";<br />
convert "$f" "$f.pict";<br />
rm -f "$f";<br />
done</code></p>
<p>This creates a list of files who&#8217;s file-name ends with WMF.  We then loop through each of these file-names converting each and saving it with a .pict file extension.  The <em>IFS= read -rd</em> parameters are absolutely necessary should your WMF files contain spaces.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2008/08/20/using-windows-clip-art-on-a-mac/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick guide to installing Ruby on Rails (Fedora 7)</title>
		<link>http://blog.philhunter.com/2008/04/16/quick-guide-to-installing-ruby-on-rails-fedora-7/</link>
		<comments>http://blog.philhunter.com/2008/04/16/quick-guide-to-installing-ruby-on-rails-fedora-7/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 15:38:49 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=10</guid>
		<description><![CDATA[First make sure Ruby is installed first.
# yum install ruby ruby-rdoc ruby-irb rubygems
Next, update the GEM repository by running
# gem update
Followed by&#8230;
# gem install -y rails --include-dependencies
yum install mod_fcgid
Add the following virtual host config to your apache config file /etc/httpd/httpd.conf
SetEnv RAILS_ENV development
ServerName rails
DocumentRoot /path/application/public/
ErrorLog /path/application/log/apache.log
&#60;Directory /path/application/public/&#62;
Options ExecCGI FollowSymLinks
AddHandler cgi-script .cgi
AllowOverride all
Order allow,deny
Allow from all
&#60;/Directory&#62;
&#60;/VirtualHost&#62;
]]></description>
			<content:encoded><![CDATA[<p>First make sure Ruby is installed first.</p>
<p><code># yum install ruby ruby-rdoc ruby-irb rubygems</code></p>
<p>Next, update the GEM repository by running</p>
<p><code># gem update</code></p>
<p>Followed by&#8230;</p>
<p><code># gem install -y rails --include-dependencies</code></p>
<p><code>yum install mod_fcgid</code></p>
<p>Add the following virtual host config to your apache config file /etc/httpd/httpd.conf</p>
<p><code>SetEnv RAILS_ENV development<br />
ServerName rails<br />
DocumentRoot /path/application/public/<br />
ErrorLog /path/application/log/apache.log</code></p>
<p><code>&lt;Directory /path/application/public/&gt;<br />
Options ExecCGI FollowSymLinks<br />
AddHandler cgi-script .cgi<br />
AllowOverride all<br />
Order allow,deny<br />
Allow from all<br />
&lt;/Directory&gt;<br />
&lt;/VirtualHost&gt;</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2008/04/16/quick-guide-to-installing-ruby-on-rails-fedora-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Self-Signed IIS SSL Certificates using OpenSSL</title>
		<link>http://blog.philhunter.com/2008/04/16/self-signed-iis-ssl-certificates-using-openssl/</link>
		<comments>http://blog.philhunter.com/2008/04/16/self-signed-iis-ssl-certificates-using-openssl/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 15:01:46 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Microsoft]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=9</guid>
		<description><![CDATA[This tutorial assumes that you have a Linux box with OpenSSL installed,and that you want to create a self-signed certificate for IIS5.0

Set up your CA (you only have to do this once)
ON THE LINUX BOX&#8230;

Create a private key
openssl genrsa -des3 -out CA.key 1024
(You&#8217;ll need to supply a passphrase.  DON&#8217;T FORGET THIS!!)
Set this to read-only [...]]]></description>
			<content:encoded><![CDATA[<p>This tutorial assumes that you have a Linux box with OpenSSL installed,and that you want to create a self-signed certificate for IIS5.0</p>
<ol>
<li><strong>Set up your CA (you only have to do this once)</strong><br />
<strong><em>ON THE LINUX BOX&#8230;</em></strong></p>
<ul>
<li>Create a private key<br />
<blockquote><p>openssl genrsa -des3 -out CA.key 1024</p></blockquote>
<p>(You&#8217;ll need to supply a passphrase.  DON&#8217;T FORGET THIS!!)</li>
<li>Set this to read-only for root access only<br />
<blockquote><p>chmod 400 CA.key</p></blockquote>
</li>
<li>Create the CA certificate<br />
<blockquote><p>openssl req -new -key CA.key -x509 -days 1095 -out CA.crt</p></blockquote>
<p>(Provide appropriate responses to the prompts&#8230;for Common Name,	you might want to use something like &#8220;OurCompany CA&#8221;)</li>
<li>Country Name: GB</li>
<li>State or Province Name: Newcastle</li>
<li>Locality Name: Gateshead</li>
<li>Organization Name: Your company name</li>
<li>Organizational Unit Name: OI</li>
<li>Common Nmae: www.yourwebsite-address.com</li>
<li>Email Address: your-admin-email@address.com</li>
<li>Set the certificate to read-only for root access only<br />
<blockquote><p>chmod 400 CA.crt</p></blockquote>
</li>
</ul>
</li>
<li><strong>Obtain a CSR</strong><br />
<strong><em>ON THE IIS BOX&#8230;</em></strong></p>
<ul>
<li>Open the Internet Manager</li>
<li>Select the site for which you want to create a key</li>
<li>Right-click and choose Properties</li>
<li>Select the &#8220;Directory Security&#8221; tab</li>
<li>Click the &#8220;Server Certificate&#8221; button</li>
<li>Follow the prompts to create a CSR</li>
<li>Save your CSR, then transfer it to the Linux box for further processing. (For the following steps, we&#8217;ll refer to your CSR as &#8220;new.csr&#8221;)</li>
</ul>
</li>
<li><strong>Sign the CSR</strong><br />
<strong><em>ON THE LINUX BOX&#8230;</em></strong></p>
<ul>
<li>Sign the CSR (all of this on one line)<br />
<blockquote><p>openssl x509 -req -days 365 -in new.csr -CA CA.crt<br />
-CAkey CA.key -CAcreateserial -out new.crt</p></blockquote>
</li>
<li>Transfer the new.crt file back to the IIS box</li>
</ul>
</li>
<li><strong>Install self-signed certificate</strong><br />
<strong><em>ON THE IIS BOX&#8230;</em></strong></p>
<ul>
<li>Open the Internet Manager</li>
<li>Select the site to install the key</li>
<li>Right-click and choose properties</li>
<li>Select the &#8220;Directory Security&#8221; tab</li>
<li>Click the &#8220;Server Certificate&#8221; button</li>
<li>Specify that you want to complete the pending request</li>
<li>Select the .crt file that you just transferred</li>
</ul>
</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2008/04/16/self-signed-iis-ssl-certificates-using-openssl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Howto burning an audio CD under Linux using just the command line</title>
		<link>http://blog.philhunter.com/2007/02/11/burning-an-audio-cd/</link>
		<comments>http://blog.philhunter.com/2007/02/11/burning-an-audio-cd/#comments</comments>
		<pubDate>Sun, 11 Feb 2007 12:07:20 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=3</guid>
		<description><![CDATA[The following command set allows you to take a selection of MP3 files, convert them into WAV file format and burn them to disc.
(run the following commands as root)
Convert the MP3 files to the WAV file format
for i in `ls *.mp3`; do lame --decode $i ; done
Before you can burn the WAV files to disc [...]]]></description>
			<content:encoded><![CDATA[<p>The following command set allows you to take a selection of MP3 files, convert them into WAV file format and burn them to disc.</p>
<p>(run the following commands as root)</p>
<p><strong>Convert the MP3 files to the WAV file format</strong><br />
<code>for i in `ls *.mp3`; do lame --decode $i ; done</code></p>
<p>Before you can burn the WAV files to disc you should know the <strong>bus address</strong> it is connected to (as far as the operating system is concerned).  To find this out, just run the following command:<br />
<code>cdrecord --scanbus</code></p>
<p>Look for the comma separated address of your cd-writer in the output and substitute the comma separated address e.g. 1,0,0 with the one shown in the <strong>dev</strong> parameter in the command line below:</p>
<p><strong>Burn the WAV files to disc</strong><br />
<code>cdrecord -dao -pad -audio -speed=4 -v dev=ATAPI:1,0,0 *.wav</code></p>
<p>After a short while you should end up with an audio CD you can play in a standard CD player.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2007/02/11/burning-an-audio-cd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create an ISO image from an existing CDROM</title>
		<link>http://blog.philhunter.com/2007/02/11/create-iso-from-existing-cdrom/</link>
		<comments>http://blog.philhunter.com/2007/02/11/create-iso-from-existing-cdrom/#comments</comments>
		<pubDate>Sun, 11 Feb 2007 12:06:10 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.philhunter.com/?p=4</guid>
		<description><![CDATA[Here is a single line shell command to convert an existing CDROM data disc into a distributable ISO image.
In this example, I&#8217;m converting one of the Fedora Core 4 installation discs which I&#8217;ve already burnt to disc, back into an ISO image called fc4_disc1.iso.
(Run as root)
dd if=/dev/cdrom of=fc4_disc1.iso bs=2048 count=`isosize -d 2048 /dev/cdrom`
Note: The single [...]]]></description>
			<content:encoded><![CDATA[<p>Here is a single line shell command to convert an existing CDROM data disc into a distributable ISO image.</p>
<p>In this example, I&#8217;m converting one of the Fedora Core 4 installation discs which I&#8217;ve already burnt to disc, back into an ISO image called fc4_disc1.iso.</p>
<p>(Run as root)<br />
<code>dd if=/dev/cdrom of=fc4_disc1.iso bs=2048 count=`isosize -d 2048 /dev/cdrom`</code></p>
<p><strong>Note:</strong> The single quotes used on the <strong>count</strong> parameter are not those typically found on the same key as the @ symbol. The quote in use here can be found to the left of the number 1 button on your keyboard.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.philhunter.com/2007/02/11/create-iso-from-existing-cdrom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
