Date: Thu, 3 Jan 2008 08:45:52 -0500 From: Robert Huff <roberthuff@rcn.com> To: "=?ISO-8859-1?Q?Fernando_Apestegu=EDa?=" <fernando.apesteguia@gmail.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Porting from linux to FreeBSD (procfs question) Message-ID: <18300.59152.910366.274124@jerusalem.litteratus.org> In-Reply-To: <1bd550a00801030514i5007c67t509e05f08c820dd@mail.gmail.com> References: <1bd550a00801030514i5007c67t509e05f08c820dd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=?ISO-8859-1?Q?Fernando_Apestegu=EDa?= writes: > First of all, Happy New Year. And to you, > The application I want to port, makes an extensive use of the > procfs in Linux. It gathers a lot of information from those files > (cpuinfo, meminfo, devices, filesystems, modules, etc...) > > As I know, FreeBSD has some kind of procfs but more limited in > terms of information. My questions is how should I proceed now? I > see two options. > > 1 - Try to rely the porting on the compatibility procfs from FreeBSD > 2 - Do the things in a completely different way (which one is this? > Invoking sysctl system call?) As I understand it, use (2). Use of FreeBSD procfs is possible, but heavily discouraged due to known security issues. Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18300.59152.910366.274124>