I dont know mate! I havent checked TBH :)

Just wondering since Snort suffers from it.

Just an update - switching to a newer Xen 4.3 dom0 (Fedora 20) still has the same issue.

Patching xenstore.c using the above patch fixes the issue.

I do not think it really matters in pfSense builder case where you adopt git with FreeBSD or not.
Our patches apply to FreeBSD repo be it SVN/GIT/whatever.

Nowdays you can clone the freebsd git repo from github for the builder.
I do not see anything here related to git+freebsd.

It might be just a question of where the anchor is setuped.
If you move the relayd anchor below nat rules it would work as expected.

tnx.
i runed ./set_version.sh RELENG_2_1
but.i saw this error.
.
.
.
/usr/pfSensesrc/src/system.rej
/usr/pfSensesrc/src/passwd.rej

######################
sometime went wrong,check errors
######################
press enter to continue.
terminated!!
please help me.

We don't test with any "smaller" kernels, so only what we have is guaranteed to work.

That said, any drivers removed could be switched to modules and it might come out OK. Maybe.

For the binaries – yes, a pull request to put the port files into the tools tree is what is required.

The the pfSense package code, a pull request in the packages repository is required.

http://forum.pfsense.org/index.php/topic,68865.0.html

Yep, and now you can see where the .mtree file is and how it sets the permissions (the last line)

Yes.

Thanks for the answer!

Yes this is on an ALIX.

Yes it works in my case too.

OK I'll try that, thanks.

I already thougt of making a package for it, but the product is not ready yet.

No it's intentional but it's not controlled in the source by the sysctl, but the "conscontrol mute [on|off]" command, notably it's run in /etc/rc and other places via the mute_kernel_msgs() / unmute_kernel_msgs()  function in /etc/inc/util.inc

no flexibility