GNUEMACS and News software

Thread View: mod.computers.apollo

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by BURATI Thu, 10 Jul 1986 15:23

#203

Author: BURATI
Date: Thu, 10 Jul 1986 15:23

32 lines
1920 bytes

I just successfully? installed gnuemacs (17.58 or something like that) on
our net but am still having problems.  The 'make' went fine, no errors or
anything like that, but emacs dies after about a minute of startup messages
(loading paths.el...) It dies with a 'Segmentation Fault' that writes over
the last startup message, so I can't tell what it was doing when it died
(sometime after 'finding doc-string pointer'?).

Before I recompile it with the debugger option set and get lost in the debugger,
has anybody else had this problem and found an easy fix?  I was under the
impression that the only changes that had to be made were using 's-bsd4.2'
and 'm-apollo.h' in the config.h file and a slight change to one of the
Makefiles.

----------

	I'm going to try and get the 'news' software running under domain/ix
soon, has anybody had any experience (success/failure?) doing this?
Right now, I have vnews running fine using a v2 link to the /usr/spool/news
directory on our vax.

	The only problem I can foresee is that I will have to get the software
to send news using tcp/ip instead of uucp over serial line.  Most of the
software looks like it relies on uucp (I could be wrong).  Any suggestions?

================
Michael Burati
University of Lowell
CS Dept
Lowell MA

uucp: .. {wanginst | apollo | masscomp | datacube} !ulowell!burati

Re: USENET news software and Apollo Domain/IX

#212

Author: dclemans%UUCP
Date: Mon, 14 Jul 1986 22:06

31 lines
2518 bytes

We have the USENET news software (news 2.10.3 beta, rn, vn) running on the Apollo
ring at Mentor Graphics. The news message directories (i.e., /usr/spool/news renamed)
are on a DSP160. That same node also handles sending/receiving news from our
feed site, sequent. People run the news reading programs from their individual
nodes.

In this environment, the BIG problem with the USENET software (specifically inews)
is that it depends on being able to write to the news active file (and the history
file?) anytime it wants to. This capability is NOT supported in general on a
multi node Domain/IX environment; i.e. if a news reading program has the "active"
file open for reading, inews/rnews WILL NOT be able to open it with write access
(unless both the news reader program and inews/rnews are running on the same node).

This causes things like multitudes of "unwritable files" messages to the news
administrator, some articles dropped on the floor, etc. EXCEPT for "rn", things
aren't too bad, because most of the news reader programs just read the active file
once, close it (or else don't use it any more), and go on with their business.
However, "rn" keeps the active file open and in use during the whole time it's
running. This can lock out inews/rnews for quite a while.

To get around this, I modified "rn" to make a copy of the active file when it starts
up and from then on reference only the copy. I also stuck some "ulkob -f" (or equivalents)
in at various places. With this there's still spurts when a few articles disappear,
but it's not too bad.

Another problem is that there are scattered uses of uninitialized local variables
throughout the USENET software. While you can get away with that most of the time
on typical UNIX architectures with entirely separate address spaces, you can't on
Domain/IX where an address space is shared.

dgc

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads