Terry et el:
It looks like most people would rather keep it as one document. It does
make it alittle more difficult to start the update process, but not that
bad. I'll keep it as one for now, and start updating it section by
section. There really is alot of interaction between hardware and
software. The only real logic split I could see is to remove the tools
section and programming into its own howto. Since the tools will be
changing as folks move to glibc, using different distros, etc. I quess
it all depends on how you look at the problem. I was looking from the OS
to the hardware, but most people probably look at the hardware and
progress to the OS. The latter makes sense to me, simply because if I
already have a particular piece of hardware, I would want to find the
specific info needed to use that hardware with Linux. So, for now I'll
just start at the top of the current howto and then go from there....
What I do like is the idea of this being database driven - would make it
alot easier to keep maintained! Maybe I should move it in that direction
and have the docs created that way...
73
.mark
=================================================
Mark Schoonover KA6WKE IS Manager
Trail Runner,HAM [EMAIL PROTECTED]
ka6wke@wb6dgr.#sca.ca.usa.noam
http://www.qsl.net/ka6wke ka6wke-1 145.05
Mobile: 146.52 & 28.470
Lat: 32.85380 Long: -117.00980 Grid: DM12LU
=================================================
>----------
>From: Terry Dawson[SMTP:[EMAIL PROTECTED]]
>Sent: Wednesday, September 01, 1999 6:09 AM
>To: [EMAIL PROTECTED]
>Subject: Re: RFC: Split AX-25 HOWTO??
>
>On Tue, Aug 31, 1999 at 05:58:53PM -0700, [EMAIL PROTECTED] wrote:
>
>> I decided after getting burned out on all this Y2K update stuff, to
>> grab a copy of the AX25-HOWTO and start updating it! After creating a
>> simple index of all the topics, I've come to the quick conclusion that I
>> think the current howto can/should be split up. I can clearly see three
>> different areas:
>>
>> AX25-KERNEL-HOWTO
>> AX25-HARDWARE-HOWTO
>> AX25-TPU-HOWTO
>
>Mark,
>I'd advise against it. While the division looks logical you'll find the
>divisions quite arbitrary and strong interrelationships between them.
>
>At the moment I don't believe there is enough material to justify it, and
>when there is, then there is a better solution altogether. For example,
>the AX25-KERNEL-HOWTO would be tiny, unless you were going to move the
>sections that describe what kernel options need to be selected for a
>particular
>piece of hardware and place them there. Of course that would be silly, that
>information should be with the rest of the information relating to that
>class of hardware, otherwise what will you put in the AX25-HARDWARE-HOWTO?
>
>Splitting the AX25-HOWTO into seperate documents will cause problems, because
>the division is fairly arbitrary and you will find strong relationships
>between
>the documents that may necessitate replicating information in order to make
>any one document suitable standalone.
>
>I think additionally it will place burden on the reader (needs to search for
>and read three seperate documents) and on the document maintainer (must
>maintain consistency between documents).
>
>regards
>Terry
>
>--
>[EMAIL PROTECTED], [EMAIL PROTECTED]
>
>
