Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Jan 2012 20:49:16 -0500
From:      Steve Wills <swills@FreeBSD.org>
To:        Michael Scheidell <scheidell@FreeBSD.org>
Cc:        ohauer@FreeBSD.org, cvs-ports@FreeBSD.org
Subject:   Re: cvs commit: ports/emulators/open-vm-tools Makefile distinfo pkg-plist
Message-ID:  <4F0A479C.4040007@FreeBSD.org>
In-Reply-To: <4F0A0D4C.5060900@freebsd.org>
References:  <201201080120.q081Kdq3018820@repoman.freebsd.org> <4F08FDB1.7000607@FreeBSD.org> <4F0981A1.4030708@freebsd.org> <4F09841D.6070701@FreeBSD.org> <4F09865C.5040905@freebsd.org> <4F09CB1F.8090103@FreeBSD.org> <4F0A0D4C.5060900@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 01/08/12 16:40, Michael Scheidell wrote:
> 
> 
> On 1/8/12 11:58 AM, Steve Wills wrote:
>> I've attached the updated patch which lets the vmhgfs.ko module
>> build in a way that allows it to at least kldload properly. But
>> note that this module produces an instant panic on trying to
>> mount an hgfs. If we think we can find a solution quickly, then
>> perhaps for now include the updated patch, but don't install the
>> hgfs module, so that the port loses the hgfs feature, but
>> hopefully only temporarily.
>> 
> don't want for me.. Q: why not 'revert' the whole source for
> vmhgfs.ko? Q2: there isn't any way to grab some old binaries (7,8,9
> i386, amd64) and have vmkgfs.ko as a seperate binary download, is
> there? Q3: I suppose in 'pkg-deinstall.in' there isn't any way to
> save OLD vmkgfs.ko and reinstall it, is there?

I'm really not sure I understand all you're saying or asking, but the
idea of using just the vmhgfs source from the older version doesn't
seem like it's going to work, based on what I know of the code.

> either case, if you want to close those two other pr's that are in
> your name steve, be my guest. apply the patches and close.

The state of the PR is somewhat irrelevant, but I would rather leave
them open and focus on getting the problems solved.

> in the mean time, I have pinged my vmware contact.
> 
> ANYONE USING COMMERCIAL VMWARE TOOLS OR SERVERS, LET ME KNOW.  The
> more ammunition $ I have the better.
> 

Again, not 100% clear here, but hopefully the vmware contact is
willing to help out. I can produce crash dumps of trying to use vmhgfs
using any of the versions of open-vm-tools we've talked about and have
even looked at the code a bit and have an idea where the problem is,
but don't know enough about the internals of how the modules work to
be sure of what the right solution is. Anyway, if you do manage to get
a good response from someone, please feel free to have them get in
touch with me directly.

Thanks,
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBAgAGBQJPCkecAAoJEPXPYrMgexuhEhUH/1RlrkklQoaW3ESBsxykTuDV
XTM6rVsJ2FHwbsdFOLlqcKH2BHOXZkjNj2BWSiFfw++qaJ3/cQDTo7sb8lToJCDk
4xC5SGD/da3KdATPxGIH3hEvz6EFBxQZIYhyOTu6PeZ/GaS0BIwsPEMEFEmd7Hcc
Va3xxSB5MN6UaJCESohZtsHJetu5O+KPc0iVXjc1fRMQvwIq1SFR8/SVhAX80K1Y
0N73njjyMEXacPrsRVOJYMUm18G3syF8h2RqCIq/QVgx1VIQVWlgFSNnOtVMnQyb
b0EPv7l/QXpj41v1QTAvdoaVkDlQivSwD9NQi+KWv7QdH7Oh5ihHtu5BPe7htlI=
=rTVY
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F0A479C.4040007>