Removed paragraph in LFS Target Architectures

that said that we can't build a 64-bit loader


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9107 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/changelog.xml

@@ -37,6 +37,16 @@
 
 -->
 
+    <listitem>
+      <para>2009-11-16</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] Removed paragraph in LFS Target Architectures
+          that said that we can't build a 64-bit loader.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>2009-11-16</para>
       <itemizedlist>

general.ent

@@ -1,5 +1,5 @@
-<!ENTITY version "SVN-20091116">
-<!ENTITY releasedate "November 16, 2009">
+<!ENTITY version "SVN-20091117">
+<!ENTITY releasedate "November 17, 2009">
 <!ENTITY copyrightdate "1999-2009"><!-- jhalfs needs a literal dash, not &ndash; -->
 <!ENTITY milestone "7.0">
 <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->

prologue/architecture.xml

@@ -23,12 +23,6 @@ Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets the system
 that you have.  Also note that a 32-bit system can be installed and used as a
 host system on a 64-bit AMD/Intel system.</para>
 
-<para>If you decide to target a 64-bit AMD/Intel system, LFS does have some
-limitations.  First, it does not currently provide instructions for a 64-bit
-boot loader.  If there is an existing boot loader, it can be used to boot to
-any LFS system you build, but <xref linkend="ch-bootable-grub"/> cannot be
-built on a 64-bit system.</para>
-
 <para>Some other facts about a 64-bit systems need to be added here.  When
 compared to a 32-bit system, the sizes of executable programs are slightly
 larger and the execution speeds are only slightly faster.  For example, in a