WARNING: Use this program at your own risk.  It backs up your .newsrc in
.newsrc~ when you run it, but there is still some possibility of losing
your .newsrc unless you make a backup somewhere.  Note that rn(1) uses
.newsrc.bak to back up the .newsrc, so there's always a mildly recent
copy around.

To run, type

	News -NewsHost <nntp_machine_name>

where <nntp_machine_name> is the internet name or number of a machine
which runs NNTP.

That's all most people at large sites will have to do.  For example,
Stanford people type
	News -NewsHost portia.stanford.edu
while UWash people type
	News -NewsHost milton.u.washington.edu

To save yourself typing, do a
	dwrite News NewsHost <nntp_machine_name>
once in a shell.  Now you can invoke News from the Workspace manager.

If your next is running nntp itself, you needn't set anything.

If you have /usr/spool/news mounted from a central server, you're
doing things the silly way.  To run News, you must either
(a) put NNTP up on the server, or
(b) put NNTP up on your machine.

To get NNTP, ftp it from uunet.uu.net, modify the config.h file and
follow the instructions on how to install it properly.

If your newsfeed is via UUCP the above discussion applies to you, too.

Eventually all this will be made easier.  This is a beta version, I've
tried to get the functionality and I haven't sweated the compatibility.
What I'd like to do is bundle nntp with News and auto-start it if there
is a /usr/spool/news directory handy.

-william shipley
july 23, 1990