Xref: utzoo news.software.b:1223 news.misc:1268
Path: utzoo!mnetor!uunet!husc6!ncar!gatech!uflorida!beach.cis.ufl.edu!esj
From: esj@beach.cis.ufl.edu (Eric S. Johnson)
Newsgroups: news.software.b,news.misc
Subject: Re: Rn support in 3.0 (was: 3.0 news -- clearing up confusion)
Message-ID: <13272@uflorida.cis.ufl.EDU>
Date: 20 Mar 88 17:32:22 GMT
References: <507@fig.bbn.com> <224167cd:252b@snark.UUCP> <2015@epimass.EPI.COM> <3203@phri.UUCP>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: esj@beach.cis.ufl.edu (Eric S. Johnson)
Organization: UF CIS Department
Lines: 24

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?)

This, is a nice idea, but it wont work for NNTP/rrn systems. 

I dont quite understand why this is a big problem. Why do people feel the
Xref header line is a terible thing? 

Please, news system developers, remember that a large percentage of news
is read and transfered via NNTP nowadays. (At our site NO ONE reads news
any other way. Everyone uses rrn or gnews.) For us to adopt a wonderful
new system, be it C news or news 3.0, it has to be compatible with what
ever is the current release of NNTP. 


--
In Real Life:           Internet: esj@beach.cis.ufl.edu
Eric S. Johnson II      UUCP: ...{codas!gatech}!uflorida!beach.cis.ufl.edu!esj
University of Florida         Think of it as entropy in action :-)