<?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>Christian&#039;s blog &#187; Gentoo</title>
	<atom:link href="http://blog.barfoo.org/categories/gentoo/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.barfoo.org</link>
	<description>The usual IT babble</description>
	<lastBuildDate>Thu, 02 Sep 2010 04:45:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
		<item>
		<title>Gentoo packages are gone now!</title>
		<link>http://blog.barfoo.org/2009/01/25/gentoo-packages-are-gone-now/</link>
		<comments>http://blog.barfoo.org/2009/01/25/gentoo-packages-are-gone-now/#comments</comments>
		<pubDate>Sun, 25 Jan 2009 14:08:30 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[binpkg]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=1626</guid>
		<description><![CDATA[Just like I announced last week, my binary packages repository is now history. I&#8217;m gonna remove the redirections from lighttpd and DNS in a few.]]></description>
			<content:encoded><![CDATA[<p>Just like <a href="http://blog.barfoo.org/2009/01/18/packagesbarfooorg-is-going-away/">I announced last week</a>, my binary packages repository is now history. I&#8217;m gonna remove the redirections from lighttpd and DNS in a few.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2009/01/25/gentoo-packages-are-gone-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>packages.barfoo.org is going away</title>
		<link>http://blog.barfoo.org/2009/01/18/packagesbarfooorg-is-going-away/</link>
		<comments>http://blog.barfoo.org/2009/01/18/packagesbarfooorg-is-going-away/#comments</comments>
		<pubDate>Sun, 18 Jan 2009 13:10:23 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[binpkg]]></category>
		<category><![CDATA[Gentoo/Hardened]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=1550</guid>
		<description><![CDATA[For those of you, still using my binary packages. It&#8217;s just a waste of disk space for me (6.8G to be exact), so I decided to remove them. I&#8217;m gonna give people one week to grab yourself a copy. I&#8217;m gonna keep the bashrc and all the other stuff I wrote back when I was]]></description>
			<content:encoded><![CDATA[<p>For those of you, still using my binary packages. It&#8217;s just a waste of disk space for me (6.8G to be exact), so I decided to remove them. I&#8217;m gonna give people one week to grab yourself a copy. I&#8217;m gonna keep the bashrc and all the other stuff I wrote back when I was <a href="http://blog.barfoo.org/2007/12/31/buildpkg-chroots/">still interested</a> in binary packages, but the binary packages <strong>are gonna vanish</strong>!</p>
<p>Again, grab yourself a copy if you need them, at some point next week (probably on Friday), I&#8217;m simply gonna <em>rm -rf</em> them.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2009/01/18/packagesbarfooorg-is-going-away/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Looong time</title>
		<link>http://blog.barfoo.org/2008/06/16/looong-time/</link>
		<comments>http://blog.barfoo.org/2008/06/16/looong-time/#comments</comments>
		<pubDate>Mon, 16 Jun 2008 18:50:58 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=196</guid>
		<description><![CDATA[Well, it&#8217;s been a loong time since I first thought about retiring (yes, I know that #-dev&#8217;s topic states &#8220;developer blogs&#8221; ain&#8217;t for announcing important things, but my blog has to do for this; if not, I don&#8217;t care anymore ). But I think it&#8217;s about time for me to leave. I haven&#8217;t done much]]></description>
			<content:encoded><![CDATA[<p>Well, it&#8217;s been a loong time since I first thought about retiring (yes, I know that #-dev&#8217;s topic states &#8220;<em>developer blogs</em>&#8221; ain&#8217;t for announcing important things, but my blog has to do for this; if not, I don&#8217;t care anymore <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_exclaim.gif' alt=':!:' class='wp-smiley' />  ).</p>
<p>But I think it&#8217;s about time for me to leave. I haven&#8217;t done much lately, I&#8217;ve been soo damn busy with work these last months like I would never have imagined. I gave it some more thought, and I finally got to the point (<strong>again</strong> I might add) where all just annoys and/or frustrates me.</p>
<p>All the damn bickering, the childish behaviour Josh talked about (&#8220;<em>noooo, that&#8217;s my TOY!</em>&#8220;), the constant abuse of power (hey #-chat, #-kde ops). I thought most of us would at least try and behave like the elderish people we are (well besides the few of us, who really are children by law&#8217;s definition &#8211; hey there welp, omp, keytoaster <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  ). But I guess that&#8217;s just been an imaginary thought I had .. *<strong>shrug</strong>*</p>
<p><span id="more-196"></span></p>
<p>Just this last thing, I&#8217;m gonna say thank to you to the few of you I&#8217;ve been gotten around to call friends.</p>
<p>Thank you</p>
<ul>
<li>Christina</li>
<li>Diego</li>
<li>Joshua (tsunam)</li>
<li>Joshua (nightmorph)</li>
<li>Łukasz</li>
<li>Jorge</li>
<li>Markus</li>
<li>Daniel (dsd)</li>
<li>Gysbert</li>
<li>Peter</li>
<li>Christian (well, not me. But hoffie and opfer)</li>
<li>Chris</li>
<li>Mike (well, three of you. &#8216;taco, mpagano and vapier)</li>
<li>solar</li>
<li>Andrew</li>
<li>Alex</li>
<li>Raúl</li>
<li>Tobias (dertobi)</li>
<li>Tobias (klausman)</li>
<li>Robert (rbu)</li>
<li>Robin</li>
<li>Shyam</li>
<li>Brent</li>
<li>Benedikt</li>
<li>Homer</li>
</ul>
<p>It&#8217;s been a hell of a ride, and I thank all of you, deeply, from the bottom of my heart for the support, advice and resources you all gave me. <strong>This is it</strong>! This time, there&#8217;s no turning back, sorry Christina <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_razz.gif' alt=':-P' class='wp-smiley' /> </p>
<p>So, I&#8217;m gonna stick to my day job, pay more attention to my trainees and maybe put some effort into getting something better! So long, farewell people. If people need to reach me; my email addresses still are in ldap, so that shouldn&#8217;t be a problem. Hasta luego (or maybe not, we&#8217;ll see &#8230;)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/06/16/looong-time/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Retiring people</title>
		<link>http://blog.barfoo.org/2008/05/28/retiring-people/</link>
		<comments>http://blog.barfoo.org/2008/05/28/retiring-people/#comments</comments>
		<pubDate>Wed, 28 May 2008 12:55:34 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[safekeeping]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=329</guid>
		<description><![CDATA[I&#8217;m not sure whether or not I blogged about this before, but here it is just for me to actually remember what, in which order I need to do. If you got the list in form of a csv file, simply do the following: $ wget -q http://tinyurl.com/4atkz7 -O - &#124; grep "(" &#124; cut]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m not sure whether or not I blogged about this before, but here it is just for me to actually remember what, in which order I need to do.  If  you got the list in form of a  csv file, simply  do the following:</p>
<pre lang="bash" line="1">
$ wget -q http://tinyurl.com/4atkz7 -O - | grep "(" | cut -d'(' -f2 | \
    cut -d')' -f1 | awk '{ print tolower($1) }' > retirements
$ for developer in $( < retirements )
    do retire.py --metadata $developer /cvs/gentoo-x86/ | \
    diffstat > ~/metadata.$developer
    done
</pre>
<p>That&#8217;ll give you a detailed list of which metadata.xml need to be changed.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/05/28/retiring-people/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>metadata.xml (the third)</title>
		<link>http://blog.barfoo.org/2008/03/14/metadataxml-the-third/</link>
		<comments>http://blog.barfoo.org/2008/03/14/metadataxml-the-third/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 20:14:28 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[herds]]></category>
		<category><![CDATA[QA]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=237</guid>
		<description><![CDATA[So Petteri came up with a nifty python script (local), which in return spit out this. Which generated a rather complete list (local), that looks like this: 700: perl 569: maintainer-needed 128: media-video 126: xemacs 47: sound 32: ha-cluster 32: crypto 19: desktop-misc 16: netmon 15: forensics 13: web-apps 10: pam-bugs 8: vserver-devs 8: mips]]></description>
			<content:encoded><![CDATA[<p>So Petteri came up with a nifty python script (<a href="http://chrischie.users.barfoo.org/gentoo/QA/redundant-metadata/dP9gSU44.txt">local</a>), which in return spit out this. Which generated a rather complete list (<a href="http://chrischie.users.barfoo.org/gentoo/QA/redundant-metadata/dxzdrF36.txt">local</a>), that looks like this:<br />
<code>700:     perl<br />
569:     maintainer-needed<br />
128:     media-video<br />
126:     xemacs<br />
47:      sound<br />
32:      ha-cluster<br />
32:      crypto<br />
19:      desktop-misc<br />
16:      netmon<br />
15:      forensics<br />
13:      web-apps<br />
10:      pam-bugs<br />
8:       vserver-devs<br />
8:       mips<br />
8:       embedded<br />
8:       app-backup<br />
8:       apache-bugs<br />
8:       alsa-bugs<br />
7:       net-im<br />
7:       kde<br />
6:       tcltk<br />
6:       media-tv<br />
6:       dev-embedded<br />
5:       voip<br />
5:       theology<br />
5:       samba<br />
5:       net-p2p<br />
5:       freedesktop-bugs<br />
4:       sparc<br />
4:       java<br />
4:       graphics<br />
2:       net-mail<br />
2:       ldap-bugs<br />
2:       kernel<br />
2:       fonts<br />
2:       cpp<br />
1:       x11<br />
1:       wxwidgets<br />
1:       www-servers<br />
1:       tex<br />
1:       shell-tools<br />
1:       sgml<br />
1:       sci<br />
1:       qmail-bugs<br />
1:       python<br />
1:       proaudio<br />
1:       media-optical<br />
1:       kerberos<br />
1:       hp-cluster<br />
1:       amd64</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/03/14/metadataxml-the-third/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>metadata.xml (the second)</title>
		<link>http://blog.barfoo.org/2008/03/14/metadataxml-the-second/</link>
		<comments>http://blog.barfoo.org/2008/03/14/metadataxml-the-second/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 18:09:26 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[herds]]></category>
		<category><![CDATA[QA]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=235</guid>
		<description><![CDATA[As I was kinda bored after work today, I had a closer look at what I saw during my fuckup in the morning. Well, Steve said, that when he looked at metadata.xml it&#8217;d be &#8220;really common&#8221; .. still that isn&#8217;t making it right .. There is a reason we do have a herds.xml (exactly for]]></description>
			<content:encoded><![CDATA[<p>As I was kinda bored after work today, I had a closer look at what I saw during my fuckup in the morning. Well, <a href="http://wonkabar.org">Steve</a> <a href="http://blog.barfoo.org/2008/03/14/metadataxml/">said</a>, that when he looked at <em>metadata.xml</em> it&#8217;d be &#8220;<strong>really common</strong>&#8221; .. still that isn&#8217;t making it right ..</p>
<p>There is a reason we do have a <em>herds.xml</em> (exactly for the reason to associate people with packages, and that&#8217;s what the &lt;herd&gt; tag is for in metadata.xml) file. So after a preliminary look through the repository, here are the winners:<br />
<code> 700	: perl<br />
 126	: xemacs<br />
 63	: haskell<br />
 47	: sound<br />
 32	: ha-cluster<br />
 31	: crypto<br />
 19	: desktop-misc<br />
 16	: netmon<br />
 15	: forensics<br />
 13	: web-apps<br />
 8	: mips<br />
 8	: app-backup<br />
 7	: kde<br />
 6	: tcltk<br />
 6	: net-im<br />
 6	: media-tv<br />
 6	: dev-embedded<br />
 5	: voip<br />
 5	: theology<br />
 5	: samba<br />
 5	: net-p2p<br />
 4	: sparc<br />
 4	: java<br />
 4	: graphics<br />
 2	: net-mail<br />
 2	: kernel<br />
 2	: fonts<br />
 2	: embedded<br />
 2	: cpp<br />
 1	: x11<br />
 1	: wxwidgets<br />
 1	: www-servers<br />
 1	: tex<br />
 1	: shell-tools<br />
 1	: sh<br />
 1	: sgml<br />
 1	: sci<br />
 1	: python<br />
 1	: proaudio<br />
 1	: php<br />
 1	: media-optical<br />
 1	: kerberos<br />
 1	: hp-cluster<br />
 1	: gentopia<br />
 1	: amd64</code></p>
<p>Don&#8217;t know how accurate that list is, but you can check it for yourself. The commands I&#8217;ve used are these:</p>
<pre lang="bash">for i in $( < ../herds.list ); do
    grep --exclude=eclass --exclude=CVS \
    --exclude=profiles --exclude=skel.* -R \
    "<email>$i@gentoo.org</email>" /cvs/gentoo-x86/* ;
 done > redundant-metadata-xml.list</pre>
<pre lang="bash">for i in $( < herds.list ); do
    echo -e " $( grep "<email>$i@gentoo.org</email>" \
                 ~/public_html/redundant-metadata-xml.list | \
                 wc -l )\t: $i"; done | \
     grep -v "^ 0" | \
     sort -nr > public_html/redundant-metadata-xml.overview</pre>
<p>While herds.list holds a list (separated by \n) with all the herds there are. The raw files are <a href="http://chrischie.users.barfoo.org/gentoo/QA/redundant-metadata/redundant-metadata-xml.list">here</a> and <a href="http://chrischie.users.barfoo.org/gentoo/QA/redundant-metadata/redundant-metadata-xml.overview">here</a> and <a href="http://chrischie.users.barfoo.org/gentoo/QA/redundant-metadata/herds.list">here</a>. Knock yourself out!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/03/14/metadataxml-the-second/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>metadata.xml</title>
		<link>http://blog.barfoo.org/2008/03/14/metadataxml/</link>
		<comments>http://blog.barfoo.org/2008/03/14/metadataxml/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 09:43:53 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[herds]]></category>
		<category><![CDATA[QA]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=234</guid>
		<description><![CDATA[So I ended up cleaning out some retired (~20) people from metadata.xml, where I found this interesting piece of metadata.xml: kernel-misc crypto@gentoo.org Crypto herd masterdriverz@gentoo.org Charlie Shephered And here the hint for all you people again: A DAMN HERD AIN&#8217;T NO MAINTAINER. SO IF YOUR HERD IS MAINTAINING A PACKAGE, PUT IT INTO &#60;herd&#62; and]]></description>
			<content:encoded><![CDATA[<p>So I ended up cleaning out some retired (~20) people from <em>metadata.xml</em>, where I found this interesting piece of metadata.xml:</p>
<pre lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<herd>kernel-misc</herd>
<maintainer>
  <email>crypto@gentoo.org</email>
  <name>Crypto herd</name>
</maintainer>
<maintainer>
  <email>masterdriverz@gentoo.org</email>
  <name>Charlie Shephered</name>
</maintainer>
</pkgmetadata>
</pre>
<p>And here the hint for all you people again: <strong>A DAMN HERD AIN&#8217;T NO MAINTAINER</strong>. SO IF YOUR HERD IS MAINTAINING A PACKAGE, PUT IT INTO &lt;herd&gt; and not into the &lt;maintainer&gt;. kthnxbye.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/03/14/metadataxml/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>To be or not to be &#8230;</title>
		<link>http://blog.barfoo.org/2008/03/09/to-be-or-not-to-be/</link>
		<comments>http://blog.barfoo.org/2008/03/09/to-be-or-not-to-be/#comments</comments>
		<pubDate>Sun, 09 Mar 2008 15:31:45 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[Philosophical]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/?p=232</guid>
		<description><![CDATA[&#8230; that&#8217;s the question. I&#8217;ve been thinking lots and lots about my involvement with our &#8220;beloved&#8221; distribution. I talked to some of the users (that is Gordon), some fellow developers (hello Christina, Łukasz, solar, Jorge, Anders) about whether or not I&#8217;m actually still wanted and/or needed. Turns out, the collective opinion is, that I am]]></description>
			<content:encoded><![CDATA[<p>&#8230; that&#8217;s the question. I&#8217;ve been thinking lots and lots about my involvement with our &#8220;<em>beloved</em>&#8221; distribution.</p>
<p>I talked to some of the users (that is Gordon), some fellow developers (hello Christina, Łukasz, solar, Jorge, Anders) about whether or not I&#8217;m actually still wanted and/or needed. Turns out, the collective opinion is, that I am fun to have around (<strong>*shrug*</strong> don&#8217;t ask me why, I don&#8217;t find myself particularly funny/amusing) and that&#8217;d I&#8217;d be the person to have around.</p>
<p>That being said, I still do have some things on my agenda (they haven&#8217;t changed .. like getting healthier &#8211; as in heading to the gym; getting a better paid job; getting my own life; getting some friends), which are going to jockey with those Gentoo interests.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/03/09/to-be-or-not-to-be/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>stages</title>
		<link>http://blog.barfoo.org/2008/01/08/stages/</link>
		<comments>http://blog.barfoo.org/2008/01/08/stages/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 00:57:29 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[Gentoo/Embedded]]></category>
		<category><![CDATA[Gentoo/Hardened]]></category>
		<category><![CDATA[PowerPC]]></category>
		<category><![CDATA[Stage tarballs]]></category>
		<category><![CDATA[uClibc]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/2008/01/08/stages</guid>
		<description><![CDATA[For what it&#8217;s worth, I&#8217;ve been trying to get some stages together the last few days. Thanks to solar and Brent, the ppc-stages are now coming along quite fast. I haven&#8217;t really tested them yet, but for what it&#8217;s worth, you&#8217;ll find stages based on Saturday&#8217;s snapshot (that is 200780105 for those not smart enough]]></description>
			<content:encoded><![CDATA[<p>For what it&#8217;s worth, I&#8217;ve been trying to get some stages together the last few days. Thanks to <a href="http://blogs.gentoo.org/solar">solar</a> and <a href="http://blogs.gentoo.org/ferdy">Brent</a>, the ppc-stages are now coming along quite fast.</p>
<p>I haven&#8217;t really tested them yet, but for what it&#8217;s worth, you&#8217;ll find stages based on Saturday&#8217;s snapshot (that is 200<strike>7</strike>80105 for those not smart enough to take a look at the calendar) here for the following profiles:</p>
<ul>
<li>uclibc/ppc (normal/-softfloat)</li>
<li>uclibc/ppc/hardened</li>
<li>uclibc/x86</li>
<li>uclibc/x86/hardened</li>
<li>hardened/amd64</li>
<li>hardened/amd64/nomultilib</li>
<li>hardened/x86/2.6 (x86/i686)</li>
</ul>
<p>Now remember, this isn&#8217;t <b>*official*</b> release material. This is just <b>*MY*</b> effort (<i>for now</i>) to provide current stages.</p>
<p>And just a side-note for those brewing their own (<a href="http://www.uclibc.org/">uClibc</a>) soup: if you remerge <i>system</i>/<i>world</i>, you&#8217;ll have to keyword <b>=sys-libs/uclibc.0.9.28.3-r2</b>. Otherwise you&#8217;ll stumble on <a href="https://bugs.gentoo.org/show_bug.cgi?id=195368">bug 195368</a>, which is fixed thanks to solar, just not marked stable yet.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2008/01/08/stages/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Advanced bashrc (&#8216;Turning a simple chroot into a binpkg repository&#8217; continued)</title>
		<link>http://blog.barfoo.org/2007/12/31/buildpkg-chroots/</link>
		<comments>http://blog.barfoo.org/2007/12/31/buildpkg-chroots/#comments</comments>
		<pubDate>Mon, 31 Dec 2007 18:13:03 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[bashrc]]></category>
		<category><![CDATA[binpkg]]></category>
		<category><![CDATA[buildnode]]></category>
		<category><![CDATA[chroot]]></category>
		<category><![CDATA[tinderbox]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/2007/12/31/buildpkg-chroots/</guid>
		<description><![CDATA[As I pointed out back in October, it&#8217;s rather easy to create a setup which syncs a built binary package to a remote node (which is serving them to the world &#8211; via http,rsync,ftp &#8211; pick your poison). Now, ever since we had slight space problems on miranda (cough my binpkgs cough), I wanted to]]></description>
			<content:encoded><![CDATA[<p>As I pointed out back in <a href="http://blog.barfoo.org/2007/10/12/turning-a-simple-chroot-into-a-binpkg-repository/" target="_blank">October</a>, it&#8217;s rather easy to create a setup which syncs a built binary package to a remote node (which is serving them to the world &#8211; via http,rsync,ftp &#8211; pick your poison).</p>
<p>Now, ever since we had slight space problems on miranda (<b>cough</b> my binpkgs <b>cough</b>), I wanted to look into methods on how to get rid of storing them on the buildnode and the webnode. I think now (hehe, it&#8217;s only 7pm), I finally managed to get a &#8220;<i>proper</i>&#8221; bashrc which does a lot of that foo. Take a look at this:</p>
<pre lang="bash">
...
syncpkg() {
  # Syncing the binary tbz2 to my webhost
  if is_feature "buildpkg" &#038;&#038; \
  [[ -n $REPO_HOST &#038;&#038; -n $REPO_BASE &#038;&#038; -n $REPO_PATH ]] ; then
    REMOTE_TARGET="$REPO_HOST:$REPO_BASE/$REPO_PATH"
    REMOTE_ECACHE="$REPO_BASE/$REPO_PATH/settings/.ebuild.x"

    einfo "Publishing data to remote repository ($REPO_PATH) on ${REPO_HOST##*@}"

    if ! $( ssh $REPO_HOST "test -d $REPO_BASE/$REPO_PATH/settings" ) ; then
      ssh $REPO_HOST "mkdir -p $REPO_BASE/$REPO_PATH/settings" \
        >> /var/log/syncpkg.log 2>&#038;1
    fi

    if [ -x /usr/bin/q ] ; then
      /usr/bin/qlist -IvCU > /etc/portage/package.list
    fi

    ebegin " [ SYNC: 1/3] /etc/make.conf, /etc/portage/package* to $REPO_PATH/settings"
    rssh /etc/{make.conf,portage/package*,portage/profile,portage/bin,portage/bashrc} \
      $REMOTE_TARGET/settings/ > /var/log/syncpkg.log 2>&#038;1
    eend $?

    ebegin " [ SYNC: 2/3] $PKGDIR to $REPO_PATH"
    rssh $PKGDIR/ $REMOTE_TARGET/ >> /var/log/syncpkg.log 2>&#038;1
    eend $?

    ebegin " [ SYNC: 3/3] Cleaning $PKGDIR"
    rm -rf $PKGDIR/* >> /var/log/syncpkg.log 2>&#038;1
    eend $?

    # We sync our copy of .ebuild.x over to the webnode, as it might not be
    # synced as often / at the same time as the buildnode. Thus the
    # `qpkg --eclean' would remove packages, which *are* in the tree, but
    # the webnode hasn't synced up yet.

    rssh $PORTDIR/.ebuild.x $REMOTE_TARGET/settings/.ebuild.x \
      >> /var/log/syncpkg.log 2>&#038;1

    if $( ssh $REPO_HOST "test -f $REMOTE_ECACHE" ) ; then
      ebegin " [MAINT: 1/3] Removing stale packages in $REPO_PATH"
      ssh $REPO_HOST "CACHE_EBUILD_FILE=$REMOTE_ECACHE qpkg -Eq -P \
        $REPO_BASE/$REPO_PATH/" >> /var/log/syncpkg.log 2>&#038;1
      eend $?
    fi

    # And now remove the .ebuild.x copy again.
    ssh $REPO_HOST "rm -f $REMOTE_ECACHE" >> /var/log/syncpkg.log 2>&#038;1

    # The user ssh'ing, needs to be in the portage group on the remote
    # end. Otherwise, things *will* go wrong (like genpkgindex being
    # unable to write to /var/cache/edb/xpak). Also /var/cache/edb/xpak
    # needs to be owned by portage:portage, as well as group-writeable.

    if $( ssh $REPO_HOST "test -w /var/cache/edb/xpak" ) ; then
      ebegin " [MAINT: 2/3] Regenerating $REPO_PATH/Packages"
      ssh $REPO_HOST "$REPO_BASE/$REPO_PATH/settings/bin/genpkgindex \
        $REPO_BASE/$REPO_PATH/All" >> /var/log/syncpkg.log 2>&#038;1
      eend $?
    fi

    if ! $( ssh $REPO_HOST "test -L $REPO_BASE/$REPO_PATH/Packages" ) ; then
      ebegin " [MAINT: 3/3] Fixing $REPO_PATH/Packages symlink"
      ssh $REPO_HOST "cd $REPO_BASE/$REPO_PATH; rm -f Packages; ln -s \
        All/Packages" >> /var/log/syncpkg.log 2>&#038;1
      eend $?
    fi
  fi
}
...
</pre>
<p>As you can see, it does a lot of things, which are all connected with binary package repositories (including cleaning up old packages no longer in the tree &#8211; trying not to waste <b>too</b> much space). Sadly, I currently have to use a custom patched qpkg version, as the one implementing the <i>&#8211;eclean</i> features isn&#8217;t in the tree yet. When I talked to Ned the other day, he complained about it being <i>slow</i> (well, yeah &#8212; it has to go through the whole tree) which I don&#8217;t really see when you look at <b>what</b> it&#8217;s doing.</p>
<p>Also, I had a weird phenomenon today happening: the buildnode built a binary package, sent it to the webnode, which ran `<i>qpkg &#8211;eclean</i>&#8216; afterwards. But after that the binary package was gone. &#8220;<b>Why</b>&#8221; you ask now ? Well, apparently the webnode isn&#8217;t synced the same time the buildnode syncs (the webnode is in Germany, the buildnode in the US). So I had to come up with a trick, in order to fool qpkg into not cleaning the freshly built binary packages. See the `rssh&#8217; in front of the qpkg call ? Guess what, that&#8217;s the lil&#8217; dirty trick &#8230;</p>
<p>Anyway, the full <a href="http://blog.barfoo.org/wp-content/uploads/2007/10/bashrc">bashrc</a> is available. The next thing I&#8217;m gonna have to look at (which Markus already <a href="http://blogs.gentoo.org/jokey/2007/09/03/tinderbox_up_and_running">did</a>), is building packages via buildbot.</p>
<p><b>Update:</b> as you see, I updated the bashrc a bit. That&#8217;s because after writing this, I started a new (fresh) binpkg repository (empty), and out of the sudden the thing ain&#8217;t syncing correctly (as in no Packages file, no portage settings). Turns out, rsync doesn&#8217;t create directories which ain&#8217;t there. So another extra `<i>ssh</i>&#8216; execution to create the <i>settings/</i> directory inside the repo.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/12/31/buildpkg-chroots/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>screen and UTF-8 (continued)</title>
		<link>http://blog.barfoo.org/2007/10/25/screen-and-utf-8-continued/</link>
		<comments>http://blog.barfoo.org/2007/10/25/screen-and-utf-8-continued/#comments</comments>
		<pubDate>Thu, 25 Oct 2007 20:04:00 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[irssi]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[unicode]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/index.php/2007/10/25/screen-and-utf-8-continued/</guid>
		<description><![CDATA[OK, since I last posted about my problems with screen and irssi being unable to handle unicode chars, I got a lot of feedback (here or on IRC), and actually it was Alexander who pointed me into the right direction. LANG=C doesn&#8217;t seem to support UTF-8 characters. So after adding export LC_ALL="en_US.UTF8" export LANG="en_US.UTF8" to]]></description>
			<content:encoded><![CDATA[<p>OK, since I last posted about my <a href="http://blog.barfoo.org/2007/10/20/screen-and-utf-8/">problems with screen and irssi</a> being unable to handle unicode chars, I got a lot of feedback (here or on IRC), and actually it was Alexander who pointed me into the right direction. <em>LANG=C</em> doesn&#8217;t seem to support UTF-8 characters.  So after adding</p>
<pre lang="bash">
export LC_ALL="en_US.UTF8"
export LANG="en_US.UTF8"
</pre>
<p>to my environment <strong>*everything*</strong> is just fine &#8230;  <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_eek.gif' alt=':shock:' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/10/25/screen-and-utf-8-continued/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>screen and UTF-8</title>
		<link>http://blog.barfoo.org/2007/10/20/screen-and-utf-8/</link>
		<comments>http://blog.barfoo.org/2007/10/20/screen-and-utf-8/#comments</comments>
		<pubDate>Sat, 20 Oct 2007 20:24:06 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[irssi]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[unicode]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/2007/10/20/screen-and-utf-8/</guid>
		<description><![CDATA[Since I got annoyed by umlauts being printed as ░, I figured I&#8217;d install a UTF-8 capable font on this box here and all my problems would be gone. But not so fast. screen is a real fucked up thing. If you&#8217;re starting screen via screen -U everything is nice and cosy, and you get]]></description>
			<content:encoded><![CDATA[<p>Since I got annoyed by umlauts being printed as ░, I figured I&#8217;d install a UTF-8 capable font on this box here and all my problems would be gone. But not so fast.</p>
<p>screen is a real fucked up thing. If you&#8217;re starting screen via <em>screen -U </em>everything is nice and cosy, and you get your UTF-8 goodness. But, don&#8217;t think you&#8217;ll get away with just enabling UTF-8 as default and enabling UTF-8 for each new window by doing this:</p>
<pre lang="bash">
defutf8 on
utf8 on on
</pre>
<p>You won&#8217;t get any UTF-8 char (at least w/ irssi) out of that ..  <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_mad.gif' alt=':mad:' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/10/20/screen-and-utf-8/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Turning a simple chroot into a binpkg repository</title>
		<link>http://blog.barfoo.org/2007/10/12/turning-a-simple-chroot-into-a-binpkg-repository/</link>
		<comments>http://blog.barfoo.org/2007/10/12/turning-a-simple-chroot-into-a-binpkg-repository/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 21:45:46 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[binpkg]]></category>
		<category><![CDATA[chroot]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/2007/10/12/turning-a-simple-chroot-into-a-binpkg-repository/</guid>
		<description><![CDATA[OK, since Alex asked me last Sunday what exactly needs to be done to turn a simple chroot (or even a bloody box) into a binpkg producing environment, here&#8217;s a little howto &#8230; First, lets start from a freshly unpacked stage3. catalyst/x86 stage3-amd64-hardened # chroot . /bin/bash --login # Now, make sure you turn on]]></description>
			<content:encoded><![CDATA[<p>OK, since Alex asked me last Sunday what exactly needs to be done to turn a simple chroot (or even a bloody box) into a binpkg producing environment, here&#8217;s a little howto &#8230;</p>
<p>First, lets start from a freshly unpacked stage3.</p>
<pre lang="bash">
catalyst/x86 stage3-amd64-hardened # chroot . /bin/bash --login
# Now, make sure you turn on FEATURES=buildpkg
# (and setup anything else you need, like CFLAGS,
# LDFLAGS, whatever)
linux # echo 'FEATURES="buildpkg"' >> /etc/make.conf
</pre>
<p>With that single change you&#8217;re basically nearly finished with setting up the whole thing, the remaining things are just</p>
<ol>
<li>Making sure the binary packages get to a web-enabled (either ftp or http) box, from where you&#8217;re going to fetch the binary packages to their target</li>
<li>Make sure you use binary packages on the target systems by default</li>
</ol>
<p>But first, we&#8217;re gonna need to emerge something within that freshly created build chroot.</p>
<pre lang="bash">
# Let's emerge some packages
linux # emerge -e world -q
... (some minutes/hours/days later)
linux #
</pre>
<p><span id="more-106"></span><br />
Since we now emerged some things we do have quite a few binary packages, which we are going to need on the target systems in order to avoid individual compile time.</p>
<pre lang="bash">
linux # cd /usr/portage/packages/; ls */*
-rw-r--r-- 1 root root  780125 Oct  9 21:59 All/autoconf-2.61-r1.tbz2
-rw-r--r-- 1 root root   24648 Oct  9 21:32 All/autoconf-wrapper-4-r3.tbz2
-rw-r--r-- 1 root root   24331 Oct  9 21:32 All/automake-wrapper-3-r1.tbz2
-rw-r--r-- 1 root root  270794 Oct  9 22:07 All/baselayout-1.12.9-r2.tbz2
-rw-r--r-- 1 root root  734855 Oct  9 21:41 All/bash-3.2_p17.tbz2
-rw-r--r-- 1 root root 3546966 Oct  9 21:51 All/binutils-2.17-r1.tbz2
-rw-r--r-- 1 root root   23989 Oct  9 21:48 All/binutils-config-1.9-r4.tbz2
-rw-r--r-- 1 root root  536021 Oct  9 21:49 All/bison-2.3.tbz2
-rw-r--r-- 1 root root 1589258 Oct  9 21:36 All/busybox-1.6.1.tbz2
-rw-r--r-- 1 root root  592700 Oct  9 21:36 All/bzip2-1.0.4.tbz2
-rw-r--r-- 1 root root  119105 Oct  9 22:03 All/ca-certificates-20070303-r1.tbz2
-rw-r--r-- 1 root root   50235 Oct  9 21:43 All/com_err-1.39.tbz2
-rw-r--r-- 1 root root 2377785 Oct  9 22:05 All/coreutils-6.9-r1.tbz2
-rw-r--r-- 1 root root  180610 Oct  9 21:37 All/cpio-2.9.tbz2
-rw-r--r-- 1 root root  256863 Oct  9 21:31 All/cracklib-2.8.10.tbz2
-rw-r--r-- 1 root root 2356960 Oct  9 21:56 All/db-4.5.20_p2.tbz2
-rw-r--r-- 1 root root   67253 Oct  9 21:58 All/debianutils-2.17.5.tbz2
-rw-r--r-- 1 root root  327359 Oct  9 21:59 All/diffutils-2.8.7-r2.tbz2
-rw-r--r-- 1 root root  805505 Oct  9 21:52 All/e2fsprogs-1.39-r2.tbz2
-rw-r--r-- 1 root root  199867 Oct  9 21:31 All/expat-2.0.1.tbz2
-rw-r--r-- 1 root root  465529 Oct  9 21:44 All/findutils-4.3.8-r1.tbz2
-rw-r--r-- 1 root root  379065 Oct  9 21:45 All/flex-2.5.33-r2.tbz2
-rw-r--r-- 1 root root  947984 Oct  9 21:47 All/gawk-3.1.5-r3.tbz2
-rw-r--r-- 1 root root   47111 Oct  9 21:32 All/gcc-config-1.3.16.tbz2
-rw-r--r-- 1 root root 2049299 Oct  9 21:39 All/gettext-0.16.1-r1.tbz2
-rw-r--r-- 1 root root   71249 Oct  9 21:31 All/gnuconfig-20070118.tbz2
-rw-r--r-- 1 root root  198718 Oct  9 21:45 All/grep-2.5.1a-r1.tbz2
-rw-r--r-- 1 root root 2770274 Oct  9 22:08 All/groff-1.19.2-r1.tbz2
-rw-r--r-- 1 root root  158291 Oct  9 21:46 All/gzip-1.3.12.tbz2
-rw-r--r-- 1 root root   31423 Oct  9 21:32 All/hashalot-0.3-r2.tbz2
-rw-r--r-- 1 root root   18045 Oct  9 21:49 All/init-0.tbz2
-rw-r--r-- 1 root root   94341 Oct  9 21:46 All/iputils-20060512.tbz2
-rw-r--r-- 1 root root 1123810 Oct  9 21:46 All/kbd-1.12-r8.tbz2
-rw-r--r-- 1 root root  183504 Oct  9 21:41 All/less-406.tbz2
-rw-r--r-- 1 root root   18560 Oct  9 21:31 All/libiconv-0.tbz2
-rw-r--r-- 1 root root   18583 Oct  9 21:31 All/libintl-0.tbz2
-rw-r--r-- 1 root root 1937796 Oct  9 21:58 All/libperl-5.8.8-r1.tbz2
-rw-r--r-- 1 root root  514331 Oct  9 21:40 All/linux-headers-2.6.21.tbz2
-rw-r--r-- 1 root root  248267 Oct  9 21:42 All/m4-1.4.9-r1.tbz2
-rw-r--r-- 1 root root  502032 Oct  9 21:48 All/make-3.81.tbz2
-rw-r--r-- 1 root root  282155 Oct  9 22:08 All/man-1.6e-r3.tbz2
-rw-r--r-- 1 root root 4013627 Oct  9 21:59 All/man-pages-2.64.tbz2
-rw-r--r-- 1 root root   40598 Oct  9 21:58 All/mktemp-1.5.tbz2
-rw-r--r-- 1 root root  360001 Oct  9 22:07 All/module-init-tools-3.2.2-r3.tbz2
-rw-r--r-- 1 root root  473826 Oct  9 21:48 All/nano-2.0.6.tbz2
-rw-r--r-- 1 root root 1371743 Oct  9 21:29 All/ncurses-5.6-r1.tbz2
-rw-r--r-- 1 root root  564916 Oct  9 21:46 All/net-tools-1.60-r12.tbz2
-rw-r--r-- 1 root root 3002432 Oct  9 22:02 All/openssl-0.9.8e-r3.tbz2
-rw-r--r-- 1 root root  730702 Oct  9 22:07 All/pam-0.78-r5.tbz2
-rw-r--r-- 1 root root  128006 Oct  9 21:36 All/patch-2.5.9.tbz2
-rw-r--r-- 1 root root   90402 Oct  9 21:31 All/pax-utils-0.1.15.tbz2
-rw-r--r-- 1 root root   23917 Oct  9 21:59 All/perl-cleaner-1.04.3.tbz2
-rw-r--r-- 1 root root  115201 Oct  9 21:32 All/pkgconfig-0.21-r1.tbz2
-rw-r--r-- 1 root root   88097 Oct  9 21:44 All/popt-1.10.7.tbz2
-rw-r--r-- 1 root root  416062 Oct  9 21:27 All/portage-2.1.3.9.tbz2
-rw-r--r-- 1 root root  262433 Oct  9 21:41 All/procps-3.2.7.tbz2
-rw-r--r-- 1 root root   20749 Oct  9 21:33 All/python-updater-0.2.tbz2
-rw-r--r-- 1 root root 1032660 Oct  9 21:45 All/readline-5.2_p7.tbz2
-rw-r--r-- 1 root root  302340 Oct  9 21:49 All/rsync-2.6.9-r3.tbz2
-rw-r--r-- 1 root root   76862 Oct  9 21:33 All/sandbox-1.2.17.tbz2
-rw-r--r-- 1 root root  221380 Oct  9 21:43 All/sed-4.1.5.tbz2
-rw-r--r-- 1 root root   37273 Oct  9 21:33 All/setarch-1.8.tbz2
-rw-r--r-- 1 root root 1186511 Oct  9 22:09 All/shadow-4.0.18.1-r1.tbz2
-rw-r--r-- 1 root root   60436 Oct  9 21:48 All/ss-1.39.tbz2
-rw-r--r-- 1 root root  136646 Oct  9 21:43 All/sysvinit-2.86-r8.tbz2
-rw-r--r-- 1 root root  819482 Oct  9 21:47 All/tar-1.18-r2.tbz2
-rw-r--r-- 1 root root  149255 Oct  9 21:33 All/tcp-wrappers-7.6-r8.tbz2
-rw-r--r-- 1 root root  836401 Oct  9 21:42 All/texinfo-4.8-r5.tbz2
-rw-r--r-- 1 root root  545686 Oct  9 21:34 All/timezone-data-2007g.tbz2
-rw-r--r-- 1 root root  318901 Oct  9 22:07 All/udev-114.tbz2
-rw-r--r-- 1 root root   33969 Oct  9 21:33 All/unifdef-1.20.tbz2
-rw-r--r-- 1 root root 1356353 Oct  9 21:56 All/util-linux-2.12r-r7.tbz2
-rw-r--r-- 1 root root  514592 Oct  9 22:03 All/wget-1.10.2.tbz2
-rw-r--r-- 1 root root   53049 Oct  9 21:49 All/which-2.16.tbz2
-rw-r--r-- 1 root root  153247 Oct  9 21:31 All/zlib-1.2.3-r1.tbz2
lrwxrwxrwx 1 root root      31 Oct  9 21:59 app-admin/perl-cleaner-1.04.3.tbz2 -> ../All/perl-cleaner-1.04.3.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 21:33 app-admin/python-updater-0.2.tbz2 -> ../All/python-updater-0.2.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:36 app-arch/bzip2-1.0.4.tbz2 -> ../All/bzip2-1.0.4.tbz2
lrwxrwxrwx 1 root root      20 Oct  9 21:37 app-arch/cpio-2.9.tbz2 -> ../All/cpio-2.9.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:46 app-arch/gzip-1.3.12.tbz2 -> ../All/gzip-1.3.12.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:47 app-arch/tar-1.18-r2.tbz2 -> ../All/tar-1.18-r2.tbz2
lrwxrwxrwx 1 root root      27 Oct  9 21:32 app-crypt/hashalot-0.3-r2.tbz2 -> ../All/hashalot-0.3-r2.tbz2
lrwxrwxrwx 1 root root      22 Oct  9 21:48 app-editors/nano-2.0.6.tbz2 -> ../All/nano-2.0.6.tbz2
lrwxrwxrwx 1 root root      39 Oct  9 22:03 app-misc/ca-certificates-20070303-r1.tbz2 -> ../All/ca-certificates-20070303-r1.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 21:31 app-misc/pax-utils-0.1.15.tbz2 -> ../All/pax-utils-0.1.15.tbz2
lrwxrwxrwx 1 root root      24 Oct  9 21:41 app-shells/bash-3.2_p17.tbz2 -> ../All/bash-3.2_p17.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:31 dev-libs/expat-2.0.1.tbz2 -> ../All/expat-2.0.1.tbz2
lrwxrwxrwx 1 root root      29 Oct  9 22:02 dev-libs/openssl-0.9.8e-r3.tbz2 -> ../All/openssl-0.9.8e-r3.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:44 dev-libs/popt-1.10.7.tbz2 -> ../All/popt-1.10.7.tbz2
lrwxrwxrwx 1 root root      29 Oct  9 21:32 dev-util/pkgconfig-0.21-r1.tbz2 -> ../All/pkgconfig-0.21-r1.tbz2
lrwxrwxrwx 1 root root      24 Oct  9 21:33 dev-util/unifdef-1.20.tbz2 -> ../All/unifdef-1.20.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 21:46 net-misc/iputils-20060512.tbz2 -> ../All/iputils-20060512.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:49 net-misc/rsync-2.6.9-r3.tbz2 -> ../All/rsync-2.6.9-r3.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 22:03 net-misc/wget-1.10.2.tbz2 -> ../All/wget-1.10.2.tbz2
lrwxrwxrwx 1 root root      32 Oct  9 22:07 sys-apps/baselayout-1.12.9-r2.tbz2 -> ../All/baselayout-1.12.9-r2.tbz2
lrwxrwxrwx 1 root root      25 Oct  9 21:36 sys-apps/busybox-1.6.1.tbz2 -> ../All/busybox-1.6.1.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 22:05 sys-apps/coreutils-6.9-r1.tbz2 -> ../All/coreutils-6.9-r1.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 21:58 sys-apps/debianutils-2.17.5.tbz2 -> ../All/debianutils-2.17.5.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 21:59 sys-apps/diffutils-2.8.7-r2.tbz2 -> ../All/diffutils-2.8.7-r2.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 21:44 sys-apps/findutils-4.3.8-r1.tbz2 -> ../All/findutils-4.3.8-r1.tbz2
lrwxrwxrwx 1 root root      25 Oct  9 21:47 sys-apps/gawk-3.1.5-r3.tbz2 -> ../All/gawk-3.1.5-r3.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:45 sys-apps/grep-2.5.1a-r1.tbz2 -> ../All/grep-2.5.1a-r1.tbz2
lrwxrwxrwx 1 root root      27 Oct  9 22:08 sys-apps/groff-1.19.2-r1.tbz2 -> ../All/groff-1.19.2-r1.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:46 sys-apps/kbd-1.12-r8.tbz2 -> ../All/kbd-1.12-r8.tbz2
lrwxrwxrwx 1 root root      20 Oct  9 21:41 sys-apps/less-406.tbz2 -> ../All/less-406.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 22:08 sys-apps/man-1.6e-r3.tbz2 -> ../All/man-1.6e-r3.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:59 sys-apps/man-pages-2.64.tbz2 -> ../All/man-pages-2.64.tbz2
lrwxrwxrwx 1 root root      22 Oct  9 21:58 sys-apps/mktemp-1.5.tbz2 -> ../All/mktemp-1.5.tbz2
lrwxrwxrwx 1 root root      38 Oct  9 22:07 sys-apps/module-init-tools-3.2.2-r3.tbz2 -> ../All/module-init-tools-3.2.2-r3.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 21:46 sys-apps/net-tools-1.60-r12.tbz2 -> ../All/net-tools-1.60-r12.tbz2
lrwxrwxrwx 1 root root      27 Oct  9 21:27 sys-apps/portage-2.1.3.9.tbz2 -> ../All/portage-2.1.3.9.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:33 sys-apps/sandbox-1.2.17.tbz2 -> ../All/sandbox-1.2.17.tbz2
lrwxrwxrwx 1 root root      21 Oct  9 21:43 sys-apps/sed-4.1.5.tbz2 -> ../All/sed-4.1.5.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:33 sys-apps/setarch-1.8.tbz2 -> ../All/setarch-1.8.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 22:09 sys-apps/shadow-4.0.18.1-r1.tbz2 -> ../All/shadow-4.0.18.1-r1.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 21:43 sys-apps/sysvinit-2.86-r8.tbz2 -> ../All/sysvinit-2.86-r8.tbz2
lrwxrwxrwx 1 root root      31 Oct  9 21:33 sys-apps/tcp-wrappers-7.6-r8.tbz2 -> ../All/tcp-wrappers-7.6-r8.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:42 sys-apps/texinfo-4.8-r5.tbz2 -> ../All/texinfo-4.8-r5.tbz2
lrwxrwxrwx 1 root root      31 Oct  9 21:56 sys-apps/util-linux-2.12r-r7.tbz2 -> ../All/util-linux-2.12r-r7.tbz2
lrwxrwxrwx 1 root root      22 Oct  9 21:49 sys-apps/which-2.16.tbz2 -> ../All/which-2.16.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 21:59 sys-devel/autoconf-2.61-r1.tbz2 -> ../All/autoconf-2.61-r1.tbz2
lrwxrwxrwx 1 root root      33 Oct  9 21:32 sys-devel/autoconf-wrapper-4-r3.tbz2 -> ../All/autoconf-wrapper-4-r3.tbz2
lrwxrwxrwx 1 root root      33 Oct  9 21:32 sys-devel/automake-wrapper-3-r1.tbz2 -> ../All/automake-wrapper-3-r1.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 21:51 sys-devel/binutils-2.17-r1.tbz2 -> ../All/binutils-2.17-r1.tbz2
lrwxrwxrwx 1 root root      34 Oct  9 21:48 sys-devel/binutils-config-1.9-r4.tbz2 -> ../All/binutils-config-1.9-r4.tbz2
lrwxrwxrwx 1 root root      21 Oct  9 21:49 sys-devel/bison-2.3.tbz2 -> ../All/bison-2.3.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:45 sys-devel/flex-2.5.33-r2.tbz2 -> ../All/flex-2.5.33-r2.tbz2
lrwxrwxrwx 1 root root      29 Oct  9 21:32 sys-devel/gcc-config-1.3.16.tbz2 -> ../All/gcc-config-1.3.16.tbz2
lrwxrwxrwx 1 root root      29 Oct  9 21:39 sys-devel/gettext-0.16.1-r1.tbz2 -> ../All/gettext-0.16.1-r1.tbz2
lrwxrwxrwx 1 root root      30 Oct  9 21:31 sys-devel/gnuconfig-20070118.tbz2 -> ../All/gnuconfig-20070118.tbz2
lrwxrwxrwx 1 root root      28 Oct  9 21:58 sys-devel/libperl-5.8.8-r1.tbz2 -> ../All/libperl-5.8.8-r1.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:42 sys-devel/m4-1.4.9-r1.tbz2 -> ../All/m4-1.4.9-r1.tbz2
lrwxrwxrwx 1 root root      21 Oct  9 21:48 sys-devel/make-3.81.tbz2 -> ../All/make-3.81.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 21:36 sys-devel/patch-2.5.9.tbz2 -> ../All/patch-2.5.9.tbz2
lrwxrwxrwx 1 root root      29 Oct  9 21:52 sys-fs/e2fsprogs-1.39-r2.tbz2 -> ../All/e2fsprogs-1.39-r2.tbz2
lrwxrwxrwx 1 root root      20 Oct  9 22:07 sys-fs/udev-114.tbz2 -> ../All/udev-114.tbz2
lrwxrwxrwx 1 root root      32 Oct  9 21:40 sys-kernel/linux-headers-2.6.21.tbz2 -> ../All/linux-headers-2.6.21.tbz2
lrwxrwxrwx 1 root root      24 Oct  9 21:43 sys-libs/com_err-1.39.tbz2 -> ../All/com_err-1.39.tbz2
lrwxrwxrwx 1 root root      27 Oct  9 21:31 sys-libs/cracklib-2.8.10.tbz2 -> ../All/cracklib-2.8.10.tbz2
lrwxrwxrwx 1 root root      24 Oct  9 21:56 sys-libs/db-4.5.20_p2.tbz2 -> ../All/db-4.5.20_p2.tbz2
lrwxrwxrwx 1 root root      26 Oct  9 21:29 sys-libs/ncurses-5.6-r1.tbz2 -> ../All/ncurses-5.6-r1.tbz2
lrwxrwxrwx 1 root root      23 Oct  9 22:07 sys-libs/pam-0.78-r5.tbz2 -> ../All/pam-0.78-r5.tbz2
lrwxrwxrwx 1 root root      27 Oct  9 21:45 sys-libs/readline-5.2_p7.tbz2 -> ../All/readline-5.2_p7.tbz2
lrwxrwxrwx 1 root root      19 Oct  9 21:48 sys-libs/ss-1.39.tbz2 -> ../All/ss-1.39.tbz2
lrwxrwxrwx 1 root root      31 Oct  9 21:34 sys-libs/timezone-data-2007g.tbz2 -> ../All/timezone-data-2007g.tbz2
lrwxrwxrwx 1 root root      25 Oct  9 21:31 sys-libs/zlib-1.2.3-r1.tbz2 -> ../All/zlib-1.2.3-r1.tbz2
lrwxrwxrwx 1 root root      24 Oct  9 21:41 sys-process/procps-3.2.7.tbz2 -> ../All/procps-3.2.7.tbz2
lrwxrwxrwx 1 root root      18 Oct  9 21:49 virtual/init-0.tbz2 -> ../All/init-0.tbz2
lrwxrwxrwx 1 root root      22 Oct  9 21:31 virtual/libiconv-0.tbz2 -> ../All/libiconv-0.tbz2
lrwxrwxrwx 1 root root      21 Oct  9 21:31 virtual/libintl-0.tbz2 -> ../All/libintl-0.tbz2
</pre>
<p>Now, we just need to figure out a way to get the packages to a <strong>remote repository</strong>. That&#8217;s where <a href="http://blog.barfoo.org/wp-content/uploads/2007/10/bashrc">bashrc</a>, rsync and ssh come into play.</p>
<p>Take a looksie at my bashrc (or at solar&#8217;s if you can find it), especially at syncpkg. That&#8217;s the actual function doing all the work for us. It&#8217;s basically guessing what profile you&#8217;re using atm (by reading the info&#8217;s on <em>/etc/make.profile</em> (<a href="http://blog.barfoo.org/wp-content/uploads/2007/10/x86-make.conf">x86</a>, <a href="http://blog.barfoo.org/wp-content/uploads/2007/10/amd64-make.conf">amd64</a>)), and the uploading it to the remote location given by <em>REPO_HOST</em>, <em>REPO_BASE</em> and <em>REPO_TYPE</em> (either via environment or by <em>/etc/make.conf</em>).</p>
<p>Sure the emerge takes a bit longer (since emerge forks an rsync process via ssh that syncs the just merged binary to our remote repository), but that way you have a nice repository, from which you can install one or 1.000 boxes.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/10/12/turning-a-simple-chroot-into-a-binpkg-repository/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>git-lkml for stupid people (like me)</title>
		<link>http://blog.barfoo.org/2007/08/16/git-lkml-for-stupid-people-like-me/</link>
		<comments>http://blog.barfoo.org/2007/08/16/git-lkml-for-stupid-people-like-me/#comments</comments>
		<pubDate>Thu, 16 Aug 2007 14:06:43 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[#gentoo-dev]]></category>
		<category><![CDATA[format-patch]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[Kernel]]></category>
		<category><![CDATA[kernel/sysctl.c]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/2007/08/16/git-lkml-for-stupid-people-like-me/</guid>
		<description><![CDATA[OK, as Stephen recently asked why there is a double inclusion of in kernel/sysctl.c (and I asked Greg and Randy); I finally decided to write a patch to the LKML for possible inclusion. But, git ain&#8217;t easy for people like me (who are used to the easiness of say &#8211; subversion or even cvs). So]]></description>
			<content:encoded><![CDATA[<p>OK, as <a href="http://www.steev.net/">Stephen</a> recently asked why there is a double inclusion of <i>
<linux/capability.h></i> in <a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=kernel/sysctl.c;hb=HEAD">kernel/sysctl.c</a> (and I asked Greg and Randy); I finally decided to write a patch to the LKML for possible inclusion.</p>
<p>But, git ain&#8217;t easy for people like me (who are used to the easiness of say &#8211; subversion or even cvs). So here&#8217;s what I did (thanks to <a href="http://blogs.gentoo.org/ferdy">Fernando</a> for the help earlier today):</p>
<pre lang="text">
$ vim kernel/sysctl.c
// change something
$ git checkout -b sysctl
// create a new branch from your changes, based upon the master repository
$ git commit -a -s
// commit the changes to your newly created branch
$ git format-patch master..sysctl
// Enter a subject and then a separate description
// and you should have a new file in the current working directory starting like 0001-*.patch
</pre>
<p>Now you should have a mailable patch, ready to be sent upstream that looks like this:</p>
<pre lang="diff">
From 839ce261cf688d62bebd9ae3a0101dd672018940 Mon Sep 17 00:00:00 2001
From: Christian Heim
<phreak@gentoo.org>
Date: Sun, 19 Aug 2007 12:51:52 +0200
Subject: [PATCH] Remove double inclusion of linux/capability.h

Remove the second inclusion of linux/capability.h, which has been introduced
with "[PATCH] move capable() to capability.h" (or commit c59ede7b78db329949d9cdcd7064e22d357560ef).

Signed-off-by: Christian Heim
<phreak@gentoo.org>
---
 kernel/sysctl.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 8bdb8c0..9029690 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -27,7 +27,6 @@
 #include
<linux/capability.h>
 #include
<linux/ctype.h>
 #include
<linux/utsname.h>
-#include
<linux/capability.h>
 #include
<linux/smp_lock.h>
 #include
<linux/fs.h>
 #include
<linux/init.h>

--
1.5.3.rc4
</pre>
<p>And if you wanna delete the branch afterwards again, just do this:</p>
<pre lang="text">
$ git checkout master
// Switch back to the master branch
$ git branch -D sysctl
// Delete the old branch named "sysctl"
</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/08/16/git-lkml-for-stupid-people-like-me/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Praise teh sed</title>
		<link>http://blog.barfoo.org/2007/08/05/praise-teh-sed/</link>
		<comments>http://blog.barfoo.org/2007/08/05/praise-teh-sed/#comments</comments>
		<pubDate>Sun, 05 Aug 2007 14:44:05 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[automation]]></category>
		<category><![CDATA[Developer Relations]]></category>
		<category><![CDATA[sed]]></category>
		<category><![CDATA[userinfo.xml]]></category>

		<guid isPermaLink="false">http://blog.barfoo.org/2007/08/05/praise-teh-sed/</guid>
		<description><![CDATA[Since my talk with Robin on Thursday regarding the autogenerated userinfo.xml, I finally found some time today to get all the info&#8217;s I need out of userinfo.xml. Since I don&#8217;t really want to manually enter all those mail addresses from userinfo into LDAP manually, I figured sed might be my best friend. *BUT* sed ain&#8217;t]]></description>
			<content:encoded><![CDATA[<p>Since my talk with <a href="http://robbat2.livejournal.com/">Robin</a> on Thursday regarding the <a href="https://bugs.gentoo.org/show_bug.cgi?id=129355">autogenerated <em>userinfo.xml</em></a>, I finally found some time today to get all the info&#8217;s I need out of <em>userinfo.xml</em>.</p>
<p>Since I don&#8217;t really want to manually enter all those mail addresses from <em>userinfo</em> into LDAP manually, I figured sed might be my best friend. <strong>*BUT*</strong> <em>sed</em> ain&#8217;t easy .. But thanks to Fabian and Gilles, I learned something new about <em>sed</em> today ..</p>
<p>Basically I searched for a way to transform <em>userinfo.xml</em> into a datafile for <em>ldapedit</em>.</p>
<p>As most of you know, <em>userinfo.xml</em> would look like this:</p>
<pre lang="xml">
  <user username="phreak">
    <realname fullname="Christian Heim">
      <firstname>Christian</firstname>
      <familyname>Heim</familyname>
    </realname>
<pgpkey>0x9A9F68E6</pgpkey>
    <email role="gentoo">phreak@gentoo.org</email>
    <joined>06 August 2005</joined>
    <birthday></birthday>
    <roles>vserver, openvz, kernel</roles>
    <location longitude="13.032" latitude="54.251">Germany, Stralsund</location>
  </user>
</pre>
<p>So the first step would be to simply use <em>egrep</em> on <em>userinfo.xm</em>l to filter only the things I needed ..</p>
<pre lang="bash">
celsius roll-call [0] $ egrep "(username=|<email |</user>)" \
userinfo.xml</pre>
<p>That looks more like a processable list to me. Now I only needed to convert the <em><user username="$name"></em> into <strong>dn</strong>, the <em><email role="*"></em> into <strong>mail</strong> and be done with it.</p>
<p>This is what I applied on top of the above filter:</p>
<pre lang="bash">
celsius roll-call [0] $ egrep "(username=|<email |</user>)" \
userinfo.xml | \
 sed -e "s,.*<user username=\",dn: uid=," \
     -e "s,\">$,\,ou=devs\,dc=gentoo\,dc=org\nadd: mail," \
     -e 's,.*<email role="\\(gentoo\\|primary\\)">,mail: ,' \
     -e "s,</email>,," -e "s,  </user>,,"</pre>
<p>And that&#8217;s it, I just need to check the dn&#8217;s for all the users, and when I&#8217;m done with that, finito!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/08/05/praise-teh-sed/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Progress with apache-2.2</title>
		<link>http://blog.barfoo.org/2007/05/28/progress-with-apache-22/</link>
		<comments>http://blog.barfoo.org/2007/05/28/progress-with-apache-22/#comments</comments>
		<pubDate>Mon, 28 May 2007 16:04:10 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[apache-tools]]></category>

		<guid isPermaLink="false">http://blogs.barfoo.org/phreak/2007/05/28/progress-with-apache-22/</guid>
		<description><![CDATA[We&#8217;re finally making some progress with apache-2.2. It left the package.mask on the 8th of May (that&#8217;s like 3 weeks from tomorrow), we split some helper scripts into a separate package (app-admin/apache-tools). I already fixed a few screwup I did myself (like apxs missing from either apache and apache-tools, or the compatibility symlinks being missing),]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re finally making some progress with apache-2.2. It left the package.mask on the 8th of May (that&#8217;s like 3 weeks from tomorrow), we split some helper scripts into a separate package (app-admin/apache-tools).</p>
<p>I already fixed a few screwup I did myself (like apxs missing from either apache and apache-tools, or the compatibility symlinks being missing), so we &#8220;just&#8221; need to fix all the modules in the tree before apache-2.2 is going to get the new stable version (and of course anything else depending on. What also remains to do, is committing the new-style virtuals for bug 11007.</p>
<p>Also apache-1* is going to get removed from the tree pretty soon now (like starting next month 12th iirc). Now if anyone is going to start again, about apache-1* being &#8220;<strong>sooo</strong>&#8221; great and &#8220;<strong>waaay</strong>&#8221; better then the 2.* series, it may be yes.</p>
<p>But the point is, we (as in the apache team) needs to maintain it. Some other points include:</p>
<ol>
<li>We don&#8217;t have the manpower and/or time to maintain it any longer</li>
<li>We don&#8217;t have the slightest interest anymore in apache-1, which hasn&#8217;t seen a release in about a year (July 2006 was the last release)</li>
</ol>
<p>So, if you want to keep it around, either grab it from the attic at <a href="http://anoncvs.gentoo.org">anoncvs.gentoo.org</a>/<a href="http://sources.gentoo.org/cgi-bin/viewvc.cgi">sources.gentoo.org</a> or copy it to an local/whatever overlay now, as its still in the tree.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/05/28/progress-with-apache-22/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>grub via serial console</title>
		<link>http://blog.barfoo.org/2007/04/10/grub-via-serial-console/</link>
		<comments>http://blog.barfoo.org/2007/04/10/grub-via-serial-console/#comments</comments>
		<pubDate>Tue, 10 Apr 2007 15:09:17 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[safekeeping]]></category>
		<category><![CDATA[serial console]]></category>

		<guid isPermaLink="false">http://blogs.barfoo.org/phreak/2007/04/10/grub-via-serial-console/</guid>
		<description><![CDATA[As I have quite some trouble every time I need grub via serial console, here&#8217;s just my personal reminder on how to do it right: # cat /boot/grub/grub.conf serial --unit=0 --speed=38400 terminal --timeout=15 console serial title hardened-sources-2.6.20-r1 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.20-hardened-r1 root=/dev/hda1 console=ttyS0,38400 console=tty0 Additionally the agetty entry for ttyS0 in /etc/inittab needs to be]]></description>
			<content:encoded><![CDATA[<p>As I have quite some trouble every time I need grub via serial console, here&#8217;s just my personal reminder on how to do it right:</p>
<pre lang="bash">
# cat /boot/grub/grub.conf
serial --unit=0 --speed=38400
terminal --timeout=15  console serial

title	hardened-sources-2.6.20-r1
root	(hd0,0)
kernel	(hd0,0)/boot/vmlinuz-2.6.20-hardened-r1 root=/dev/hda1 console=ttyS0,38400 console=tty0</pre>
<p>Additionally the agetty entry for ttyS0 in <em>/etc/inittab</em> needs to be uncommented and changed accordingly to the serial speed</p>
<pre lang="bash">
# cat /etc/inittab | tail
s0:12345:respawn:/sbin/agetty 38400 ttyS0 vt100</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/04/10/grub-via-serial-console/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Saying thank you</title>
		<link>http://blog.barfoo.org/2007/04/08/saying-thank-you/</link>
		<comments>http://blog.barfoo.org/2007/04/08/saying-thank-you/#comments</comments>
		<pubDate>Sun, 08 Apr 2007 05:30:20 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[FOSDEM]]></category>
		<category><![CDATA[Gentoo/Hardened]]></category>
		<category><![CDATA[releng]]></category>

		<guid isPermaLink="false">http://blogs.barfoo.org/phreak/2007/04/08/saying-thank-you/</guid>
		<description><![CDATA[As I&#8217;m way better writing stuff than saying it with my own words, here a short &#8220;Thank you!&#8220; Christel, you have been a gracious and honest person, thanks for all the advice and help in the last year Chrissy, thanks for the inspiring words, you really made/make me feel better Alec (antarus), you&#8217;ve been a]]></description>
			<content:encoded><![CDATA[<p>As I&#8217;m way better writing stuff than saying it with my own words, here a short <em>&#8220;</em><strong>Thank you!</strong><em>&#8220;</em></p>
<ol>
<li>Christel, you have been a gracious and honest person, thanks for all the advice and help in the last year</li>
<li>Chrissy, thanks for the inspiring words, you really made/make me feel better</li>
<li>Alec (antarus), you&#8217;ve been a real friend and to say it with your own words <em>&#8220;It sucks to be you&#8221;</em>; to phrase it differently, I&#8217;m really going to miss you</li>
<li>Bryan, thanks for all the help, thanks for all the fun at FOSDEM (and after FOSDEM, hah)</li>
<li>Ned, Alexander (pappy); you&#8217;ve both been an inspiration, thanks for letting me work on hardened foo; it has been real fun</li>
<li>Mike (vapier), thanks for being a smart ass and inspiration at the same time</li>
<li>Chris, thanks for the inspiration and for being a sarcastic person <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </li>
<li>Andrew, thanks for trying to make a fun out of me <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' />  and thanks for warning me of Chris&#8217;s sarcasm</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/04/08/saying-thank-you/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Post FOSDEM 2007 thoughts (do I know you ?)</title>
		<link>http://blog.barfoo.org/2007/03/26/post-fosdem-2007-thoughts-do-i-know-you/</link>
		<comments>http://blog.barfoo.org/2007/03/26/post-fosdem-2007-thoughts-do-i-know-you/#comments</comments>
		<pubDate>Mon, 26 Mar 2007 19:19:09 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[FOSDEM]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Vacation]]></category>

		<guid isPermaLink="false">http://blogs.barfoo.org/phreak/2007/03/26/post-fosdem-2007-thoughts-do-i-know-you/</guid>
		<description><![CDATA[Some of us attended this years FOSDEM in Brussels (thanks to Dimitry it was *really*, *really* great). We (at least the ones attending) got to know each other a bit better (I even got to know some pre Gentoo devs .. yeah, you), and some time after FOSDEM (I think it was ~3 days afterwards),]]></description>
			<content:encoded><![CDATA[<p>Some of us attended this years FOSDEM in Brussels (thanks to Dimitry it was <strong>*really*</strong>, <strong>*really*</strong> great).</p>
<p>We (at least the ones attending) got to know each other a bit better (I even got to know some pre Gentoo devs .. yeah, you), and some time after FOSDEM (I think it was ~3 days afterwards), Petteri (betelgeuse) asked me why people all of the sudden start to call him with his first name on IRC.</p>
<p>I think the cause for that is just seeing each other for some time (like 2 days in a row), talking to the other(s) in person makes you feel closer to him/her (you hopefully know what I mean <img src='http://blog.barfoo.org/wp-includes/images/smilies/icon_eek.gif' alt=':shock:' class='wp-smiley' />  ). Or maybe that&#8217;s just me.</p>
<p>After FOSDEM the <em>virtual bonds</em> changed, I started to call quite some people by their first name as did others.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/03/26/post-fosdem-2007-thoughts-do-i-know-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gentoo/hardened and the new toolchain</title>
		<link>http://blog.barfoo.org/2007/02/26/gentoohardened-and-the-new-toolchain/</link>
		<comments>http://blog.barfoo.org/2007/02/26/gentoohardened-and-the-new-toolchain/#comments</comments>
		<pubDate>Mon, 26 Feb 2007 09:28:44 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Life]]></category>
		<category><![CDATA[GDB]]></category>
		<category><![CDATA[Gentoo/Hardened]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[toolchain]]></category>

		<guid isPermaLink="false">http://blogs.barfoo.org/phreak/2007/02/26/gentoohardened-and-the-new-toolchain/</guid>
		<description><![CDATA[OK, as some of you have noticed; I prepared my box for the new toolchain, recompiled the stuff Kevin mentioned in the exact same order wrote down in his README, and it looks like it actually works with all my stuff I have on my box; except sys-libs/grub! *sigh* Apparently, grub segfaults at boot and/or]]></description>
			<content:encoded><![CDATA[<p>OK, as some of you have noticed; I prepared my box for the new toolchain, recompiled the stuff Kevin mentioned in the exact same order wrote down in his README, and it looks like it actually works with all my stuff I have on my box; except <em>sys-libs/grub</em>! <strong>*sigh*</strong></p>
<p>Apparently, grub segfaults at boot and/or while running it from the chroot in the exact same spot, the new QA warnings complain about ..</p>
<pre lang="text">* QA Notice: Package has poor programming practices which may compile
*            fine but exhibit random runtime failures.
* char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:222: warning: dereferencing type-punned pointer will break strict-aliasing rules
builtins.c:4862: warning: dereferencing type-punned pointer will break strict-aliasing rules
disk_io.c:1027: warning: dereferencing type-punned pointer will break strict-aliasing rules
disk_io.c:1057: warning: dereferencing type-punned pointer will break strict-aliasing rules
tparm.c:719: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:222: warning: dereferencing type-punned pointer will break strict-aliasing rules
builtins.c:4862: warning: dereferencing type-punned pointer will break strict-aliasing rules
disk_io.c:1027: warning: dereferencing type-punned pointer will break strict-aliasing rules
disk_io.c:1057: warning: dereferencing type-punned pointer will break strict-aliasing rules
tparm.c:719: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules
char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules</pre>
<p>So, I unpacked the libc and grub debug files, to get a clue where it&#8217;s failing and fed the program execution into gdb and viola:</p>
<pre lang="text">GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) run
Starting program: /sbin/grub --no-floppy

Program received signal SIGSEGV, Segmentation fault.
grub_putstr (str=0xa1660489) at char_io.c:174
in char_io.c
(gdb) quit
The program is running.  Exit anyway? (y or n)</pre>
<p>I&#8217;m not yet sure if it really is the same spot, but I&#8217;ll let Kevin have a shot at it &#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.barfoo.org/2007/02/26/gentoohardened-and-the-new-toolchain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
