<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>cestdelamerde.com - linux</title>
    <link>http://cestdelamerde.com/</link>
    <description></description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <pubDate>Tue, 12 Aug 2008 13:54:15 GMT</pubDate>

    <image>
        <url>http://cestdelamerde.com/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: cestdelamerde.com - linux - </title>
        <link>http://cestdelamerde.com/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Apache Virtual Hosts and DNS Web Redirection</title>
    <link>http://cestdelamerde.com/archives/41-Apache-Virtual-Hosts-and-DNS-Web-Redirection.html</link>
            <category>linux</category>
            <category>macosx</category>
    
    <comments>http://cestdelamerde.com/archives/41-Apache-Virtual-Hosts-and-DNS-Web-Redirection.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=41</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=41</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    A friend of mine tried to setup some days ago an Apache web server with two virtual hosts. Unfortunately, he was only able to reach it&#039;s first defined virtual host. We found nothing bad in the Apache conf files. So we suspected an Apple conspiracy as the server was launched from an mac mini. &lt;br /&gt;
&lt;br /&gt;
But it was not a conspiracy &lt;img src=&quot;http://cestdelamerde.com/templates/default/img/emoticons/sad.png&quot; alt=&quot;:-(&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;br /&gt;
&lt;br /&gt;
He was using Gandi as registrar, DNS provider and registered what Gandi calls DNS Web Redirection : you hosts your zone on gandi DNS servers, all subdomain (eg www or blog) are recorded as a CNAME of webredir.vip.gandi.net. Then webredir.vip.gandi.net acts as a proxy to the real website of your choice (eg: a Mac Mini behind a Free DSL connection). &lt;br /&gt;
&lt;br /&gt;
This method DOES NOT WORK when the target website uses Apache Virtual Hosts. (wrong Host header)&lt;br /&gt;
&lt;br /&gt;
Do not use those kind of hacky redirection unless there is no other choice available. Use A and CNAME records, like cestdelamerde does :&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;&lt;br /&gt;
@ 10800 IN A 217.70.191.204 &lt;br /&gt;
* 10800 IN CNAME cestdelamerde.com. &lt;br /&gt;
&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
The ultimate DNS zone file if you are hosting all you&#039;re VH under the same IP...&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 12 Aug 2008 15:54:15 +0200</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/41-guid.html</guid>
    
</item>
<item>
    <title>Unbelievable Debian Security Issue</title>
    <link>http://cestdelamerde.com/archives/37-Unbelievable-Debian-Security-Issue.html</link>
            <category>linux</category>
    
    <comments>http://cestdelamerde.com/archives/37-Unbelievable-Debian-Security-Issue.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=37</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=37</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    Two days ago, Debian developpers annouced a huge security breach has been introduced in libssl since september 2006 as a patch to the random number generator (&lt;a href=&quot;http://article.gmane.org/gmane.linux.debian.security.announce/1614&quot;&gt;[DSA 1571-1] New openssl packages fix predictable random number generator&lt;/a&gt; ; &lt;a href=&quot;http://www.debian.org/security/2008/dsa-1571&quot;&gt;Debian -- Security&amp;#160;Information -- DSA-1571-1 openssl&lt;/a&gt;).&lt;br /&gt;
&lt;br /&gt;
Unfortunately, this unstable version of libssl is the one used for a while in Debian based distributions like Ubuntu, thus all debian or Ubuntu, Kubuntu, Xubuntu (...) users are required to upgrade their version of libssl and also check all key material generated since 2006 &lt;img src=&quot;http://cestdelamerde.com/templates/default/img/emoticons/sad.png&quot; alt=&quot;:-(&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;br /&gt;
&lt;br /&gt;
For &lt;a href=&quot;http://www.gentoo.org&quot;&gt;Gentoo&lt;/a&gt; users, nothing has to be done ; their non patched openssl version is ok. &lt;br /&gt;
&lt;br /&gt;
Again, a new reason for not using any debian based distributions... &lt;a href=&quot;http://www.gentoo.org&quot;&gt;Gentoo&lt;/a&gt; rocks.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 15 May 2008 15:16:50 +0200</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/37-guid.html</guid>
    
