I would like to build a bridge using FREEBSD system.At the same time,
they can do the network traffic control.How to do it?
read manuals
thank you!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
I think this is unintentionally specious reasoning. No offense intended. :)
true
The program itself is fairly trivial to write.
i don't need such a tool, but if it would be separate tool, then it is all
right if someone like to write it. This would be unix way.
So it's really not possibl
greatest resistance to writing any documentation.
I'll just note that over the past ~6 months, the documentation team has
seen a lot of new contributors and new energy. So from my view, the
situation is improving.
And is already great. The topic wasn't about documentation.
___
On 18 Jul 2012 09:39, "Wojciech Puchar"
wrote:
>>
>>
>> I think this is unintentionally specious reasoning. No offense intended.
:)
>>
> true
>
>
>> The program itself is fairly trivial to write.
>
>
> i don't need such a tool, but if it would be separate tool, then it is
all right if someone like
On 07/18/12 01:36, Wojciech Puchar wrote:
not really. the idea was to integrate it with shell and turn on it by
default, prefering newbies over norml users, and making another change
that would actually prevent getting knowledge to newbie.
I don't agree with modifying the shell either, and I re
Xin,
Thanks for the reply!
Unfortunately I tried to put the code from the patch in place but there
seems to be some missing functions in the header file and too many
arguments to a function and some other errors below:
../../../amd64/amd64/trap.c: In function `syscall':
../../../amd64/amd64/trap
At $WORK we use a modification of DEVICE_POLLING instead of running
our NICs in interrupt mode. With the ULE scheduler we are seeing that
CPU utilization (e.g. in top -SH) is completely wrong: the polling
threads always end up being reported at a utilization of 0%.
I see problems both with the CP
On 18.07.2012 23:29, Ryan Stone wrote:
At $WORK we use a modification of DEVICE_POLLING instead of running
our NICs in interrupt mode. With the ULE scheduler we are seeing that
CPU utilization (e.g. in top -SH) is completely wrong: the polling
threads always end up being reported at a utilizatio
On Wed, Jul 18, 2012 at 3:26 PM, Bill Crisp wrote:
>
> Unfortunately I tried to put the code from the patch in place but there
> seems to be some missing functions in the header file and too many
> arguments to a function and some other errors below:
Hi Bill. Yes, the patch for >= FreeBSD 7 w
9 matches
Mail list logo
