Explorar o código

Finished various TODO's

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@290 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Gerard Beekmans %!s(int64=24) %!d(string=hai) anos
pai
achega
5ce7896297
Modificáronse 1 ficheiros con 1 adicións e 23 borrados
  1. 1 23
      TODO

+ 1 - 23
TODO

@@ -1,29 +1,9 @@
 These are the TODO items for the next LFS release (3.0):
 These are the TODO items for the next LFS release (3.0):
 
 
-* Chapter 5, tar: remove prefix=$LFS/usr from the 'make install'
-
-* Chapter 5, mawk: instead of putting -static in CFLAGS which is sloppy
-  sed the Makefile to add an LDFLAGS variable similar to what we do
-  with bzip2 in chapter 5
-
-* Chapter 5, makedev: instead of sed "s/.../.../" put the quotations
-  marks inside the search reg ex (sed s/"..."/.../).
-
-* Chapter 5, makedev: cd to $LFS/dev first, then cp to makedev-temp and
-  patch it.
-
-* Chapter 6, glibc: after copying pt_chown set mode 4755 on it (Glibc
-  doesn't do this because it failed to copy pt_chown. It tried to chown
-  root it which failed because glibc wasn't fully installed yet)
-
 * Chapter 5, bash: add note that when error occurs regarding
 * Chapter 5, bash: add note that when error occurs regarding
   install-info (on Debian systems for example) it can be safely
   install-info (on Debian systems for example) it can be safely
   ignored.
   ignored.
 
 
-* Chapter 5, kernel: Remove the exessive explanations. Just the
-  commands in sequence like with any other package and explain below
- in the "command explanations"
-
 * Chapter 5, bash: when the 'install-info' error corrurs on Debian
 * Chapter 5, bash: when the 'install-info' error corrurs on Debian
   systems, check if this affects && (the message is Error 2 (ignored)
   systems, check if this affects && (the message is Error 2 (ignored)
   but does that mean the return value is set to 0 as well...)
   but does that mean the return value is set to 0 as well...)
@@ -50,7 +30,7 @@ These are the TODO items for the next LFS release (3.0):
 * Don't use \u in PS1 when entering chroot to avoid the 'i have no
 * Don't use \u in PS1 when entering chroot to avoid the 'i have no
   name'. After Glibc installation we could modify the PS1 (export
   name'. After Glibc installation we could modify the PS1 (export
   PS1=newvalues) and test that way if glibc is working properly. This
   PS1=newvalues) and test that way if glibc is working properly. This
-  saves us the having to exit and re-end chroot environtment. Another
+  saves us the having to exit and re-enter chroot environtment. Another
   idea is to run 'id' or 'whoami' after Glibc installation and check if
   idea is to run 'id' or 'whoami' after Glibc installation and check if
   it's able to find a matching username with root's id.
   it's able to find a matching username with root's id.
 
 
@@ -62,8 +42,6 @@ These are the TODO items for the next LFS release (3.0):
 * Mention more hints through out the books (like BSD hint before
 * Mention more hints through out the books (like BSD hint before
   staring with chapter 7, devfs hint before running MAKEDEV, etc)
   staring with chapter 7, devfs hint before running MAKEDEV, etc)
 
 
-* Fix the layout of intel/chapter7/usage.xml
- 
 * Consider ftp://ftp.win.tue.nl/pub/linux-local/utils/kbd/
 * Consider ftp://ftp.win.tue.nl/pub/linux-local/utils/kbd/
   to replace console-tools/console-data
   to replace console-tools/console-data