Re: [Devil-Linux-discuss] Install Documentation

[Karl K. <la...@so...>]

	Since the main point of Devil-Linux (in my opinion) is to have a 
pre-compiled, everything-you-need-for-this-one-job, completely stable 
(since it is on a cd, you can't recompile things) distribution. I think 
that having setup how-to's for most of the modules would be a good 
thing.
	I completely agree that more detailed instructions and troubleshooting 
should be left to projects (a link in the DL documentation would be 
good), but since many projects have a lot of variables to deal with 
when writing their documentation, much of it does not apply (or is less 
helpful) in Devil-Linux. By focusing on a specific release version of 
DL for documentation I think we can play to our strengths.
	As a specific example: I started with DL because I was trying to get a 
PPtP server up and running. I tried out a number of distributions 
looking for a quick fix. I got very frustrated because the PoPToP 
documentation (and various mailing list discussion) is full of 
special-case information that only applies to a specific version 
compiled with specific patches, and linked with specific versions of 
other libraries...
	With DL I had a static target to work against. I wound up moving to 
1.1.x for a couple of fixes that were brought in. But the nice thing is 
that I can now document what I did against a static target, rather that 
having a long list of caveats. This is something that could drive new 
people to DL: simple instructions that are function oriented. You want 
this? Then here are the steps. This is something that the bigger 
projects will have trouble doing.

		Karl Kuehn
			la...@so...


On Mar 19, 2004, at 10:29 AM, Heiko Zuerker wrote:

>> Start where? Where to start? Pointers (to especially needy bits, for
>> instance) are welcome.

> Start here: http://www.devil-linux.org/newdoc/ch03s01.html#d0e1095
> The documentation is part of the CVS repository and everything you 
> need is
> in there.
>
> I think it would be best to ask here on the mailinglist what users are
> missing in our documentation. We just need to be carefull that requests
> like "how to configure postfix" don't go in our docs, because this 
> info is
> available on the postfix website and impossible for us to keep it
> up-to-date.