<?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>chys&#039;s random notes &#187; Gentoo</title>
	<atom:link href="http://en.chys.info/tag/gentoo/feed/" rel="self" type="application/rss+xml" />
	<link>http://en.chys.info</link>
	<description>Study more problems; Talk less of isms.</description>
	<lastBuildDate>Tue, 27 Dec 2011 11:56:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>NPTL_KERN_VER</title>
		<link>http://en.chys.info/2010/05/nptl_kern_ver/</link>
		<comments>http://en.chys.info/2010/05/nptl_kern_ver/#comments</comments>
		<pubDate>Mon, 03 May 2010 08:14:08 +0000</pubDate>
		<dc:creator>chys</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Gentoo]]></category>

		<guid isPermaLink="false">http://en.chys.info/?p=805</guid>
		<description><![CDATA[In Gentoo, this variable can be used to specify the lowest kernel version we want glibc to support. For example, I am completely certain I will never use a kernel older than 2.6.30 on my Gentoo box, so I may want to add NPTL_KERN_VER="2.6.30" to /etc/make.conf. This way, glibc will assume the kernel supports all [...]<hr/>
No related posts.]]></description>
			<content:encoded><![CDATA[<p>In Gentoo, this variable can be used to specify the lowest kernel version we want glibc to support. For example, I am completely certain I will never use a kernel older than 2.6.30 on my Gentoo box, so I may want to add <code>NPTL_KERN_VER="2.6.30"</code> to <code>/etc/make.conf</code>. This way, glibc will assume the kernel supports all features that 2.6.30 supports and remove fallback codes written for old kernels.</p>
<p>The default value for <code>NPTL_KERN_VER</code> has been 2.6.9 for years.</p>
<p>That will not make a real difference, though. By switching from 2.6.9 to 2.6.30, the size of my <code>/lib/libc.so.6</code> reduced by approximately 20KiB, or 1.3%.</p>
<hr/><p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://en.chys.info/2010/05/nptl_kern_ver/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Removed some distribution-specific patches</title>
		<link>http://en.chys.info/2010/03/removed-some-distribution-specific-patches/</link>
		<comments>http://en.chys.info/2010/03/removed-some-distribution-specific-patches/#comments</comments>
		<pubDate>Wed, 24 Mar 2010 06:56:21 +0000</pubDate>
		<dc:creator>chys</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://en.chys.info/?p=783</guid>
		<description><![CDATA[With all due respect to Gentoo developers, I really hate the patches they made for coreutils, especially the one to have uname parse /proc/cpuinfo. The result is that uname -a displays more info, specifically the mode of the CPU, on Gentoo than other Linux distributions. Generally this is not a bad thing. But I do [...]<hr/>
No related posts.]]></description>
			<content:encoded><![CDATA[<p>With all due respect to Gentoo developers, I really hate the patches they made for <a href="http://www.gnu.org/software/coreutils/">coreutils</a>, especially the one to have <code><a href="http://linux.die.net/man/1/uname">uname</a></code> parse <code>/proc/cpuinfo</code>.</p>
<p>The result is that <code>uname -a</code> displays more info, specifically the mode of the CPU, on Gentoo than other Linux distributions. Generally this is not a bad thing. But I do have concerns:</p>
<p>(1) In my view the utility <code>uname</code> should remain a simple wrapper of the <a href="http://linux.die.net/man/2/uname">homonym system call</a>. If CPU/vendor info really needs to be returned by <code>uname</code>, it is better to add it to kernel. This is also part of the reason why upstream <a href="http://lists.gnu.org/archive/html/bug-coreutils/2005-09/msg00063.html">rejected</a> this patch.</p>
<p>(2) If I am used to finding CPU info from <code>uname</code>, I will likely forget the more orthodox method (<code>cat /proc/cpuinfo</code>). A job interviewer may not be that patient to listen to my explanation about the patch.</p>
<hr/><p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://en.chys.info/2010/03/removed-some-distribution-specific-patches/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Extract Deb files from command line</title>
		<link>http://en.chys.info/2010/02/extract-deb-files/</link>
		<comments>http://en.chys.info/2010/02/extract-deb-files/#comments</comments>
		<pubDate>Mon, 01 Feb 2010 16:15:12 +0000</pubDate>
		<dc:creator>chys</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://en.chys.info/?p=739</guid>
		<description><![CDATA[Debian and its derivatives use the .deb format to distribute their packages. To extract them, use ar &#8211; Yes, the very program we programmers use to make static libraries. ar x sudo_1.6.9p17-2_i386.deb Or we can directly extract things from data.tar.gz contained in the .deb file: ar p sudo_1.6.9p17-2_i386.deb data.tar.gz &#124; tar -xzf - No longer [...]<hr/>
Related posts:<ol>
<li><a href='http://en.chys.info/2010/12/concatenate-pdf-files-in-linux/' rel='bookmark' title='Concatenate PDF files in Linux'>Concatenate PDF files in Linux</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.debian.org">Debian</a> and its derivatives use the <code>.deb</code> format to distribute their packages. To extract them, use <code>ar</code> &#8211; Yes, the very program we programmers use to make static libraries.</p>
<blockquote><p><code>ar x sudo_1.6.9p17-2_i386.deb</code></p></blockquote>
<p>Or we can directly extract things from <code>data.tar.gz</code> contained in the <code>.deb</code> file:</p>
<blockquote><p><code>ar p sudo_1.6.9p17-2_i386.deb data.tar.gz | tar -xzf -</code></p></blockquote>
<p>No longer a user of Debian GNU/Linux, I still have to remember how to extract <code>.deb</code> files. I frequently need to cross-compile a 64-bit version of my program on a 32-bit system, and vice versa; but I don&#8217;t want to cross-compile by myself so many libraries on which my program depends. Instead, I find it a good idea to download a right <code>.deb</code> file from the <a href="http://www.debian.org/distrib/packages">Debian Packages Repository</a> and pick out the <code>.so</code> files.</p>
<hr/><p>Related posts:<ol>
<li><a href='http://en.chys.info/2010/12/concatenate-pdf-files-in-linux/' rel='bookmark' title='Concatenate PDF files in Linux'>Concatenate PDF files in Linux</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://en.chys.info/2010/02/extract-deb-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[Gentoo] Logrotating emerge.log</title>
		<link>http://en.chys.info/2009/04/logrotating-emergelog/</link>
		<comments>http://en.chys.info/2009/04/logrotating-emergelog/#comments</comments>
		<pubDate>Sat, 04 Apr 2009 18:20:50 +0000</pubDate>
		<dc:creator>chys</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[logrotate]]></category>
		<category><![CDATA[portage]]></category>

		<guid isPermaLink="false">http://en.chys.info/?p=452</guid>
		<description><![CDATA[It seems the reason why emerge.log is not logrotate&#8216;d is that log analyzers (qlop and genlop) expect a full log. I&#8217;m not sure about qlop, but since I use only genlop, it seems okay to add it to /etc/logrotate.d &#8211; genlop supports reading logs from multiple files and also from compressed files (gzip and bzip2). [...]<hr/>
Related posts:<ol>
<li><a href='http://en.chys.info/2009/05/liblzmadec-sucks/' rel='bookmark' title='liblzmadec sucks'>liblzmadec sucks</a></li>
<li><a href='http://en.chys.info/2009/03/gentoo-begins-to-mark-gcc-43-stable/' rel='bookmark' title='Gentoo begins to mark gcc-4.3 stable'>Gentoo begins to mark gcc-4.3 stable</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>It seems the reason why <code>emerge.log</code> is not <a href="https://fedorahosted.org/logrotate/">logrotate</a>&#8216;d is that log analyzers (<code>qlop</code> and <code>genlop</code>) expect a full log. I&#8217;m not sure about <code>qlop</code>, but since I use only <code>genlop</code>, it seems okay to add it to <code>/etc/logrotate.d</code> &#8211; <code>genlop</code> supports reading logs from multiple files and also from compressed files (<code>gzip</code> and <code>bzip2</code>).</p>
<p>Create a logrotate configuration file. <code>/etc/logrotate.d/emergelog</code>:</p>
<blockquote><pre>/var/log/emerge.log {
    compresscmd /bin/bzip2
    uncompresscmd /bin/bunzip2
    compressext .bz2
    rotate 100
    create 660 portage portage
    delaycompress
    daily
    size 2M
}</pre>
</blockquote>
<p>I configured my logrotate to compress using <code><a href="http://tukaani.org/lzma/">lzma</a></code> by default, but <code>genlop</code> recognizes only <code>gz</code> and <code>bz2</code>, so I need to explicitly specify <code>bzip2</code> (or <code>gzip</code>) here.</p>
<p>A wrapper for genlop is also necessary. <code>/usr/local/bin/genlop</code>:</p>
<blockquote><pre>#!/bin/bash

f=()
for x in /var/log/emerge.log*; do
    f=("${f[@]}" -f "$x")
done
exec /usr/bin/genlop "${f[@]}" "$@"</pre>
</blockquote>
<hr/><p>Related posts:<ol>
<li><a href='http://en.chys.info/2009/05/liblzmadec-sucks/' rel='bookmark' title='liblzmadec sucks'>liblzmadec sucks</a></li>
<li><a href='http://en.chys.info/2009/03/gentoo-begins-to-mark-gcc-43-stable/' rel='bookmark' title='Gentoo begins to mark gcc-4.3 stable'>Gentoo begins to mark gcc-4.3 stable</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://en.chys.info/2009/04/logrotating-emergelog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gentoo begins to mark gcc-4.3 stable</title>
		<link>http://en.chys.info/2009/03/gentoo-begins-to-mark-gcc-43-stable/</link>
		<comments>http://en.chys.info/2009/03/gentoo-begins-to-mark-gcc-43-stable/#comments</comments>
		<pubDate>Mon, 30 Mar 2009 05:46:08 +0000</pubDate>
		<dc:creator>chys</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[GCC]]></category>
		<category><![CDATA[Gentoo]]></category>

		<guid isPermaLink="false">http://blog.chys.info/?p=437</guid>
		<description><![CDATA[Already done in amd64. It seems it&#8217;s going to happen to all others arches very soon. I have been waiting for this for more than six months&#8230; GCC 4.3 eliminated some implicit inclusions among headers, and therefore has caused many compilation errors &#8211; most notably missing &#60;cstdlib&#62; and &#60;cstring&#62;. (It&#8217;s not GCC&#8217;s fault; it&#8217;s the [...]<hr/>
Related posts:<ol>
<li><a href='http://en.chys.info/2009/04/globstar-in-bash-4-follows-symlinks/' rel='bookmark' title='globstar in bash 4 follows directory symlinks'>globstar in bash 4 follows directory symlinks</a></li>
<li><a href='http://en.chys.info/2009/04/logrotating-emergelog/' rel='bookmark' title='[Gentoo] Logrotating emerge.log'>[Gentoo] Logrotating emerge.log</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Already done in amd64. It seems it&#8217;s going to happen to all others <acronym title="architectures">arches</acronym> very soon.</p>
<p>I have been waiting for this for more than six months&#8230;</p>
<p>GCC 4.3 eliminated some implicit inclusions among headers, and therefore has caused <a href="http://bugs.gentoo.org/show_bug.cgi?id=198121">many compilation errors</a> &#8211; most notably missing <code>&lt;cstdlib&gt;</code> and <code>&lt;cstring&gt;</code>. (It&#8217;s not GCC&#8217;s fault; it&#8217;s the coders&#8217;.)</p>
<p>I switched my default compiler from 4.2.4 to 4.3.2 just a few days ago, so I&#8217;m not a real hacker &#8211; hackers* always live on the <a href="http://en.wikipedia.org/wiki/Bleeding_edge">bleeding edge</a>. I reported only two bugs exposed by GCC 4.3 &#8211; should have been more had I switched earlier..</p>
<p>* A hacker is different from a cracker! Those who illegally and/or immorally crack computer systems or proprietary software should be called crackers.</p>
<hr/><p>Related posts:<ol>
<li><a href='http://en.chys.info/2009/04/globstar-in-bash-4-follows-symlinks/' rel='bookmark' title='globstar in bash 4 follows directory symlinks'>globstar in bash 4 follows directory symlinks</a></li>
<li><a href='http://en.chys.info/2009/04/logrotating-emergelog/' rel='bookmark' title='[Gentoo] Logrotating emerge.log'>[Gentoo] Logrotating emerge.log</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://en.chys.info/2009/03/gentoo-begins-to-mark-gcc-43-stable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disk size needed to compile OpenOffice</title>
		<link>http://en.chys.info/2008/10/disk-size-needed-to-compile-openoffice/</link>
		<comments>http://en.chys.info/2008/10/disk-size-needed-to-compile-openoffice/#comments</comments>
		<pubDate>Sun, 19 Oct 2008 06:25:00 +0000</pubDate>
		<dc:creator>chys</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[OpenOffice]]></category>

		<guid isPermaLink="false">http://blog.chys.info/2008/10/disk-size-needed-to-compile-openoffice/</guid>
		<description><![CDATA[Gentoo today stabilized openoffice 3.0. I then emerged it in two systems. OpenOffice 3 now supports parallel building, so there should be a speedup compared with 2.4 in an multi-core system. x86 laptop: debugging is completely disabled. About 5 GiB. amd64 desktop: CFLAGS=&#8221;&#8230; -ggdb&#8221;; FEATURES=&#8221;splitdebug&#8220;. More than 11GiB! This work is licensed under a Creative [...]<hr/>
Related posts:<ol>
<li><a href='http://en.chys.info/2008/10/c0x-draft-finished/' rel='bookmark' title='C++0x draft finished'>C++0x draft finished</a></li>
<li><a href='http://en.chys.info/2008/11/ssh-without-password/' rel='bookmark' title='SSH without password'>SSH without password</a></li>
<li><a href='http://en.chys.info/2009/01/difference-between-dup0-and-opendevfd0/' rel='bookmark' title='Difference between dup(0) and open(&#8220;/dev/fd/0&#8243;,&#8230;);'>Difference between dup(0) and open(&#8220;/dev/fd/0&#8243;,&#8230;);</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Gentoo today stabilized openoffice 3.0. I then emerged it in two systems. OpenOffice 3 now supports parallel building, so there should be a speedup compared with 2.4 in an multi-core system.</p>
<p>x86 laptop: debugging is completely disabled. About 5 GiB.</p>
<p>amd64 desktop: CFLAGS=&#8221;&#8230; -ggdb&#8221;; FEATURES=&#8221;<a href="http://www.tarkblog.org/general/476">splitdebug</a>&#8220;. More than 11GiB!
<div class="blogger-post-footer">
<hr />
<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://creativecommons.org/images/public/somerights20.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/">Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License</a>.</div>
<hr/><p>Related posts:<ol>
<li><a href='http://en.chys.info/2008/10/c0x-draft-finished/' rel='bookmark' title='C++0x draft finished'>C++0x draft finished</a></li>
<li><a href='http://en.chys.info/2008/11/ssh-without-password/' rel='bookmark' title='SSH without password'>SSH without password</a></li>
<li><a href='http://en.chys.info/2009/01/difference-between-dup0-and-opendevfd0/' rel='bookmark' title='Difference between dup(0) and open(&#8220;/dev/fd/0&#8243;,&#8230;);'>Difference between dup(0) and open(&#8220;/dev/fd/0&#8243;,&#8230;);</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://en.chys.info/2008/10/disk-size-needed-to-compile-openoffice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

