<?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 Pat Rice</title>
	<atom:link href="http://patrick-rice.net/daybook/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://patrick-rice.net/daybook</link>
	<description>Stuff, nonsense &#38; blather.</description>
	<lastBuildDate>Sun, 25 Jul 2010 21:42:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Cygwin vs. Windows 7 by Andy</title>
		<link>http://patrick-rice.net/daybook/2010/07/14/cygwin-vs-windows-7/comment-page-1/#comment-531</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sun, 25 Jul 2010 21:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6249#comment-531</guid>
		<description>Thanks for writing a more detailed account, and apologies for drawing wrong conclusions from your original moan. I guess all I can recommend at this point is to look at what the automatic conversion has written to /etc/fstab, for future reference. And I&#039;ll take away the point that there&#039;s lack of usability here somewhere.

It&#039;s unfortunate it&#039;s caused you nothing but bother, but the reasons for changing to the /etc/fstab approach are to allow multiple parallel Cygwin installs as well as portable installs, and to make things easier for Unix exiles.

Textmode is being discouraged by removing it from the installer because the concept is essentially broken. Unix programs don&#039;t usually indicate whether they want a file to be treated as text or binary, because on actual Unix it makes no difference. Hence in textmode everything is treated as a text file, yet of course adding carriage returns doesn&#039;t do binary data any good.

