<?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 on: A BSD without i386	</title>
	<atom:link href="https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Thu, 15 Aug 2013 08:59:06 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>
		By: Frank Leonhardt		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-71625</link>

		<dc:creator><![CDATA[Frank Leonhardt]]></dc:creator>
		<pubDate>Thu, 15 Aug 2013 08:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-71625</guid>

					<description><![CDATA[It would be a pity to drop the i386/32-bit as people still use it (check the FreeBSD questions list). Having a 4Gb RAM address limit is meaningless if you don&#039;t have that much RAM, and 32-bit code is more compact. Likewise, the 64-bit sector threshold that stops gmirror working on drives beyond 2Tb (512-byte/sector) is the only reason many will have to go to ZFS right now.

In some parts of the world, 32-bit is the only option and I think it&#039;d be a shame for FreeBSD to freeze them out. I don&#039;t really want to have to direct people to Ubuntu as the only option.

For the sake of balance in this comment, I will concede that 32-bit is really dead. Microsoft says so.]]></description>
			<content:encoded><![CDATA[<p>It would be a pity to drop the i386/32-bit as people still use it (check the FreeBSD questions list). Having a 4Gb RAM address limit is meaningless if you don&#8217;t have that much RAM, and 32-bit code is more compact. Likewise, the 64-bit sector threshold that stops gmirror working on drives beyond 2Tb (512-byte/sector) is the only reason many will have to go to ZFS right now.</p>
<p>In some parts of the world, 32-bit is the only option and I think it&#8217;d be a shame for FreeBSD to freeze them out. I don&#8217;t really want to have to direct people to Ubuntu as the only option.</p>
<p>For the sake of balance in this comment, I will concede that 32-bit is really dead. Microsoft says so.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Lars Schotte		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70894</link>

		<dc:creator><![CDATA[Lars Schotte]]></dc:creator>
		<pubDate>Wed, 26 Jun 2013 21:48:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70894</guid>

					<description><![CDATA[I think it&#039;s OK to drop support for i386. however, there are still some computers out there, which are quite new and though are still i386 architecture, like my acer aspire one netbook with an atom processor. Linux distros are making a fine step in between like they do not support anything but i686 with PAE extension. that&#039;s something one can live with for a few years and would still support old hw like AMD AthlonXP can be often found among old computers that are still in use.]]></description>
			<content:encoded><![CDATA[<p>I think it&#8217;s OK to drop support for i386. however, there are still some computers out there, which are quite new and though are still i386 architecture, like my acer aspire one netbook with an atom processor. Linux distros are making a fine step in between like they do not support anything but i686 with PAE extension. that&#8217;s something one can live with for a few years and would still support old hw like AMD AthlonXP can be often found among old computers that are still in use.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Zoey4ever		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70882</link>

		<dc:creator><![CDATA[Zoey4ever]]></dc:creator>
		<pubDate>Wed, 26 Jun 2013 08:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70882</guid>

					<description><![CDATA[@hrt

This document explains some of the difficulties Sun faced when porting Solaris to amd64 (there&#039;s more than just 4G+ Mem when using the amd64 instruction set)

http://www.cs.dartmouth.edu/~sergey/cs108/solaris-on-x86.pdf

I guess the same applies to other OSs.]]></description>
			<content:encoded><![CDATA[<p>@hrt</p>
<p>This document explains some of the difficulties Sun faced when porting Solaris to amd64 (there&#8217;s more than just 4G+ Mem when using the amd64 instruction set)</p>
<p><a href="http://www.cs.dartmouth.edu/~sergey/cs108/solaris-on-x86.pdf" rel="nofollow ugc">http://www.cs.dartmouth.edu/~sergey/cs108/solaris-on-x86.pdf</a></p>
<p>I guess the same applies to other OSs.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: John		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70849</link>

		<dc:creator><![CDATA[John]]></dc:creator>
		<pubDate>Tue, 25 Jun 2013 14:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70849</guid>

					<description><![CDATA[@skdj : However, the last i386 release of DragonFly will also work for years to come.  I ran Solaris 10 for 6 years without touching it.  Ditto for FreeBSD 6, although one box had a bad drive so I upgraded to FreeBSD 7.2 and ran that for 4 years.

Once installed, there&#039;s usually not a driving reason to upgrade the OS itself.  None of the pro-i386 folks has answered why long term support on the last i386 is not satisfactory, or why this old/weak boxes require the latest release when the 3.x releases are so robust now.

The EOL of a platform doesn&#039;t mean users of that platform are cut off from DragonFly, only the very latest releases.]]></description>
			<content:encoded><![CDATA[<p>@skdj : However, the last i386 release of DragonFly will also work for years to come.  I ran Solaris 10 for 6 years without touching it.  Ditto for FreeBSD 6, although one box had a bad drive so I upgraded to FreeBSD 7.2 and ran that for 4 years.</p>
<p>Once installed, there&#8217;s usually not a driving reason to upgrade the OS itself.  None of the pro-i386 folks has answered why long term support on the last i386 is not satisfactory, or why this old/weak boxes require the latest release when the 3.x releases are so robust now.</p>
<p>The EOL of a platform doesn&#8217;t mean users of that platform are cut off from DragonFly, only the very latest releases.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70842</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 25 Jun 2013 04:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70842</guid>

					<description><![CDATA[hrt - there are operations possible on x86_64 that are not possible in i386, so you can potentially get better comparative performance on a 64-bit system.  

Being limited to &#039;only&#039; 4G of RAM can be significant.  For example:  

http://lists.dragonflybsd.org/pipermail/commits/2013-June/130228.html]]></description>
			<content:encoded><![CDATA[<p>hrt &#8211; there are operations possible on x86_64 that are not possible in i386, so you can potentially get better comparative performance on a 64-bit system.  </p>
<p>Being limited to &#8216;only&#8217; 4G of RAM can be significant.  For example:  </p>
<p><a href="http://lists.dragonflybsd.org/pipermail/commits/2013-June/130228.html" rel="nofollow ugc">http://lists.dragonflybsd.org/pipermail/commits/2013-June/130228.html</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: skdj		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70834</link>

		<dc:creator><![CDATA[skdj]]></dc:creator>
		<pubDate>Mon, 24 Jun 2013 23:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70834</guid>

					<description><![CDATA[Computers without &quot;a lot of RAM and CPU horsepower&quot; need not necessarily be old computers. You might not yet be able to find a fanless 4x4x1 inch sized computer that is cheap and 64bit. That&#039;s why some folks might still see use for 32bit x86 support for years to come.]]></description>
			<content:encoded><![CDATA[<p>Computers without &#8220;a lot of RAM and CPU horsepower&#8221; need not necessarily be old computers. You might not yet be able to find a fanless 4x4x1 inch sized computer that is cheap and 64bit. That&#8217;s why some folks might still see use for 32bit x86 support for years to come.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Charles Rapenne		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70825</link>

		<dc:creator><![CDATA[Charles Rapenne]]></dc:creator>
		<pubDate>Mon, 24 Jun 2013 13:47:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70825</guid>

					<description><![CDATA[Supporting 2 architectures takes more time because you need to generates more ISO, build more packages, verify that it builds correctly on both archs. 

I think PC-BSD should drop i386 support as it aims computers that can run ZFS (which shouldn&#039;t be used on 32 bits systems !). Why would you run PC-BSD if your computer is old and doesn&#039;t have a lot of ram ? Just install FreeBSD, you won&#039;t use firefox or libreoffice anyway as it takes too much memory/cpu.]]></description>
			<content:encoded><![CDATA[<p>Supporting 2 architectures takes more time because you need to generates more ISO, build more packages, verify that it builds correctly on both archs. </p>
<p>I think PC-BSD should drop i386 support as it aims computers that can run ZFS (which shouldn&#8217;t be used on 32 bits systems !). Why would you run PC-BSD if your computer is old and doesn&#8217;t have a lot of ram ? Just install FreeBSD, you won&#8217;t use firefox or libreoffice anyway as it takes too much memory/cpu.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: hrt		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70798</link>

		<dc:creator><![CDATA[hrt]]></dc:creator>
		<pubDate>Sun, 23 Jun 2013 20:27:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70798</guid>

					<description><![CDATA[Is not the only significant difference between 32bit and 64bit processors just the limitation of the former to 4GB of main memory? I wonder why the architecture matters at all. Shouldn&#039;t software written cleanly and in a high level language be unconcerned with the machine that is compiled for? A clean software design would also not prevent optimization for specific machines either.]]></description>
			<content:encoded><![CDATA[<p>Is not the only significant difference between 32bit and 64bit processors just the limitation of the former to 4GB of main memory? I wonder why the architecture matters at all. Shouldn&#8217;t software written cleanly and in a high level language be unconcerned with the machine that is compiled for? A clean software design would also not prevent optimization for specific machines either.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Zoey4Ever		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70783</link>

		<dc:creator><![CDATA[Zoey4Ever]]></dc:creator>
		<pubDate>Sun, 23 Jun 2013 07:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70783</guid>

					<description><![CDATA[Solaris 11 (hey it has at least some distant BSD ancestors) dropped support for i386 as well ;)]]></description>
			<content:encoded><![CDATA[<p>Solaris 11 (hey it has at least some distant BSD ancestors) dropped support for i386 as well ;)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70779</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Sun, 23 Jun 2013 00:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70779</guid>

					<description><![CDATA[It&#039;s not the same, but it&#039;s a blurry line between the two.  The fact that it supports a limited number of platforms already makes it not surprising that it&#039;s the first to go... but it is the first.]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s not the same, but it&#8217;s a blurry line between the two.  The fact that it supports a limited number of platforms already makes it not surprising that it&#8217;s the first to go&#8230; but it is the first.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Sascha Wildner		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70776</link>

		<dc:creator><![CDATA[Sascha Wildner]]></dc:creator>
		<pubDate>Sat, 22 Jun 2013 22:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70776</guid>

					<description><![CDATA[This is not really comparable to what John proposed (dropping i386 support from DragonFly base). PC-BSD is technically &quot;just&quot; a distro of FreeBSD and I&#039;ve heard nothing of FreeBSD planning to drop i386 support from their base.

PC-BSD isn&#039;t released for a lot more architectures which FreeBSD proper supports.]]></description>
			<content:encoded><![CDATA[<p>This is not really comparable to what John proposed (dropping i386 support from DragonFly base). PC-BSD is technically &#8220;just&#8221; a distro of FreeBSD and I&#8217;ve heard nothing of FreeBSD planning to drop i386 support from their base.</p>
<p>PC-BSD isn&#8217;t released for a lot more architectures which FreeBSD proper supports.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: matthiasr		</title>
		<link>https://www.dragonflydigest.com/2013/06/22/a-bsd-without-i386/comment-page-1/#comment-70775</link>

		<dc:creator><![CDATA[matthiasr]]></dc:creator>
		<pubDate>Sat, 22 Jun 2013 22:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11990#comment-70775</guid>

					<description><![CDATA[Not sure if this qualifies, but OS X dropped i386-only-CPU support with Lion http://en.wikipedia.org/wiki/OS_X_Lion#System_requirements :)]]></description>
			<content:encoded><![CDATA[<p>Not sure if this qualifies, but OS X dropped i386-only-CPU support with Lion <a href="http://en.wikipedia.org/wiki/OS_X_Lion#System_requirements" rel="nofollow ugc">http://en.wikipedia.org/wiki/OS_X_Lion#System_requirements</a> :)</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
