Changes between Version 5 and Version 6 of LFSFuture


Ignore:
Timestamp:
05/17/2008 01:22:46 AM (17 years ago)
Author:
gerard@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LFSFuture

    v5 v6  
    1414The book needs to improve on the educational front. This “issue” will never get “resolved” as it will always be an ongoing project. We can, however, pay extra attention to a few areas in particular.
    1515
    16 There are many areas where after installing a package you don't come away with a true understanding of what you have just done or why a package is needed. Sometimes all you get from it is that some other package required it and you'll settle for that.
     16There are many areas where after installing a package you don't come away with a true understanding of what you have just done or why a package is needed. Sometimes all you get from it is that another package required it and you'll settle for that.
    1717
    18 In some cases there is no real reason why a package has been selected for inclusion in the book. Take Vim for example. There is no technical reason for choosing Vim over any other editor other than the fact we had to pick one. Vim was as good choice at the time. Those bits of information should be communicated.
     18In other cases there is no real (technical) reason why a package has been selected for inclusion in the book. Take Vim for example. There is no real significant reason for choosing Vim over any other editor other than the fact we had to pick one. Vim was as good choice at the time. Such information should be communicated.
    1919
    2020We should also expand significantly on major areas and subsystems. For example, both kernel configuration and udev setup need elaboration. The user is sometimes left hanging after (or in the case of kernel configuration, before) installation of a package. Additional help, information and suggestions would go a long way to steer our users into the right direction.
     
    2727  * Automating the installation of individual packages or the entire system. This would including re-deploying the installed packages to another system without having to recompile again.
    2828
    29 There have been discussions about which package management system to use. We would either have to decide on one and have the book use it or not pick one and devote a chapter to the various choices. In the latter case, the user decides which one (or none) to use.
     29There have been discussions about which package management system to use. We would either 1) have to decide on one, have the book use it or 2) not pick one and devote a chapter to the various choices. In the latter case, the user decides which one (or none) to use.
    3030
    3131Choice is good. But it can also be an Achilles heel. If the book is to be made PM-aware we need a sample implementation. Not only for our own internal needs (to speed up editorial and testing cycles) but also to show users how it can be done in showing a fully implemented and working system.
     
    3737If the book is going to officially support a system, it should be one that can provide automated installations and dependency resolving. Not just an installation logger that keeps track of installed and modified files. We'd definitely point out that such a method exists and could be good enough for a group of people, but most people would benefit from something a little more advanced.
    3838
    39 Another method of installing software that needs to be considered is to initially install the software in an alternate directory, say /tmp/<packagname> for the user to inspect the files actually installed. This is generally done with a command similar to
     39Another method of installing software that needs to be considered is to initially install the software in an alternate directory, say /tmp/<packagname> for the user to inspect the files before they are actually installed. This is generally done with a command similar to
    4040
    4141  make DESTDIR=/tmp/packagename install
     
    5656== 4. 64-bit Support ==
    5757
    58 Multi-lib or Pure. That is the question.
     58Multi-lib or Pure or both. That is the question.
    5959
    6060== 5. Licensing and trademark ==
     
    6464This is not the final verdict but some license changes should be discussed and then implemented.
    6565
    66 Another suggestion made is for us to consider trademarking “Linux From Scratch” and probably “Beyond Linux From Scratch".  Since Linus holds the Linux trademark we need to get permission (http://www.linuxmark.org/license.php).
     66Another suggestion that was made is for us to consider trademarking “Linux From Scratch” and probably “Beyond Linux From Scratch".  Since Linus holds the Linux trademark we need to get permission (http://www.linuxmark.org/license.php).
    6767
    6868== 6. Legal organization ==
     
    7070To continue on the last point regarding licensing, currently the LFS book is copyrighted under Gerard's personal name. The BLFS book under the “BLFS Development Team.” In the past we have had discussions about founding a not-for-profit organization under which the LFS products can be licensed and copyrighted. It would be better than under an individual's name.
    7171
    72 We're resuming this research to see what it will entail to setup that sort of organization. There are matters to figure out having to do with finances, receiving money for the LFS project, etc.
    73 
     72We're resuming this research to see what it will entail to setup that sort of organization. There are matters to figure out having to do with finances, receiving money for the LFS project, etc. It's not an easy straight-forward process and also pretty expensive from what we've learned so far.