home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.bugs.misc
- Path: sparky!uunet!decwrl!deccrl!news.crl.dec.com!pa.dec.com!alf.dec.com!netnews.alf.dec.com!libove
- From: libove@libove.alf.dec.com (Jay Vassos-Libove)
- Subject: Re: "talk" bugs on the "uhunix" system
- In-Reply-To: craig@ec.uwa.oz.au's message of 7 Sep 1992 09:15:25 GMT
- Message-ID: <LIBOVE.92Sep7095743@libove.alf.dec.com>
- Sender: news@netnews.alf.dec.com (USENET News System)
- Organization: Digital Equipment Corporation, Atlanta Customer Support Center
- References: <1992Sep6.094437.11877@news.Hawaii.Edu>
- <LIBOVE.92Sep6091912@libove.alf.dec.com> <18f6jdINN2vn@uniwa.uwa.edu.au>
- Date: Mon, 7 Sep 1992 14:57:43 GMT
- Lines: 26
-
- It isn't a matter of porting the bit of code - there are two different
- talk protocols out there. It would be possible to modify the talk
- code to try its default protocol and, failing that, try the other,
- but it would be heuristic, and not 100% reliable. It would also
- lead to rather long delays in getting connected, sometimes, plus
- would fail badly if the network connection was down at the time.
-
- It makes more sense, for now, to have the two versions of talk
- available. The symptom of reaching a talk daemon of the other protocol
- version is easily recognizable (as posted by the first person to ask
- here) and running a different program isn't so bad.
-
- The real problem is that talk runs as root, and you can't just port
- the code and install it - the system administrators at every site would
- have to evaluate its safety and then choose to install it, and then
- maintain through operating system upgrades.
-
- The best possible solution is to get the people at the remote sites
- running the older version to UPGRADE.
-
- --
-
- Jay Vassos-Libove libove@alf.dec.com
- Digital Equipment Corporation decwrl!alf.dec.com!libove
- Atlanta Customer Support Center Opinions? They're mine, mine, all mine!
- Alpharetta, Georgia and D.E.C. Can't have 'em!
-