[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FreeBSD 5.3 setup help

From: David Ayers
Subject: Re: FreeBSD 5.3 setup help
Date: Wed, 02 Feb 2005 14:47:53 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910

Chris Vetter wrote:


You've made you point clear that you dislike the usage of procfs. The question remains, do we have a /dependency/ that leads to certain features of the API not functioning on FreeBSD?


I never said the API wouldn't work on FreeBSD.

I said, even though there is no /proc on FreeBSD 5.x, you can always
use --disable-proc (or something similar) on 'configure' since BSD
does have libkvm.

The problem with NSProcessInfo is, that if libkvm does NOT exist, and
tries /proc instead, it most likely will fail, because NSProcessInfo
tries to open and read file '/proc/<pid>/cmdline' which may well exist
on Linux, but does not necessarily exist on other systems. Or if it does,
it does not necessarily have the expected information.

So what is the "standard" alternative you are suggesting? For which platforms would it be valid? What assertions should we insert either in NSProcessInfo or in configure to insure that

On a side note regarding NSProcessInfo+load:
The arguments passed to kvm_open() differ from what Solaris' kvm_open()
expects and kvm_getprocs() doesn't even exist on Solaris. Contrary to
what the opening comment states about being compatible.

Indeed the comment says "supposedly backward compatible" so I guess who ever added the comment never claimed to have first hand knowledge. I'll be glad to correct that comment, but I hope this is not the final result of this issue.

Even if you're not going to propose a patch it would be nice to have some concrete idea of what you believe the better alternative would be. Maybe you're suggesting we should use the fake-main hack on every platform. But that also has drawbacks.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]