LLVM errors out on the i2o code with the following warning..
../../../../dev/i2o/iop.c:2399:42: error: comparison of unsigned expression < 0
is always false [-Werror,-Wtautological-compare]
pt->pt_nbufs < 0 || pt->pt_replylen < 0 ||
~~~ ^ ~
After rev 1.144 of re.c MSIs seem to work better with the 8168 variants of
the Realtek PCIe GigE chipsets. So I am looking for any additional testing
with the Realtek re(4) PCIe Ethernet chipsets.
Index: if_re_pci.c
===
RCS file: /ho
Hi,
then to explain my draft here is my own configuration, and why it could
be useful to set custom priorities:
OSPF Scheme:
| - RT1 - | | - RT3
WAN | | OSPF AREA |
| - RT2 - | | - RT4
RIP Scheme:
| - RT1 - |
WAN | | RIP AREA | - CISCO 45XX
Hello, that's powerful but my improvement isn't for this use. It's only an
improvement to route packets correctly, not dispatch charge.
I'll give you a concrete example this evening.
Loïc Blot,
Ingénieur systèmes UNIX, Sécurité et Réseaux
http://www.unix-experience.fr
Stuart Henderson a écri
On Sun, Nov 03, 2013 at 03:06:23PM +, Stuart Henderson wrote:
> cc1plus: warnings being treated as errors
> In file included from
> /usr/obj/squid-3.4.0.2/squid-3.4.0.2/src/DiskIO/DiskThreads/aiops.cc:43:
> /usr/include/sys/stat.h:199: warning: 'int stat(const char*, stat*)' hides
> construct
cc1plus: warnings being treated as errors
In file included from
/usr/obj/squid-3.4.0.2/squid-3.4.0.2/src/DiskIO/DiskThreads/aiops.cc:43:
/usr/include/sys/stat.h:199: warning: 'int stat(const char*, stat*)' hides
constructor for 'struct stat'
I can just get rid of -Werror, but is this important?
On 2013/11/01 19:57, sven falempin wrote:
> FreeBSD propose to have a specific routing table for a process, which is
> even more powerful.
> When the router has multiple gateway i guess when a source address is
> choose the route should be chosen given that. Nothing more.
>
> What use of this <> d
--- disklabel.h.origSat Nov 2 18:48:46 2013
+++ disklabel.h Sat Nov 2 18:49:51 2013
@@ -43,7 +43,7 @@
* disk geometry, filesystem partitions, and drive specific information.
* The location of the label, as well as the number of partitions the
* label can describe and the number of the
