Is the VMWare Player package broken for everyone (64-bit)?

[dibl]

In the Kubuntu 64-bit Gutsy repo, there's a version of VMWare Player. However, marking it for installation gives a BREAK error for me. Is it the same for everyone?

[oznoob]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Hi dibl
Just checked on my machine (32bit) and it is the same, it seems a dependencies problem
vmware-player-kernel-modules (2.6.20-15) is needed but is not installable
hope that helps

Uli

[dibl]

Re: Is the VMWare Player package broken for everyone (64-bit)?

THANKS Uli -- that makes TWO of us!

[Fintan]

Re: Is the VMWare Player package broken for everyone (64-bit)?

This may be of interest

http://npw.net/2007/05/17/vmware-workstation-60-on-linux-2622/

[dibl]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Yes, I see the last guy on the thread reports the same issue as I found. :P

[Fintan]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Hi dible,
I got mine working except for a share issue.
For this I have no answer yet

did you also apply the anyany 113 patch

http://knihovny.cvut.cz/ftp/pub/vmware/

before doing vmware-config?

also read:
http://kubuntuforums.net/forums/inde...opic=3085027.0

[dibl]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Yes, I did use that anyany 113 patch on my attempted VMWare Player 2 installation. That fixed the first round of problems, related to vmnet.

But upon running configuration again, there were a few missing library files. It was last weekend and I don't remember their names, but I looked them up and they are included in a package named "glibc". In the Gutsy repo you can find glibc-doc, the documentation package, but not glibc itself. So that kind of brought the ver. 2 experiment to a halt. I next tried to install the older VMWare Player package from the repo. It gave me a BREAK error when I marked it for installation. So, that was the end of that adventure, for the moment.

I still have my Ubuntu 64-bit Feisty installation, with VMWare Player and my custom virtual Win XP machine, so I'm OK, I just can't do some things on Kubuntu yet.

[Fintan]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Then it must be a 64bitter issue.

Bythw can you make anything of this:

mount error 20 = Not a directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

This is he man page:

MOUNT.CIFS(8) MOUNT.CIFS(8)

NAME
mount.cifs - mount using the Common Internet File System (CIFS)

SYNOPSIS
mount.cifs {service} {mount-point} [-ooptions]

DESCRIPTION
This tool is part of the samba(7) suite.

mount.cifs mounts a Linux CIFS filesystem. It is usually invoked indi‐
rectly by the mount(8) command when using the "-t cifs" option. This
command only works in Linux, and the kernel must support the cifs
filesystem. The CIFS protocol is the successor to the SMB protocol and
is supported by most Windows servers and many other commercial servers
and Network Attached Storage appliances as well as by the popular Open
Source server Samba.

The mount.cifs utility attaches the UNC name (exported network
resource) to the local directory mount-point. It is possible to set the
mode for mount.cifs to setuid root to allow non-root users to mount
shares to directories for which they have write permission.

I think I'll start a new thread.

Good luck

[dibl]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Then it must be a 64bitter issue.

Yes, I think it is.

Bythw can you make anything of this:

mount error 20 = Not a directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

This is he man page:

MOUNT.CIFS(8) MOUNT.CIFS(8)

NAME
mount.cifs - mount using the Common Internet File System (CIFS)

SYNOPSIS
mount.cifs {service} {mount-point} [-ooptions]

DESCRIPTION
This tool is part of the samba(7) suite.

mount.cifs mounts a Linux CIFS filesystem. It is usually invoked indi‐
rectly by the mount(8) command when using the "-t cifs" option. This
command only works in Linux, and the kernel must support the cifs
filesystem. The CIFS protocol is the successor to the SMB protocol and
is supported by most Windows servers and many other commercial servers
and Network Attached Storage appliances as well as by the popular Open
Source server Samba.

The mount.cifs utility attaches the UNC name (exported network
resource) to the local directory mount-point. It is possible to set the
mode for mount.cifs to setuid root to allow non-root users to mount
shares to directories for which they have write permission.

Looks like there is some confusion about your cifs mount point. You might want to check out the "properties" of your mount point, and make sure it looks like a directory, and not a file. (Yes, I'm guessing .....)

[Fintan]

Re: Is the VMWare Player package broken for everyone (64-bit)?

Thanks for the cifs proposal. For some reason gutsy/samba wants to mount cifs instead of smbmount (or something). Got that. Remains the rest of my samba BS. That is on another thread.

I just came across this on the mepis forum:
http://mepislovers.org/forums/showth...5219#post75219

It is a long shot but it may help.

Mepis 7.0 beta uses the same kernel (afaik)