Re: Status of AX.25 in 2.5 / 2.6

[Chuck Gelm <nc8q@gelm.net>]

ditto on the note from Robert Jenkins  :-)
...
and use the same keyword|token|name for the same thing
in all configuration files:

An excerpt from a message dated 3/12/02 8:56 AM
"  What I noticed was the different token names.  
Many applications and 'man' pages refer to the same thing, 
but use a different token 'name'.

 To make it easier for newbies, wouldn't it be great if all
applications, documentation, and configuration files all
used the same token name for the same thing?

Token name      Place where used
-----           ----
name            man axports
port            man kissattach
<port_name>     AX25-HOWTO/x1474.html
portname        AX25-HOWTO/x495.html#AEN1143
Port Name       man ax25d
-----           ----

 It seems to me that "<port_name>", "portname", and "Port Name" 
are close enough, but "port" (kissattach) and "name" ('axports')
are too dissimilar to tell that they both refer to the same thing.
:-|
Chuck nc8q
Espouse Elucidation, Eschew Obfuscation."

Robert Jenkins wrote:
> 
> Hi,
> 
> Another couple of points with the present AX25 which I (and I believe
> others) find annoying:-
> 
> 1: The insistance on a separate call+ssid for each port.
> 
> Every port is allocated a unique name in axports anyway, so why the need
> for the unique call as well???
> 
> (This is WAY more annoying to me than the requirement for an IP address
> - at least it will accept the same IP on multiple ports!)
> 
> It certainly does not seem to be a requirement for AX25, as the Dos BPQ
> node works fine with one call for the whole system. Being able to use
> the same callsign/ssid for multiple ports would greatly simplify some
> more comnplex configs.
> 
> As far as I know, the callsigns / aliases that the AX25 code uses for
> incoming connects are the ones set in ax25d.conf and have no connection
> to the 'axports' callsigns; these are used for outgoing connects only.
> 
> 2: The apparent requirement for two or more Netrom ports / aliases for
> the Netrom system to work correctly? Most of the docs on setting up
> netrom say separate ports are needed for incoming and outgoing connects.
> Why???
> Again, it's not a fundamental requirement for Netrom, it's an oddity in
> the Linux implementation.
> 
> One other request to anyone doing updates; please keep adding comments &
> useage notes to the sources!
> 
> Some functions do have brief descriptions, others have 'to do' notes or
> nothing at all. It makes it hard to do anything productive with the code
> when you can only spend short periods of time on it, and spend most of
> that time just trying to refresh your memory of what does what.
> 
> Regards,
> 
> Robert Jenkins.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html