Re: SLFS book chapter proposals
Robert Day <[email protected]> Sat, 27 Dec 2003 23:06:55 -0500
| Newsgroups | gmane.linux.lfs.security |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 2003-12-27 at 22:32, Archaic wrote: > Total agreement. But as far as hindering, I think the instructions > should allow for building a production server, with many of the steps > marked in some way to show trade off. For instance, remote logging. Not > needed for a one box network. :) There are certainly others as well. > Though many will come with so little loss of functionality or > performance that they should be marked for every use. That's what I've > been thinking about the last couple of days. A rating system of how > intrusive each technique is. Not in the install, as some will be quite > complicated, but in the use of the system with said technique in place. Agreed. And marked in memor (as well as saved on ym system) for when the book gets to that point. > > We agree on overall goals, as you have stated exactly what my vision is. > We just disagree on implementation. Then we need to come to an agreement. Either that or we need to separate ways, and make two books ;) LOL I think a good "best of both worlds" implimentation is to recommend that users start with a fresh LFS system, as the host, but I still think that the SLFS book should be written as a from scratch. I know the arguments for both sides are valid.. And maybe it can start off it's life (SLFS that is) as an extention to LFS to get the book underway, but I think the ultimate goal should be a standalone build, from toolchain through completion. No requirements for pre-building anything that is not in the book. I think the end goal should be a printed, published book, with a BootCD and all sources, included in the book, as well as the online errata pages etc. I know it's a bog project, and I am sure alot of the hesitation is because the task seems so daunting.. but as the famous saying goes, even a journy of a thousand miles begins with a single step. Our first step has been taken - the decision that this was a needed thing, and that we wanted to build it. Now that we took the first step, let's all agree on the destination. How we get there we can work out tomorrow, or the next day, or next week (next year to be exact ;) Sound acceptable? Rob Day (BOFH) -- http://linuxfromscratch.org/mailman/listinfo/lfs-security FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page