From owner-freebsd-ports  Wed Jul  9 19:24:09 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA00220
          for ports-outgoing; Wed, 9 Jul 1997 19:24:09 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca13-05.ix.netcom.com [204.32.168.37])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA00214
          for <freebsd-ports@FreeBSD.ORG>; Wed, 9 Jul 1997 19:24:06 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id TAA16313; Wed, 9 Jul 1997 19:23:56 -0700 (PDT)
Date: Wed, 9 Jul 1997 19:23:56 -0700 (PDT)
Message-Id: <199707100223.TAA16313@silvia.HIP.Berkeley.EDU>
To: chuckr@glue.umd.edu
CC: avenirint@hol.fr, freebsd-ports@FreeBSD.ORG
In-reply-to: <Pine.BSF.3.96.970709201757.4768O-100000@Journey2.mat.net> (message from Chuck Robey on Wed, 9 Jul 1997 20:20:36 -0400 (EDT))
Subject: Re: Compatibility between releases of freeBSD ports
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * We've never had a report like this, not a single one.  Since we don't have
 * a port of the xcannon game, this makes me doubly skeptical about your
 * claim.  Could you maybe be just a little more complete in describing where
 * you got the software and what you did that caused all that lossage?

Furthermore, if this is a bug, it is in the kernel, not the xcannon
program (or whatever game you tried to run).  Unless that program is a
serious trojan horse, these kind of situations are caused by the
system crashing catastrophically at exactly the moment you tried to
run the game.

Satoshi