RE: Split AX-25 HOWTO??
I support the idea. I can also supply some info to the AX25-HARDWARE-HOWTO (if it comes to exist) on how to configure the German-made SCC board 'Primus' and its derivatives (Clark etc) Best 73 de Bent/OZ6BL
RE: Split AX-25 HOWTO??
Hello Bent, hello all, I support the idea. I can also supply some info to the AX25-HARDWARE-HOWTO (if it comes to exist) on how to configure the German-made SCC board 'Primus' and its derivatives (Clark etc) Since I am always collecting such information for updated versions of the German AX.25-HOWTO and (if nobody has to say something against it) its retranslation into English I am very interested in your experiences. Cheers, 73 Gerd
Re: RFC: Split AX-25 HOWTO??
Hello Mark, hello all, 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 Why would you want to separate this? In order to set up the hardware, you first will have to set up the AX.25 kernel subsystem. AX25-HARDWARE-HOWTO Yes, that's a good idea. AX25-TPU-HOWTO Not enough information available to create a whole HOWTO document from only this. My proposal: 1. The AX.25-HOWTO (maybe renamed to AX.25-Hardware- HOWTO) -contains the setup of the AX.25 kernel subsystem -contains the setup of the drivers -does NOT contain that whole bunch of examples any more, these are moved to the 2. AX.25-Software-HOWTO -contains the basic application setup -contains hints on available Packet Radio Software for Linux (Terminal programs, BBSs etc.) - the HAM HOWTO could be disburdened a little bit -contains sample configurations to help installing the software -contains explanations of common pitfalls when using Linux AX.25 software -AND ALSO contains some docomentation to the AX.25 programming interface as long as it is Linux specific. Just a suggestion... Cheers, 73 Gerd
Re: Split AX-25 HOWTO??
i have been working in an update of AX-25 HOWTO in Spanish since one year ago... available in http://atlas.gbt.tfo.upm.es Very please to help Cheers alberto Gerd wrote: Hello Bent, hello all, I support the idea. I can also supply some info to the AX25-HARDWARE-HOWTO (if it comes to exist) on how to configure the German-made SCC board 'Primus' and its derivatives (Clark etc) Since I am always collecting such information for updated versions of the German AX.25-HOWTO and (if nobody has to say something against it) its retranslation into English I am very interested in your experiences. Cheers, 73 Gerd
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]
Re: RFC: Split AX-25 HOWTO??
On Wed, Sep 01, 1999 at 10:56:43AM +, Gerd wrote: 2. AX.25-Software-HOWTO -contains the basic application setup -contains hints on available Packet Radio Software for Linux (Terminal programs, BBSs etc.) - the HAM HOWTO could be disburdened a little bit The HAM-HOWTO will cease to exist, real soon now. It will be replaced by a dynamically generated document from the radio software database. Personally, before embarking on using HOWTO documents as a means for describing how to install/configure individual pieces of application software I'd take a look at existing HOWTOs that tackle this problem. It hasn't proved very succesful. -AND ALSO contains some docomentation to the AX.25 programming interface as long as it is Linux specific. This defininetly needs capturing somewhere. I'd intended to put it into the AX25-HOWTO .. I'd put a place holder in there in the hope that someone (maybe even me) would contribute the relevant information. regards Terry -- [EMAIL PROTECTED], [EMAIL PROTECTED]
Re: RFC: Split AX-25 HOWTO??
Terry Dawson wrote: 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. Yup From time to time I try to create an ax25 configuration tool. I don't ever seen to find a clean place to divide the work. It can get real messy. ;-) How about adding the information needed to create an ax25 loopback pair to the howto? I don't think there's anything in there about sharing an ax25 interface using net2kiss or sharing a kiss device using kissnetd either. Bob
RE: RFC: Split AX-25 HOWTO??
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 KA6WKEIS 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]
Re: RFC: Split AX-25 HOWTO??
Hello Arno, hello all, My proposal: 1. The AX.25-HOWTO (maybe renamed to AX.25-Hardware- HOWTO) -contains the setup of the AX.25 kernel subsystem -contains the setup of the drivers -does NOT contain that whole bunch of examples any more, these are moved to the 2. AX.25-Software-HOWTO -contains the basic application setup -contains hints on available Packet Radio Software for Linux (Terminal programs, BBSs etc.) - the HAM HOWTO could be disburdened a little bit -contains sample configurations to help installing the software -contains explanations of common pitfalls when using Linux AX.25 software -AND ALSO contains some docomentation to the AX.25 programming interface as long as it is Linux specific. I like this better than splitting it into three. But why split it? The only reason I can think of is maintainability. To me it only makes sense if the AX25-HARDWARE-HOWTO and AX.25-Software-HOWTO would have two different maintainers. The ease of maintaining is not the only reason. The current version of the German AX.25-HOWTO I am working on is a document of more than 300 kB in size. It simply becomes too big. The other reason is that AX.25 software should have its very own place of HOWTO-like documentation. AFAIK this is not the case at the moment, but there are a lot of frequently asked questions for that kind of software, though, that should be covered in an easy-to- read, short and precise way. And, at least, there's a problem for one single person that deals with something like different software packages in his spare time: He would under no circumstance be able to know everything about every single software that should be mentioned in a Software- HOWTO. So, a Software-HOWTO preferrably should be a teamwork where everyone can participate who is very familiar with a certain program. Maybe the best solution is a separate chapter for every program with its own maintainer and contributors. Cheers, 73 Gerd
RFC: Split AX-25 HOWTO??
Thanks for Reading! 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 Description: AX25-KERNEL-HOWTO How to compile the kernel for AX25 support with different hardware. AX25-HARDWARE-HOWTO How to configure the different hardware supported by the kernel. AX25-TPU-HOWTO Find, compile, configure and use the different AX25 tools and utilities. AX25 programming, and other low-level topics. TPU = Tools, Programming Utilities Feel free to comment! I'm looking for input on this. This is right off the top of my head, as I've only spent about an hour with the current HOWTO. There's a bunch to do. 73 .mark = Mark Schoonover KA6WKEIS 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 Long: 32.85380 Lat: -117.00980 Grid: DM12LU = Right now, I'm having amnesia and deja vu at the same time...
