diff options
| author | Archaic <archaic@linuxfromscratch.org> | 2006-04-20 05:43:39 +0000 |
|---|---|---|
| committer | Archaic <archaic@linuxfromscratch.org> | 2006-04-20 05:43:39 +0000 |
| commit | d8af60f758582ee2f6142543621a113005a0a75e (patch) | |
| tree | 347f34fa4269ba4cf391cb3711e4899929e753ee /chapter06 | |
| parent | dc5f1f842795f930c5412050fe691ee2244846a4 (diff) | |
Slight wording change to GDBM note.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7540 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06')
| -rw-r--r-- | chapter06/db.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/chapter06/db.xml b/chapter06/db.xml index 753069090..42a2b6c53 100644 --- a/chapter06/db.xml +++ b/chapter06/db.xml @@ -42,11 +42,11 @@ <para>Also, GDBM <emphasis>could</emphasis> be used in place of Berkeley DB to satisfy Man-DB. However, since Berkeley DB is considered a core part of the LFS build, it will not be listed as a dependency for any package in - the BLFS book. Likewise, dozens of hours go into testing LFS with Berkeley - DB installed, not with GDBM. If you fully understand the risks versus + the BLFS book. Likewise, many hours go into testing LFS with Berkeley DB + installed, not with GDBM. If you fully understand the risks versus benefits of using GDBM and wish to use it anyway, see the BLFS - instructions located at - <ulink url="&blfs-root;view/svn/general/gdbm.html"/></para> + instructions located at <ulink + url="&blfs-root;view/svn/general/gdbm.html"/></para> </tip> |