Re: Debian Testing VMWare-Tools Bad Variable Name
Hi, Starting VMware Tools services in the virtual machine: Switching to guest configuration:[71G done /etc/init.d/vmware-tools: 1090: local: ': bad variable name /etc/init.d/vmware-tools: 1090: local: ': bad variable name Blocking file system:[71Gfailed /etc/init.d/vmware-tools: 1187: local: ': bad variable name Guest operating system daemon:[71G done Unable to start services for VMware Tools The problem lies in the output of uname -r: root@wheezy:~# uname -r 3.2.0-4-686-pae root@jessie:~# uname -r 3.11-2-686-pae get_version_integer expects a version like v1 dot v2 dot v3 from uname -r. So a quick'n'dirty fix for the current jessie kernel 3.11.8-1 is: root@jessie:/etc/init.d# diff vmware-tools.orig vmware-tools 846c846,847 version_uts=`uname -r` --- #version_uts=`uname -r` version_uts=3.11.8-1-686-pae But the new kernel version format also causes problems in vmware-config- tools.pl so currently i am unable to compile the vm* kernel modules. See also https://communities.vmware.com/message/2263010#2263010 Regards, Helmar. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201312091213.32251.hel...@gerloni.net
Re: Debian Testing VMWare-Tools Bad Variable Name
On Mon, Dec 9, 2013 at 11:13 AM, Helmar Gerloni hel...@gerloni.net wrote: Starting VMware Tools services in the virtual machine: Switching to guest configuration: [71G done /etc/init.d/vmware-tools: 1090: local: ': bad variable name /etc/init.d/vmware-tools: 1090: local: ': bad variable name Blocking file system: [71Gfailed /etc/init.d/vmware-tools: 1187: local: ': bad variable name Guest operating system daemon: [71G done Unable to start services for VMware Tools The problem lies in the output of uname -r: root@wheezy:~# uname -r 3.2.0-4-686-pae root@jessie:~# uname -r 3.11-2-686-pae get_version_integer expects a version like v1 dot v2 dot v3 from uname -r. Upstream still uses the 0 (or n) sublevel so the kernel team might be amenable to changing its numbering scheme. # head -n4 Makefile VERSION = 3 PATCHLEVEL = 13 SUBLEVEL = 0 EXTRAVERSION = -rc3 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SxuXtuM4otmO3Mt4tnxz56XymdGf=3mg6oxptswl7h...@mail.gmail.com
Re: Debian Testing VMWare-Tools Bad Variable Name
On Mon, Jul 22, 2013 at 09:31:34AM -0500, Selim T. Erdogan wrote: This is a long shot but for some reason I was reminded of having trouble with a non-debian script a few months ago, that also asked to be run by /bin/sh (as your attachment did). At the time, on my wheezy system (while it was still in testing), /bin/sh pointed to dash, not bash, so the script didn't work right. I fixed it with dpkg-reconfigure dash. So you could check if the /bin/sh on the two systems points to the same shell with the same version. Wouldn't it be better to change the line in the script to point to bash? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130724140038.GF13587@tal
Re: Debian Testing VMWare-Tools Bad Variable Name
Chris Bannister, 25.07.2013: On Mon, Jul 22, 2013 at 09:31:34AM -0500, Selim T. Erdogan wrote: This is a long shot but for some reason I was reminded of having trouble with a non-debian script a few months ago, that also asked to be run by /bin/sh (as your attachment did). At the time, on my wheezy system (while it was still in testing), /bin/sh pointed to dash, not bash, so the script didn't work right. I fixed it with dpkg-reconfigure dash. So you could check if the /bin/sh on the two systems points to the same shell with the same version. Wouldn't it be better to change the line in the script to point to bash? Yeah, maybe. I don't really know enough about the differences between bash and dash. I can't remember if I considered changing the one line, but I had the impression that bash was the default for a long time, and that dash was relatively new, so I must have thought going back to bash would be safe. Also, there were a number of scripts and more than one had problems. Selim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130724163126.ga25...@cs.utexas.edu
Re: Debian Testing VMWare-Tools Bad Variable Name
Hello List Maybe i wrong but i think the error is local run_kver=`get_version_integer` the script calls get_version_integer like external command, but it's a function Thanks 2013/7/21 William Hopkins we.hopk...@gmail.com On 07/21/13 at 04:09pm, Stephen P. Molnar wrote: In the case of Debian 7.1.0 the vmware tools installed without any problems. Unfortunately, this was not the case with Debian Testing. the tools installed without any problems, but when the installer ran /usr/bin/ware/vmware.config.tools.pl there were errors: Starting VMware Tools services in the virtual machine: Switching to guest configuration: [71G done /etc/init.d/vmware-tools: 1090: local: ': bad variable name /etc/init.d/vmware-tools: 1090: local: ': bad variable name Blocking file system: [71Gfailed /etc/init.d/vmware-tools: 1187: local: ': bad variable name Guest operating system daemon: [71G done Unable to start services for VMware Tools The lines in question are: 1090 local run_kver=`get_version_integer` and 1187local run_kver=`get_version_integer` Can you provide the vmware.config.tools.pl from your system? Can you `type get_version_integer`? if it's referenced in that script, can you provide it also? Sounds like an unescaped quote in one of these scripts, might have to identify the maintainer and bugreport upstream. Also, didn't you post this recently, with a longer log? Is this the same issue? -- William -- esta es mi vida e me la vivo hasta que dios quiera
Re: Debian Testing VMWare-Tools Bad Variable Name
Sorry Forgot the previous mail 2013/7/22 emmanuel segura emi2f...@gmail.com Hello List Maybe i wrong but i think the error is local run_kver=`get_version_integer` the script calls get_version_integer like external command, but it's a function Thanks 2013/7/21 William Hopkins we.hopk...@gmail.com On 07/21/13 at 04:09pm, Stephen P. Molnar wrote: In the case of Debian 7.1.0 the vmware tools installed without any problems. Unfortunately, this was not the case with Debian Testing. the tools installed without any problems, but when the installer ran /usr/bin/ware/vmware.config.tools.pl there were errors: Starting VMware Tools services in the virtual machine: Switching to guest configuration: [71G done /etc/init.d/vmware-tools: 1090: local: ': bad variable name /etc/init.d/vmware-tools: 1090: local: ': bad variable name Blocking file system: [71Gfailed /etc/init.d/vmware-tools: 1187: local: ': bad variable name Guest operating system daemon: [71G done Unable to start services for VMware Tools The lines in question are: 1090 local run_kver=`get_version_integer` and 1187local run_kver=`get_version_integer` Can you provide the vmware.config.tools.pl from your system? Can you `type get_version_integer`? if it's referenced in that script, can you provide it also? Sounds like an unescaped quote in one of these scripts, might have to identify the maintainer and bugreport upstream. Also, didn't you post this recently, with a longer log? Is this the same issue? -- William -- esta es mi vida e me la vivo hasta que dios quiera -- esta es mi vida e me la vivo hasta que dios quiera
Re: Debian Testing VMWare-Tools Bad Variable Name
Hello List
I try to figure out i what i think, get_version_integer function get 3
parameters
+
# Get the running kernel integer version
get_version_integer() {
local version_uts
local v1
local v2
local v3
version_uts=`uname -r`
# There is no double quote around the back-quoted expression on purpose
# There is no double quote around $version_uts on purpose
set `IFS='.'; echo $version_uts`
v1=$1
v2=$2
v3=$3
# There is no double quote around the back-quoted expression on purpose
# There is no double quote around $v3 on purpose
set `IFS='-ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz'; echo
$v3`
v3=$1
kernel_version_integer $v1 $v2 $v3
}
+++
the 3 paraters are passed to function kernel_version_integer, but i see in
whole script, get_version_intege function is called without parameters
+
vmware_start_acpi_hotplug() {
if [ `isLoaded $acpi` = 'yes' ]; then
# acpiphp is already loaded. Success.
return 0
fi
# Don't allow pciehp and acpiphp to overlap. Also don't unload
# pciehp in order to then load acpiphp as this won't avoid acpiphp
# crashing while trying to register a device node pciehp already has.
# All this only before 2.6.17 - since 2.6.17 pciehp and acpiphp can
# coexist.
if [ `isLoaded pciehp` = 'yes' ]; then
local ok_kver=`kernel_version_integer '2' '6' '17'`
local run_kver=`get_version_integer`
if [ $run_kver -lt $ok_kver ]; then
return 1
fi
fi
modprobe $acpi
return 0
}
+++
I don't use vmware for do a test
Thanks an sorry for my english :)
2013/7/22 emmanuel segura emi2f...@gmail.com
Sorry
Forgot the previous mail
2013/7/22 emmanuel segura emi2f...@gmail.com
Hello List
Maybe i wrong but i think the error is local
run_kver=`get_version_integer` the script calls get_version_integer like
external command, but it's a function
Thanks
2013/7/21 William Hopkins we.hopk...@gmail.com
On 07/21/13 at 04:09pm, Stephen P. Molnar wrote:
In the case of Debian 7.1.0 the vmware tools installed without any
problems.
Unfortunately, this was not the case with Debian Testing. the tools
installed without any problems, but when the installer ran
/usr/bin/ware/vmware.config.tools.pl there were errors:
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [71G done
/etc/init.d/vmware-tools: 1090: local: ': bad variable name
/etc/init.d/vmware-tools: 1090: local: ': bad variable name
Blocking file system: [71Gfailed
/etc/init.d/vmware-tools: 1187: local: ': bad variable name
Guest operating system daemon: [71G done
Unable to start services for VMware Tools
The lines in question are:
1090 local run_kver=`get_version_integer`
and
1187local run_kver=`get_version_integer`
Can you provide the vmware.config.tools.pl from your system?
Can you `type get_version_integer`? if it's referenced in that script,
can you
provide it also? Sounds like an unescaped quote in one of these scripts,
might
have to identify the maintainer and bugreport upstream.
Also, didn't you post this recently, with a longer log? Is this the same
issue?
--
William
--
esta es mi vida e me la vivo hasta que dios quiera
--
esta es mi vida e me la vivo hasta que dios quiera
--
esta es mi vida e me la vivo hasta que dios quiera
Re: Debian Testing VMWare-Tools Bad Variable Name
On Mon, 22 Jul 2013 11:23:00 +0200
emmanuel segura emi2f...@gmail.com wrote:
Hello List
I try to figure out i what i think, get_version_integer function get 3
parameters
+
# Get the running kernel integer version
get_version_integer() {
local version_uts
local v1
local v2
local v3
version_uts=`uname -r`
# There is no double quote around the back-quoted expression on
purpose # There is no double quote around $version_uts on purpose
set `IFS='.'; echo $version_uts`
v1=$1
v2=$2
v3=$3
# There is no double quote around the back-quoted expression on
purpose # There is no double quote around $v3 on purpose
set `IFS='-ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz';
echo $v3`
v3=$1
kernel_version_integer $v1 $v2 $v3
}
+++
the 3 paraters are passed to function kernel_version_integer, but i
see in whole script, get_version_intege function is called without
parameters
+
vmware_start_acpi_hotplug() {
if [ `isLoaded $acpi` = 'yes' ]; then
# acpiphp is already loaded. Success.
return 0
fi
# Don't allow pciehp and acpiphp to overlap. Also don't unload
# pciehp in order to then load acpiphp as this won't avoid acpiphp
# crashing while trying to register a device node pciehp already
has. # All this only before 2.6.17 - since 2.6.17 pciehp and acpiphp
can # coexist.
if [ `isLoaded pciehp` = 'yes' ]; then
local ok_kver=`kernel_version_integer '2' '6' '17'`
local run_kver=`get_version_integer`
if [ $run_kver -lt $ok_kver ]; then
return 1
fi
fi
modprobe $acpi
return 0
}
+++
I don't use vmware for do a test
Thanks an sorry for my english :)
2013/7/22 emmanuel segura emi2f...@gmail.com
Sorry
Forgot the previous mail
2013/7/22 emmanuel segura emi2f...@gmail.com
Hello List
Maybe i wrong but i think the error is local
run_kver=`get_version_integer` the script calls
get_version_integer like external command, but it's a function
Thanks
2013/7/21 William Hopkins we.hopk...@gmail.com
On 07/21/13 at 04:09pm, Stephen P. Molnar wrote:
In the case of Debian 7.1.0 the vmware tools installed without
any
problems.
Unfortunately, this was not the case with Debian Testing. the
tools installed without any problems, but when the installer ran
/usr/bin/ware/vmware.config.tools.pl there were errors:
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [71G done
/etc/init.d/vmware-tools: 1090: local: ': bad variable name
/etc/init.d/vmware-tools: 1090: local: ': bad variable name
Blocking file system: [71Gfailed
/etc/init.d/vmware-tools: 1187: local: ': bad variable name
Guest operating system daemon: [71G done
Unable to start services for VMware Tools
The lines in question are:
1090 local run_kver=`get_version_integer`
and
1187local run_kver=`get_version_integer`
Can you provide the vmware.config.tools.pl from your system?
Can you `type get_version_integer`? if it's referenced in that
script, can you
provide it also? Sounds like an unescaped quote in one of these
scripts, might
have to identify the maintainer and bugreport upstream.
Also, didn't you post this recently, with a longer log? Is this
the same issue?
--
William
--
esta es mi vida e me la vivo hasta que dios quiera
--
esta es mi vida e me la vivo hasta que dios quiera
Thanks for you reply and suggestion. Unfortunately, diffuse show
no differences between the two /etc/init.d/vmware-tools files.
Incidentally, your English is far better that my (non-existent) Spanish.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130722082311.7d12a...@inga.att.net
Re: Debian Testing VMWare-Tools Bad Variable Name
On 07/22/13 at 08:23am, Stephen P. Molnar wrote: 2013/7/22 emmanuel segura emi2f...@gmail.com 2013/7/21 William Hopkins we.hopk...@gmail.com On 07/21/13 at 04:09pm, Stephen P. Molnar wrote: In the case of Debian 7.1.0 the vmware tools installed without any problems. Unfortunately, this was not the case with Debian Testing. the tools installed without any problems, but when the installer ran /usr/bin/ware/vmware.config.tools.pl there were errors: Starting VMware Tools services in the virtual machine: Switching to guest configuration: [71G done /etc/init.d/vmware-tools: 1090: local: ': bad variable name /etc/init.d/vmware-tools: 1090: local: ': bad variable name Blocking file system: [71Gfailed /etc/init.d/vmware-tools: 1187: local: ': bad variable name Guest operating system daemon: [71G done Unable to start services for VMware Tools The lines in question are: 1090 local run_kver=`get_version_integer` and 1187local run_kver=`get_version_integer` Can you provide the vmware.config.tools.pl from your system? Can you `type get_version_integer`? if it's referenced in that script, can you provide it also? Sounds like an unescaped quote in one of these scripts, might have to identify the maintainer and bugreport upstream. Also, didn't you post this recently, with a longer log? Is this the same issue? Hello List Maybe i wrong but i think the error is local run_kver=`get_version_integer` the script calls get_version_integer like external command, but it's a function Thanks for you reply and suggestion. Unfortunately, diffuse show no differences between the two /etc/init.d/vmware-tools files. Did I miss it, or have you provided the script I requested? -- WIlliam signature.asc Description: Digital signature
Re: Debian Testing VMWare-Tools Bad Variable Name
This is a long shot but for some reason I was reminded of having trouble with a non-debian script a few months ago, that also asked to be run by /bin/sh (as your attachment did). At the time, on my wheezy system (while it was still in testing), /bin/sh pointed to dash, not bash, so the script didn't work right. I fixed it with dpkg-reconfigure dash. So you could check if the /bin/sh on the two systems points to the same shell with the same version. Selim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130722143134.gc22...@cs.utexas.edu
Re: Debian Testing VMWare-Tools Bad Variable Name
On Mon, 22 Jul 2013 09:31:34 -0500 Selim T. Erdogan se...@alumni.cs.utexas.edu wrote: This is a long shot but for some reason I was reminded of having trouble with a non-debian script a few months ago, that also asked to be run by /bin/sh (as your attachment did). At the time, on my wheezy system (while it was still in testing), /bin/sh pointed to dash, not bash, so the script didn't work right. I fixed it with dpkg-reconfigure dash. So you could check if the /bin/sh on the two systems points to the same shell with the same version. Selim Thanks for the reply, and suggestion. If it had worked even a long shot is useful. Unfortunately, it didn't work. I am, however, grateful for the suggestion. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130722110655.454f7...@inga.att.net
Re: Debian Testing VMWare-Tools Bad Variable Name
On 07/21/13 at 04:09pm, Stephen P. Molnar wrote: In the case of Debian 7.1.0 the vmware tools installed without any problems. Unfortunately, this was not the case with Debian Testing. the tools installed without any problems, but when the installer ran /usr/bin/ware/vmware.config.tools.pl there were errors: Starting VMware Tools services in the virtual machine: Switching to guest configuration:[71G done /etc/init.d/vmware-tools: 1090: local: ': bad variable name /etc/init.d/vmware-tools: 1090: local: ': bad variable name Blocking file system:[71Gfailed /etc/init.d/vmware-tools: 1187: local: ': bad variable name Guest operating system daemon:[71G done Unable to start services for VMware Tools The lines in question are: 1090 local run_kver=`get_version_integer` and 1187local run_kver=`get_version_integer` Can you provide the vmware.config.tools.pl from your system? Can you `type get_version_integer`? if it's referenced in that script, can you provide it also? Sounds like an unescaped quote in one of these scripts, might have to identify the maintainer and bugreport upstream. Also, didn't you post this recently, with a longer log? Is this the same issue? -- William signature.asc Description: Digital signature
