From owner-freebsd-ports  Tue Apr 23 12:32:14 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA28206
          for ports-outgoing; Tue, 23 Apr 1996 12:32:14 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA28195
          for <freebsd-ports@freebsd.org>; Tue, 23 Apr 1996 12:32:09 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id MAA04887; Tue, 23 Apr 1996 12:31:17 -0700 (PDT)
Date: Tue, 23 Apr 1996 12:31:17 -0700 (PDT)
Message-Id: <199604231931.MAA04887@silvia.HIP.Berkeley.EDU>
To: bmc@telebase.com
CC: freebsd-ports@freebsd.org
In-reply-to: <199604231521.LAA01153@telebase.com.> (message from Brian Clapper on Tue, 23 Apr 1996 11:21:09 -0400 (EDT))
Subject: Re: 2.2-960323-SNAP and `top'
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Hopefully I've chosen the right mailing lists to which to send this FYI.

It should have been directed to -ports and -ports only, sending mail
to multiple open lists is unnecessary unless it's an announcement or
something.

 * I installed 2.2-960323-SNAP on my home machine (a 486/66 IDE-disked box)
 * and my work machine (a Pentium/150 SCSI-disked box).  In both cases, once a
 * 2.2 kernel was up and running, top(1) broke.  Every invocation of top
 * produced a seg fault.  Reinstalling the top-3.3 package from the Walnut
 * Creek 2.2-960323-SNAP CD/ROM didn't fix the problem.  Building and
 * installing the top-3.3 port, however, *did* fix it.

It is because the program "top" depends heavily on the kernel you are
running.  The old one was for your old kernel; the one in the CDROM
was probably old too, maybe the time I did a rebuild of top wasn't
close enough to the snap press, sorry.

Satoshi