TODO 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687
  1. These are the TODO items for the next LFS release (3.0):
  2. * When installing Glibc in chapter 6 glibc-build/login/pt_chown isn't
  3. installed (we'll copy manually for now) and the mtrace program isn't
  4. build. Find out why.
  5. * Rewrite all of the mailinglist info (book and website) and give more
  6. information how you can set to things like digest, digest2, vacation
  7. and other useful modes.
  8. * Incorporate LFS FAQ in the book
  9. * Add dedicated package version number entities (to avoid having to make
  10. changes to 2-7 files to just change the version number of a package).
  11. * Full dependency list. This list isn't a list of "package a depends on
  12. package b", but a list of "package a depends on b and c from
  13. package d"
  14. * Bring the book up to speed with the current FHS specs.
  15. * Mention security patches that can be applied to packages.
  16. * At the end of the book suggest the user create the /etc/lfs-<version>
  17. file and give a few reasons why the user would want
  18. such a file (example: it's easy to forget after a while which LFS version
  19. you run; it makes debugging easier for us knowing which LFS version a user
  20. is running).
  21. * Explain how changing runlevels works. Use the file written by Simon
  22. Perreault at http://download.linuxfromscratch.org/misc/runlevels.txt
  23. * Don't run lilo from inside chroot anymore. This causes severe problems
  24. sometimes including LILO not bootstrapping properly.
  25. * Bring back the PPC book (recreate from scratch using current intel
  26. book) using Jesse McCrosky's notes at
  27. http://download.linuxfromscratch.org/misc/ppc-notes.txt
  28. and the patch to the 'patch' package at:
  29. http://download.linuxfromscratch.org/misc/ppc-patch.patch
  30. * Add descriptions what the patches do we use (like the console-tools and gzip
  31. patches)
  32. * Try out Slackware's MAKEDEV script and see if it's any better than the
  33. currently used one. A copy can be found at
  34. http://download.linuxfromscratch.org/misc/Slackware-MAKEDEV
  35. * Sed'ing the MAKEDEV script gives us hda[1-20], hdb[1-20] and so forth.
  36. Mention that all of these can't actually be used due to kernel
  37. limitations (IDE goes to 16 max for example).
  38. * Type in chapter 2 - how to install software: Last paragraph:
  39. s/There is on exception/There is one exception/
  40. * Rewrite chapter 2 a little bit. Add that export LFS=/mnt/lfs could be
  41. added to root's .bash_profile/.bashrc (outside chroot) to make sure
  42. that between build sessions the variable is still set.
  43. * Add to chapter 2 how to use .gz files (not just .tar.gz)
  44. * Mention LFS should be installed as user root
  45. * Single user mode has been reported not to work properly. Shutdown
  46. doesn't seem to unmount file systems and the shell doesn't come up
  47. properly when 'telinit S'.
  48. * Add netkit-base and net-tools to Appendix A.
  49. * Use /etc/HOSTNAME for setting the hostname. This is a bit more
  50. compliant with other distributions and therefore less confusing to
  51. people.
  52. * Suggest using this command to strip debug symbols after you finish
  53. chapter 6: find $LFS -type f -exec strip --strip-debug '{}' ';'
  54. * Modify the killproc function in the functions script. Right now it
  55. works roughly as follows: killl, wait 2 secs, check if pid's are gone.
  56. If not, kill with -KILL (aka -9), wait 2 secs, checkif pid's are gone.
  57. If no, print error message.
  58. Change this into: kill, don't wait 2 secs but check for pid's right
  59. away. If pid's are still there, then wait 2 seconds and kill -KILL,
  60. wait, if pid's still there, print error. Most daemons will exit
  61. immediately and the 2 second wait for every daemon slows things down
  62. unnessary.