Textmode is fine though if you know that everything stored in a directory is text (or at least it isn&#039;t used to exchange binary data between Cygwin and non-Cygwin programs), which is why textmode on specific mount points continues to be supported. Shame cvs doesn&#039;t have a line ending option.

The Cygwin mailing list may be short on formalities and patience with people who don&#039;t do their homework (not that you seem the type to be bothered by that), but it sure is responsive to bug reports and questions.</description>
		<content:encoded><![CDATA[<p>Thanks for writing a more detailed account, and apologies for drawing wrong conclusions from your original moan. I guess all I can recommend at this point is to look at what the automatic conversion has written to /etc/fstab, for future reference. And I&#8217;ll take away the point that there&#8217;s lack of usability here somewhere.</p>
<p>It&#8217;s unfortunate it&#8217;s caused you nothing but bother, but the reasons for changing to the /etc/fstab approach are to allow multiple parallel Cygwin installs as well as portable installs, and to make things easier for Unix exiles.</p>
<p>Textmode is being discouraged by removing it from the installer because the concept is essentially broken. Unix programs don&#8217;t usually indicate whether they want a file to be treated as text or binary, because on actual Unix it makes no difference. Hence in textmode everything is treated as a text file, yet of course adding carriage returns doesn&#8217;t do binary data any good.</p>
<p>Textmode is fine though if you know that everything stored in a directory is text (or at least it isn&#8217;t used to exchange binary data between Cygwin and non-Cygwin programs), which is why textmode on specific mount points continues to be supported. Shame cvs doesn&#8217;t have a line ending option.</p>
<p>The Cygwin mailing list may be short on formalities and patience with people who don&#8217;t do their homework (not that you seem the type to be bothered by that), but it sure is responsive to bug reports and questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cygwin vs. Windows 7 by Pat</title>
		<link>http://patrick-rice.net/daybook/2010/07/14/cygwin-vs-windows-7/comment-page-1/#comment-530</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Sun, 25 Jul 2010 12:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6249#comment-530</guid>
		<description>I don&#039;t care whether cygwin stores its mount points in the registry or in /etc/fstab, I care whether C:/ is mounted in text mode. If it isn&#039;t, cvs checkout gives me files with unix eol, and the build process that relies on cygwin stops working.

The 1.5 installer asked whether I wanted dos mode or unix mode. The current 1.7 installer does not, instead forcing unix mode.

It may be that my changes to /etc/fstab were incorrect. But they were based on the documentation you keep saying I haven&#039;t read. It may also be that I didn&#039;t wait for all cygwin processes to finish before doing a cvs checkout. But I&#039;m not running any cygwin servers / daemons / etc. All my cygwin usage is command-line. So I&#039;m pretty confident there were no lingering cygwin processes to keep the /etc/fstab changes from taking effect.

Perhaps I should have kept detailed notes on my efforts to fix this latest cygwin breakage. But my searches through the cygwin mailing list persuaded me that bug reports &amp; support questions would not be well-received by the cygwin developers.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t care whether cygwin stores its mount points in the registry or in /etc/fstab, I care whether C:/ is mounted in text mode. If it isn&#8217;t, cvs checkout gives me files with unix eol, and the build process that relies on cygwin stops working.</p>
<p>The 1.5 installer asked whether I wanted dos mode or unix mode. The current 1.7 installer does not, instead forcing unix mode.</p>
<p>It may be that my changes to /etc/fstab were incorrect. But they were based on the documentation you keep saying I haven&#8217;t read. It may also be that I didn&#8217;t wait for all cygwin processes to finish before doing a cvs checkout. But I&#8217;m not running any cygwin servers / daemons / etc. All my cygwin usage is command-line. So I&#8217;m pretty confident there were no lingering cygwin processes to keep the /etc/fstab changes from taking effect.</p>
<p>Perhaps I should have kept detailed notes on my efforts to fix this latest cygwin breakage. But my searches through the cygwin mailing list persuaded me that bug reports &#038; support questions would not be well-received by the cygwin developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cygwin vs. Windows 7 by Andy</title>
		<link>http://patrick-rice.net/daybook/2010/07/14/cygwin-vs-windows-7/comment-page-1/#comment-529</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sun, 25 Jul 2010 05:54:40 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6249#comment-529</guid>
		<description>a) Yep, the Cygwin developers&#039; motto is &quot;We&#039;re Just Mean&quot;. You&#039;re doing a pretty good job living up to your billing too though.

b) What do you want? Cygwin to stick with bad design decisions like the registry mount points into all eternity? The new /etc/fstab approach is pretty much what you get on Linux, so it&#039;s not like it&#039;s completely outlandish. And you&#039;ve said yourself that the automatic mount point conversion from 1.5 to 1.7 worked fine. Beyond that, yes, command line interfaces are intrinsically unintuitive, so reading documentation is necessary and expected. Both setup.exe and the website make a special point of that regarding the change to 1.7.

Bug reports against the software and the documentation are of course always welcome, but I&#039;m afraid so far there&#039;s nothing actionable here.</description>
		<content:encoded><![CDATA[<p>a) Yep, the Cygwin developers&#8217; motto is &#8220;We&#8217;re Just Mean&#8221;. You&#8217;re doing a pretty good job living up to your billing too though.</p>
<p>b) What do you want? Cygwin to stick with bad design decisions like the registry mount points into all eternity? The new /etc/fstab approach is pretty much what you get on Linux, so it&#8217;s not like it&#8217;s completely outlandish. And you&#8217;ve said yourself that the automatic mount point conversion from 1.5 to 1.7 worked fine. Beyond that, yes, command line interfaces are intrinsically unintuitive, so reading documentation is necessary and expected. Both setup.exe and the website make a special point of that regarding the change to 1.7.</p>
<p>Bug reports against the software and the documentation are of course always welcome, but I&#8217;m afraid so far there&#8217;s nothing actionable here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cygwin vs. Windows 7 by Pat</title>
		<link>http://patrick-rice.net/daybook/2010/07/14/cygwin-vs-windows-7/comment-page-1/#comment-528</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Sat, 24 Jul 2010 15:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6249#comment-528</guid>
		<description>You must be one of the cygwin developers - I can tell from a) your snide attitude and b) your delusion that all problems are due to idiot users who haven&#039;t read the documentation.

http://cygwin.com/ml/cygwin/ is full of examples of both, going back ten years or more.

Maybe I tried editing /etc/fstab, and it didn&#039;t fix the problem. But I don&#039;t suppose you&#039;re all that interested in hearing what I&#039;ve tried, and whether it worked. Blaming the users is more fun than helping them.</description>
		<content:encoded><![CDATA[<p>You must be one of the cygwin developers &#8211; I can tell from a) your snide attitude and b) your delusion that all problems are due to idiot users who haven&#8217;t read the documentation.</p>
<p><a href="http://cygwin.com/ml/cygwin/" rel="nofollow">http://cygwin.com/ml/cygwin/</a> is full of examples of both, going back ten years or more.</p>
<p>Maybe I tried editing /etc/fstab, and it didn&#8217;t fix the problem. But I don&#8217;t suppose you&#8217;re all that interested in hearing what I&#8217;ve tried, and whether it worked. Blaming the users is more fun than helping them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cygwin vs. Windows 7 by Andy</title>
		<link>http://patrick-rice.net/daybook/2010/07/14/cygwin-vs-windows-7/comment-page-1/#comment-527</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 24 Jul 2010 15:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6249#comment-527</guid>
		<description>Cygwin 1.7 reads its mount points from /etc/fstab instead of storing them in the registry, which is what the mount command did in 1.5. This is of course documented in the User&#039;s Guide. Heck, it&#039;s even mentioned at the top of http://cygwin.com. But yeah, moaning is much more fun than reading documentation.</description>
		<content:encoded><![CDATA[<p>Cygwin 1.7 reads its mount points from /etc/fstab instead of storing them in the registry, which is what the mount command did in 1.5. This is of course documented in the User&#8217;s Guide. Heck, it&#8217;s even mentioned at the top of <a href="http://cygwin.com" rel="nofollow">http://cygwin.com</a>. But yeah, moaning is much more fun than reading documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Muddled thinker of the week by VXBush</title>
		<link>http://patrick-rice.net/daybook/2010/06/06/muddled-thinker-of-the-week/comment-page-1/#comment-510</link>
		<dc:creator>VXBush</dc:creator>
		<pubDate>Tue, 08 Jun 2010 13:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6166#comment-510</guid>
		<description>And given how long it takes to have a reasoned discourse that actually results in understanding for each party, in our hectic world it isn&#039;t going to happen soon.</description>
		<content:encoded><![CDATA[<p>And given how long it takes to have a reasoned discourse that actually results in understanding for each party, in our hectic world it isn&#8217;t going to happen soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Muddled thinker of the week by Pat</title>
		<link>http://patrick-rice.net/daybook/2010/06/06/muddled-thinker-of-the-week/comment-page-1/#comment-509</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Mon, 07 Jun 2010 13:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6166#comment-509</guid>
		<description>The sad thing is, there are just as many annoying bloviators on the other side of the aisle. Interest in / aptitude for calm, reasoned discourse is at an all-time low.</description>
		<content:encoded><![CDATA[<p>The sad thing is, there are just as many annoying bloviators on the other side of the aisle. Interest in / aptitude for calm, reasoned discourse is at an all-time low.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Muddled thinker of the week by VXBush</title>
		<link>http://patrick-rice.net/daybook/2010/06/06/muddled-thinker-of-the-week/comment-page-1/#comment-508</link>
		<dc:creator>VXBush</dc:creator>
		<pubDate>Mon, 07 Jun 2010 13:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6166#comment-508</guid>
		<description>Geller has always been a muddled thinker, for years. She&#039;s gotten worse as she&#039;s gotten more and more press. A lot of people think she represents the conservative side of things, which is really bad for conservatives. But Pat Buchanan is just as bad, if not worse. Why he is still paid to come on shows is a mystery to me.</description>
		<content:encoded><![CDATA[<p>Geller has always been a muddled thinker, for years. She&#8217;s gotten worse as she&#8217;s gotten more and more press. A lot of people think she represents the conservative side of things, which is really bad for conservatives. But Pat Buchanan is just as bad, if not worse. Why he is still paid to come on shows is a mystery to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Third chance by Pat</title>
		<link>http://patrick-rice.net/daybook/2010/05/23/third-chance/comment-page-1/#comment-503</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Wed, 26 May 2010 00:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6128#comment-503</guid>
		<description>Looks interesting...thanks for the tip!</description>
		<content:encoded><![CDATA[<p>Looks interesting&#8230;thanks for the tip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Third chance by Michael</title>
		<link>http://patrick-rice.net/daybook/2010/05/23/third-chance/comment-page-1/#comment-502</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 25 May 2010 01:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://patrick-rice.net/daybook/?p=6128#comment-502</guid>
		<description>You should give RootsMagic Essentials a try.  It&#039;s free, lightweight, doesn&#039;t include shovelware, and doesn&#039;t require you to share any information or even register.

http://www.rootsmagic.com/essentials</description>
		<content:encoded><![CDATA[<p>You should give RootsMagic Essentials a try.  It&#8217;s free, lightweight, doesn&#8217;t include shovelware, and doesn&#8217;t require you to share any information or even register.</p>
<p><a href="http://www.rootsmagic.com/essentials" rel="nofollow">http://www.rootsmagic.com/essentials</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
