<?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/"
		>
<channel>
	<title>Comments for Humboldt Solutions Ltd</title>
	<atom:link href="http://www.humboldt.co.uk/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.humboldt.co.uk</link>
	<description>Software Development and Consulting</description>
	<lastBuildDate>Fri, 18 Jun 2010 23:44:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>Comment on A Working TFTP Server for Multi-Homed Linux Systems by Ean</title>
		<link>http://www.humboldt.co.uk/2008/11/a-working-tftp-server-for-multi-homed-linux-systems.html/comment-page-1#comment-3879</link>
		<dc:creator>Ean</dc:creator>
		<pubDate>Fri, 18 Jun 2010 23:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=25#comment-3879</guid>
		<description>Thanks for the concise summary of the issue!  My searching didn&#039;t turn up the Debian bug, but did turn up your page and it was a huge help.

Fyi, dnsmasq&#039;s TFTP server does support multi-homed servers, but it doesn&#039;t support ipv6.  If you need both multi-homing and ipv6, I&#039;ve had luck hand-applying the patch from the debian bug thread above to the latest tftpd-hpa.
Ean</description>
		<content:encoded><![CDATA[<p>Thanks for the concise summary of the issue!  My searching didn&#8217;t turn up the Debian bug, but did turn up your page and it was a huge help.</p>
<p>Fyi, dnsmasq&#8217;s TFTP server does support multi-homed servers, but it doesn&#8217;t support ipv6.  If you need both multi-homing and ipv6, I&#8217;ve had luck hand-applying the patch from the debian bug thread above to the latest tftpd-hpa.<br />
Ean</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Slow Reboots of NFS Server by K.Bala</title>
		<link>http://www.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html/comment-page-1#comment-3599</link>
		<dc:creator>K.Bala</dc:creator>
		<pubDate>Tue, 27 Apr 2010 12:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html#comment-3599</guid>
		<description>Great  its worked for me too..

su -
rm /var/lib/nfs/rmtab
reboot

NFS started instantaneously rather than taking several minutes.

Thanks,
K.Bala</description>
		<content:encoded><![CDATA[<p>Great  its worked for me too..</p>
<p>su -<br />
rm /var/lib/nfs/rmtab<br />
reboot</p>
<p>NFS started instantaneously rather than taking several minutes.</p>
<p>Thanks,<br />
K.Bala</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mystery of ProxyPassReverse by MIke</title>
		<link>http://www.humboldt.co.uk/2009/02/the-mystery-of-proxypassreverse.html/comment-page-1#comment-3435</link>
		<dc:creator>MIke</dc:creator>
		<pubDate>Fri, 16 Apr 2010 22:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=119#comment-3435</guid>
		<description>Thank you, thank you, thank you.  Everybody else neglected this very important part of the configuration.  I actually needed both, but now it works like a charm.</description>
		<content:encoded><![CDATA[<p>Thank you, thank you, thank you.  Everybody else neglected this very important part of the configuration.  I actually needed both, but now it works like a charm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mystery of ProxyPassReverse by Adrian Cox</title>
		<link>http://www.humboldt.co.uk/2009/02/the-mystery-of-proxypassreverse.html/comment-page-1#comment-2657</link>
		<dc:creator>Adrian Cox</dc:creator>
		<pubDate>Sat, 06 Jun 2009 08:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=119#comment-2657</guid>
		<description>The ProxyPassReverse is still required to rewrite the headers in the redirect, whether you use AJP or HTTP. To get a clearer view of what is going on, install &lt;a href=&quot;http://getfirebug.com/&quot; rel=&quot;nofollow&quot;&gt;Firebug&lt;/a&gt; and look at the network activity during the redirect.

You should see that without the ProxyPassReverse line, an application redirect to &quot;test.jsp&quot; will become a HTTP redirect to &quot;http://www.example.com/jspdir/test.jsp&quot;. The ProxyPassReverse line will translate that redirect to the correct &quot;http://www.example.com/test.jsp&quot;.</description>
		<content:encoded><![CDATA[<p>The ProxyPassReverse is still required to rewrite the headers in the redirect, whether you use AJP or HTTP. To get a clearer view of what is going on, install <a href="http://getfirebug.com/">Firebug</a> and look at the network activity during the redirect.</p>
<p>You should see that without the ProxyPassReverse line, an application redirect to &#8220;test.jsp&#8221; will become a HTTP redirect to &#8220;http://www.example.com/jspdir/test.jsp&#8221;. The ProxyPassReverse line will translate that redirect to the correct &#8220;http://www.example.com/test.jsp&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mystery of ProxyPassReverse by Rafael Santini</title>
		<link>http://www.humboldt.co.uk/2009/02/the-mystery-of-proxypassreverse.html/comment-page-1#comment-2656</link>
		<dc:creator>Rafael Santini</dc:creator>
		<pubDate>Sat, 06 Jun 2009 04:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=119#comment-2656</guid>
		<description>I would like to know why &quot;ProxyPass / http://localhost/jspdir&quot; does not works with sendRedirect. What is the difference between ajp and http? To me, this appear a bug with proxy_http.</description>
		<content:encoded><![CDATA[<p>I would like to know why &#8220;ProxyPass / <a href="http://localhost/jspdir">http://localhost/jspdir</a>&#8221; does not works with sendRedirect. What is the difference between ajp and http? To me, this appear a bug with proxy_http.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mystery of ProxyPassReverse by Rafael Santini</title>
		<link>http://www.humboldt.co.uk/2009/02/the-mystery-of-proxypassreverse.html/comment-page-1#comment-2655</link>
		<dc:creator>Rafael Santini</dc:creator>
		<pubDate>Sat, 06 Jun 2009 04:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=119#comment-2655</guid>
		<description>Finally, I found an example that works!</description>
		<content:encoded><![CDATA[<p>Finally, I found an example that works!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Working TFTP Server for Multi-Homed Linux Systems by Simon Kelley</title>
		<link>http://www.humboldt.co.uk/2008/11/a-working-tftp-server-for-multi-homed-linux-systems.html/comment-page-1#comment-2654</link>
		<dc:creator>Simon Kelley</dc:creator>
		<pubDate>Thu, 28 May 2009 12:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=25#comment-2654</guid>
		<description>Just a quick correction about dnsmasq. It can use either of the two approaches to UDP source control that you describe. By default it does the IP_PKTINFO thing (and its equivalent for the other supported platforms) but can be configured to use the multiple-socket solution with --bind-interfaces.

HTH

Simon.</description>
		<content:encoded><![CDATA[<p>Just a quick correction about dnsmasq. It can use either of the two approaches to UDP source control that you describe. By default it does the IP_PKTINFO thing (and its equivalent for the other supported platforms) but can be configured to use the multiple-socket solution with &#8211;bind-interfaces.</p>
<p>HTH</p>
<p>Simon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Slow Reboots of NFS Server by ChrisP</title>
		<link>http://www.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html/comment-page-1#comment-6</link>
		<dc:creator>ChrisP</dc:creator>
		<pubDate>Wed, 25 Jul 2007 02:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html#comment-6</guid>
		<description>Excellent - worked for me.&lt;br/&gt;&lt;br/&gt;su -&lt;br/&gt;rm /var/lib/nfs/rmtab&lt;br/&gt;reboot&lt;br/&gt;&lt;br/&gt;NFS started instantaneously rather than taking several minutes.&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;Chris.</description>
		<content:encoded><![CDATA[<p>Excellent &#8211; worked for me.su -rm /var/lib/nfs/rmtabrebootNFS started instantaneously rather than taking several minutes.Thanks,Chris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Embedded Theora Video by Timothy B. Terriberry</title>
		<link>http://www.humboldt.co.uk/2006/02/embedded-theora-video.html/comment-page-1#comment-5</link>
		<dc:creator>Timothy B. Terriberry</dc:creator>
		<pubDate>Fri, 01 Dec 2006 18:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/02/embedded-theora-video.html#comment-5</guid>
		<description>The real problem, as I saw it, was not the raster/Hilbert curve ordering (though this certainly introduces many complexities in the encoder; the decoder is not as bad), but the fact that coefficients are ordered by their frequency first, and the block they belong to second, meaning that if the 63rd coefficient in a block is non-zero, you need to decode virtually all the coefficients in the frame before you can decode that one block.&lt;br/&gt;&lt;br/&gt;This structure actually helps avoid the raster order problem for DC prediction, because you can undo the DC prediction after decoding just the DC coefficients, i.e., on 1/64th of the final image data, which often fits entirely in cache (at 640x480 it&#039;s less than 16k of data).&lt;br/&gt;&lt;br/&gt;The loop filter problem can similarly be handled by applying it (with a one block row delay) after each super block row is decoded. This requires slightly more cache (just under 64k of image data at 640x480, plus additional overhead for the coefficients that were decoded), but should still fit well within the 256K L2 cache on your DSP.&lt;br/&gt;&lt;br/&gt;The &lt;a HREF=&quot;http://svn.xiph.org/trunk/theora-exp/&quot; REL=&quot;nofollow&quot;&gt;theora-exp&lt;/a&gt; decoder does both these things, to good effect. The spec describes everything as separate processes for conceptual simplicity, but to get good preformance they really need to be pipelined.&lt;br/&gt;&lt;br/&gt;For the loop filter at larger resolutions, you could (if you&#039;re careful about it), process 3/4 of each superblock (with a one block column delay) immediately after decoding it, without waiting for the entire row to finish. Then you only need to cache one row of block data between superblock rows.</description>
		<content:encoded><![CDATA[<p>The real problem, as I saw it, was not the raster/Hilbert curve ordering (though this certainly introduces many complexities in the encoder; the decoder is not as bad), but the fact that coefficients are ordered by their frequency first, and the block they belong to second, meaning that if the 63rd coefficient in a block is non-zero, you need to decode virtually all the coefficients in the frame before you can decode that one block.This structure actually helps avoid the raster order problem for DC prediction, because you can undo the DC prediction after decoding just the DC coefficients, i.e., on 1/64th of the final image data, which often fits entirely in cache (at 640&#215;480 it&#8217;s less than 16k of data).The loop filter problem can similarly be handled by applying it (with a one block row delay) after each super block row is decoded. This requires slightly more cache (just under 64k of image data at 640&#215;480, plus additional overhead for the coefficients that were decoded), but should still fit well within the 256K L2 cache on your DSP.The <a HREF="http://svn.xiph.org/trunk/theora-exp/">theora-exp</a> decoder does both these things, to good effect. The spec describes everything as separate processes for conceptual simplicity, but to get good preformance they really need to be pipelined.For the loop filter at larger resolutions, you could (if you&#8217;re careful about it), process 3/4 of each superblock (with a one block column delay) immediately after decoding it, without waiting for the entire row to finish. Then you only need to cache one row of block data between superblock rows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Slow Reboots of NFS Server by Anonymous</title>
		<link>http://www.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html/comment-page-1#comment-4</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 29 May 2006 04:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html#comment-4</guid>
		<description>Ah. This post solved my slow nfs startup problem, which has been annoying me. Thanks for the author.</description>
		<content:encoded><![CDATA[<p>Ah. This post solved my slow nfs startup problem, which has been annoying me. Thanks for the author.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

