TODO 3.9 KB

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