search for: newhandler

...ll handling. Dieter #---------------------- library(rgl) r3dDefaults open3d() shade3d(cube3d(color=rep(rainbow(6),rep(4,6)))) btn3d <- function() { begin <- function(x, y) { # Add checking for key down later cat(x,y,"\n") # Forward to trackball (no easier way?) newhandler <- par3d("mouseMode") newhandler[1] <- "trackball" par3d(mouseMode = newhandler) } rgl.setMouseCallbacks(1, begin) } btn3d()

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_doorbell.c | 749 +++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_doorbell.h | 54 ++ 2 files changed, 803 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_doorbell.c create mode 100644 drivers/misc/vmw_vmci/vmci_doorbell.h diff --git

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_doorbell.c | 749 +++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_doorbell.h | 54 ++ 2 files changed, 803 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_doorbell.c create mode 100644 drivers/misc/vmw_vmci/vmci_doorbell.h diff --git

First time poster - hope I''ve done sufficient homework to get more than an rtfm: In my view, I have a <ul> list wherein each list element is identified with an id, thusly: <ul id="todoHandle"> <% for task in @tasks %> <li id="task_<%=task.id%>"> <%= task.Description %> </li> <% end %>

-------- --Multipart_Thu_Apr__8_13:33:51_1999-1 Content-Type: text/plain; charset=US-ASCII Hello guys, I always wondered why smbclient keeps timestamp in `put'ting a file but does not keep it in `get'ting a file. Alternative to keep the time stamp in `get'ting file is to use -Tc option or smbtar script, but they are a bit hairy for interactive use, and it can only dump files with an

period of time (hours up to weeks sometimes), and then 'certain' pc's would no longer be able to connect to samba, but other pc's would still be working. And the pc's affected are not the same each time. this might be the case if what is REALLY going on is that the pc's that are STILL working never lost their connection to SAMBA/iX, so they already(still) have a working

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

\\Pettit Connect As: Password: On the server side, I didn't get far because the domain name come up NULL so it failed on that test. Below are two logs log98.txt and log2000.txt that show full debug info. I might just have a stupid configuration or installation mistakes. I am sure that my basic configuration must work since it is a very typical setup. Any help will be highly appreciated