</item>
<item>
    <title>Firefox and Color Management</title>
    <link>http://cestdelamerde.com/archives/26-Firefox-and-Color-Management.html</link>
            <category>linux</category>
            <category>macosx</category>
    
    <comments>http://cestdelamerde.com/archives/26-Firefox-and-Color-Management.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=26</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=26</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    While I was uploading pictures from Lightroom to the web (flickr), I used firefox on OS X to preview uploaded galleries and colors of uploaded picture were insipid. I&#039;ve first suspected Lightroom to create fucked jpeg files, but viewing with another web browser like Safari just shows perfect colors.&lt;br /&gt;
&lt;br /&gt;
It seems that the Mac OS X version of Firefox 2 is not able to apply right color profiles to render jpeg pictures. The screenshot below is self explanatory...&lt;br /&gt;
&lt;br /&gt;
The only workaround is not to use Firefox !&lt;br /&gt;
&lt;br /&gt;
&lt;!-- s9ymdb:4 --&gt;&lt;a href=&quot;http://cestdelamerde.com/uploads/Image2.png&quot; target=&quot;_blank&quot;&gt;&lt;img width=&quot;110&quot; height=&quot;65&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://cestdelamerde.com/uploads/Image2.serendipityThumb.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Sat, 15 Mar 2008 17:17:07 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/26-guid.html</guid>
    
</item>
<item>
    <title>Monitoring Bandwidth from Command Line</title>
    <link>http://cestdelamerde.com/archives/18-Monitoring-Bandwidth-from-Command-Line.html</link>
            <category>linux</category>
    
    <comments>http://cestdelamerde.com/archives/18-Monitoring-Bandwidth-from-Command-Line.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=18</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=18</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    First option : &lt;br /&gt;
{code}cat /proc/net/dev{code}&lt;br /&gt;
&lt;br /&gt;
This shows all network interfaces and some statistics associated with them, but is not very user friendly.&lt;br /&gt;
&lt;br /&gt;
User friendly option : install &lt;a href=&quot;http://www.gropp.org/?id=projects&amp;amp;sub=bwm-ng&quot;&gt;Bandwidth Monitor NG&lt;/a&gt; (package name is bwm-ng in most common distribution) and execute it : &lt;br /&gt;
{code}bwm-ng{code}&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 14 Feb 2008 14:10:20 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/18-guid.html</guid>
    
</item>
<item>
    <title>Flush Linux Caches</title>
    <link>http://cestdelamerde.com/archives/17-Flush-Linux-Caches.html</link>
            <category>linux</category>
    
    <comments>http://cestdelamerde.com/archives/17-Flush-Linux-Caches.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=17</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=17</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    It is now possible from kernel version 2.6.16 to drop Linux internal caches (page caches, inodes and dentry caches). This can be done by echoing a number into &lt;b&gt;/proc/sys/vm/drop_caches&lt;/b&gt; : &lt;br /&gt;
&lt;br /&gt;
To drop page cache : &lt;br /&gt;
&lt;code&gt;echo 1 &gt;  /proc/sys/vm/drop_caches&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
To drop inode and dentry cache :&lt;br /&gt;
&lt;code&gt;echo 2 &gt;  /proc/sys/vm/drop_caches&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
And finally to drop everything : &lt;br /&gt;
&lt;code&gt;echo 3 &gt;  /proc/sys/vm/drop_caches&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Source : &lt;a href=&quot;http://linux-mm.org/Drop_Caches&quot;&gt;Drop Caches - linux-mm.org&lt;/a&gt; 
    </content:encoded>

    <pubDate>Thu, 14 Feb 2008 09:47:49 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/17-guid.html</guid>
    
</item>
<item>
    <title>KDE 4.0 Final - A Pre-Alpha Release ?</title>
    <link>http://cestdelamerde.com/archives/12-KDE-4.0-Final-A-Pre-Alpha-Release.html</link>
            <category>linux</category>
    
    <comments>http://cestdelamerde.com/archives/12-KDE-4.0-Final-A-Pre-Alpha-Release.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=12</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=12</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    January 11, 2008 kde.org annouced KDE 4.0 is released !&lt;br /&gt;
&lt;br /&gt;
Unfortunately, this release is not really ready for day to day use. &lt;br /&gt;
&lt;br /&gt;
The new interface is beautyful but lacks of configuration options (eg:resizing/masking the taskbar).&lt;br /&gt;
&lt;br /&gt;
A lot of application that used to work in kde 3.5 does not work anymore (eg: Kopete has a random behaviour when it talks to some Jabber servers).&lt;br /&gt;
&lt;br /&gt;
Some kickass features in applications have been disabled : it is not possible to access directly to a tab in Konsole using a keyboard shortcut, adding custom applet (like a &quot;show desktop button&quot;) to the taskbar seems not possible anymore....&lt;br /&gt;
&lt;br /&gt;
Even worse, some settings are not accessible through the control panel anymore, eg: the number of desktops available for application windows can only be configured by right-clicking on the pager taskbar applet, the taskbar options (size, automasking...) seems to be gone, when removing the pager applet, there seems to be no way to enable it back !&lt;br /&gt;
&lt;br /&gt;
After some time, keyboard shortcuts did not work anymore : Alt+TAB just does nothing, Ctrl+Shift+N (new tab in Konsole)  split the screen...&lt;br /&gt;
&lt;br /&gt;
So do not even think about installing it &lt;img src=&quot;http://cestdelamerde.com/templates/default/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; 
    </content:encoded>

    <pubDate>Mon, 28 Jan 2008 10:41:30 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/12-guid.html</guid>
    
</item>
<item>
    <title>Dell D630 Docking Station and Gentooo Linux</title>
    <link>http://cestdelamerde.com/archives/4-Dell-D630-Docking-Station-and-Gentooo-Linux.html</link>
            <category>linux</category>
    
    <comments>http://cestdelamerde.com/archives/4-Dell-D630-Docking-Station-and-Gentooo-Linux.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=4</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=4</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    Dell provides a nice docking station where the Dell D630 can be plugged on. But Linux kernel lacks support of this kind of hardware. Even if a &quot;dock&quot; ACPI module is existing in recent 2.6 kernels, it fails to provide ACPI events to acpid : it just have not been implemented in the kernel code &lt;img src=&quot;http://cestdelamerde.com/templates/default/img/emoticons/sad.png&quot; alt=&quot;:-(&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; :( &lt;img src=&quot;http://cestdelamerde.com/templates/default/img/emoticons/sad.png&quot; alt=&quot;:-(&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; The quick hack below send some crappy events to the ACPI event bus : &lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;--- ../../../linux-2.6.22-gentoo-r9/drivers/acpi/dock.c 2007-10-31 17:30:44.000000000 +0100&lt;br /&gt;
+++ dock.c      2007-11-09 15:06:25.000000000 +0100&lt;br /&gt;
@@ -68,6 +68,8 @@&lt;br /&gt;
&lt;br /&gt;
 static struct dock_station *dock_station;&lt;br /&gt;
&lt;br /&gt;
+static struct acpi_device &lt;strong&gt;device;&lt;br /&gt;
+&lt;br /&gt;
 /****************************************************************************&lt;/strong&gt;&lt;br /&gt;
  &lt;strong&gt;                         Dock Dependent device functions                   &lt;/strong&gt;&lt;br /&gt;
  *****************************************************************************/&lt;br /&gt;
@@ -320,7 +322,7 @@&lt;br /&gt;
                if (event == ACPI_NOTIFY_EJECT_REQUEST)&lt;br /&gt;
                        dock_remove_acpi_device(dd-&gt;handle);&lt;br /&gt;
                else&lt;br /&gt;
-                       dock_create_acpi_device(dd-&gt;handle);&lt;br /&gt;
+                       device = dock_create_acpi_device(dd-&gt;handle);&lt;br /&gt;
        }&lt;br /&gt;
        mutex_unlock(&amp;amp;ds-&gt;hp_lock);&lt;br /&gt;
 }&lt;br /&gt;
@@ -333,6 +335,7 @@&lt;br /&gt;
         &lt;strong&gt; changed.&lt;br /&gt;
         &lt;/strong&gt;/&lt;br /&gt;
        kobject_uevent(&amp;amp;dev-&gt;kobj, KOBJ_CHANGE);&lt;br /&gt;
