Searches without login should now work. You must get asked to click a button.
Port details
vmware-guestd4VMware time synchronization daemon for FreeBSD guest OS (for VMware 4.x)
4.5.2.8848_4emulatorsΣ=6 4.5.2.8848_4Version of this port present on the latest quarterly branch.
DEPRECATED: No more supported upstream This port expired on: 2013-03-14 IGNORE: is only for i386, while you are running amd64 RESTRICTED: "Not sure if we can redistribute this." IS INTERACTIVE: yes
There is no maintainer for this port.
Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
vmware-guestd daemon is for time synchronization with host OS and others.
Beware, this port is for FreeBSD _guest_ OS. You don't need to install
this ports to FreeBSD _host_ OS. This ports also installs a kernel modules
for FreeBSD guest.
If you want to run FreeBSD as a VMware guest OS, install this port
would help you. If you want to run X, install vmware-tools too.
WWW: http://www.vmware.com/products/desktop/ws_features.html
Remove expired, unmaintained ports:
2013-03-14 emulators/vmware-tools5: No more supported upstream
2013-03-14 emulators/vmware-tools6: No more supported upstream
2013-03-14 emulators/vmware-tools4: No more supported upstream
2013-03-14 emulators/vmware-guestd4: No more supported upstream
2013-03-14 emulators/linux-vmware-toolbox6: No more supported upstream
2013-03-14 emulators/vmware-guestd6: No more supported upstream
2013-03-14 emulators/linux-vmware-toolbox4: No more supported upstream
2013-03-14 emulators/linux-vmware-toolbox5: No more supported upstream
2013-03-14 emulators/vmware-guestd5: No more supported upstream
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
Replace all INSTALL_DATA/INSTALL_SCRIPT and INSTALL_PROGRAM/STRIP=
hacks to install kernel loadable modules correctly on amd64 platforms
with the new INSTALL_KLD command.
All PORTREVISIONS have been bumped to show when the new version of
installing became available.
Use '@stopdaemon' command recently introduced.
Actually, vmware-guestd4 package content is changed but I don't want to
bump the version -- it is used only in uninstallation phase (and VMware
Workstation 4.x is no longer updated so no uninstallation will be needed.)
Set LC_CTYPE to 'C' for ${REINPLACE_CMD}, since if LC_CTYPE is set to
others (such as ja_JP.eucJP), replacing string may fail.
No bumps, since nothing changed if REINPLACE_CMD works as expected.
Requested by: kuriyama
Follow the new world order: use 'USE_RC_ORDER=file.sh' feature.
- 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.
Remove the FreeBSD KEYWORD from all rc.d scripts where it appears.
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.
o Make sure that /etc/vmware-tools is created as symlink pointing out to
${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.
- Add the X_WINDOW_SYSTEM={xorg,xfree86-4,xfree86-3} variable to bsd.port.mk,
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)
Fix kernel module build.
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
Kill Linux-guest specific bogus messages by vmware-guestd.
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
Update to 4.5.1 build 7568, with lots of cleanup.
- 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.
(Only the first 15 lines of the commit message are shown above )
Update VMware Tools for 4.0.1 build-5289, the latest version of VMware
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.
Fixup for package cluster building.
- 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).
I've too much asked that where to get files for install. Apparantly,
the word 'none' is an obscure comment.
No content change, no procedure change, so no bump.
Update VMware-related tools to the of VMware Workstation 4.0.0 build-4460
(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)