<?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: AMD64 progress update	</title>
	<atom:link href="https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Thu, 16 Jul 2009 23:58:31 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/comment-page-1/#comment-33231</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 23:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=4467#comment-33231</guid>

					<description><![CDATA[Roger - I&#039;m pretty sure AMD64 DragonFly will be available for 2.4.  It may not support 32-bit binaries, and it probably won&#039;t build as many packages out of pkgsrc, or other things may be missing, so don&#039;t plan to run any production machines with it, if it does happen.]]></description>
			<content:encoded><![CDATA[<p>Roger &#8211; I&#8217;m pretty sure AMD64 DragonFly will be available for 2.4.  It may not support 32-bit binaries, and it probably won&#8217;t build as many packages out of pkgsrc, or other things may be missing, so don&#8217;t plan to run any production machines with it, if it does happen.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chirstian Sturm		</title>
		<link>https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/comment-page-1/#comment-33230</link>

		<dc:creator><![CDATA[Chirstian Sturm]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 22:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=4467#comment-33230</guid>

					<description><![CDATA[Looks really nice.

While I understand your concerns and why you added the &quot;terrorism, paedophilia or crimes against humanity&quot; part I ask you to change back to the original license. First of all these things are illegal anyway, you don&#039;t need to make this part of your license. I guess no terrorist would really care about this anyway. I&#039;m also not sure if this part of the license is even of relevance in the law. If the software is used for such things it wouldn&#039;t defend you and on the other side I&#039;m not sure if a license can really forbid usage cases like this. I know a lot of licenses include &quot;you are not allowed to do this or that&quot;, but in many cases it&#039;s forbidden by the law or has no relevance.

Now the reason I care for it: To make it short it is not an OSI or FSF or otherwise widely used license. This makes it harder to be added to a linux distribution, pkgsrc or ports. In pkgsrc it would require an additional license because of this little addition and a lot of linux distributions wouldn&#039;t allow it, because it&#039;s not an OSI or FSF licensed software.]]></description>
			<content:encoded><![CDATA[<p>Looks really nice.</p>
<p>While I understand your concerns and why you added the &#8220;terrorism, paedophilia or crimes against humanity&#8221; part I ask you to change back to the original license. First of all these things are illegal anyway, you don&#8217;t need to make this part of your license. I guess no terrorist would really care about this anyway. I&#8217;m also not sure if this part of the license is even of relevance in the law. If the software is used for such things it wouldn&#8217;t defend you and on the other side I&#8217;m not sure if a license can really forbid usage cases like this. I know a lot of licenses include &#8220;you are not allowed to do this or that&#8221;, but in many cases it&#8217;s forbidden by the law or has no relevance.</p>
<p>Now the reason I care for it: To make it short it is not an OSI or FSF or otherwise widely used license. This makes it harder to be added to a linux distribution, pkgsrc or ports. In pkgsrc it would require an additional license because of this little addition and a lot of linux distributions wouldn&#8217;t allow it, because it&#8217;s not an OSI or FSF licensed software.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Robin Carey		</title>
		<link>https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/comment-page-1/#comment-33229</link>

		<dc:creator><![CDATA[Robin Carey]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 15:59:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=4467#comment-33229</guid>

					<description><![CDATA[If you&#039;re interested in Hard Disk Encryption, you should check out my Caesarion-v12 software:

http://www.leopard.uk.com/cion

It has a new type of encryption (which I invented) which as far as I&#039;m aware has never been done before, and therefore breaks new ground in terms of cryptography.

If Hammer was to support hard disk encryption, I would recommend it uses Cipher-Packet as found in Caesarion-V12.

Cheers!]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re interested in Hard Disk Encryption, you should check out my Caesarion-v12 software:</p>
<p><a href="http://www.leopard.uk.com/cion" rel="nofollow ugc">http://www.leopard.uk.com/cion</a></p>
<p>It has a new type of encryption (which I invented) which as far as I&#8217;m aware has never been done before, and therefore breaks new ground in terms of cryptography.</p>
<p>If Hammer was to support hard disk encryption, I would recommend it uses Cipher-Packet as found in Caesarion-V12.</p>
<p>Cheers!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chirstian Sturm		</title>
		<link>https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/comment-page-1/#comment-33228</link>

		<dc:creator><![CDATA[Chirstian Sturm]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 15:20:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=4467#comment-33228</guid>

					<description><![CDATA[Great job!
Huge thanks to Jordan :-)

AMD64 support is one of the two features missing before I install it on the rest of my boxes. The other would be support for hard disk encryption, but I guess there are many other much more important things to do in HAMMER.]]></description>
			<content:encoded><![CDATA[<p>Great job!<br />
Huge thanks to Jordan :-)</p>
<p>AMD64 support is one of the two features missing before I install it on the rest of my boxes. The other would be support for hard disk encryption, but I guess there are many other much more important things to do in HAMMER.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Roger Sistla		</title>
		<link>https://www.dragonflydigest.com/2009/07/15/amd64-progress-update/comment-page-1/#comment-33227</link>

		<dc:creator><![CDATA[Roger Sistla]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 14:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=4467#comment-33227</guid>

					<description><![CDATA[Does this mean that an AMD64 port/iso will be released in September ?

/RS]]></description>
			<content:encoded><![CDATA[<p>Does this mean that an AMD64 port/iso will be released in September ?</p>
<p>/RS</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
