From owner-freebsd-questions  Tue Nov  4 12:28:39 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA04924
          for questions-outgoing; Tue, 4 Nov 1997 12:28:39 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA04916
          for <support@FreeBSD.ORG>; Tue, 4 Nov 1997 12:28:35 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id MAA29035;
          Tue, 4 Nov 1997 12:28:32 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Tue, 4 Nov 1997 12:28:32 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
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.971104122812.29009C-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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.

You need to add

options SYSVSHM

to your kernel config & recompile.  That will shut it up.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major