Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.gmi.edu!usenet.eel.ufl.edu!news.ultranet.com!news.sprintlink.net!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!purdue!mozo.cc.purdue.edu!vic.cc.purdue.edu!abe From: abe@vic.cc.purdue.edu (Vic Abell) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: kinfo_proc.h and sysctl.h in FreeBSD 2.0 Date: 8 Jun 1995 16:28:31 GMT Organization: Purdue University Lines: 31 Message-ID: <3r78ff$dd9@mozo.cc.purdue.edu> References: <3r47rn$5oe@mozo.cc.purdue.edu> <3r6lso$sp3@bonnie.tcd-dresden.de> NNTP-Posting-Host: vic.cc.purdue.edu In article <3r6lso$sp3@bonnie.tcd-dresden.de>, j@narcisa.sax.de (J Wunsch) writes: > Vic Abell <abe@vic.cc.purdue.edu> wrote: > >I'm a quondam user of FreeBSD who accesses it to do development > >and testing of a multi-dialect Unix application, lsof. > > lsof should be in the ``ports collection'', so you might wish to have > a look at what the port's maintainer had to change in order to get it > work on FreeBSD 2.0. Since the ports are stored as deltas against the > official version, it should not be a very big deal for you to find > about this. Perhaps I didn't make myself clear. I am the lsof developer and maintainer. I did both the 1.x and 2.x ports of lsof to FreeBSD. As far as I know, lsof is not in a ``ports collection,'' but, since it is a multi-dialect port, is distributed via anonymous ftp from its home site, vic.cc.purdue.edu, and a number of well-known mirrors, including coast.cs.purdue.edu, ftp.auscert.org.au, ftp.cert.dfn.de, ftp.sunet.se, wuarchive.wustl.edu, and about 10 others. I certainly don't object of the ``ports collection'' maintainer wants to mirror vic.cc.purdue.edu, too, but the lsof distribution changes too rapidly for a static copy to have much value. Back to the original question; after looking at NetBSD 1.0a in pursuit of the answer, I now suspect that FreeBSD's </sys/kinfo*.h> header files are being deprecated in favor of the <kvm.h> and <sys/sysctl.h> combination. Is there anyone familiar with FreeBSD 2.0.5 who can conform that? (I don't yet have access to a 2.0.5 system.) Vic Abell, lsof author