Mateusz Piotrowski

I believe that GNU install's `-D` is not portable. See [GNU install](http://man7.org/linux/man-pages/man1/install.1.html) and [FreeBSD install](https://www.freebsd.org/cgi/man.cgi?install) manuals, for example.

I think that I'd go for `mkdir -p` and `install -m XXX`. That seems to be fairly standard across different operating systems. To be extra careful maybe we could go...

@swills What's the status? I was wondering recently as well if I can run this wonderful piece of software on FreeBSD.

Hi! I’d like to give a bit more insight regrading shells from the FreeBSD project point of view. Currently, FreeBSD ships two shells, [sh(1)](https://www.freebsd.org/cgi/man.cgi?query=sh&sektion=1&manpath=FreeBSD+12.2-RELEASE+and+Ports) and [tcsh(1)](https://www.freebsd.org/cgi/man.cgi?query=tcsh&sektion=1&manpath=FreeBSD+12.2-RELEASE+and+Ports). sh is meant to...

> Hello @0mp and thanks for chiming in. > helloSystem doesn't want to deviate from FreeBSD standards if it can be avoided For example, we don't build our own kernel...

Just a note: as @schmitmd said, you may use `e` to enter the editor in GRUB, you may use `Ctrl-x` to leave the editor and boot with your changes applied.

I am not sure, really. I've not tested in personally; I just wanted to share the good news. I'll let the maintainer about this thread we have here so that...

As per [this ancient commit message][1]: > Use HAVE_AUDIT_SYSCALLS to detect if we are being compiled on a > system that will also use our auditd. If HAVE_AUDIT_SYSCALLS is >...

Heads-up: `herbe` has landed in the FreeBSD Ports Collection: https://cgit.freebsd.org/ports/commit/?id=1b6314a7773b47e18f5da903035bca74a235f35c

There are 2 reasons for it not being available on your system (yet). First, FreeBSD releases default to a quarterly branch for packages. This branch gets updated every 3 months...