Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!DECWRL.DEC.COM!mogul
From: mogul@DECWRL.DEC.COM (Jeffrey Mogul)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Many things on ethernet together???
Message-ID: <8805190239.AA10180@acetes.dec.com>
Date: 19 May 88 02:39:35 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

When I saw the first message asking about how to deal with
Pups on 802.3 networks (the old Ethernet type code for Pup
is a legal 802.3 length code), I thought to myself "nobody
runs Pup on 10mb nets any more" (I wrote the code in the
Stanford Unix Pup package to handle the 10mb stuff, and
since this is apparently the only Pup code for Unix systems,
I thought I knew something.)  Then Darrel VanBuer writes
that there's a new, "legal" code for Pup and Pup ARP.

Does this mean that people still use Pup (outside of Xerox?)
Wow!  (Dave Boggs is going to love this one.)  Does anyone
really care if Pup coexists with 802.3 systems?  If so, I'm
doubly surprised.  Does anyone want the same host to speak
Pup and 802.3 ('cause otherwise the Pup hosts should drop
the 802.3 packets due to bad checksums, and vice versa)?

Sorry this is on TCP-IP, but I've noticed a tendency towards
protocol archeology this week, and Pup certainly is a relic.

-Jeff