open-vm-tools.paketlendi

This commit is contained in:
milisarge 2017-06-13 18:43:37 +03:00
parent 0e07b02c8d
commit 82e9a1bd7e
6 changed files with 210 additions and 0 deletions

View File

@ -0,0 +1,18 @@
# Description: ARP arkaplan çalıştırma ve araçlar
# URL: http://arpon.sf.net
# Packager: milisarge
# Depends on: libpcap libnet
name=libdnet
version=1.11
release=1
source=(http://download.sourceforge.net/$name/$name-$version.tar.gz)
build() {
cd $name-$version
autoreconf -i -Iconfig
./configure --prefix=/usr \
--mandir=/usr/man
make
make install DESTDIR=$PKG
}

View File

@ -0,0 +1,18 @@
# Description: Microsoft sıkıştırma kütüphaneleri
# URL: http://www.cabextract.org.uk/libmspack/
# Packager: milisarge
# Depends on:
name=libmspack
version=1.5
release=1
source=(https://github.com/kyz/libmspack/archive/v$version.tar.gz)
build() {
cd $name-$version/$name/trunk
autoreconf -vfi
./configure --prefix=/usr --disable-static
make
make check
make DESTDIR="$PKG/" install
}

View File

@ -0,0 +1,45 @@
README for open-vm-tools
INTRODUCTION
This port contains VMware Tools. You should install it if you are running CRUX
as a virtual machine under the VMware hypervisor.
This has only been tested on single core 32-bit virtual machines.
The VMware filesystem (vmhgfs) has not been tested.
Feedback is appreciated.
POST-INSTALL
1. Run the post-install script.
2. Add vmtools to the list of services to start at boot time.
FAQ
Q: What is the difference between this and the official commercial VMware Tools
distribution?
A: This code comes from the GPL release of VMware's tools, so in theory
it should work just as the commercial version.
That said, since this port is intended to be used on a server environment,
all the desktop utilities have been removed (eg: no GUI applications).
Q: Where is the driver for the VMware network adapter and disk controller?
A: Some device drivers are already included in the Linux kernel and disabled
in this port.
Please enable these kernel options:
* CONFIG_VMWARE_BALLOON
* CONFIG_VMWARE_PVSCSI
* CONFIG_VMXNET3
If your boot filesystem is connected to a paravirtual SCSI interface make
sure CONFIG_VMWARE_PVSCSI is set as builtin instead of module.
Q: Why do I have to shutdown/reboot twice my VM from VMware before it reacts?
A: Did you run the post-install script?
--
If you have any feedback/problems please email me:
Alan Mizrahi, alan at mizrahi dot com dot ve

View File

@ -0,0 +1,41 @@
# Description: VMWare Araçları
# URL: http://open-vm-tools.sf.net/
# Packager: milisarge
# Depends on: libdnet glib libmspack
name=open-vm-tools
version=10.1.5
release=1
source=(https://github.com/vmware/open-vm-tools/archive/stable-${version/_/-}.tar.gz
vmtools.rc
tools.conf)
build(){
cd $name-stable-$version
cd $name
sed -ie 's|-Werror||g' configure.ac
autoreconf -iv
CXXFLAGS+=' -std=gnu++11 -fpermissive '
CFLAGS+=' -fpermissive '
CUSTOM_PROCPS_NAME=procps \
./configure \
--prefix=/usr \
--disable-static \
--without-root-privileges \
--without-x \
--without-gtk2 \
--without-xmlsecurity \
--without-gtkmm \
--without-icu \
--without-pam \
--without-kernel-modules
make
make DESTDIR=$PKG install
mv $PKG/usr/sbin/mount.vmhgfs $PKG/sbin/mount.vmhgfs
install -D $SRC/vmtools.rc $PKG/etc/rc.d/init.d/vmtools
rm -rf $PKG/usr/{etc,sbin,share} $PKG/etc/vmware-tools/scripts/vmware/network
rm -f $PKG/usr/lib/open-vm-tools/plugins/common/*.la
install -m644 $SRC/tools.conf $PKG/etc/vmware-tools/tools.conf
}

View File

@ -0,0 +1,11 @@
[logging]
log=syslog
level=warning
vmsvc.level=warning
vmsvc.data=/var/log/vmware-vmsvc.log
vmusr.handler=syslog
vmusr.level=warning
vmusr.data=/var/log/vmware-vmsvc.log.user
[vmsvc]
disable-tools-version=true

View File

@ -0,0 +1,77 @@
#!/bin/bash
NAME=vmtools
USER=root
CONFIG="/etc/vmware-tools/tools.conf"
RUNDIR="/var/run"
PIDFILE="$RUNDIR/vmtoolsd.pid"
STARTCMD="/usr/bin/vmtoolsd --config=$CONFIG --background=$PIDFILE"
STOPCMD=""
STOPTIMEOUT=300
function getpid() {
if [ -z "$PIDFILE" ]; then
pid="$(pgrep -xfn "$STARTCMD")"
else
if [ -f "$PIDFILE" ]; then
pid=$(< $PIDFILE)
if [ ! -d /proc/"$pid" ]; then
echo "$NAME: removing stale pidfile $PIDFILE" >&2
rm -f "$PIDFILE"
unset pid
fi
fi
fi
echo "$pid"
}
case $1 in
start)
pid=$(getpid)
install -d -m 755 -o $USER $RUNDIR || exit 1
if [ -n "$pid" ]; then
echo "$NAME already running with pid $pid" >&2
exit 1
fi
eval "$STARTCMD"
;;
stop)
pid=$(getpid)
if [ -n "$pid" ]; then
if [ -n "$STOPCMD" ]; then
eval "$STOPCMD"
else
kill "$pid"
fi
t=$(printf '%(%s)T' -1)
tend=$((t+STOPTIMEOUT))
while [ -d /proc/$pid -a $t -lt $tend ]; do
sleep 0.5
t=$(printf '%(%s)T' -1)
done
if [ -d /proc/"$pid" ]; then
echo "$NAME still running with pid $pid" >&2
else
[ -n "$PIDFILE" ] && rm -f "$PIDFILE"
fi
else
echo "$NAME is not running" >&2
fi
;;
restart)
$0 stop
$0 start
;;
status)
pid=$(getpid)
if [ -n "$pid" ]; then
echo "$NAME is running with pid $pid"
else
echo "$NAME is not running"
fi
;;
*)
echo "usage: $0 [start|stop|restart|status]"
;;
esac