Xref: utzoo news.software.b:1230 news.misc:1273
Path: utzoo!mnetor!uunet!epiwrl!epimass!jbuck
From: jbuck@epimass.EPI.COM (Joe Buck)
Newsgroups: news.software.b,news.misc
Subject: Re: Rn support in 3.0 (was: 3.0 news -- clearing up confusion)
Message-ID: <2020@epimass.EPI.COM>
Date: 21 Mar 88 18:41:22 GMT
References: <507@fig.bbn.com> <224167cd:252b@snark.UUCP> <2015@epimass.EPI.COM> <3203@phri.UUCP>
Reply-To: jbuck@epimass.EPI.COM (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 18

In article <3203@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>	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?  This forces you to keep the entire
>/usr/spool/news hierarchy on a single file system but I don't think that's
>a big problem (how many people keep /usr/spool/news/comp on one filesystem
>and /usr/spool/news/sci on another?)

News already requires that everything be on one file system.  But
your solution won't work, because news users don't necessarily read
all articles and groups in every news reading session.  For example,
if an article is cross-posted to news.software.b and news.misc like
this one is, and I read all of news.misc and then quit before
starting to read news.software.b, the article in news.software.b
won't be marked as read and I'll see it twice.
-- 
- Joe Buck  {uunet,ucbvax,sun,<smart-site>}!epimass.epi.com!jbuck
	    Old Internet mailers: jbuck%epimass.epi.com@uunet.uu.net