Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Dec 2017 15:47:41 -0800
From:      Doug Hardie <bc979@lafn.org>
To:        FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   Re: Of LSOF
Message-ID:  <E356D2DC-BE3F-47B7-9570-98173A456BDA@mail.sermon-archive.info>
In-Reply-To: <alpine.BSF.2.21.1712280806320.64029@aneurin.horsfall.org>
References:  <alpine.BSF.2.21.1712271008040.27626@aneurin.horsfall.org> <4DB6D455-3F50-4AC9-83A4-0AFD06B6058C@FreeBSD.org> <alpine.BSF.2.21.1712271111260.27626@aneurin.horsfall.org> <CAN6yY1uW1oiVFAesocuszWcoRYYYWTLucqzvFuq4nOqgxfty7Q@mail.gmail.com> <alpine.BSF.2.21.1712280806320.64029@aneurin.horsfall.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> On 27 December 2017, at 13:26, Dave Horsfall <dave@horsfall.org> =
wrote:
>=20
> On Tue, 26 Dec 2017, Kevin Oberman wrote:
>=20
>> [...] Putting header files into the port is a non-starter as they =
MUST match the kernel on which lsof is built. I added lsof to =
PORTS_MODULES so it is rebuilt with any new kernel on my stable system =
and on one release system so I can use that package to install elsewhere =
rather then use the repo package.
>=20
> Good point; thanks.  "lsof" is a superb tool, BTW...
>=20
>> Now that 10.3 is EOL I would expect that the package built for =
10-STABLE would be built on 10.4-RELEASE, but I don't know for sure. It =
should be and the next quarterly should be 10.4 based, too.
>=20
> OK.
>=20
> The history is that I used to build from ports because the then-boss =
did, and I didn't even know about pre-built packages.  Then, one day, =
Ruby needed to be rebuilt, which promptly blew away /tmp i.e. swap...  =
I'm a big fan of TMPFS; I had it on the old BSDi box (where it was =
"mfs"), and even my old CP/M box (where it was "M:").

Why not add losf to the base?  Its a useful tool like ping, traceroute =
etc.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E356D2DC-BE3F-47B7-9570-98173A456BDA>