From owner-freebsd-current Fri Jun 23 12:50:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 4302737B89C; Fri, 23 Jun 2000 12:50:30 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id PAA23290; Fri, 23 Jun 2000 15:50:28 -0400 (EDT) Message-ID: <20000623155028.B18588@netmonger.net> Date: Fri, 23 Jun 2000 15:50:28 -0400 From: Christopher Masto To: Shawn Halpenny , Maxim Sobolev Cc: gnome-list@gnome.org, current@FreeBSD.ORG Subject: Re: Gnome INSANE shared memory usage References: <20000623131006.A10060@netmonger.net> <39539CB7.FCB177A0@FreeBSD.org> <20000623143041.A27140@cs163.humb.nt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <20000623143041.A27140@cs163.humb.nt.com>; from Shawn Halpenny on Fri, Jun 23, 2000 at 02:30:42PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 23, 2000 at 02:30:42PM -0400, Shawn Halpenny wrote: > I have not had any of the problems he's describing. I have never modified > my shared memory settings in my kernel config either. If the problem is > indeed Xfree 4.0, then I guess it must be a driver issue (I'm using > the neomagic driver). I think you may have a point there. While trying to find out whether XFree86 had an option to disable the MIT-SHM extension (it doesn't as far as I could tell - I ended up editing the binary and NOPping it out) I noticed that some of the code seems to be in the hardware driver area. I'm using a dual-headed configuration with a Voodoo 3 and a Number Nine (S3 ViRGE VX). -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message