<?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>kb.hurricane-ridge.com &#187; ports</title>
	<atom:link href="http://kb.hurricane-ridge.com/tag/ports/feed" rel="self" type="application/rss+xml" />
	<link>http://kb.hurricane-ridge.com</link>
	<description>My personal - but public - knowledge base</description>
	<lastBuildDate>Tue, 31 Aug 2010 22:18:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Passing options to the Exim port on FreeBSD</title>
		<link>http://kb.hurricane-ridge.com/os/freebsd/passing-options-to-the-exim-port-on-freebsd</link>
		<comments>http://kb.hurricane-ridge.com/os/freebsd/passing-options-to-the-exim-port-on-freebsd#comments</comments>
		<pubDate>Wed, 31 Dec 2008 20:20:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[exim]]></category>
		<category><![CDATA[ports]]></category>
		<category><![CDATA[portupgrade]]></category>

		<guid isPermaLink="false">http://kb.hurricane-ridge.com/?p=70</guid>
		<description><![CDATA[The Exim port on FreeBSD does not have a menu-driven configuration system accessible by running make config, although it does have a plethora of options described in /usr/ports/mail/exim/options.  If using portupgrade, you can pass these options with the -m flag; for example:
# portupgrade -m "WITH_CONTENT_SCAN=yes WITH_SASLAUTHD=yes WITH_DOMAINKEYS=yes" exim
]]></description>
			<content:encoded><![CDATA[<p>The Exim port on FreeBSD does not have a menu-driven configuration system accessible by running <code>make config</code>, although it does have a plethora of options described in <code>/usr/ports/mail/exim/options</code>.  If using portupgrade, you can pass these options with the <code>-m</code> flag; for example:</p>
<pre><code># portupgrade -m "WITH_CONTENT_SCAN=yes WITH_SASLAUTHD=yes WITH_DOMAINKEYS=yes" exim</code></pre>
]]></content:encoded>
			<wfw:commentRss>http://kb.hurricane-ridge.com/os/freebsd/passing-options-to-the-exim-port-on-freebsd/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Ports Installation Checklist</title>
		<link>http://kb.hurricane-ridge.com/applications/mysql-ports-installation-checklist</link>
		<comments>http://kb.hurricane-ridge.com/applications/mysql-ports-installation-checklist#comments</comments>
		<pubDate>Tue, 30 Dec 2008 20:39:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[ports]]></category>

		<guid isPermaLink="false">http://kb.hurricane-ridge.com/?p=68</guid>
		<description><![CDATA[A brief summary of after-installation MySQL configuration when using FreeBSD&#8217;s ports system.

Log into the database as root, and run the following commands to remove anonymous accounts:
use mysql;
delete from user where User='';
delete from db where User='';
flush privileges;
SET PASSWORD FOR root@localhost=PASSWORD('newgoodstrongpassword');
SET PASSWORD FOR root@127.0.0.1=PASSWORD('newgoodstrongpassword');
SET PASSWORD FOR root@host.example.com=PASSWORD('newgoodstrongpassword');

]]></description>
			<content:encoded><![CDATA[<p>A brief summary of after-installation MySQL configuration when using FreeBSD&#8217;s ports system.</p>
<ul>
<li>Log into the database as root, and run the following commands to remove anonymous accounts:<code><br />
use mysql;<br />
delete from user where User='';<br />
delete from db where User='';<br />
flush privileges;<br />
SET PASSWORD FOR root@localhost=PASSWORD('newgoodstrongpassword');<br />
SET PASSWORD FOR root@127.0.0.1=PASSWORD('newgoodstrongpassword');<br />
SET PASSWORD FOR root@host.example.com=PASSWORD('newgoodstrongpassword');</code></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://kb.hurricane-ridge.com/applications/mysql-ports-installation-checklist/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Overriding portaudit&#8217;s known vulnerabilities check</title>
		<link>http://kb.hurricane-ridge.com/os/freebsd/overriding-portaudits-known-vulnerabilities-check</link>
		<comments>http://kb.hurricane-ridge.com/os/freebsd/overriding-portaudits-known-vulnerabilities-check#comments</comments>
		<pubDate>Mon, 29 Dec 2008 19:07:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[ports]]></category>

		<guid isPermaLink="false">http://kb.hurricane-ridge.com/?p=47</guid>
		<description><![CDATA[When attempting to upgrade a port on FreeBSD, you may run into a problem like this:
&#62; sudo portupgrade -rR php5
---&#62; Upgrading 'php5-5.1.6' to 'php5-5.1.6_1' (lang/php5)
---&#62; Building '/usr/ports/lang/php5'
===&#62; Cleaning for autoconf-2.59_2
===&#62; Cleaning for pkg-config-0.21
===&#62; Cleaning for libxml2-2.6.26
===&#62; Cleaning for perl-5.8.8
===&#62; Cleaning for m4-1.4.4
===&#62; Cleaning for help2man-1.36.4_1
===&#62; Cleaning for gmake-3.81_1
===&#62; Cleaning for libiconv-1.9.2_2
===&#62; Cleaning for p5-gettext-1.05_1
===&#62; Cleaning [...]]]></description>
			<content:encoded><![CDATA[<p>When attempting to upgrade a port on FreeBSD, you may run into a problem like this:</p>
<p><code>&gt; sudo portupgrade -rR php5<br />
---&gt; Upgrading 'php5-5.1.6' to 'php5-5.1.6_1' (lang/php5)<br />
---&gt; Building '/usr/ports/lang/php5'<br />
===&gt; Cleaning for autoconf-2.59_2<br />
===&gt; Cleaning for pkg-config-0.21<br />
===&gt; Cleaning for libxml2-2.6.26<br />
===&gt; Cleaning for perl-5.8.8<br />
===&gt; Cleaning for m4-1.4.4<br />
===&gt; Cleaning for help2man-1.36.4_1<br />
===&gt; Cleaning for gmake-3.81_1<br />
===&gt; Cleaning for libiconv-1.9.2_2<br />
===&gt; Cleaning for p5-gettext-1.05_1<br />
===&gt; Cleaning for gettext-0.14.5_2<br />
===&gt; Cleaning for libtool-1.5.22_2<br />
===&gt; Cleaning for php5-5.1.6_1<br />
===&gt; php5-5.1.6_1 has known vulnerabilities:<br />
=&gt; php -- open_basedir Race Condition Vulnerability.<br />
Reference: &lt;http://www.FreeBSD.org/ports/portaudit/edabe438-542f-11db-a5ae-00508d6a62df.html&gt;<br />
=&gt; Please update your ports tree and try again.<br />
*** Error code 1<br />
Stop in /usr/ports/lang/php5.</code></p>
<p>Portaudit has stopped your portupgrade because one of the ports you are installing has a known security vulnerability &#8211; it&#8217;s even handy enough to provide a link to more information.</p>
<p>But what if you are willing to accept or mitigate the risk of the security hole &#8211; how do you build the port without portaudit stopping you? The answer is the<code>-DDISABLE_VULNERABILITIES</code> flag:</p>
<p><code>&gt; sudo portupgrade -rR -m -DDISABLE_VULNERABILITIES php5<br />
Password:<br />
---&gt; Upgrading 'php5-5.1.6' to 'php5-5.1.6_1' (lang/php5)<br />
---&gt; Building '/usr/ports/lang/php5' with make flags: -DDISABLE_VULNERABILITIES<br />
===&gt; Cleaning for autoconf-2.59_2<br />
===&gt; Cleaning for pkg-config-0.21<br />
===&gt; Cleaning for libxml2-2.6.26<br />
===&gt; Cleaning for perl-5.8.8<br />
===&gt; Cleaning for m4-1.4.4<br />
===&gt; Cleaning for help2man-1.36.4_1<br />
===&gt; Cleaning for gmake-3.81_1<br />
===&gt; Cleaning for libiconv-1.9.2_2<br />
===&gt; Cleaning for p5-gettext-1.05_1<br />
===&gt; Cleaning for gettext-0.14.5_2<br />
===&gt; Cleaning for libtool-1.5.22_2<br />
===&gt; Cleaning for php5-5.1.6_1<br />
===&gt; Found saved configuration for php5-5.1.6_1<br />
[...]</code></p>
<p>Obviously, use the <code>-DDISABLE_VULNERABILITIES</code> flag with caution. Tip seen at <a href="http://taosecurity.blogspot.com/2004/05/disabling-vulnerability-checks-with.html">TaoSecurity</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://kb.hurricane-ridge.com/os/freebsd/overriding-portaudits-known-vulnerabilities-check/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Checking for modified files in installed FreeBSD ports or packages</title>
		<link>http://kb.hurricane-ridge.com/os/freebsd/checking-for-modified-files-in-installed-freebsd-ports-or-packages</link>
		<comments>http://kb.hurricane-ridge.com/os/freebsd/checking-for-modified-files-in-installed-freebsd-ports-or-packages#comments</comments>
		<pubDate>Mon, 29 Dec 2008 18:42:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[ports]]></category>

		<guid isPermaLink="false">http://kb.hurricane-ridge.com/?p=45</guid>
		<description><![CDATA[When upgrading FreeBSD ports, you will lose any customizations that you&#8217;ve made to files within the port; this is especially problematic with configuration files. A quick and easy way to check for modifications you may have made is to use the -g flag to pkg_info. For example:
&#62; pkg_info -g -x drupal
Information for drupal-4.6.9:
Mismatched Checksums:
/usr/local/www/drupal/.htaccess fails the original MD5 [...]]]></description>
			<content:encoded><![CDATA[<p>When upgrading FreeBSD ports, you will lose any customizations that you&#8217;ve made to files within the port; this is especially problematic with configuration files. A quick and easy way to check for modifications you may have made is to use the <code>-g</code> flag to <code>pkg_info</code>. For example:</p>
<p><code>&gt; pkg_info -g -x drupal<br />
Information for drupal-4.6.9:</code></p>
<p><code>Mismatched Checksums:<br />
/usr/local/www/drupal/.htaccess fails the original MD5 checksum</code></p>
<p>In this case, you might want to preserve your <code>.htaccess</code> file to merge it back in to your drupal installation after upgrading.</p>
]]></content:encoded>
			<wfw:commentRss>http://kb.hurricane-ridge.com/os/freebsd/checking-for-modified-files-in-installed-freebsd-ports-or-packages/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building FreeBSD Ports as an Unprivileged User</title>
		<link>http://kb.hurricane-ridge.com/os/freebsd/building-freebsd-ports-as-an-unprivileged-user</link>
		<comments>http://kb.hurricane-ridge.com/os/freebsd/building-freebsd-ports-as-an-unprivileged-user#comments</comments>
		<pubDate>Mon, 29 Dec 2008 18:40:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[ports]]></category>

		<guid isPermaLink="false">http://kb.hurricane-ridge.com/?p=41</guid>
		<description><![CDATA[Set the following in /etc/make.conf:
WRKDIRPREFIX=/home/anl/ports-build
DISTDIR=/home/anl/ports-dist
WRKDIRPREFIX is a directory that the unprivileged user as able to write to; DISTDIR is the directory their downloads of source files are written to.
If the port you are building requires another port to be installed for it to be built, you will be prompted for the root password, so this technique is not suitable [...]]]></description>
			<content:encoded><![CDATA[<p>Set the following in <code>/etc/make.conf</code>:</p>
<p><code>WRKDIRPREFIX=/home/anl/ports-build<br />
DISTDIR=/home/anl/ports-dist</code></p>
<p><code>WRKDIRPREFIX</code> is a directory that the unprivileged user as able to write to; <code>DISTDIR</code> is the directory their downloads of source files are written to.</p>
<p>If the port you are building requires another port to be installed for it to be built, you will be prompted for the root password, so this technique is not suitable for unattended port installations.</p>
]]></content:encoded>
			<wfw:commentRss>http://kb.hurricane-ridge.com/os/freebsd/building-freebsd-ports-as-an-unprivileged-user/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrading Perl 5.6 to Perl 5.8 Using Portupgrade and perl-after-upgrade</title>
		<link>http://kb.hurricane-ridge.com/scripting/perl/upgrading-perl-56-to-perl-58-using-portupgrade-and-perl-after-upgrade</link>
		<comments>http://kb.hurricane-ridge.com/scripting/perl/upgrading-perl-56-to-perl-58-using-portupgrade-and-perl-after-upgrade#comments</comments>
		<pubDate>Mon, 29 Dec 2008 18:36:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Perl]]></category>
		<category><![CDATA[ports]]></category>

		<guid isPermaLink="false">http://kb.hurricane-ridge.com/?p=36</guid>
		<description><![CDATA[Use the -o flag to portupgrade to replace the perl5 port with a the perl5.8 port:
# portupgrade -rR -o lang/perl5.8 lang/perl5
After the upgrade (this is applicable after any Perl ports upgrade, such as 5.8.8 to 5.8.9), run the perl-after-upgrade script, first in test mode, then in fix mode:
# perl-after-upgrade
# perl-after-upgrade -f
Fix any errors highlighted by perl-after-upgrade, and reinstall any required packages.  [...]]]></description>
			<content:encoded><![CDATA[<p>Use the <code>-o</code> flag to <code>portupgrade</code> to replace the perl5 port with a the perl5.8 port:</p>
<p><code># portupgrade -rR -o lang/perl5.8 lang/perl5</code></p>
<p>After the upgrade (this is applicable after <em>any</em> Perl ports upgrade, such as 5.8.8 to 5.8.9), run the <code>perl-after-upgrade</code> script, first in test mode, then in fix mode:</p>
<p><code># perl-after-upgrade<br />
# perl-after-upgrade -f</code></p>
<p>Fix any errors highlighted by <code>perl-after-upgrade</code>, and reinstall any required packages.  Review files left behind from the older Perl installation (typically <code>/usr/local/lib/perl5/site_perl/5.X.Y/</code>).  After verifying that the upgraded Perl works as expected, remove <code>+CONTENTS.bak</code> files from subdirectories under <code>/var/db/pkg</code>.</p>
<p>See the <code>perl-after-upgrade</code> man page for more details.</p>
]]></content:encoded>
			<wfw:commentRss>http://kb.hurricane-ridge.com/scripting/perl/upgrading-perl-56-to-perl-58-using-portupgrade-and-perl-after-upgrade/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
