Date: Fri, 17 Dec 1999 10:20:38 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Chuck Robey <chuckr@picnic.mat.net> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: linux /proc and vmware. Message-ID: <20167.945422438@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 16 Dec 1999 22:09:02 EST." <Pine.BSF.4.10.9912162208150.16082-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.10.9912162208150.16082-100000@picnic.mat.net>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20167.945422438>