Warning: Failed mail to VMS host

[mail-support%cernvax.cern.ch at pucc.princeton.edu]

Your message to <@DxMINT.cern.ch:OLAVI%13411.decnet.CERN at CERNVAX> could not be
 delivered.
The error message was:

Deferred: %MAIL-E-OPENOUT, error openning as output

This message is equivalent to the DECnet-VAX error message:

 -SYSTEM-F-EXDISKQUOTA, disk quota exceeded

The reason why your message could not be delivered is caused by the fact that
your correspondants account has ran out of diskquota. Please contact your
correspondant (by phone or otherwise) and tell him about this problem.


====== The start of Your original message ======

UNIX-WIZARDS Digest          Wed, 14 Nov 1990              V11#031

Today's Topics:
                    Re: Bad login user id(sco-unix)
             Re: Problems with July 90 release of RISC6000
                             Socket number?
                                 YA4.1B
                         SLIP/streams problems
             Re: Problems with July 90 release of RISC6000
                         Killer Micro Question

-----------------------------------------------------------------

From: "John F. Haugh II" <jfh at rpp386.cactus.org>
Subject: Re: Bad login user id(sco-unix)
Date: 24 Oct 90 06:49:33 GMT
X-Clever-Slogan: Recycle or Die.
To:       unix-wizards at sem.brl.mil

In article <1826 at overlf.UUCP> emanuele at overlf.UUCP (Mark A. Emanuele) writes:
>In article <24816 at adm.BRL.MIL>, hliao at opus.calstatela.edu writes:
>> 	Why don't you try "exec login"?
>
>That won't work because of the security "features" included with SCO.

there is an alleged attempt to port my login suite to SCO UNIX.  if
you want to join in on the fun, why don't you try to pick up a copy
of the sources from an archive site near you.  or just wait until
the appropriate bodies send their changes back to me to post ...

i don't know what all SCO did to UNIX to make it so ornery, so i
can't comment on how bizarre the security features in SCO UNIX are.

just remember boys and girls - security is your FRIEND!
--
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh at rpp386.cactus.org
"SCCS, the source motel!  Programs check in and never check out!"
		-- Ken Thompson

-----------------------------

From: "John F. Haugh II" <jfh at rpp386.cactus.org>
Subject: Re: Problems with July 90 release of RISC6000
Date: 13 Nov 90 13:46:14 GMT
X-Clever-Slogan: Recycle or Die.
To:       unix-wizards at sem.brl.mil

In article <5274 at basecamp.UUCP> jsg at basecamp.UUCP (JS Goldlin) writes:
>I am running the original golden release (july '90) on the RISC6000 &
>experiencing numerous problems:

the original "golden release" was 9021F, a june release.  if you are
running on a july release it would be PTF 3001 (or 2001).

>	3) Has anybody out there loaded any of the update releases for the
>	   RISC6000?  Are they worth the effort at this time?

if you have july AIX V3.1, you already have loaded an update.  some
of the problems you describe sound familiar in older releases.  give
your support team a call and they will tell you if those problems
have been corrected.

>Please mail any responses to the following net address
>and I will post any useful information.

you really need to contact your IBM support team.  the net is a
wonderful resource for some things, but this is not one of them.
--
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh at rpp386.cactus.org
"SCCS, the source motel!  Programs check in and never check out!"
		-- Ken Thompson

-----------------------------

From: Jim Hudgens <hudgens at sun13.scri.fsu.edu>
Subject: Re: Problems with July 90 release of RISC6000
Date: 13 Nov 90 15:41:57 GMT
Sender: hudgens at sun13.scri.fsu.edu
Followup-To: comp.unix.aix
To:       unix-wizards at sem.brl.mil




In article <5274 at basecamp.UUCP> jsg at basecamp.UUCP (JS Goldlin) writes:
>   1) First and foremost is a system crash with the message "Data
>      Storage Proc - Interrupt" when X is running along with a data
>      communications product.  Anybody else having problems
>      running other products with X?

    We complained about this, and sent in a few crash dumps.  One
machine crashed 6-8 times very sporadically over a period of a few
months.  The person I spoke to asked if there was large NFS mounted
filesystems on the machine having this problem.  There was in this
case and they sent us a patched /etc/nfs.ext (I think) file, and we
haven't had a recurrence of this problem.  Not sure if this patch was
folded into the new releases.