<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Blog Pseudoaccidentale</title>
	<atom:link href="http://keramida.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://keramida.wordpress.com</link>
	<description></description>
	<lastBuildDate>Wed, 25 Nov 2009 18:57:43 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by ArenWeeld</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12369</link>
		<dc:creator>ArenWeeld</dc:creator>
		<pubDate>Wed, 25 Nov 2009 18:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12369</guid>
		<description>Waow loved reading your blogpost. I submitted your rss to my reader.</description>
		<content:encoded><![CDATA[<p>Waow loved reading your blogpost. I submitted your rss to my reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by pac</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12368</link>
		<dc:creator>pac</dc:creator>
		<pubDate>Sun, 22 Nov 2009 18:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12368</guid>
		<description>I just chsh take it that this might affect me.....
Shell: /usr/local/bin/bash</description>
		<content:encoded><![CDATA[<p>I just chsh take it that this might affect me&#8230;..<br />
Shell: /usr/local/bin/bash</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by Elias Chrysocheris</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12366</link>
		<dc:creator>Elias Chrysocheris</dc:creator>
		<pubDate>Wed, 18 Nov 2009 15:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12366</guid>
		<description>Basically, that is why you NEVER change the csh shell of the root account and do all your updates WITHOUT sudo (Ubuntu haters) when you do such trivial tasks as updates! An su will also save you some time because:
1. it is 2 characters smaller :-P
2. You don&#039;t have to type it again and again when performing portsnap updates and portupgrades e.t.c.</description>
		<content:encoded><![CDATA[<p>Basically, that is why you NEVER change the csh shell of the root account and do all your updates WITHOUT sudo (Ubuntu haters) when you do such trivial tasks as updates! An su will also save you some time because:<br />
1. it is 2 characters smaller :-P<br />
2. You don&#8217;t have to type it again and again when performing portsnap updates and portupgrades e.t.c.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by Ben Grimm</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12365</link>
		<dc:creator>Ben Grimm</dc:creator>
		<pubDate>Wed, 18 Nov 2009 13:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12365</guid>
		<description>I have upgraded gettext several times (even recurisvely, when /usr/ports/UPDATING mandated it) and I can&#039;t say that I have ever come across this problem. The difference may be that I have bash as a shell in /etc/passwd (on the toor account, not the root account, of course), so it&#039;s not launched from .cshrc, but invoked directly on logon. Could it be that the way you invoke bash exposes it to this specific problem?</description>
		<content:encoded><![CDATA[<p>I have upgraded gettext several times (even recurisvely, when /usr/ports/UPDATING mandated it) and I can&#8217;t say that I have ever come across this problem. The difference may be that I have bash as a shell in /etc/passwd (on the toor account, not the root account, of course), so it&#8217;s not launched from .cshrc, but invoked directly on logon. Could it be that the way you invoke bash exposes it to this specific problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by keramida</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12364</link>
		<dc:creator>keramida</dc:creator>
		<pubDate>Wed, 18 Nov 2009 10:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12364</guid>
		<description>@adamo: That&#039;s I don&#039;t actually change the shell of root in /etc/master.passwd but I exec the bash/ksh version.  I was just amused by the interaction of exec bash and gettext upgrades.  Now that I have understood what&#039;s going on, I&#039;m going to be careful when rebuilding ports from source.

@stathis: One of the things I want to experiment with is zfs snapshots before major upgrades.  That&#039;s why my laptop now runs with a ZFS root filesystem and the root fs is a zfs dataset of its own:

&lt;pre&gt;keramida@kobe:~$ &lt;strong&gt;df -ht zfs&lt;/strong&gt;
Filesystem            Size    Used   Avail Capacity  Mounted on
kobe                   98G    1.2G     97G     1%    /
kobe/local            101G    3.9G     97G     4%    /usr/local
kobe/ports             97G    622M     97G     1%    /usr/ports
kobe/distfiles         99G    2.5G     97G     2%    /usr/ports/distfiles
kobe/packages          98G    1.7G     97G     2%    /usr/ports/packages
kobe/home/keramida    108G     11G     97G    11%    /home/keramida
...
keramida@kobe:~$&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>@adamo: That&#8217;s I don&#8217;t actually change the shell of root in /etc/master.passwd but I exec the bash/ksh version.  I was just amused by the interaction of exec bash and gettext upgrades.  Now that I have understood what&#8217;s going on, I&#8217;m going to be careful when rebuilding ports from source.</p>
<p>@stathis: One of the things I want to experiment with is zfs snapshots before major upgrades.  That&#8217;s why my laptop now runs with a ZFS root filesystem and the root fs is a zfs dataset of its own:</p>
<pre>keramida@kobe:~$ <strong>df -ht zfs</strong>
Filesystem            Size    Used   Avail Capacity  Mounted on
kobe                   98G    1.2G     97G     1%    /
kobe/local            101G    3.9G     97G     4%    /usr/local
kobe/ports             97G    622M     97G     1%    /usr/ports
kobe/distfiles         99G    2.5G     97G     2%    /usr/ports/distfiles
kobe/packages          98G    1.7G     97G     2%    /usr/ports/packages
kobe/home/keramida    108G     11G     97G    11%    /home/keramida
...
keramida@kobe:~$</pre>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by Stathis</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12363</link>
		<dc:creator>Stathis</dc:creator>
		<pubDate>Wed, 18 Nov 2009 10:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12363</guid>
		<description>On a more general note, I like the way Solaris handles system updates. Creating a clone of the root filesystem and updating the clone, with the ability to rollback to your last good working snapshot. This solves or rather it avoids a whole class of problems.

I hope BSDs and Linux will eventually provide something similar (no, chroots aren&#039;t good enough :P). FreeBSD has zfs so it should be doable in principle.

Cheers</description>
		<content:encoded><![CDATA[<p>On a more general note, I like the way Solaris handles system updates. Creating a clone of the root filesystem and updating the clone, with the ability to rollback to your last good working snapshot. This solves or rather it avoids a whole class of problems.</p>
<p>I hope BSDs and Linux will eventually provide something similar (no, chroots aren&#8217;t good enough :P). FreeBSD has zfs so it should be doable in principle.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Careful With SHELL=/usr/local/bin/bash by adamo</title>
		<link>http://keramida.wordpress.com/2009/11/18/be-careful-with-bash/#comment-12362</link>
		<dc:creator>adamo</dc:creator>
		<pubDate>Wed, 18 Nov 2009 09:42:16 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=729#comment-12362</guid>
		<description>I am now reminded of our discussion with @mperedim on how it is inadvisable to not change the root shell.</description>
		<content:encoded><![CDATA[<p>I am now reminded of our discussion with @mperedim on how it is inadvisable to not change the root shell.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using the Condensed DejaVu Font-Family Variant by Default by keramida</title>
		<link>http://keramida.wordpress.com/2009/11/07/dejavu-condensed-as-default/#comment-12361</link>
		<dc:creator>keramida</dc:creator>
		<pubDate>Tue, 17 Nov 2009 12:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=652#comment-12361</guid>
		<description>I know the feeling.  I still use my own hacked version of lucida-sans-typewriter-12 for terminals.  TrueType fonts look less pleasing to my eyes for code and terminal windows.

I&#039;m glad you liked the condensed variants, Philip :-)</description>
		<content:encoded><![CDATA[<p>I know the feeling.  I still use my own hacked version of lucida-sans-typewriter-12 for terminals.  TrueType fonts look less pleasing to my eyes for code and terminal windows.</p>
<p>I&#8217;m glad you liked the condensed variants, Philip :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using the Condensed DejaVu Font-Family Variant by Default by Philip Paeps</title>
		<link>http://keramida.wordpress.com/2009/11/07/dejavu-condensed-as-default/#comment-12360</link>
		<dc:creator>Philip Paeps</dc:creator>
		<pubDate>Tue, 17 Nov 2009 10:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=652#comment-12360</guid>
		<description>I&#039;ve been using these fonts for a couple of days now and I have to say: much friendlier on the eyes than the &quot;default&quot; DejaVu fonts.  I&#039;m still absolutely not convinced about &quot;truetype&quot; fonts for code (I still use terminus for all my fixed-width needs), but this tip made &quot;the web&quot; slightly less unpleasant for me again.

Thanks. :-)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using these fonts for a couple of days now and I have to say: much friendlier on the eyes than the &#8220;default&#8221; DejaVu fonts.  I&#8217;m still absolutely not convinced about &#8220;truetype&#8221; fonts for code (I still use terminus for all my fixed-width needs), but this tip made &#8220;the web&#8221; slightly less unpleasant for me again.</p>
<p>Thanks. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using the Condensed DejaVu Font-Family Variant by Default by keramida</title>
		<link>http://keramida.wordpress.com/2009/11/07/dejavu-condensed-as-default/#comment-12359</link>
		<dc:creator>keramida</dc:creator>
		<pubDate>Tue, 17 Nov 2009 00:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://keramida.wordpress.com/?p=652#comment-12359</guid>
		<description>Thanks Philip.  I think I fixed it, by copying the &quot;hinting&quot; section from my current &lt;code&gt;~/.fonts.conf&lt;/code&gt;.  Wordpress comment-syntax keeps amazing me too; not always in a nice way.</description>
		<content:encoded><![CDATA[<p>Thanks Philip.  I think I fixed it, by copying the &#8220;hinting&#8221; section from my current <code>~/.fonts.conf</code>.  WordPress comment-syntax keeps amazing me too; not always in a nice way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
