Sunyny,

...

...

On 3/9/2008 at 15:22, Sunny wrote: open-vm-tools installs the service vmware-guest (get's automatically activated) and the toolbox. In my tests, the mouse was after installation freely going in and out the VM (normally one of the easiest indices that the VM tools work), I could mount a shared host (mount.vmhgfs .host:/test /mnt) and access it and the clipboard was shared between host and guest...

so now I have to ask you fellows to help me improve it, to make it undergo a lot of testing so we can convince coolo that he wants to include this package in the upcoming alphas and betas and finals of openSUSE (ups... we still don't have the procedures in place for community maintained packages).

so for now that's it from my side... any sort of comment is highly appreciated.

Hi Dominique, Thanks a bunch. Unfortunately, right now I have only factory in VM, so I can not test what you did. Maybe later today or tomorrow I'll install 10.3 to see how it works. Meanwhile - some questions and suggestions:

Well, factory just drifted to Kernel 2.6.25-rc1, which is not yet supported by the open-vm-tools. We can expect an update from the upstream project during this week though. The patch is available in the internal SVN of vmware already.

1. Does the rpm installs the user scripts (power-off, reboot, etc.) in a proper locations (/etc/xxx)

All the files get installed as described on the open-vm-tools packaging guideline. So power-off and all those things are in /etc/vmware-tools

2. As you know, vmware-config-tools.pl (supplied with the "original" vm tools), besides that builds the modules, also makes changes in xorg.conf, so the resolution of the screen can me "auto" adjusted, if you resize the VM window. Do you plan this? I.e. maybe this is more for the upstream devs, if they decide to put this functionality in the "tools" application itself - I think it belongs there. Or I guess, it does not hurt if the post-install script of the rpm you build just modifies the xorg file with the highest possible resolution.

So far, I do not modify the config files. The graphic card is already perfectly detected by openSUSE 10.3 itself and a higher resolution can be set even without the tools (they infact to not contain a driver for Xorg). But still, the auto-adjust of the resolution is a nice thing... I'll have to check how this is achieved. I'm not sure the open-vm-tools support this already at this point in time.

Cheers, and thanks again.

You're welcome... I hope the tools help you a bit. Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

...

...

On 3/10/2008 at 10:11, Adrian Schröter wrote: On Saturday 08 March 2008 16:52:48 wrote Dominique Leuenberger: .. openSUSE Factory (for fActory, i586 fails to compile because of inconsistency within BS... for the moment, the kernel-source matching the kernel-syms can not be found).

Are you sure with that ?

When I wrote the mail, Factory was in a BIG loop of being built and the kernel source was one of the scheduled packages... the message at that time was: nothing provides kernel-source in the correct version...

kernel-source and kernel-syms do build fine in openSUSE:Factory and should match (or we have a complete different problem).

Yes.. by now they build correctly... nevertheless, the KMPs built for Factory are useless even for i586. Why: the kernel-source and kernel-syms installed during the KMP build process are of version 2.6.25_rc4_git1-1.1. Anybody up to par with current Factory from download.o.o still has a kernel-default-2.6.24.1-6.i586.rpm. So anyhow: it will never match until we get on the FTP what we have in OBS for the Factory builds.

The log file seems more to point to a missing #include header ?

Yes, I've seen that.. I'll get in touch with the upstream project to see if there is a known incompatibility with 2.6.25 kernels introduced... it might be a change in the newer kernel that is found on OBS Factory/i586... x886_64 still has 2.6.24.1 in OBS.

The x86_64 build in OBS is currently using an older Factory state, so it is not really usefull atm for kernel modules.

As stated above, even if the i586 would build, it would not really be useful neither, because OBS is a bit ahead of what is out on the mirrors for Factory. But I'm sure this can be teemed up somehow in the process.

bye adrian

Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Am Montag 10 März 2008 schrieb Adrian Schröter:

Hm, I would have expected a BLOCKED state in this case, need to check ... No, what Dominique describes is exactly what happens whenever a new version is checked in required by some other package.

Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org