Re: Of LSOF

[Adam Vande More]

On Wed, Dec 27, 2017 at 6:59 PM, Dave Horsfall  wrote:

> On Wed, 27 Dec 2017, Kevin Oberman wrote:
>
> fstat(1) does much of what lsof does.
>>
>
> I'll be damned; so it does...  Thanks!
>

As well as procstat -f


-- 
Adam
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Of LSOF

[Larry Rosenman]

On Thu, Dec 28, 2017 at 11:59:26AM +1100, Dave Horsfall wrote:
> On Wed, 27 Dec 2017, Kevin Oberman wrote:
> 
> > fstat(1) does much of what lsof does.
> 
> I'll be damned; so it does...  Thanks!

As maintainer of sysutils/lsof, the major thing is cross-platform compatibility.
That said, Vic Abell (Author of lsof) has retired from Purdue, and is slowing
down on the releases.  

We'll see what happens in 2018, and I'll keep lsof up to date with the releases
from Vic. 


-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106


signature.asc
Description: PGP signature

Re: Of LSOF

[Dave Horsfall]

On Wed, 27 Dec 2017, Kevin Oberman wrote:


fstat(1) does much of what lsof does.


I'll be damned; so it does...  Thanks!

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Of LSOF

[Doug Hardie]

> On 27 December 2017, at 16:05, Kevin Oberman  wrote:
> 
> On Wed, Dec 27, 2017 at 3:47 PM, Doug Hardie  wrote:
> > On 27 December 2017, at 13:26, Dave Horsfall  wrote:
> >
> > On Tue, 26 Dec 2017, Kevin Oberman wrote:
> >
> >> [...] 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.
> >
> > Good point; thanks.  "lsof" is a superb tool, BTW...
> >
> >> 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.
> >
> > OK.
> >
> > 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.
> 
> While I can't say the exact reason, though I'd guess that it might be a 
> licensing issue, though the license is very similar to a BSD license. Another 
> possible issue is that lsof is frequently updated and that would mean that 
> the version in FreeBSD base would get fairly old before EOL.
> 
> fstat(1) does much of what lsof does.  
> 

I can't speak to the licensing issue as I have never looked into that.  
However, the frequently updated issue doesn't seem to be an issue for openssl.  
The base version is sometimes old, and the port versions are newer.  At least 
lsof would be a working version for those who only use packages.  If you need 
the newer features, then you would need to install the port.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Of LSOF

[Kevin Oberman]

On Wed, Dec 27, 2017 at 3:47 PM, Doug Hardie  wrote:

> > On 27 December 2017, at 13:26, Dave Horsfall  wrote:
> >
> > On Tue, 26 Dec 2017, Kevin Oberman wrote:
> >
> >> [...] 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.
> >
> > Good point; thanks.  "lsof" is a superb tool, BTW...
> >
> >> 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.
> >
> > OK.
> >
> > 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.


While I can't say the exact reason, though I'd guess that it might be a
licensing issue, though the license is very similar to a BSD license.
Another possible issue is that lsof is frequently updated and that would
mean that the version in FreeBSD base would get fairly old before EOL.

fstat(1) does much of what lsof does.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Of LSOF

[Doug Hardie]

> On 27 December 2017, at 13:26, Dave Horsfall  wrote:
> 
> On Tue, 26 Dec 2017, Kevin Oberman wrote:
> 
>> [...] 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.
> 
> Good point; thanks.  "lsof" is a superb tool, BTW...
> 
>> 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.
> 
> OK.
> 
> 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.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: License and adopting software

[Sid]

I think we should consider gradually using the Clear BSD license whenever 
someone decides to make an alternate, where a GPL licensed code was inserted on 
top of less restrictive licenses.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Of LSOF

[Dave Horsfall]

On Tue, 26 Dec 2017, Kevin Oberman wrote:

[...] 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.


Good point; thanks.  "lsof" is a superb tool, BTW...

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.


OK.

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:").


--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Should building for different SIMD levels be supported using flavors?

[Jan Beich]

(Resent to ports@ because, apparently, I wasn't subscribed to the list anymore)

Yuri  writes:

> Some projects rely on SIMD to perform computations. Sometimes,
> utilizing specific SIMD instructions can result in 10 times better
> performance, so it is important for the ports system to properly
> support SIMD. There are some projects that do automatic run-time SIMD
> detection, like Embree, but there are many that do not.

"10x times better performance" usually requires more than just passing
-msse* or -march=native without underlying code doing anything to take
advantage of it. Do you expect auto-vectorization to be that good?
Projects that use SSE 4.1 or AVX without runtime detections are rare
because they'd risk to shun away users if binaries are prebuilt on
modern hardware.

> I proposed the solution for this using flavors, see the proposed port
> science/g2o: https://reviews.freebsd.org/D13610

What in there actually requires -msse*? I can't find any __SSE*__ blocks
or #include <*intrin.h> while CMakeLists.txt tries to mimic -march=native 
by parsing /proc/cpuinfo then passing -msse* individually. Looks like
a regular violation of

https://www.freebsd.org/doc/en/books/porters-handbook/dads-cflags.html

> It maps SIMD levels into port flavors. So that g2o-sse42 is for SSE42,
> and g2o-nosimd is not using SIMD.

This won't work for ports with consumers until pkg supports a way to
swap dependencies e.g., g2o -> g2o-sse41, ffmpeg -> libav. On Linux
systems this is usually handled by update-alternatives(8).

> Later, the user will to install the flavor corresponding to his
> machine's SIMD support.
>
> Further, ports framework and tools (pkg) should automatically detect
> machine's SIMD, and install the ports with the correct SIMD flavor for
> it.

ABI string is probably where SIMD should be advertised but pkg repo
format, currently, isn't even flexible for ports marked as NO_ARCH.

> How can FreeBSD support SSE then?

For one, Linux i686 assumes SSE2. To mimic on FreeBSD i386 try
adding the following to make.conf(5)

  CPUTYPE?= pentium4

then in the port use MACHINE_CPU, port options or both e.g.,

  OPTIONS_DEFINE=   SSE2 SSE41 AVX AVX2
  OPTIONS_DEFAULT=  ${MACHINE_CPU:tu}

  SSE2_CONFIGURE_ENABLE=sse2
  ...
  AVX2_CONFIGURE_ENABLE=avx2
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to reinstall pkg(8) itself?

[Kurt Jaeger]

Hi!

> > > You have pkg(8) installed, but want to recompile and reinstall it.
> > > How do you do this?
> > 
> > cd /usr/ports/ports-mgmt/pkg
> > make install
> 
> ===>  Installing for pkg-1.10.3_1
> ===>  Checking if pkg already installed
> ===>   pkg-1.10.3_1 is already installed
>   You may wish to ``make deinstall'' and install this port again
>   by ``make reinstall'' to upgrade it properly.

If it tells you to

make deinstall
make reinstall

then I use that in almost every case and it fixes it. I don't remember
a case where this did not fix it.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Should building for different SIMD levels be supported using flavors?

[Yuri]

Some projects rely on SIMD to perform computations. Sometimes, utilizing 
specific SIMD instructions can result in 10 times better performance, so 
it is important for the ports system to properly support SIMD. There are 
some projects that do automatic run-time SIMD detection, like Embree, 
but there are many that do not.



I proposed the solution for this using flavors, see the proposed port 
science/g2o: https://reviews.freebsd.org/D13610


It maps SIMD levels into port flavors. So that g2o-sse42 is for SSE42, 
and g2o-nosimd is not using SIMD.


Later, the user will to install the flavor corresponding to his 
machine's SIMD support.


Further, ports framework and tools (pkg) should automatically detect 
machine's SIMD, and install the ports with the correct SIMD flavor for it.



It seems to me that this is the right solution, and that flavors fit the 
purpose very well. Flavors are defined as needed for situations when the 
whole project needs to be rebuilt, and in this case it needs to be 
rebuilt because SIMD instructions inside are different.



Sadly, Mathieu disagreed, and asked to "Always build with the lowest 
available instructions."


How can FreeBSD support SSE then? There should be some consistent path 
forward on SIMD support. Just always using the lowest SIMD isn't an answer.



Yuri

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to reinstall pkg(8) itself?

[Eugene Grosbein]

27.12.2017 23:13, Christian Weisgerber пишет:
> Eugene Grosbein:
> 
>>> You have pkg(8) installed, but want to recompile and reinstall it.
>>> How do you do this?
>>
>> Use pkg-static.
> 
> How?

"pkg-static install -f pkg" if you already have newly built local package file
for pkg itself or just "make deinstall install" in the ports-mgmt/pkg directory
to compile it before same move.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to reinstall pkg(8) itself?

[Christian Weisgerber]

Eugene Grosbein:

> > You have pkg(8) installed, but want to recompile and reinstall it.
> > How do you do this?
> 
> Use pkg-static.

How?

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to reinstall pkg(8) itself?

[Christian Weisgerber]

Kurt Jaeger:

> > You have pkg(8) installed, but want to recompile and reinstall it.
> > How do you do this?
> 
> cd /usr/ports/ports-mgmt/pkg
> make install

===>  Installing for pkg-1.10.3_1
===>  Checking if pkg already installed
===>   pkg-1.10.3_1 is already installed
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of pkg
  without deleting it first, set the variable "FORCE_PKG_REGISTER"
  in your environment or the "make install" command line.
*** Error code 1

Stop.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to reinstall pkg(8) itself?

[Eugene Grosbein]

27.12.2017 22:33, Christian Weisgerber пишет:
> You have pkg(8) installed, but want to recompile and reinstall it.
> How do you do this?

Use pkg-static.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to reinstall pkg(8) itself?

[Kurt Jaeger]

Hi!

> You have pkg(8) installed, but want to recompile and reinstall it.
> How do you do this?
> 
> portmaster manages to do this somehow, but how would you do it
> manually?

cd /usr/ports/ports-mgmt/pkg
make install

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

How to reinstall pkg(8) itself?

[Christian Weisgerber]

You have pkg(8) installed, but want to recompile and reinstall it.
How do you do this?

portmaster manages to do this somehow, but how would you do it
manually?

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Of LSOF

[Julian Elischer]

On 27/12/17 7:14 am, Dave Horsfall wrote:

aneurin# freebsd-version
10.4-RELEASE-p5
aneurin# which lsof
/usr/local/sbin/lsof
aneurin# lsof > /dev/null
lsof: WARNING: compiled for FreeBSD release 10.3-RELEASE-p22; this 
is 10.4-RELEASE-p3.

aneurin# pkg upgrade lsof
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
aneurin#

Building it from ports updated it (as I probably did before), but 
should not the binary have been updated?  Or are binaries not 
available for all ports (I guess)?


there is no per release active branch for pkgs, just one for the whole 
branch.


Because we keep binary compatibility we compile for the oldest 
supported branch. Maybe we should change the test to be less specific, 
but lsof breaks a lot of rules so maybe it matters more than in other 
programs.



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: gogs-0.11.34_1 rc.d script status does not work correctly

[Dmitri Goutnik]

Hi Douglas,

This should be fixed by
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224614

Regards,
Dmitri

On Tue, Dec 26, 2017 at 8:25 PM, Douglas Thrift 
wrote:

> Hello,
>
> I just noticed that the gogs rc.d script's status subcommand does not
> work, when I have verified that gogs is actually running, it just says:
>
> gogs is not running.
>
> It seems to stop and restart just fine though.
> --
> Douglas William Thrift
> 
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: rebuilding apache24 and php70

[@lbutlr]

On 26 Dec 2017, at 14:24, Johan Hendriks  wrote:
> 
> I run my roundcube through php-fpm on FreeBSD 11.1 and it works pretty well.
> So there should be no show stoppers. Do not forget to select fpm in the
> lang/php{56,70,71,72} port

thanks. I did get php70 finally installed and seems to be working (I can load 
postfixadmin), but now get to figure out why I can't login! :)

It's always something.

I had to completely remove all of php70 (pkg delete -f php70*) and rebuild.

And of course make some edits to the http.conf since php-fpm is far more fiddly 
than mod_php was.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
games/connectagram  | 1.2.5   | 1.2.6
+-+
games/gottet| 1.1.3   | 1.1.5
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How do I recover a lost ports directory with svn?

[Thomas Mueller]

from Lowell Gilbert:

> That's fair. The help messages are enough for me to work out syntax
> without going back to first principles, but, yes, that's pretty much
> what I expect from a man page.

> > Personally, I would much prefer a real man page.

> Funny you should mention that. Some years back, I bashed out a script
> that turned the svn help into a browsable document. I can't find that
> tool in a quick search of my backups, and I don't even remember whether
> it converted things into HTML or info files. [As an emacs user, info is
> roughly equivalent to HTML for such things; I have no idea how info can
> be useful if you aren't using emacs to browse the docs.]

> But the point is that I found the cross-link information fairly easy to
> parse. And once you can do that, you can turn it into anything useful.

I wish GNU would switch away from info in favor of man or html!

When I ran Linux Slackware 13.0, Konqueror in KDE had a good info viewer.

Otherwise, there is misc/pinfo in ports.


Tom

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"