Date: Tue, 27 Sep 2005 13:27:50 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Phil Cryer <phil@cryer.us> Cc: ports@FreeBSD.org, ale@FreeBSD.org Subject: Re: How to deal with a port that uses /proc in FreeBSD 6.0? Message-ID: <20050927172750.GA63138@xor.obsecurity.org> In-Reply-To: <1127838504.869949cphil@cryer.us> References: <1127838504.869949cphil@cryer.us>
next in thread | previous in thread | raw e-mail | index | archive | help
--opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 27, 2005 at 11:28:24AM -0500, Phil Cryer wrote: > Anyone have any idea on this? Basically writing a port that uses /proc (= since all the dev work is done in Linux) but doesn't debug properly since t= here is no /proc in FreeBDS 6.x+ =20 >=20 > http://fak3r.com/articles/2005/09/26/deprecated-proc-and-c-debugging >=20 > Is there a way to use sysctl in place of it? If so, how can you 'symlink= ' an app to use it instead of /proc? There is /proc, it just doesn't get mounted by default. If your software really really needs it and you can't patch it to obtain the information another way (it sounds like you aren't experienced enough to do this, but maybe you could talk to the developers), you can look at what other ports like valgrind do to check and report a missing procfs. Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDOYEWWry0BWjoQKURAg+eAKC7hJmzNMrphYH3LVbZFf3IRAcBAwCgjI09 JujhPkrL8v5XJXmamEtIvfI= =T7UJ -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050927172750.GA63138>