search for: ws6

I need to get a new computer and am looking at Intel E6600 Core 2 Duo. I'll be running Centos5. I have a couple of VMware Workstation 6 licenses, is there a way to install and run 64 bit inside an VMware virtual machine? I don't care about performance, it's only for testing and debugging purposes. This is not production. Any suggestion? -- Thanks http://www.sqlhacks.com The

...are: checking whether we can compute C Make dependencies... yes, using cc -M checking whether cc supports -c -o FILE.lo... yes checking how to get verbose linking output from f77... -v checking for Fortran 77 libraries... -L/usr/local/lib -R/opt/SUNWspro/lib -L/opt/SUNWspro/lib -L/opt/SUNWspro/WS6/lib -L/usr/ccs/lib -L/usr/lib -lF77 -lM77 -lsunmath -lm -lcx checking for dummy main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... lower case, underscore, no extra underscore checking whether f77 appends underscores to external names... yes checking wh...

...ailed to get machine password for account GRADE7-8$: NT_STATUS_LOGON_FAILURE I started looking at all the password hashes using pdbedit -Lw, and found the following: * There are no LanMan password hashes (all set to XXXX...) * All machine accounts have neither LanMan nor NT password hashes: WS6$:576:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[W ]:LCT-48D8EC0E: * The NT hashes for the user accounts appear to be incorrect. Otherwise everything looks right. The account flags look to be correct, and they all appear under the CLS domain. The Logon time fie...

...age comes from ld.so.1 when loading the acomp program. What this is saying is that acomp actually calls vsnprintf but ld.so.1 couldn't resolve that symbol. Since the Forte Developer 6 update 1 acomp was compiled and linked on Solaris 2.6, it won't run on Solaris 2.5.1. Forte Developer 6 (WS6) dropped Solaris 2.5.1 support; so did Forte Developer 6 update 1 (WS6U1) and Forte Developer 6 update 2 (WS6U2). So if you want to compile on Solaris 2.5.1 you need to use an older compiler. So this isn't a bug in OpenSSH. ------- You are receiving this mail because: ------- You are the a...

.../* + * The following used to be for shared memory. It is now + * unused and and is reserved for future use. It will fail if + * issued. + */ + IOCTLCMD(RESERVED3), + + /* + * The follwoing three were also used to be for shared + * memory. An old WS6 user-mode client might try to use them + * with the new driver, but since we ensure that only contexts + * created by VMX'en of the appropriate version + * (VMCI_VERSION_NOTIFY or VMCI_VERSION_NEWQP) or higher use + * these ioctl, everything is fine. + */ +...

.../* + * The following used to be for shared memory. It is now + * unused and and is reserved for future use. It will fail if + * issued. + */ + IOCTLCMD(RESERVED3), + + /* + * The follwoing three were also used to be for shared + * memory. An old WS6 user-mode client might try to use them + * with the new driver, but since we ensure that only contexts + * created by VMX'en of the appropriate version + * (VMCI_VERSION_NOTIFY or VMCI_VERSION_NEWQP) or higher use + * these ioctl, everything is fine. + */ +...

* * * 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

* * * 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

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.

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with