On May 29, 2009, at 11:01 AM, Mel Flynn wrote:
On Friday 29 May 2009 18:19:52 Steven Schlansker wrote:
[ste...@gateway2:~]% sudo /etc/rc.d/pfsync start
/etc/rc.d/pfsync: WARNING: pfsync(4) must be statically compiled in
Is pfsync not in GENERIC? I checked the amd64 config file and indeed
it does not show up, however pf and pflog are not there either but
usable in the base system, so I am not positive that pfsync being
missing is therefore conclusive.
I would like to if at all possible use GENERIC so that I can take
advantage of freebsd-update etc. Is there some way to get this all
running without recompiling the kernel?
No, the error message is clear. pfsync cannot currently be loaded as
module and it's not in GENERIC. The same goes for altq. See sys/conf/
Ah, now I get it. I'm used to the Linux way of configuring modules
where if a device is a module, it still appears in the configuration
file. So I was interpreting the missing "pf" and "pflog" entries not
as "built as a module" but as "missing, why can I still use them?"
And not to be argumentative, but sys/conf/NOTES does not really
provide any information. The only comment explains what the device
does, not why it wouldn't be enabled in GENERIC. Is there any reason
it could not be? (For those of us who want to use freebsd-update, for
By digging around on the internet it seems that the problem arises
from the use of multicast protocols (ref: http://lists.freebsd.org/pipermail/freebsd-pf/2005-October/001521.html)
. pfsync allows the use of unicast as well - would it be feasible to
have a modular version that only supports unicast (via syncpeer)
There's not been much of a discussion about this since 2005, it seems.
I'm curious as to that the prevailing opinion is.
FYI: On -current it's still not possible to load as a module.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"