search for: newhandle

...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()

...+int vmci_doorbell_create(struct vmci_handle *handle, + uint32_t flags, + uint32_t priv_flags, + vmci_callback notify_cb, + void *client_data) +{ + struct dbell_entry *entry; + struct vmci_handle newHandle; + int result; + + if (!handle || !notify_cb || flags & ~VMCI_FLAG_DELAYED_CB || + priv_flags & ~VMCI_PRIVILEGE_ALL_FLAGS) + return VMCI_ERROR_INVALID_ARGS; + + entry = kmalloc(sizeof(*entry), GFP_KERNEL); + if (entry == NULL) { +...

...+int vmci_doorbell_create(struct vmci_handle *handle, + uint32_t flags, + uint32_t priv_flags, + vmci_callback notify_cb, + void *client_data) +{ + struct dbell_entry *entry; + struct vmci_handle newHandle; + int result; + + if (!handle || !notify_cb || flags & ~VMCI_FLAG_DELAYED_CB || + priv_flags & ~VMCI_PRIVILEGE_ALL_FLAGS) + return VMCI_ERROR_INVALID_ARGS; + + entry = kmalloc(sizeof(*entry), GFP_KERNEL); + if (entry == NULL) { +...

...;"> <%= task.Description %> </li> <% end %> </ul> Next I have a sortable that is intended to make a callback after things are updated: <%= sortable_element :todoHandle, :handle => ''handle'' , :containment => [''newHandle'',''todoHandle'',''doneHandle'',''trashHandle''], :dropOnEmpty => true, :onUpdate => ??????????? %> What I would like to understand is how to define an action which may be called from onUpdate in order to resequence the task...

...ULL, NULL, NULL, NULL, NULL) && !cli_getattrE(cli, fnum, @@ -513,6 +550,7 @@ DEBUG(0,("getattrib: %s\n",cli_errstr(cli))); return; } +#endif DEBUG(2,("getting file %s of size %.0f as %s ", lname, (double)size, lname)); @@ -538,6 +576,36 @@ if (newhandle) { close(handle); + + /* s.n. Tue Apr 6 22:18:17 1999 */ + if (timestamp) { +#if 0 /* Unused */ + /* Works fine for NT/and linux samba-2.0.3 server, but + Win98 returns garbage a_time, m_time (Win95 not tested). + ( Using gmtime() is correct here ? ) + printf("a:%ld...

...lname); } +/**************************************************************************** + get a file from rname to lname + ****************************************************************************/ +static void do_reget(char *rname,char *lname) +{ + int handle=0,fnum; + BOOL newhandle = False; + char *data; + struct timeval tp_start; + int read_size = io_bufsize; + uint16 attr; + size_t size; + off_t nread = 0; + off_t hashbytes = HASHBYTES; + + GetTimeOfDay(&tp_start); + + if (lowercase) { + strlower(lname)...

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.

...o_get(rname, lname); } +/**************************************************************************** + get a file from rname to lname + ****************************************************************************/ +static void do_reget(char *rname,char *lname) +{ + int handle=0,fnum; + BOOL newhandle = False; + char *data; + struct timeval tp_start; + int read_size = io_bufsize; + uint16 attr; + size_t size; + off_t nread = 0; + off_t hashbytes = HASHBYTES; + + GetTimeOfDay(&tp_start); + + if (lowercase) { + strlower(lname); + } + + fnum = cli_open(cli, rname, O_RDONLY, DENY_NONE); + + if...