From owner-freebsd-emulation Tue Feb 1 0:10:33 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from fb02.eng00.mindspring.net (fb02.eng00.mindspring.net [207.69.229.20]) by builder.freebsd.org (Postfix) with ESMTP id 666B53D47 for ; Tue, 1 Feb 2000 00:10:30 -0800 (PST) Received: from mindspring.com (user-2ivec69.dialup.mindspring.com [165.247.48.201]) by fb02.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA12131 for ; Mon, 31 Jan 2000 21:34:36 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id VAA00753 for freebsd-emulation@freebsd.org; Mon, 31 Jan 2000 21:33:16 -0500 (EST) (envelope-from vsilyaev) Date: Mon, 31 Jan 2000 21:32:22 -0500 From: "Vladimir N. Silyaev" To: freebsd-emulation@FreeBSD.ORG Subject: Re: /proc/meminfo problem ... Message-ID: <20000131213222.A701@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Mailer: Mutt 1.0i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Okay, I have rtc installed and loaded ... linuxprocfs installed and loaded > ... /usr/compat/linux/proc/meminfo even reports accurately: [skipped] > But when I run vmware, I get: > Error opening /proc/meminfo: grep: /proc/meminfo: No such file or directory 'grep ...' it's your part or for vmware log? To test linuxprocfs you can just launch linux sh (bash) and to do something like: cat /proc/meminfo > This is as a regular user ... as root, it appears to work fine though ... Try to launch vmware with enabled kernel tracing (man ktrace) and find what it's happened in your case. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message