Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!uunet!in2.uu.net!204.178.176.27!hunter.premier.net!europa.clark.net!howland.erols.net!newsfeed.internetmci.com!news.easystreet.com!not-for-mail From: "Ted Mittelstaedt" <tedm@portsoft.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: NNTP help Date: 16 Jun 1997 20:07:53 GMT Organization: Portland Software Lines: 32 Message-ID: <01bc7a90$e60ca940$6601a8c0@teds.portsoft.com> References: <339d8b75.7748544@news.gol.com> <slrn5pu9qa.25a.ripley@nortobor.nostromo.in-berlin.de> <33a55a42.1167101@news.gol.com> NNTP-Posting-Host: mail.portsoft.com X-Newsreader: Microsoft Internet News 4.70.1155 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42898 I've dealt with the NNTP and Cnews from the Ports collection and I eventually had to chuck them and recompile from the sources. NNTP is compiled with authorizations turned on in the ports, which makes it worthless for me, and it's an old version besides. Cnews doesen't include the libnews.a archive file (which is built when you compile Cnews from the sources) and which is required for building nntp (because nntp needs to know how cnews has the history file database built) so you can't take the port and then compile nntp, you have to build both from scratch. In any case, there are dozens of places in Cnews where absolute pathnames are present so you really should build it yourself. I used the "classic" instructions from the O'Reilly book and they worked fine for Cnews. For NNTP, you want the "full" distribution, NOT the so-called "nntp client" distribution which is mainly intended to support _old_ newsreading programs (like the character-based rn) on Unix systems where there is no news server present. Ted Kurt Keller <Kurt@pinboard.com> wrote in article <33a55a42.1167101@news.gol.com>... > On 11 Jun 1997 22:31:38 GMT, ripley@nostromo.in-berlin.de (H. Eckert) > wrote: > > > > I'm struggling setting up CNews and NNTP from the ports collection on my > > [...] > > > > What's wrong about INN ? > > Unfortunately too resource hungry for that particular machine. Upgrade > impossible.