On Oct 1, 2011, at 07:12, Doug Barton wrote:
On 09/30/2011 21:10, Mike Brown wrote:
Eitan Adler wrote:
do I reboot for this one, or not?
The kernel is changed, so yes.
Thanks. I had guessed a reboot was needed, but the advisory only mentioned a
reboot in the context of building the
On Dec 11, 2010, at 17:03, Michael Scheidell wrote:
Probably.
does everyone put 32 bit compatibility libraries in their amd64 builds?
__
Never, unless running cosed source software. It seems to triple your
attack surface area.
than the answer is no' you would not want an i386
Your uname -a will say you're running -STABLE, not -RELEASE-something. This is
a result of using source upgrades to anything but RELENG_6_X in the past.
Which, in turn, is why freebsd-update fails.
Move /usr/bin/uname out of the way, create a shell script like so:
---
#!/bin/sh
On 1. okt. 2009, at 10.59, Tom Evans wrote:
On Thu, 2009-10-01 at 02:40 +0200, Thomas Rasmussen wrote:
Martin Turgeon wrote:
Hi list!
We tested mod_antiloris 0.4 and found it quite efficient, but before
putting it in production, we would like to hear some feedback from
freebsd users. We are
On 11. mars. 2009, at 21.59, Ed Sykes wrote:
I am essentially asking the same question that Eirik Overby asked a
couple of years ago. Is anyone aware of PCI-X/PCIe hardware
security modules that are supported on FreeBSD? I have not seen any
on the FreeBSD hardware compatibility lists.
On Nov 23, 2008, at 18:52, Pieter de Boer wrote:
Eirik Øverby wrote:
I have a FreeBSD based firewall (pfsense) and, behind it, a few
dozen FreeBSD servers. Now we're required to run external security
scans (nessus++) on some of the hosts, and they constantly come
back with a high
Hi all,
I have a FreeBSD based firewall (pfsense) and, behind it, a few dozen
FreeBSD servers. Now we're required to run external security scans
(nessus++) on some of the hosts, and they constantly come back with a
high or medium severity problem: The host replies to TCP packets
with
