[nos-bbs] netrom alias - discussion on uppercase / lowercase

[Gustavo Ponza]

Hi all,

On Mon, 2011-08-29 at 14:28 -0500, Maiko Langelaar wrote:
> I see alot of lower case netrom ALIAS values, mostly from Xnet routers.
> 

One of them it's mine: 'colle:I0OJJ-3' which was recently adopted, but
only to easy individuate/verify my XNET node inside on a list containing
over 400 nodes...

> My understanding is that the ALIAS is supposed to be UPPERCASE.

However the uppercase 'only' derives from the MSDOS and similar
environments... for linux no problem to manage upper/lower case
and any other character... (some stupid setup are also around).

... just discovered a JNOS bug: the JNOS seems to impose the
same 'alias' [JNOS] to yours and mine systems, i.e.: JNOS:IR0JW-5
and JNOS:VE4KLM-3 skipping the one setup on the 'autoexec.nos'
(I have setup GWOJJ on my system) - see the XNET node listing:

08:23:58 01.09.11 I0OJJ de I0OJJ-3 >n j

JO30qj:DB0LJ        JNOS:IR0JW-5    JOABPQ:N4JOA-3    JLGDXC:PA1JLG-1
JLGBBS:PA1JLG-3   JLGCMS:PA1JLG-5   JLGRMS:PA1JLG-10  JLGNOD:PA1JLG-12
  JNOS:VE4KLM-3
08:24:07 01.09.11 I0OJJ de I0OJJ-3 >

> The *specs* are telling me I should have JNOS force these to uppercase
> before I add them to my JNOS node tables. But then if I broadcast my nodes
> to others, what is the consequence of this ?
> 
> Any comments or suggestions ?
> 
> Maiko Langelaar / VE4KLM

No reason (for me) to force the JNOS to translate into UPPERCASE... and,
furthermore, if your system, for example, translate: colle:I0OJJ-3 into
COLLE:I0OJJ-3, your broadcasts will confuse the 'linux' systems because
'colle' is another thing (different) with respect to 'COLLE' ... and
(perhaps) also two stations having the I0OJJ-3 callsign cannot exist :)

73, Gustavo / I0OJJ

> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs