On Mon, Oct 16, 2000 at 10:44:34AM +0200, Kai Altenfelder wrote:
What do you think is best: To install and configure this atuff auto- magically without bothering the user of what is done in the background, i.e. with YaST/2 or to improve the documentation perhaps by rewriting the whole stuff and to concentrate on the main issues?
We definitely need a nice interface to configure a start script. The script itself should be independent of the distribution, a Yast2 configuration interface certainly would be SuSE specific. But nothing stops anyone to write a different interface, for example for linuxconf. There is a start of a configuration script on http://www.1409.org/projects/ax25-config.html The problem is, however, that the script for the user interface also writes the startup script instead of just dumping the configuration variables to a file. I'd like to see a more flexible solution.
Please help me because I am ignorant in this case: How do you autodetect a TNC connected to the serial port?
It's tricky due to the great number of different firmware implementations and you have to take care not to accidently send UI frames while probing the hardware. Worse, there's one case you cannot detect: pure KISS TNCs.
What I can think of is to autodetect all PCI-or PCMCIA-based cards, e.g. the new PCI-SCC card from Baycom.
That would be easy. ISA SCC cards are impossible to auto detect safely, however. Too many possible ports, too many brands...
My dream is to call YaST/2, install the hardware drivers and configure them within one step and off you go. This would be really smooth!
Indeed! Joerg Reuter DL1BKE http://yaina.de/jreuter And I make my way to where the warm scent of soil fills the evening air. Everything is waiting quietly out there.... (Anne Clark)