From owner-freebsd-questions  Tue Nov  4 09:40:15 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA23971
          for questions-outgoing; Tue, 4 Nov 1997 09:40:15 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from iconoclastic.com (dyna199.dialup.dti.net [206.252.158.45])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA23962
          for <support@FreeBSD.ORG>; Tue, 4 Nov 1997 09:40:09 -0800 (PST)
          (envelope-from spork@dti.net)
Received: from localhost (spork@localhost)
	by iconoclastic.com (8.8.5/8.8.5) with SMTP id MAA00265;
	Tue, 4 Nov 1997 12:39:01 GMT
X-Authentication-Warning: iconoclastic.com: spork owned process doing -bs
Date: Tue, 4 Nov 1997 12:39:00 +0000 (GMT)
From: sporkl <spork@dti.net>
X-Sender: spork@iconoclastic.com
Reply-To: sporkl@dti.net
To: Parker Brown <phbrown@gte.net>
cc: support@FreeBSD.ORG
Subject: Re: Cleaning up wierd system messages to root
In-Reply-To: <345EAD68.262@gte.net>
Message-ID: <Pine.BSF.3.96.971104123831.257A-100000@iconoclastic.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hey.

	Did you include "option SYSVSHM" in your kernel config?



 -Spike Gronim
  sporkl@dti.net

	"Tradition is the chastity belt of the mind" 



On Mon, 3 Nov 1997, Parker Brown wrote:

> This could conceivably (that doesn't look right!) be an XFree86
> question, but I don't think so.
> When I bring FreeBSD up, I usually login as root on console 1, then as a
> regular user on console 2 (<alt><F2>) and use the system there without
> worrying about a global wipeout.  Also, just to monitor the efficiency
> of the system, I usually run systat -vmstat as root.  Anyway,  after
> using startx to use X-windows as a regular user, error messages
> something like "/kernel: cmd XF86-SVGA --- tried to use non-present
> SYSVSHM" show up on root's screen.  That blow's systat's whole screen
> (ok, no biggie) but I'm enough of a perfectionist to want to know what's
> wrong.  SYSVSHM refers to System V Shared Memory, I guess.  I think this
> only happens with my reconfigured kernel, and I know of nothing that
> I've omitted there.
> 
> Please give jme some suggestions where to look so I can clean my system
> up.
> 
>