Search results

What you did is correct. The maintainer-approval+ on the approved patch shows the PR is ready. When it either gets looked at by a committer or marked as maintainer approved it will show up in the pool of ready to go PRs. I just committed it. Unfortunately there is 1927 open PRs as of closing...

If you plan to use textproc/elasticsearch2 I found that would not start without a loopback device. So I switched my testing jail to a VIMAGE jail. There may be a configuration option that prevents the need for this if VIMAGE is an issue since it's not available by default. However, in my...

The same question recently came up on the freebsd-net mailing list (see https://lists.FreeBSD.org/pipermail/freebsd-net/2016-January/044272.html). The end was patches to implement the feature are welcome.

I noticed reading the daily commit message that another ext4 related read panic got fixed today in 205938. I CC'd that committer to see if he can offer any extra insight.

Yes. Do keep in mind what phoenix mentioned. In my example this is my desktop with a new 1/3 full pool and I mainly cared about a stress test for damaged disks while shipping. Enough for me. Not enough if you are putting your company's bottom line on the line.

Yes. Fail2ban uses /var/db/fail2ban/fail2ban.sqlite3 by default to store which IP addresses should be banned and just calls pfctl to ban each address.

Hello. An output of what the failure is would be helpful. When it comes to shell scripting the -x flag (see sh) can be very helpful if not a bit noisy at first look. So sh -x /usr/local/etc/rc.d/<yourscript> start will give some clues at what the issue is. Also, I notice you are rolling some...

I've done several repeated scrubs after moving data from older disks on my desktop to newer disks. Between the re-sliver to writes to each new disk as I replaced one by one and 2 or 3 scrubs afterwards I was satisfied I didn't see any early symptoms of disk failure. There's probably a more...

https://bits.debian.org/2015/12/mourning-ian-murdock.html A worthwhile mention here for our brothers and sisters in the wider open source community. Debian's founder has recently passed away.

The general rule of thumb is if the option doesn't introduce any extra dependencies and/or is useful to most of its end users than the option should be on. It's worth asking the maintainer.

The information is stored in the annotations for the package. You can see it with pkg info <packagename>. The pkg-query can be used to get it for all packages. Something like pkg query 'Package %n-%v installed from %R' would do.

No, the options are compiled in during the build process so they cannot be changed through the package manager.

A netstat -n -p tcp and netstat -s -p tcp could be helpful here when you next see the error. A pfctl -si would also add some context when this happens.

From /usr/src/Makefile (https://svnweb.FreeBSD.org/base/head/Makefile?view=markup#l59) It would take a while, days not hours. This is probably the territory to just crossbuild on a faster amd64 host and mount it's /usr/obj from the Raspberry. I haven't looked into the syntax on that but it...

Correct. The +MANIFEST is one of the files included in a package that is installed via pkg install <package>. This has nothing to do with the source code of the FreeBSD base system that belongs in /usr/src. Remove all the files in /usr/src and follow the steps above to get the system source code.

There is no +MANIFEST in /usr/src. If you didn't select the src option to extract the src.txz during the installation you can either get it now from http://ftp.FreeBSD.org/pub/FreeBSD/releases/amd64/10.2-RELEASE/. Alternately, you can get it via Subversion via svnlite checkout...

It looks like the version we have in ports is the most current one. See if you can file a bug at http://pcb.geda-project.org/bugs.html to get the issue fixed. If it's fixed without a new upstream release we can potentially apply the patch to the port until a new release comes out.

PC-BSD uses pkg quite differently and uses boot environments and does updates as a full download/reinstall of all packages. The best source of information is going to be through PC-BSD forums on this topic.

Did you get everything you needed from the mailing list thread? (https://lists.FreeBSD.org/pipermail/freebsd-net/2015-December/044160.html)

The jailbreak referenced in the article was a kernel issue. I would advise reading the series of articles regarding the issue. http://cturt.github.io/ps4.html http://cturt.github.io/ps4-2.html http://cturt.github.io/ps4-3.html It was resolved months ago in SA-15:21...