aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/ed.xml
diff options
context:
space:
mode:
authorAlex Gronenwoud <alex@linuxfromscratch.org>2003-11-01 22:31:50 +0000
committerAlex Gronenwoud <alex@linuxfromscratch.org>2003-11-01 22:31:50 +0000
commit73aedd1d35747ff2fad4ddf514dca810721a612a (patch)
treed05f8b503f210d7248c2b2abea9e5528fc04d90a /chapter06/ed.xml
parent0b400add2ba87352e955326bcb931e53864cc2ae (diff)
Merging caption and installation sections for all packages in chapters 5 and 6.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3052 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/ed.xml')
-rw-r--r--chapter06/ed.xml49
1 files changed, 47 insertions, 2 deletions
diff --git a/chapter06/ed.xml b/chapter06/ed.xml
index e5a0c3100..078f0a45a 100644
--- a/chapter06/ed.xml
+++ b/chapter06/ed.xml
@@ -7,8 +7,53 @@ Estimated required disk space: &ed-compsize;</screen>
&aa-ed-shortdesc;
&aa-ed-dep;
-&c6-ed-inst;
-</sect1>
+<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
+
+<sect2>
+<title>Installation of Ed</title>
+
+<note><para>Ed isn't something which many people use. It's installed here
+because it can be used by the patch program if you encounter an ed-based patch
+file. This happens rarely because diff-based patches are preferred these
+days.</para></note>
+
+<para>Ed normally uses the mktemp function to create temporary files in
+<filename class="directory">/tmp</filename>, but this function contains a
+vulnerability (see the section on Temporary Files in <ulink
+url="http://en.tldp.org/HOWTO/Secure-Programs-HOWTO/avoid-race.html"/>). The
+following patch makes Ed use mkstemp instead, which is the recommended way to
+create temporary files.</para>
+
+<para>Apply the patch:</para>
+
+<screen><userinput>patch -Np1 -i ../&ed-patch;</userinput></screen>
+
+<para>Now prepare Ed for compilation:</para>
+
+<screen><userinput>./configure --prefix=/usr</userinput></screen>
+
+<para>Compile the package:</para>
+<screen><userinput>make</userinput></screen>
+
+<para>This package has a test suite available which can perform a number of
+checks to ensure it built correctly. Should you choose to run it, the
+following command will do so:</para>
+
+<screen><userinput>make check</userinput></screen>
+
+<para>Install the package:</para>
+
+<screen><userinput>make install</userinput></screen>
+
+<para>And move the programs to the <filename>/bin</filename> directory, so
+they can be used in the event that the <filename>/usr</filename> partition is
+unavailable.</para>
+
+<screen><userinput>mv /usr/bin/{ed,red} /bin</userinput></screen>
+
+</sect2>
+
+</sect1>