From 6370fa6cff0ec2a8ac8d50d1595ec9500f6631c9 Mon Sep 17 00:00:00 2001
From: Gerard Beekmans <gerard@linuxfromscratch.org>
Date: Wed, 24 Jan 2001 00:31:17 +0000
Subject: Initial commit - LFS 2.4.4 files

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@14 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter05/bash-static-exp.sgml | 55 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 chapter05/bash-static-exp.sgml

(limited to 'chapter05/bash-static-exp.sgml')

diff --git a/chapter05/bash-static-exp.sgml b/chapter05/bash-static-exp.sgml
new file mode 100644
index 000000000..8d627237e
--- /dev/null
+++ b/chapter05/bash-static-exp.sgml
@@ -0,0 +1,55 @@
+<sect2>
+<title>Command explanations</title>
+
+<para>
+<userinput>--enable-static-link:</userinput> This configure 
+option causes Bash to be linked statically
+</para>
+
+<para>
+<userinput>--prefix=$LFS/usr:</userinput> This configure option installs 
+all of Bash's files under the $LFS/usr directory, which becomes the /usr 
+directory after you chroot into $LFS or when you reboot the system into LFS.
+</para>
+
+<para>
+<userinput>--bindir=$LFS/bin:</userinput> This installs the executable 
+files in $LFS/bin. We do this because we want bash to be in /bin, not in 
+/usr/bin. One reason being: your /usr partition might be on a seperate 
+partition which has to be mounted at some point. Before that partition is 
+mounted you need and will want to have bash available (it will be hard to 
+execute the boot scripts without a shell for instance).
+</para>
+
+<para>
+<userinput>--disable-nls:</userinput> This disables the build of NLS 
+(National Language Support). It's only a waste of time for now as Bash 
+will be reinstalled in the next chapter.
+</para>
+
+<para>
+<userinput>--with-curses:</userinput> This causes Bash to be linked 
+against the curses library instead of the default termcap library which 
+is becoming obsolete.
+</para>
+
+<para>
+<userinput>ln -s bash sh:</userinput> This command creates the sh
+symlink that points to bash. Most scripts run themselves via 'sh'; sh
+being a symlink to the default system shell. Because programs and
+scripts don't know what shell you use by default (could be bash, ksh,
+korn, tch, csh and others) they use the common symlink sh which, if the 
+system is properly setup, always points to the system's default shell.
+</para>
+
+<para>
+The <userinput>&amp;&amp;</userinput>'s at the end of every line cause 
+the next command only to be executed when the previous command exists 
+with a return value of 0 indicating success. In case you copy&amp;paste 
+all of these commands on the shell you want to be ensured that if 
+./configure fails, make isn't being executed and likewise if make fails 
+that make install isn't being executed, and so forth.
+</para>
+
+</sect2>
+
-- 
cgit v1.2.3-54-g00ecf