Usenet News HOWTO
Prev |  | Next

# 14. Documentation, information and further reading

This section fills in gaps which were hard to classify under any of the previous chapters.

## 14.1. The manpages

The following manpages are installed automatically when our integrated software distribution is compiled and installed, listed here in no particular order:

- `badexpiry:` utility to look for articles with bad explicit Expiry headers

- `checkactive:` utility to perform some sanity checks on the `active` file

- `cnewsdo:` utility to perform some checks and then run C-News maintenance commands

- `controlperm:` configuration file for controlling responses to Usenet control messages

- `expire:` utility to expire old articles

- `explode:` internal utility to convert a master batch file to ordinary batch files

- `inews:` the program which forms the entry point for fresh postings to be injected into the Usenet system

- `mergeactive:` utility to merge one site's newsgroups to another site's `active` file

- `mkhistory:` utility to rebuild news `history` file

- `news(5):` description of Usenet news article file and batch file formats

- `newsaux:` a collection of C-News utilities used by its own scripts and by the Usenet news administrator for various maintenance purposes

- `newsbatch:` covers all the utilities and programs which are part of the news batching system of C-News

- `newsctl:` describes the file formats and uses of all the files in `$NEWSCTL` other than the two key files, `sys` and `active`

- `newsdb:` describes the key files and directories for news articles, including the structure of `$NEWSARTS`, the `active` file, the `active.times` file, and the `history` file.

- `newsflag:` utility to change the flag or type column of a newsgroup in the `active` file

- `newsmail:` utility scripts used to send and receive newsfeeds by email. This is different from a mail-to-news gateway, since this is for communication between two Usenet news servers.

- `newsmaint:` utility scripts used by Usenet administrator to manage and maintain C-News system

- `newsoverview(5):` file formats for the NOV database

- `newsoverview(8):` library functions of the NOV library and the utilities which use them

- `newssys:` the important `sys` file of C-News

- `relaynews:` the `relaynews` program of C-News

- `report:` utility to generate and send email reports of errors and events from C-News scripts

- `rnews:` receive news batches and queue them for processing

- `nntpd:` The NNTP daemon

- `nntpxmit:` The NNTP batch transmit program for outgoing push feeds

## 14.2. Papers, documents, articles

There are certain documents and published conference papers which are a must-read for Usenet server administrators, both for their historical value and for the insight they give into Usenet server architecture in general. We list our chart-toppers here.

### 14.2.1. The Usenix paper on C News

This very interesting paper has been mentioned in the section titled "Usenet software: a historical perspective>". It is titled ``News Need Not Be Slow'', and is available from `ftp://ftp.cs.toronto.edu/doc/programming/c-news.*` or from our Website (`http://www.starcomsoftware.com/proj/usenet/doc/c-news.{ps,pdf}`).

It focuses on B News, analyses it for performance, and demonstrates how specific changes in design and implementation can speed things up. It is well-written, and is educative in many areas independent of Usenet news.

### 14.2.2. The Usenix paper on INN

This paper talks about the things that C News didn't address, and takes Usenet news processing into the world of pure Internet connectivity. Its author is Rich Salz, the author of INN, and the paper is titled ``InterNetNews: Usenet Transport for Internet Sites.'' This can be picked up from `ftp://ftp.uu.net/networking/news/nntp/inn/inn.usenix.ps.Z` or from our Website (`http://www.starcomsoftware.com/proj/usenet/doc/inn.usenix.{ps,pdf}`), uncompressed. Be warned: this PostScript file is probably missing some mandatory first-line tag like `%!PS-Adobe-1.0` and some PostScript processors can have problems with it. For instance, on our Linux boxes, `ghostview` can display it, but `kghostview` can't, which is very strange.

This paper analyses the world of Usenet servers with C News and NNTPd, in the presence of multiple parallel feeds, and proceeds to build a case for a powerful NNTP-optimised software architecture which will handle multiple parallel incoming NNTP feeds efficiently. What later INN users appear to miss sometimes when comparing C-News+NNTPd with INN, is that INN's strengths are only in situations which its author had specifically targeted, i.e. multiple parallel incoming NNTP feeds. There is no clear superiority of one system over the other in any other situation.

### 14.2.3. The C News guide

This document is part of the C-News source, and is available in the `c-news/doc` directory of the source tree. The `makefile` here uses `troff` and the source files to generate `guide.ps`. This C News Guide is a very well-written document and provides an introduction to the functioning of C News.

## 14.3. O'Reilly's books on Usenet news

O'Reilly and Associates had an excellent book that can form the foundations for understanding C-News and Usenet news in general, titled ``Managing UUCP and Usenet,'' dated 1992. This was considered a bit dated because it did not cover INN or the Internet protocols.

They have subsequently published a more recent book, titled ``Managing Usenet,'' written by Henry Spencer, the co-author of C-News, and David Lawrence, one of the most respected Usenet veterans and administrators today. The book was published in 1998 and includes both C-News and INN.

We have a distinct preference for books published by O'Reilly; we usually find them the best books on their subjects. We make no attempts to hide this bias. We recommend both books. In fact, we believe that there is very little of value in this HOWTO for someone who studies one of these books and then peruses information on the Internet.

## 14.4. Usenet-related RFCs

TO BE ADDED

## 14.5. The source code

TO BE ADDED

## 14.6. Usenet newsgroups

There are many discussion groups on the Usenet dedicated to the technical and non-technical issues in managing a Usenet server and service. These are:

- `news.admin.technical` Discusses technical issues about administering Usenet news

- `news.admin.policy` Discusses policy issues about Usenet news

- `news.software.b` Discusses C-News (no separate newsgroup was created after B-News gave way to C-News) source, configuration and bugs (if any)

MORE WILL BE ADDED LATER

## 14.7. We

We, at Starcom Software, offer the services of our Usenet news team to provide assistance to you by email, as a service to the Linux and Usenet administrator community, on a best effort basis.

We also offer you an integrated source distribution of C News, NNTPd, as discussed earlier in the section titled "Setting up C News + NNTPd>". This integrated source distribution fixes some bugs in the component packages it includes, and it comes pre-configured with ready made configuration files which allow all components to be compiled and installed on a Linux server in a manner by which they can work together (e.g. key directory paths are specified consistently across all components, etc.) This is available at `http://www.starcomsoftware.com/proj/usenet/src/`

The URL `http://www.starcomsoftware.com/proj/usenet/src/archives/` holds the original sources of some of the software components we base our distribution on. These include C News (`c-news.tar.Z`), NNTPd (`nntp.1.5.12.1.tar.Z`), and Nestor (`nestor.tar.Z`). Other components, like `pgpverify` are maintained by their current maintainers and can be obtained from their respective sites. Therefore, they are not included in our archives.

The URL `http://www.starcomsoftware.com/proj/usenet/doc/` carries copies of some of the important technical articles and Usenix papers on the subject of the Usenet.

We will endeavour to answer all queries sent to `usenet@starcomsoftware.com`, pertaining to the source distribution we have put together and its configuration and maintenance, and also pertaining to general technical issues related to running a Usenet news service off a Unix or Linux server.

We may not be in a position to assist with software components we are not familiar with, e.g. Leafnode, or platforms we do not have access to, e.g. SGI IRIX. Intel Linux will be supported as long as our group is alive; our entire office runs on Linux servers and diskless Linux desktops.

You are not forced to be dependent on us, because neither do we have proprietary knowledge nor proprietary closed-source software. All the extensions we are currently involved in with C-News and NNTPd will immediately be made available to the Internet in freely redistributable source form.

Prev | Home | Next
Usenet software: a historical perspective |  | Wrapping up