TODO 4.0 KB

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