Date: Wed, 6 Jan 93 04:30:14 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #6
To: tcp-group-digest
TCP-Group Digest Wed, 6 Jan 93 Volume 93 : Issue 6
Today's Topics:
BM
Compiling
CPU ID test code
Dialing, Kicking, and Serving
Linux NET
mail error flooding
Message CC's and SNR... (2 msgs)
MX records (again)
NOS BBS (2 msgs)
Re: Problem with personal messages
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Tue, 5 Jan 93 10:55:37 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: BM
To: tcp-group@ucsd.edu
Correction - the BM on UCSD is July 1990 not 91.
Also Dave your reply was nn2z@nn2z.ucsd.edu ??? That bounced...
Doug
------------------------------
Date: Tue, 5 Jan 93 12:16:49 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: Compiling
To: tcp-group@ucsd.edu
As Phil K pointed out the code needs to be modified in order to use the
-3 switch under BC3.1 - So anyone attempting to do that is wasting there
time without the mods.
Doug
------------------------------
Date: Wed, 6 Jan 1993 5:07:20 -0500 (EST)
From: MIKEBW@ids.net (Mike Bilow, <MIKEBW@ids.net>)
Subject: CPU ID test code
To: tcp-group@ucsd.edu
I am trying to put something together that will allow identifying the
type of CPU on the fly. Below is a debug script to make a 161 byte
COM file that, when run, should tell you whether you have an 8088, a
80286, or an 80386/80486. It isn't very sophisticated, but it should
serve the purposes of NOS. I would appreciate anyone who wants to try
it doing so and letting me know what happens; I am especially interested
to know what it thinks of NEC V20 CPUs and similarly oddball things.
To make the COM file, clip out this script with a text editor to make
file NOS_CPU.SCR. Run "DEBUG < NOS_CPU.SCR" and it shoud create file
NOS_CPU.COM, which can be run directly. (No warranty!)
N NOS_CPU.COM
E 0100 BA 60 01 B4 09 CD 21 E8 29 00 3D 01 00 75 09 BA 77 01 B4 09 CD
E 0115 21 EB 15 3D 02 00 75 09 BA 8B 01 B4 09 CD 21 EB 07 BA 93 01 B4
E 012A 09 CD 21 B4 4C CD 21 CD 20 52 33 D2 9C 58 80 E4 0F 50 9D 9C 58
E 013F 80 E4 F0 80 FC F0 74 12 FE C2 9C 58 80 CC F0 50 9D 9C 58 80 E4
E 0154 F0 74 02 FE C2 FE C2 8B C2 5A C3 00 0D 0A 50 72 6F 63 65 73 73
E 0169 6F 72 20 64 65 74 65 63 74 65 64 3A 20 24 38 30 38 38 2F 38 30
E 017E 38 36 2F 56 32 30 2F 56 33 30 0D 0A 24 38 30 32 38 36 0D 0A 24
E 0193 38 30 33 38 36 2F 38 30 34 38 36 0D 0A 24
Rcx
00A1
W
Q
-- Mike Bilow, <mikebw@ids.net> (Internet)
------------------------------
Date: Tue, 5 Jan 93 17:06:12 -0800
From: chuckb@babbage.ecs.csus.edu (Chuck Bland)
Subject: Dialing, Kicking, and Serving
To: tcp-group@ucsd.edu
In my autoexec.nos file, I start a dial process to establish a
modem connection to my remote host. The lines after that command
kick POP, NNTP, and SMTP. The problem is that none of the servers
(such as domain, NNTP, POP, SMTP) are available until the dialing
process is finished. Apparently NOS doesn't wait for that to happen.
Is there a better way to do this ?
Chuck Bland
chuckb@babbage.ecs.csus.edu
------------------------------
Date: Tue, 5 Jan 93 18:45:41 GMT
From: Alan Cox <iiitac@pyr.swan.ac.uk>
Subject: Linux NET
To: tcp-group@ucsd.edu
I've knocked together a rough package from my Linux NET stuff,
mainly because quite a few people keep asking for it. This is
strictly alpha stuff. In general it works but its more a snapshot
of the workshop than the product.
It's on sunacm.swan.ac.uk:/pub/Linux/RADIO, the main tar has
a file called 'manual' in it. Hopefully this makes enough sense
as a starter.
PS: Yes X-Windows over packet works - (SLOWLY)
Alan
------------------------------
Date: Tue, 5 Jan 93 7:47:17 PST
From: Glenn Elmore <glenne@srlr12.sr.hp.com>
Subject: mail error flooding
To: tcp-group@ucsd.edu
Doug Crompton wrote:
> Question that I have - is the digest edited?? If so why do subscribe and
> mail failure messages appear in it? One recent digest had 4 messages, 3
> of which were mail failure messages from hp.com. The message descriptions
> even listed this.
and
> Ok well if it is automatic it possibly could be smart enough to reject
> messages from 'postmaster' etc.
>
> No one cares about BW on the internet but when you have a 15K message
> being sent all over AMPR with about 1K meaningful it makes sense to do
> some editing. The banner could probably be reduced in size considerably
> and still convey the message.
When I returned after the holidays from a nice vacation encouraged by
the closure of the plant during the period I was embarassed to discover
that the site mail server had been been issuing delayed-mail replies on
my "behalf" and in quantity!
I immediately agressively pursued the issue with the mail
administrator and, after receiving his apologies, have been promised
that such automatic replies will now be directed to the address listed
under the "Errors-To:" header rather than the "Reply-To:" header.
My apologies to the group for the unnecessary traffic, particularly to
those who have to pay for incoming data by the bit. I think there may
be some on the internet who *do* care about the extra BW. Certainly
ampr in its present state doesn't need the extra loading either. My
opinion is that the reply banner, short or long, has no place on the
distribution and I evidently made my point sufficiently strongly to the
local administrator. He claims to have modified the code so that
sr.hp.com will not do that again.
73 and best wishes for the new year.
Glenn Elmore n6gn
amateur IP: glenn@SantaRosa.ampr.org
Internet: glenne@sr.hp.com
------------------------------
Date: Tue, 5 Jan 93 15:07:47 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: Message CC's and SNR...
To: tcp-group@ucsd.edu
I just had a complaint about sending personal mail CC'ed to the
TCP-GROUP. It kinda hit a nerve because first of all many return
addresses appearing on this group are bogus. The only way in many
cases to return info is to send it to the group.
Actually well before this I was thinking somewhat the opposite.
Many times I send a message that could have broad interest and
I get personal return mail which really would be of interest to
the group. What is the point of having a group if the free flow
of ideas is discouraged. All this crap about signal to noise -
you might think you were first graders and couldn't read. Did
you ever here of skimming. I routinely go right by messages that
I have no interest in. It takes seconds of my precious time.
I know much of what is seen on TCP-GROUP is not in it's original
charter. I won't get into that. My point is that if a discussion
gets started that has general interest the responses should be
offered to the entire group. Since this routinely happens to me I
am sure it is with others. Free flow of information is what it is
all about. If we all had our own private dialogs there would be no
reason for a group to begin with.
Doug
------------------------------
Date: Tue, 05 Jan 93 23:17:35 MST
From: rnielsen@tapr.ampr.org (Bob Nielsen)
Subject: Message CC's and SNR...
To: tcp-group@ucsd.edu
I agree, Doug. Quite often I find the answers to other peoples questions
of great value. Now on the other hand, there are quite a few
"unsubscribe" messages that are well meant, but originated in ignorance,
and we can all hopefully live with a bit of that. Glenn saw a problem
with messages bouncing and fixed it. Hopefully others in that position
will do the same. I don't think I ever saw an explanation of why the
personal messages between some folks in Northern California showed up
here, but at least they have stopped. I don't think the snr is
unreasonable at this time.
Bob Nielsen W6SWE
ax.25: w6swe@wb7tpy.az.usa.na Internet: rnielsen@tapr.ampr.org
amateur IP: 44.124.12.16 CIS: 71540,2364
------------------------------
Date: Wed, 6 Jan 1993 4:43:08 -0500 (EST)
From: MIKEBW@ids.net (Mike Bilow, <MIKEBW@ids.net>)
Subject: MX records (again)
To: jangus@skyld.tele.com, tcp-group@ucsd.edu
Without belaboring the point too much -- and I think we have each set
out our views -- NOS does not assume that the domain suffix is to be
added to all domain names. In fact, NOS will not append the domain
suffix to any name which has a rightmost field of three characters
("bbs" or "edu"), nor a rightmost field of four characters, none of
which is a digit. In other words, NOS appends the domain suffix to
anything that looks like a callsign in the rightmost field, either
because it has five or more character or because it has four characters,
at least one of which is a digit.
-- Mike Bilow, <mikebw@ids.net> (Internet)
------------------------------
Date: Tue, 5 Jan 1993 07:46:37 -0500 (EST)
From: "David J. Trulli" <nn2z@nn2z.UCSD.EDU>
Subject: NOS BBS
To: "D. Crompton" <crompton@nadc.nadc.navy.mil>
The current bm on ucsd.edu sends all mail to NOS to be run through the rewrite
rules. This causes NOS to open an smtp connection to itself but
it does get things through the rewrite rules.
I have used this method here for over 6 months.
Dave
>
> Tony,
>
>
> That makes sense but if I do not have the gateway to myself it breaks
> all kinds of other things - like being able to send mail to w3eee@w3ddd.bbs
> This would have no domain entry but would have a rewrite entry - But the
> external mailer - BM/VIEW etc does NOT get scanned by rewrite unless
> the gateway is set to yourself.
>
> Seems like you are damned if youdo damned if you don't!!
>
> It is obvious to me now that I can't get where I want to go without
> some code changes.
>
> Doug
>
--
Dave Trulli internet: nn2z@nn2z.ampr.org, david.trulli@att.com
packet: nn2z@nn2z.nj.usa.na
------------------------------
Date: Tue, 5 Jan 93 10:49:32 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: NOS BBS
To: nn2z@nn2z.UCSD.EDU
Dave,
I checked UCSD and the last BM is dated July 1991 in the BM directory.
Is this the one you are talking about?
Doug
------------------------------
Date: Tue, 5 Jan 93 12:13:55 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: Re: Problem with personal messages
To: nos-bbs@hydra.carleton.ca
Phil F,
(we have at least two Phil's on here)
We need to fix NOS so that EACH message has a different MID - I suspect
Johan will have this on his hot list of things to do when he gets back.
He just put the MID stuff in and he should be able to make the correction
very easily. Having the MID as MSGID with call letters would probably be
the answer. Anything to make it unique. I suspect that NOS also needs to
stop trying when it gets a NO and possibly send the mail to some local
holding tank like 'refuse'.
Doug
------------------------------
End of TCP-Group Digest V93 #6
******************************
******************************