search for: 01b

Displaying 8 results from an estimated 8 matches for "01b".

Did you mean: 01
2010 Nov 29
1
Writing to the wrong directory
...darxus at dancer:~$ history | grep rsync 3471 man rsync 4997 history | grep rsync | less 4999 history | grep "sudo.*rsync" 5004 history | grep rsync darxus at dancer:~$ root's history contains rsync commands with the targets: /media/2tb/bak/dancer-`date +%F`/ dancer-2010-11-01b dancer-2010-11-01b /media/2tb/bak/dancer-`date +%F`/ I did verify the copy of / in /media/2tb/ contained an update to a file I made just last night. Since I used the -a flag to rsync, I don't think it's possible to verify the copy happened around the time of the cron job. Any other...
2013 Jun 26
1
[LLVMdev] Auxiliary operand types for disassembler.
...odd. If bits [18:16] had been 0x5 then register 17 would have been used. - Parse bits can be used to designate the end of a hardware loop. If the parsebits are set to 10b in the first insn of the packet then this packet is the end of hardware loop 0, if the parse bits in insn 1 are set to 01b and the parse bits in insn 2 are set to 10b then this is the last packet in hardware loop 1. If the parse bits in insn 1 and insn 2 are both set to 10b then this is then end in both hardware loops 0 and 1. At the tail of the packet the disassembler would add the following: }:endloop0...
2007 Mar 20
0
[R-downunder] las with stripchart
...s), las=pars$las) Also col=pars$col and bg=pars$bg should probably get passed in the call to points() Are there also parameters that should be passed in the call to title(), as Paul mooted in that July 2001 discussion? For the earlier 2001 discussion, see http://tolstoy.newcastle.edu.au/R/devel/01b/0089.html John Maindonald email: john.maindonald at anu.edu.au phone : +61 2 (6125)3473 fax : +61 2(6125)5549 Centre for Mathematics & Its Applications, Room 1194, John Dedman Mathematical Sciences Building (Building 27) Australian National University, Canberra ACT 0200. On 2...
2023 May 09
5
[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr ===== This patchset adds a single bit to the skb to indicate that a packet encountered a layer 2 miss in the bridge and extends flower to match on this metadata. This is required for non-DF (Designated Forwarder) filtering in EVPN multi-homing which prevents decapsulated BUM packets from being forwarded multiple times to the same multi-homed host. Background ========== In a typical EVPN
2023 May 18
5
[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr ===== This patchset adds a single bit to the skb to indicate that a packet encountered a layer 2 miss in the bridge and extends flower to match on this metadata. This is required for non-DF (Designated Forwarder) filtering in EVPN multi-homing which prevents decapsulated BUM packets from being forwarded multiple times to the same multi-homed host. Background ========== In a typical EVPN
2013 Apr 06
5
arrange data
Hello all! I have a problem to arrange data in another form. My initial data is like this: 'data.frame': 421 obs. of 58 variables: $ 01A: num NA NA NA NA NA NA NA NA NA NA ... $ 01B: num NA NA NA NA NA NA NA NA NA NA ... $ 03A: num NA NA NA NA NA NA NA NA NA NA ... $ 03B: num NA NA NA NA NA NA NA NA NA NA ... $ 05A: num NA NA NA NA NA NA NA NA NA NA ... $ 05B: num NA NA NA NA NA NA NA 3.64 2.48 1.87 ... $ 07A: num NA NA NA NA NA NA NA NA NA NA ... $ 07B: num NA NA...
2013 Jun 25
0
[LLVMdev] Auxiliary operand types for disassembler.
Hi Sid, This feels like it’s exposing too much of the disassembler internals into the MCOperand representation. I’m not sure I follow why that’s necessary. Can you elaborate a bit? -Jim On Jun 25, 2013, at 8:24 AM, Sid Manning <sidneym at codeaurora.org> wrote: > > I'm working on a disassembler for hexagon (vliw) architecture and I would like to add an additional operand type,
2013 Jun 25
2
[LLVMdev] Auxiliary operand types for disassembler.
I'm working on a disassembler for hexagon (vliw) architecture and I would like to add an additional operand type, "kAux" to the MCOperand class. The reason for this is that each insn has parse bits which are not explicit operands and have differing meanings based on the insn's location within the packet and the number of insns inside the packet. In order for the disassembler