From owner-freebsd-ports@FreeBSD.ORG Tue Sep 27 20:42:11 2005 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1299916A440; Tue, 27 Sep 2005 20:42:11 +0000 (GMT) (envelope-from phil@cryer.us) Received: from cryer.us (dsl093-192-243.stl1.dsl.speakeasy.net [66.93.192.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F98743D48; Tue, 27 Sep 2005 20:42:10 +0000 (GMT) (envelope-from phil@cryer.us) Received: from phil [199.249.176.251] by cryer.us with NetMail ModWeb Module; Tue, 27 Sep 2005 15:43:56 -0500 From: "Phil Cryer" To: kris@obsecurity.org Date: Tue, 27 Sep 2005 15:43:56 -0500 X-Mailer: NetMail ModWeb Module X-Sender: phil X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Message-ID: <1127853836.8699c9cphil@cryer.us> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: ports@FreeBSD.org, ale@FreeBSD.org Subject: Re: Re: How to deal with a port that uses /proc in FreeBSD 6.0? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: phil@cryer.us List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2005 20:42:11 -0000 =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=20 >>'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 Thanks, currently I just manually mount /proc with: echo "proc /proc procfs rw 0 0" >> /etc/fstab; mount /proc anytime I need to debug some code, and that works, I was just wondering if = there was any sort of better/long term solution. A current open source p= roject I'm working is written in C, and there's plenty to debug since the= y devel on Linux only, so I have to run gdb and the like rather often. J= ust wondering if this is the best way to deal with this or if there's som= e "official" way that I don't know about. Thanks again. P Kris "You teach best what you most need to learn." - Richard Bach