On Friday 29 February 2008 03:20:44 Alan Lord wrote: > Here's the original suggestion I made: > > --- > So perhaps the LFS project becomes some sort of "course" (and I use > the term loosely). The "modules" of which, could be something like: > > * Learning the basics (Command Line, cmmi, security, toolchain, blah > blah) > > * Scripting/Automating (A subject about how LFS gets built, the > tools, the processes involved etc) [This is where PM would probably > go too] > > * Basic Useful Applications (A sort of mini BLFS where we get > networking, X and maybe Firefox/TB type apps installed) > > * Building your Distro (Completing the core build-out adding your > chosen apps and utilities and configuring) > > * Making your Distro distributable (How to make a liveCD of "your > distro", how to make an installer script...) > > ---- >
I've been thinking about this 'modules' idea, and also the idea about the automatically generated personalized book, and I came up with the following: 1) Bootstrapping a toolchain - Pretty much equivalent to Chapter 5. 2) Package Management - Choose your package manager, learn how it works, why they exist. Maybe a basic scripting tutorial as well. 3) Basic CLI - Chapter 6. Add gpm, choice of text editor. 4) Security - How to secure a linux system, cover options like PAM, SELinux, sudo, and whatever else is appropriate. 5) CLI Apps - Applications to make a system useful from a command line. Wget, text web browsers, etc. 6) Desktops: Probably one of the larger sections. Cover KDE, Gnome, Xfce, and more basic window managers. Also include desktop frameworks like Xorg, HAL, and DBus. 7) Desktop Apps - Things like office suites, multimedia applications, graphical web browsers, etc. 8) Server Software - LAMP stack and whatever else is appropriate for a server, cuz I don't really know. A lot of the structure here looks similar to what we already have. 1-3 pretty much have to go in order, and I think 4 should also follow immediately after, but the rest is fairly nonlinear and/or optional. The idea for the earlier parts is to shift the focus away from the current 'this is how you build it' scenario. Instead focus on theory, why things work the way they do. Same for the later modules, but also I thought to shift the main focus to applications. Currently there is a very large number of libraries listed in BLFS. Nobody cares about libraries, they want applications ( well, mostly. I like to read what libraries can do, but if no app uses it, it actually does nothing ) The modules would concentrate on letting the user decide what apps they want, then automatically pick out libraries necessary for the task, without having to wade through so many unneccessary ones. I think this would also be easier to expand on than the current setup in whatever frontend is chosen. Add in games later, or maybe media center functions, or something like that. Probably throw in a module on distribution / livecd's. I just forgot to list it up there. A lot of this internally would be just a reorganization, so editing wouldn't change too much. Anyway, just another thought for the pile we're getting. Good to see the lists so busy. -- Robert Daniels -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
