Xref: utzoo news.sysadmin:2358 news.admin:5728 Path: utzoo!attcan!uunet!crdgw1!crdgw1.ge.com!barnett From: barnett@crdgw1.crd.ge.com (Bruce G. Barnett) Newsgroups: news.sysadmin,news.admin Subject: Re: rrn installation woes Message-ID: <390@crdgw1.crd.ge.com> Date: 12 May 89 16:00:45 GMT References: <465@ssbell.UUCP> <30506@sri-unix.SRI.COM> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.crd.ge.com (Bruce G. Barnett) Followup-To: news.sysadmin Organization: GE Corp. R & D, Schenectady, NY Lines: 25 In-reply-to: ellis@unix.SRI.COM (Michael Ellis) In article <30506@sri-unix.SRI.COM>, ellis@unix (Michael Ellis) writes: > Evidently, nobody running nntp.1.5 also runs rrn.39, regardless of > what the source code says, right? If so, just what does it take > bring rrn up? I just did this. I got nntp.1.5 with the 3 patches, and tried to install the patches into my original copy of rn, and found it easier to get the vanilla version (guess I mangled mine too much :-). I did a "make client" in the nntp directory. This worked. nntp included a bunch of patches for rn. I copied them into the ../rn directory and executed the script to install the patches. This worked. I think I just ran the Rn configure, and told it the nntp sources were in ../nntp - and it worked reasonably well. I also build the nntp versions of readnews and vnews before I built rn. I had to modify Pnews.SH and common.h because rn thought we had a sitename.UUCP return address instead of a domain address. -- Bruce G. Barnett a.k.a. uunet!steinmetz!barnett,