From owner-freebsd-emulation Sun Dec 12 19:33:20 1999 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id BBBBD14D48 for ; Sun, 12 Dec 1999 19:33:18 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ivebjp.dialup.mindspring.com [165.247.46.121]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA28696; Sun, 12 Dec 1999 22:33:16 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id WAA22871; Sun, 12 Dec 1999 22:33:15 -0500 (EST) (envelope-from vsilyaev) Date: Sun, 12 Dec 1999 22:33:14 -0500 From: "Vladimir N. Silyaev" To: Andrew Gallatin Cc: "Vladimir N. Silyaev" , freebsd-emulation@FreeBSD.ORG Subject: Re: vmware questions Message-ID: <19991212223313.A22833@jupiter.delta.ny.us> References: <14420.14744.875394.54896@grasshopper.cs.duke.edu> <19991212204415.A18746@jupiter.delta.ny.us> <14420.22891.749447.645628@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14420.22891.749447.645628@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Sun, Dec 12, 1999 at 09:59:33PM -0500 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Dec 12, 1999 at 09:59:33PM -0500, Andrew Gallatin wrote: > Sounds like it. I wonder if this is vmware's problem, or if it is a > general linux-emu problem.. I have another assumption, may be this is a bug in SCSI CDROM driver, because linux-emu and vmware doesn't have a difference between SCSI and IDE drivers, and SCSI and IDE driver have the same IOCTL interface. > > > > > > I have appended a small patch to linprocfs_misc so that linprocfs > > > reports memory size correctly. > > Really this is patch must be addressed to Pierre Beyssac. > > If you are interested on more correctly work of .../meminfo I have > > just another patch, probably much more correct (probably only one leak > > in swap info). > > Nice. I was wondering to myself why you need sysctl, but then I > realized that you need it for meminfo.mem_shared.. Exactly, not all information exported by sysctl available via global variables (and vice versa). And at all, sysctl is a more common interface. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message