Xref: utzoo news.software.b:1226 news.misc:1270
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: news.software.b,news.misc
Subject: Re: Rn support in 3.0 (was: 3.0 news -- clearing up confusion)
Message-ID: <7773@oberon.USC.EDU>
Date: 20 Mar 88 20:41:09 GMT
References: <507@fig.bbn.com> <224167cd:252b@snark.UUCP> <2015@epimass.EPI.COM> <3203@phri.UUCP>
Sender: news@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Organization: USC AIS, Los Angeles
Lines: 30

In article <3203@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>jbuck@epimass.EPI.COM (Joe Buck) writes:
>> What there is demand for is that rn not be broken.  Another option is
>> to provide a patch to rn to do cross-referencing through the history
>> file.  (Hey, there's a fourth option!). Either way will do.

Remeber the replacment for the Xrefs line should be low overhead.
Adding several disk reads to every article read will add a lot of
overhead to news reading.  (Since rn would probably do it while
waiting for terminal input, the main impact would be on other system
users.)

>	Why do you need either Xrefs or the history file to eliminate
>seeing cross posted articles twice?  Why not just keep track of the inode
>number of every article file you open?

Because it won't work.  Inodes are reused after expire is run, some
people leave their terminals logged in for days.  If I read an
article, leave rn, and come back to rn again I don't want to see the
article again.

>  This forces you to keep the entire
>/usr/spool/news hierarchy on a single file system

This is alread required.
-- 
Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%fns1@ecla.usc.edu
			oberon!fns1!info-prime-request