From owner-freebsd-hackers  Mon Jul  7 21:52:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA27654
          for hackers-outgoing; Mon, 7 Jul 1997 21:52:34 -0700 (PDT)
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27646
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 7 Jul 1997 21:52:31 -0700 (PDT)
Received: from new-world.cs.rice.edu (new-world.cs.rice.edu [128.42.6.103]) by cs.rice.edu (8.8.5/8.7.1) with ESMTP id XAA00257 for <freebsd-hackers@FreeBSD.ORG>; Mon, 7 Jul 1997 23:52:08 -0500 (CDT)
From: "Mark W. Krentel" <krentel@cs.rice.edu>
Received: (from krentel@localhost) by new-world.cs.rice.edu (8.8.5/8.7.3) id XAA13559 for freebsd-hackers@FreeBSD.ORG; Mon, 7 Jul 1997 23:52:26 -0500 (CDT)
Date: Mon, 7 Jul 1997 23:52:26 -0500 (CDT)
Message-Id: <199707080452.XAA13559@new-world.cs.rice.edu>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: no SYSVSHM in GENERIC now..
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I can't remember - why did we take it out?

I don't know, but I recommend putting SYSVSHM, SYSVSEM and SYSVMSG
back into GENERIC.  I've seen things in XFree86 that barf without them.

Mark Krentel
Rice University
krentel@cs.rice.edu