Hi,
This server is built with Xeon cpu processor, Intel based.
Can FreeBSD 8+ fully compatible with this server like those ordinary
Intel i386 machine?
Thanks
SW
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
Antoine Brodin wrote:
> I am looking at PR 137487, world broken WITHOUT_NETGRAPH.
> Is it reasonable to have MK_NETGRAPH=no enforce MK_ATM=no and MK_BLUETOOTH=no?
> The bluetooth stack is implemented using the netgraph framework. Some
> bluetooth userland tools include netgraph headers or use netg
Hi there,
I am looking at PR 137487, world broken WITHOUT_NETGRAPH.
Is it reasonable to have MK_NETGRAPH=no enforce MK_ATM=no and MK_BLUETOOTH=no?
The bluetooth stack is implemented using the netgraph framework. Some
bluetooth userland tools include netgraph headers or use netgraph
sockets.
There
>
> We only need one 'me' option that matches v4 and v6, because the
> other two can be implemented as 'ip4 me' and 'ip6 me' at no extra
> cost (the code for 'me' only scans the list corresponding to the
> actual address family of the packet). I would actually vote for
> removing the 'me6' microi
On Mon, Jan 11, 2010 at 03:27:13AM +0900, Hajimu UMEMOTO wrote:
> Hi,
>
> > On Sat, 2 Jan 2010 20:36:45 -0500
> > David Horn said:
>
> > dhorn2000> Yes, "me" matching either ipv4/ipv6 would certainly simplify the
> > default
> > dhorn2000> rc.firewall flow.
> >
> > Here is my proposed p
Hi,
> On Sat, 2 Jan 2010 20:36:45 -0500
> David Horn said:
> dhorn2000> Yes, "me" matching either ipv4/ipv6 would certainly simplify the
> default
> dhorn2000> rc.firewall flow.
>
> Here is my proposed patch. With this patch, 'me' matches to both IPv4
> and IPv6, and 'me4' is added for
The following reply was made to PR bin/142547; it has been noted by GNATS.
From: Bernhard Schmidt
To: bug-follo...@freebsd.org, sweetpea-free...@tentacle.net
Cc:
Subject: Re: bin/142547: wpa_supplicant(8) drops connection on key renegotiation
Date: Sun, 10 Jan 2010 10:28:14 +0100
Hi,
can y
