search for: shrb

Hi, When I try to do anything on my samba system a connection is made to IPC$, but this is mapped to a directory /root/tmp. This seems odd. To make matters worse ordinary users cannot access this directory, so the only user who can access the IPC$ share (ie, do anything at all) is the root user. What have I don wrong. I cannot find any reference to IPC$ being linked to a directory

...50.3011 5000 2 0.5563025 7.116200 6.467652 3.973543 4.894322 6.279565 5.872954 5.460165 3.973543 6.985068 4.958779 6.431883 7.524418 825 365.8802 548.6984 5000 2 0.5314789 7.236186 6.739166 5.571924 5.729373 6.810875 6.049045 4.537781 3.973543 6.921747 5.335227 5.892576 7.425795 nlcd.shrb nlcd.grshrb forest o.legume devel wetland grains ra.SDI 821 5.504978 6.599838 6.661026 4.450634 6.974943 6.640015 4.838805 25.94976 822 5.758828 5.736926 5.027859 5.064582 6.652622 7.020253 3.973543 25.62106 823 5.840769 5.937286 5.399468 4.274550 6.959373 7.125071 4.496390 27.7...

...e is what the asm for the above looks like: baz: leaq .L__unnamed_1(%rip), %rax subl %eax, %edi roll $30, %edi ; CONSTANT: 32-rotate count cmpl $65, %edi ; CONSTANT: size of byte array ja .LBB2_1 movslq %edi, %rax leaq .Lbits_use(%rip), %rcx movb (%rax,%rcx), %al andb $2, %al ; CONSTANT: bit mask shrb %al retq .LBB2_1: xorl %eax, %eax retq A naive summary encoding would map a type identifier to a tuple of (resolution, rotate count, size of byte array, bit mask), and pull the latter three out of the summary as constants. However, the disadvantage of hard coding the constants in the IR like this...

...leaq .L__unnamed_1(%rip), %rax > subl %eax, %edi > roll $30, %edi ; CONSTANT: 32-rotate count > cmpl $65, %edi ; CONSTANT: size of byte array > ja .LBB2_1 > > movslq %edi, %rax > leaq .Lbits_use(%rip), %rcx > movb (%rax,%rcx), %al > andb $2, %al ; CONSTANT: bit mask > shrb %al > retq > .LBB2_1: > xorl %eax, %eax > retq > > A naive summary encoding would map a type identifier to a tuple of > (resolution, rotate count, size of byte array, bit mask), and pull the > latter three out of the summary as constants. However, the disadvantage of > ha...

...retrieve drive number */ + movb $0x08, %ah + int $0x13 /* get drive parameters; returns CH LSB of max cyl., CL(7-6) MSb max cyl., */ + /* CL(5-0) max sector, DH max head, DL drive qty, ES:DI floppy parameter table */ + movb %ch, %bl /* transfer maximum cylinder number */ + movb %cl, %bh + shrb $6, %bh /* move bits into correct positions */ + pushw %bx /* preserve maximum cylinder number */ + incb %dh /* convert zero-based maximum to quantity */ + movzbw %dh, %ax /* DH = maximum head number */ + pushw %ax /* preserve maximum head number */ + andw $0x3f, %cx /* mask to enforce...

...retrieve drive number */ + movb $0x08, %ah + int $0x13 /* get drive parameters; returns CH LSB of max cyl., CL(7-6) MSb max cyl., */ + /* CL(5-0) max sector, DH max head, DL drive qty, ES:DI floppy parameter table */ + movb %ch, %bl /* transfer maximum cylinder number */ + movb %cl, %bh + shrb $6, %bh /* move bits into correct positions */ + pushw %bx /* preserve maximum cylinder number */ + incb %dh /* convert zero-based maximum to quantity */ + movzbw %dh, %ax /* DH = maximum head number */ + pushw %ax /* preserve maximum head number */ + andw $0x3f, %cx /* mask to enforce...

...retrieve drive number */ + movb $0x08, %ah + int $0x13 /* get drive parameters; returns CH LSB of max cyl., CL(7-6) MSb max cyl., */ + /* CL(5-0) max sector, DH max head, DL drive qty, ES:DI floppy parameter table */ + movb %ch, %bl /* transfer maximum cylinder number */ + movb %cl, %bh + shrb $6, %bh /* move bits into correct positions */ + pushw %bx /* preserve maximum cylinder number */ + incb %dh /* convert zero-based maximum to quantity */ + movzbw %dh, %ax /* DH = maximum head number */ + pushw %ax /* preserve maximum head number */ + andw $0x3f, %cx /* mask to enforce...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths