[FADCA] Re: Rookie Mistake

[Chuck Hast]

On Thu, 30 Dec 2004 09:52:26 -0500, Charles S Schuman
<k4gbb at earthlink.net> wrote:
> As that old beer commercial says "Beware of the Penguin!"
> 
> I used your ax25.conf file as an example and several permutations of the
>   example in the HOW TO doc. The simple thing would connect and then
> disconnect.
> 
> The exe file would run from the command line w/o any problem. After many
> days of this I checked the permissions on the exe file and found that I
> didn't have a permission. I fixed that minor detail and it now works.
> 
> I keep running into missing files. One was the /var/ax25/fpac/loggins.
> The docs say that the needed files will be created upon install, but
> some come up missing.
> 
> I noticed that you have numbered your AXports rather than naming them.
> I didn't catch that till I got to the FPAC node and tried to make a
> connection using a port #. I guess I'll have to go back and redo the
> AX25 setup.
> 
> One of the things that slows me down is trying to catch errors on
> startup. I have been using the ol Scroll lock trick, but it is somewhat
> imprecise and I have to write out the errors on paper. I am fairly sure
> there is a log file, but haven't figured out how to access it.
> 
> After I straighten out the Port naming thing, I'll start in on the NIC
> connection.

right after you start the console at the cmd line type script filename
where filename is the file you want to capture the console session to.

This is a application that has been around for ages, it was used to check
and see what students were doing at the console, and of course used to
see what was going on when the stuff ran off the screen.

Take note that it captured both the screen output AND the keyboard input,
but is quite handy for doing exactly what you want to do if you are not using
a xterm console which allows you to scroll up and see what happened.

In the building of switches and other network devices GUI's are not of that
much use, particularly when you have so many tools that take up so much
less disk/cpu etc.

A normal linux install will have 6 consoles available, you can add more if
you so desire. Indeed Knoppix when you do the TNC install sets "listen" up
on the F11 key, so if you want to see what is happening on your radio ports
just hit F11 and you will see the fun.

I will usually open 1 console where I send commands, then I will have another
one doing some other trace of the fpacnode so I am actually on the network
then there is F11 which is the listen function.

> 
> 


-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."