search for: itnerfac

I should probably elaborate on why I feel the interface should be as such. It seems to be the common case is compiler outputting to object files. In this case, all fragments are associated with symbols. What section the fragments go into is generally irrelevant to the compiler, except in special cases like global variable constructor/destructor lists and the like. At code generation time, the

This is a brain-dump of my thoughts on the MCStreamer interface after several days of digging around trying to get a COFF writer working. All fragments should be associated with a symbol. For assembler components, a unnammed "virtual" symbol can be used when there is no explicit label defined. Section assignment should be the responsiblity of the object imlementing the MCStreamer

(e-mailing to R-bugs is intentional - the web itnerface seems to be down) > a<- cbind(c(1,2), c(3,4)) > a [,1] [,2] [1,] 1 3 [2,] 2 4 > a[cbind(c(2,2), c(2,1))] [1] 4 2 > a[cbind(c(2,3), c(2,1))] Error: subscript out of bounds > a[cbind(c(2,-1), c(2,1))] Error: negative values are not allowed in a matrix subsc...

...ng between A and B. Traffic originating from A going to B will be load balanced packet by packet across cipcb0 and cipcb1. What I have tried ================= ip route add 10.3.3.3/32 equalize nexthop via 10.2.2.2 dev cipcb0 nexthop via 10.2.2.6 dev cipcb1 I also run a tcpdump on each of the two itnerfaces cipcb0 and cipcb1 to see where the traffic goes. On A : ping 10.3.3.3 : this makes all outgoing traffic go through a single link. I tried it while at the same time i ran while true;do ip route flush cache; done but that just made tcpdump show the echo reply packet coming back jump back a...