+    acpi_bus_generate_event(device, event, num);&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
 /**&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
In Gentoo the event can be matched using the code extracted from my /etc/acpi/default.sh : &lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
if [ $1 = &quot;GDCK&quot; ] ;then&lt;br /&gt;
    export XAUTHORITY=/var/run/xauth/`ls /var/run/xauth/`&lt;br /&gt;
    export DISPLAY=:0&lt;br /&gt;
    if [ $2 = &quot;00000000&quot; ] ; then&lt;br /&gt;
        logger &quot;docking ?&quot;&lt;br /&gt;
    else&lt;br /&gt;
        logger &quot;undocking ?&quot;&lt;br /&gt;
    fi&lt;br /&gt;
    exit;&lt;br /&gt;
fi&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Unfortunately, this quick hack fails to detect the first &quot;undock&quot; event if the laptop is docked at boot time... 
    </content:encoded>

    <pubDate>Wed, 21 Nov 2007 15:55:55 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/4-guid.html</guid>
    
</item>
<item>
    <title>Xorg, Dual Head and Dell D630</title>
    <link>http://cestdelamerde.com/archives/3-Xorg,-Dual-Head-and-Dell-D630.html</link>
            <category>linux</category>
    
    <comments>http://cestdelamerde.com/archives/3-Xorg,-Dual-Head-and-Dell-D630.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=3</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=3</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    Having the dual head working properly on Linux is a pain in the ass. Especially when your laptop comes with an Intel card. &lt;br /&gt;
&lt;br /&gt;
For an unknown reason using the latest stable intel drivers of the Gentoo linux distribution, getting the DVI output of the docking station working is not possible ; you have to unmask the intel drivers package to get it work. Unfortunately, even with the last drivers, it fails to detects video modes of the DELL 2007WFP flat screen &lt;img src=&quot;http://cestdelamerde.com/templates/default/img/emoticons/sad.png&quot; alt=&quot;:-(&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; It detects a wrong 1680x1050 video mode (59Hz instead of the required 60Hz). Even worse, this video mode is not selected by default and only detected if X starts while the laptop is docked. To solve this, a ad-hoc xorg.conf file must be setup :&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
Section &quot;Monitor&quot;&lt;br /&gt;
        Identifier      &quot;dvi&quot;&lt;br /&gt;
        Option &quot;PreferredMode&quot;  &quot;1680x1050@60&quot;&lt;br /&gt;
        Option        &quot;Position&quot; &quot;1280 0&quot;&lt;br /&gt;
        Modeline &quot;1680x1050@60&quot; 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync +Vsync&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &quot;Monitor&quot;&lt;br /&gt;
        Identifier      &quot;lcd&quot;&lt;br /&gt;
        Option &quot;LeftOf&quot;  &quot;dvi&quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &quot;Device&quot;&lt;br /&gt;
        Identifier  &quot;Card0&quot;&lt;br /&gt;
        Driver      &quot;i810&quot;&lt;br /&gt;
        ChipSet     &quot;965GM&quot;&lt;br /&gt;
        Card        &quot;i810 965GM&quot;&lt;br /&gt;
        Option          &quot;monitor-LVDS&quot; &quot;lcd&quot;&lt;br /&gt;
        Option         &quot;monitor-TMDS-1&quot; &quot;dvi&quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
Even with this config specials scripts have to be written in order to get it work (this must be launched after the X startup) :&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
/usr/bin/xrandr  --output TMDS-1 --mode 1680x1050@60&lt;br /&gt;
/usr/bin/xrandr --output TMDS-1 --pos 1280x0&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 19 Nov 2007 10:15:41 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/3-guid.html</guid>
    
</item>
<item>
    <title>Timemachine &amp; Network Shares</title>
    <link>http://cestdelamerde.com/archives/2-Timemachine-Network-Shares.html</link>
            <category>linux</category>
            <category>macosx</category>
    
    <comments>http://cestdelamerde.com/archives/2-Timemachine-Network-Shares.html#comments</comments>
    <wfw:comment>http://cestdelamerde.com/wfwcomment.php?cid=2</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cestdelamerde.com/rss.php?version=2.0&amp;type=comments&amp;cid=2</wfw:commentRss>
    

    <author>nospam@example.com (philou)</author>
    <content:encoded>
    By default, the Leopard TimeMachine is not able to write to Windows network shares. But it comes with an hidden option that allows this to happen. You only have to do this : &lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1&lt;/code&gt; 
    </content:encoded>

    <pubDate>Thu, 15 Nov 2007 18:09:31 +0100</pubDate>
    <guid isPermaLink="false">http://cestdelamerde.com/archives/2-guid.html</guid>
    
</item>

</channel>
</rss>