[nos-bbs] anyone seen this?

[Don Moore]

Whatever it is must be related to jnos2.0e because the error does not exist in jnos2.0f4

Thanks for the advise and I may try them later.


73 and have a great 2010
Don - ve3zda




________________________________
From: on4hu.0 <on4hu.0 at gmail.com>
To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
Sent: Tue, December 29, 2009 12:44:00 PM
Subject: Re: [nos-bbs] anyone seen this?

i using the following scipt to satar JNOS with the command ./dojnos




#=============================================
#! /bin/sh

# Script to invoke the Unix Jnos.
# Usage:  dojnos [-gdb|-inittab] [optional_args]
# where -gdb means to invoke the gdb debugger with Jnos
#       -inittab is followed by VC-device, terminfo-name and optional Jnos 
args
#       (otherwise an interactive invocation is assumed).
# Example inittab entry:
#7:2345:respawn:/jnos/dojnos -inittab /dev/tty7 sl0 -C
#
# CHANGE THE DEFINITIONS FOR jnosroot AND autoexec, THE $local, $remote AND
# $mtu VALUES BELOW, AS WELL AS ANY VARIABLES CONTAINING "n5knx":

jnosroot=/jnos
autoexec=autoexec.nos

cd $jnosroot
rm /spool/mqueue/*.lck 2> /dev/null

#QRZDRV=/mnt/cdrom
MSGUSER=on4hu
USER=root
export QRZDRV MSGUSER USER
#
# Add some more to allow access even when ftpusers is damaged:
# YOU MUST 'CUSTOMIZE' THE NEXT 3 LINES OR YOU WILL HAVE A BIG SECURITY FLAW.
#
NOSSYSOP=on4hu
NOSPASSWD=xxxxxxxxxxxx
NOSPATH="/ 0x24037f"
#
export NOSSYSOP NOSPASSWD NOSPATH

# It seems that the proxyarp DIP cmd is failing...so we do it ourselves.
# We want the Linux ip stack to respond to ARPs for the Jnos IP addr,
# for those packets received via eth0 (ethernet).
arp -Ds 44.144.195.2 eth0 pub
arp -Ds 44.144.195.1 eth0 pub

# Corresponding to the above slip setup, are matching Jnos attachments:
#
#
attach asy ttypf - slip sl0 1536 576 38400
asyconfig sl0 txq 10
asyconfig sl0 rxq 10
#
#===========================================


Le mardi 29 décembre 2009 18:18:07, George [ham] VerDuin a écrit :
> Hi Don.
> 
> On 12/29/2009 07:24 AM, Don Moore wrote:
> > I am using a Dell P2 400 with slackware 13.0.
> >
> > When I try to start up jnos 2.0e using
> 
> Question: is
> 
> > ./jnos -c
> 
> the entire command line you use to start jnos?
> See:
> 
> http://jnoswiki.no-ip.org/jnoswiki/CommandLineParms?highlight=%28-c%29
> page and note the number of columns is missing from the example?
> This implies you want a screen width of zero or default?
> 
> Your question is interesting, so I tried:
>       "...# ./jnos"
>       "...# ./jnos -c80"
>       "...# ./jnos -c 80"
>       "...# ./jnos -c66"
>       "...# ./jnos -c"
> and got no "Segmentation Fault" in any of the trials.
> The example of "-c 80" [with a space] did start very poorly because the
> "80" was confusing to jnos.
> 
> > I get the following message
> > when the jnos window pops up and of course jnos does not start up.
> >
> > Segmentation fault
> 
> I suspect the memory fault is connected to something other than the "-c"
> parm.
> 
> > 73, Don - ve3zda
> 
> Best of luck with isolating the source of the fault.
> You might employ "gdb" as a tool?
> 
> 73
> Skip
> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
> 

-- 
    http://www.on4hu.be:81/ -  http://www.on4hu.be/
    ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/
    COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING
    PROPERLY AS SOON AS YOU OPEN WINDOWS..




_______________________________________________
nos-bbs mailing list
nos-bbs at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20091229/178f134f/attachment.html>