- repocopy vmware-guestd.sh to vmware-guestd.sh.in (by portmgr)
- remove vmware-guestd.sh
- remove vmware-guestd.sh entry from pkg-plist
- update Makefile
It is intensional that I do NOT bump PORTREVISION by this commit, since
any executable is not changed, and startup script itself is also NOT
changed, only the filename is changed. I do not want to bother users
to update their port by this non-functional change.
If you have any reasonable reason to bump PORTREVISION, let me know, and
I'll update the version asap.
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
- Build fix when WITH_VMWARE_GTK is set.
- Reorder pkg-plist so that @unexec vmware-guestd.sh successfully done.
- Create directories for server modules, since xserver may not be installed.
Even though this makes no "installed" content change, but bump
PORTREVISION since pkg-plist/pkg-plist.tools are changed.
PR: 93100
Submitted by: Scot Hetzel, swhetzel at gmail dotcom
that is bundled with VMware Workstation 5.5 fails to suspend, warns
on poweron/resume.
Bump PORTREVISION for both vmware-tools5 and vmware-guestd5.
PR: 90488
Submitted by: NIIMI Satoshi
revision number. It may help to avoid unwanted version bump to
vmware-tools5 if vmware-guestd5 specific changes are happen to
vmware-guestd5/Makefile.
Since no content changes at this time, no bump.
VMware Workstation FreeBSD-guest related ports for VMware Workstation
5.5.0 build 18463.
New features are:
- Spell "VMware Workstation" appropriately.
There are much VMware products, it would be the time that I have
to spell VMware Workstation as VMware Workstation.
- Support FreeBSD/amd64 since 64-bit binaries are provided from VMware.
I don't test any of 64-bit related portion, since I have no
FreeBSD/amd64 machine. If something trouble please email me.
- New variable "WITH_VMWARE_GTK" (emulators/vmware-tools5)
Install gtk version of VMware Tools if defined
(add more dependencies on other gtk-related ports)
- New variable "WITH_VMWARE_VMXNET" (emulators/vmware-guestd5)
Install "vmxnet.ko" kernel module (vmxnet driver) if defined
Usage:
- shutdown FreeBSD guest VM
- add following line to FreeBSD guest VM config file
Ethernet0.virtualDev="vmxnet"
- Boot FreeBSD guest VM
- load vmxnet.ko kernel module
- ifconfig vxn0 ...
New rc.conf variable "vmware_guest_vmxnet_enable" is also added
to vmware-guestd.sh to load kernel module at startup. However,
${PREFIX}/etc/rc.d/vmware-guestd.sh run _after_ /etc/rc.d/netif,
so it maybe too late to load here...
Note that vmxnet.ko supports FreeBSD 4.8-RELEASE or later, and
5.3-RELEASE and later (as VMware said). I've confirmed that
recent 7-current got 100% instant panic if vmxnet.ko is loaded.
- "vmware_guest_kmod_enable" is renamed to "vmware_guest_vmmemctl_enable"
Now this ports has two kernel modules now, old name is not
appropriate one, hard to understand this variable is for which
kernel module. I also put backward compatibility code, but users
of vmware_guest_kmod_enable please change variable name.
Bugfixes are:
- Resolve conflicts on ${PREFIX}/share/vmware-tools.
Unfortunately both vmware-guestd5 and vmware-tools5 installs
files to ${PREFIX}/share/vmware-tools directory. Since this
directory is only for vmware-tools, vmware-guestd5 doesn't do
anything for now.
- WWW: line in pkg-descr points bogus page.
- Add note that there's official VMware Tools installer, and what is the
difference between the two.
Finally, as usual, bump PORTVERSION.
${PREFIX}/share/vmware-tools. And create three symlinks to true(1) there
(poweroff-vm-default, poweron-vm-default, suspend-vm-default), which makes
it possible to shutdown or reboot guest FreeBSD system cleanly at the request
of the host. vmware-guestd expects those binaries/scripts to be present.
o Use `shutdown -p now' instead of `shutdown -h now', which in the case of
vmware allows to avoid spinning host CPU after shutdown.
o Patch vmware-checkvm, so that it traps proper signal (SIGBUS not SIGSEGV).
Apparently checkvm utility have not been tested on FreeBSD (apart from the
fact that it compiles).
Bump PORTREVISION.
and make XFREE86_VERSION map to it. XFREE86_VERSION is now deprecated.
- Make xorg the default X_WINDOW_SYSTEM on -current.
- Add several new X_*_PORT variables which point to various pieces of X11 based
on the setting of X_WINDOW_SYSTEM, and make ports use them.
- Add information to CHANGES about how to handle the transition.
PR: ports/68763
Approved by: portmgr (marcus)
Approved by: re (scottl)
Since 'OBJS=' line is inserted _after_ bsd.kmod.mk, OBJS value is
overridden by the line (ahh...) Hopefully, 'OBJS=' line is inserted
after 'SRCS=' line, but there's no handy way I suppose (sed's command
'i' requires to follow a newline, but how can I put a newline within
a one line?)
Since the contents (actually, kernel module) are changed,
bump PORTREVISION.
Submitted by: sobomax
In fact, the message was killed in old startup script. While converting
to the script for RCng era, I just forget to do that. I don't know that
"command_args" variable is ok in this case , but /etc/rc.d/ipxrouted
and /etc/rc.d/ntpdate already did it so it seems there's no problem.
Since the script is changed, bump PORTREVISION.
Noticed by: Alan Barber <abarber _at_ alanbarber.org>
Pointy hat to: matusita
- USE_RC_SUBR. Inspired by ports/net/dtcpclient (thanks ume-san).
Since now, loading kernel modules and/or start vmware-guestd can
be tweaked via following rc.conf variables:
* vmware_guestd_enable (default to YES)
* vmware_guest_kmod_enable (default to NO)
vmware-guest_kmod.sh is removed; both are handled by a single
shell script, vmware-guestd.sh.
- Bulid kernel module iff kernel source files are available.
This check is just a static checking of /usr/src/sys/Makefile.
It would be even better that '/usr/src' can be changed to other
place, but I believe that most user puts a source code under /usr/src,
or other places and set a symlink to there. If it hits you badly,
I'm willing to apply your patch to fix(?) it.
- If this ports is used by ports/emulators/vmware-tools4, install XFree86
server modules, vmware_drv.o and vmmouse_drv.o.
The vmware_drv.o is a (virtual) graphic chip driver. I believe that
if you have already installed XFree86 4.3.0, it should be the same
one but compiled on XFree86 4.3.99.2. I've confirmed that it should
work with XFree86 4.3.0 server.
The vmmouse_drv.o is a mouse driver, use it instead of default
mouse driver, mouse_drv.o. It works, but if my test is correct,
it doesn't support Emulate3Buttons. Use with care.
Both drivers are installed to appropriate directory, but renamed
(append '_VMware' to the filename) to avoid any conflicts to other
ports (especially ports/x11/XFree86*).
P.S.: Happy version 4.5.1, ACPI is enabled by default for FreeBSD guest OS.
Workstation.
This commit makes vmware-tools4 a slave port of vmware-guestd4, since
both are made from the same tarball, and it would be easy to maintain.
Vmware-guestd4 also installs a kernel module named vmmemctl; you may
want to kldload(8) it with a shell script under rc.d/ directory.
VMware Workstation 4.0.1 does fix "jumping the pointer" bug (yeah, thanks
VMware developer team). This means that you do not have to install
linux-vmware-toolbox4. However, it can be used as it should be, I
do not disable and/or remove this port.
- Mark NO_PACKAGE since these ports require VMware itself.
(and avoid using .ifdef(PACKAGE_BUILDING) also)
- Forget to mark IS_INTERACTIVE if !BATCH (vmware-guest4).
(after repocopying old ones, thank you joe).
It seems that VMware does not provide a new version of guest tools
for VMware 4.x to FreeBSD guest, but it would be better to add these
ports, since users will know FreeBSD runs on VMware 4.x.
I've also add vmware-toolbox port for VMware 4.x, which is for Linux
guest. In VMware 3.x, we FreeBSD guest user are happy to use FreeBSD
version of vmware-toolbox so we don't need the Linux version. However,
at least my VMs, FreeBSD version's vmware-toolbox causes X pointer a
bumpy one (pointer moves every seconds); it is unusable. Linux version
seems OK for me, so if you have seen such behavior, please try
linux-vmware-toolbox4 instead.
Old ports cleanup will come later.
Reviewed by: kuriyama (mentor)
either IGNORE or BROKEN.
Since there seems to be some confusion, for the record:
BROKEN is reserved for ports that don't work. This will prevent
users from installing the port, but please note that
ports marked as BROKEN will still be built by bento
IGNORE is reserved for ports that should not be built for one
reason or another (including bento). Users and bento
will not build ports marked as IGNORE.
FORBIDDEN is reserved for security breakages only!!! Only mark a
port as FORBIDDEN if there is a security issue with the
port at the time.
Reviewed by: kris (portmgr)
