TODO 3.8 KB

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