From owner-freebsd-current Fri Dec 17 1:21:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id F2D9D14EB1; Fri, 17 Dec 1999 01:21:13 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA20169; Fri, 17 Dec 1999 10:20:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: Andrew Gallatin , Julian Elischer , current@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: linux /proc and vmware. In-reply-to: Your message of "Thu, 16 Dec 1999 22:09:02 EST." Date: Fri, 17 Dec 1999 10:20:38 +0100 Message-ID: <20167.945422438@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Rob ey writes: >> I'd also like to see us have enough information in /proc to be able to >> divorce ps & friends from libkvm. It would be nice to be able to have >> most tools continue to work if you have mismatched kernels & >> userlands. Such transparancy can be made with with either /proc or sysctl. >I thought the work was going in precisely the opposite way, so that jail >could work without any visibility to /proc. Well, if you want to run linux binaries which insist on peeking into /proc you will need to mount a procfs there. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message