VMware Command Line Tools
On this page, you'll find command line programs which can replace and/or
supplement the VMware's official VMwareTools.
These programs use VMware's undocumented and therefore not officially
supported feature to communicate with VMware (see VMware Backdoor I/O Port).
Information on these functions have come entirely from my personal research
and quite a few contributions by fellow VMware users.
These programs are intended partly as illustrative examples of how to use the
VMware backdoor function and I have cut many corners writing them.
* vmw: generic backdoor access program
* vmshrink: virtual disk shrink program
* vmftp: host-guest file transfer program
LICENSE: no particular restriction on redistribution
===> The following configuration options are available for vmw-060510_2:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Mk/bsd.port.mk: Add __MAKE_CONF=${NONEXISTENT} to WRK_ENV
And remove it from individual ports. Use WRK_ENV in custom build
commands where necessary.
FreeBSD make(1) includes /usr/share/mk/sys.mk and that includes
/etc/make.conf if it exists. This happens when you run make in a port
directory but it also happens when the upstream build system uses make.
This commit disables make.conf inclusion in the latter case because
users can define variables like CFLAGS in make.conf that override ports
framework variables and this can cause problems that are difficult to
diagnose.
If there are any build customisations made through make.conf that stop
working because of this commit then they should be made available by the
(Only the first 15 lines of the commit message are shown above )
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Remove iconv(), iconv_open() and iconv_close() symbols from libiconv.
These were FreeBSD specific aliases for libiconv(), libiconv_open() and
libiconv_close() that are now also provided by libc which complicates
writing configure tests that work correctly when both libc iconv and
libiconv are available.
Also, because the libiconv iconv.h header redefines iconv* to libiconv*
correct use of the header implies that the aliases aren't used.
The following ports needed fixes because there was something wrong with
the way they tried to detect or use iconv:
audio/deadbeef: Remove LIBICONV_PLUG from a source file. It's a
compile-time option and should not be set in source code.
(Only the first 15 lines of the commit message are shown above )
According to the Porter's Handbook (5.12.2.3.) default options must be added to
OPTIONS_DEFINE. This policy has been implemented only recently that's why we
have many ports violating this policy.
This patch adds the default options specified in the Porter's Handbook to
OPTIONS_DEFINE where they are being used. Ports maintained by
gnome@FreeBSD.org, kde@FreeBSD.org and x11@FreeBSD.org have been excluded.
Approved by: portmgr (bapt)
VMware Command Line Tools
On this page, you'll find command line programs which can replace and/or
supplement the VMware's official VMwareTools.
These programs use VMware's undocumented and therefore not officially
supported feature to communicate with VMware (see VMware Backdoor I/O Port).
Information on these functions have come entirely from my personal research
and quite a few contributions by fellow VMware users.
These programs are intended partly as illustrative examples of how to use the
VMware backdoor function and I have cut many corners writing them.
* vmw: generic backdoor access program
* vmshrink: virtual disk shrink program
* vmftp: host-guest file transfer program
WWW: http://chitchat.at.infoseek.co.jp/vmware/vmtools.html
