From owner-freebsd-questions Mon Nov 3 21:52:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA13583 for questions-outgoing; Mon, 3 Nov 1997 21:52:39 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from Bayou.UH.EDU (jef53313@Bayou.UH.EDU [129.7.1.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA13570 for ; Mon, 3 Nov 1997 21:52:30 -0800 (PST) (envelope-from jef53313@Bayou.UH.EDU) Received: from localhost (jef53313@localhost) by Bayou.UH.EDU (8.8.7/8.8.7) with SMTP id XAA07542; Mon, 3 Nov 1997 23:52:23 -0600 (CST) Date: Mon, 3 Nov 1997 23:52:23 -0600 (CST) From: Jonathan Fosburgh To: Parker Brown cc: support@FreeBSD.ORG Subject: Re: Cleaning up wierd system messages to root In-Reply-To: <345EAD68.262@gte.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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. > I think everything you need can be found in LINT. It seems to have worked for me. Jonathan Fosburgh, wotan@scientist.com , University of Houston Geophysics http://www.geocities.com/vienna/1498 FreeBSD: Turning PCs into Workstations http://www.freebsd.org ******************************************************************************* We shall not cease from exploration, And the end of our exploring shall be to arrive Where we started from, and know the place for the first time. --T.S. Eliot, The Four Quartets *******************************************************************************