Well, today I encountered a old problem (or so I thought). Basically a specific udevadm version causes the vmware-config-tools.pl script to error out like this:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
The vmblock enables dragging or copying files between host and guest in a Fusion or Workstation virtual environment. Do you wish to enable this feature? [no] !!! [EXPERIMENTAL] !!! VMware automatic kernel modules enables automatic building and installation of VMware kernel modules at boot that are not already present. By selecting yes, you will be enabling this experimental feature. You can always disable this feature by re-running vmware-config-tools.pl. Would you like to enable VMware automatic kernel modules? [no] No X install found. Could not find Parent Node... |
I’ve had encountered this before in the past, and before there was some explanation on the VMware forums, which I couldn’t locate. Lucky me, the VMware Tools updater keeps modified versions of vmware-tools-config.pl around. So I ended up creating this short diff, so that I may find it in the future – if I still need it:
|
1 2 3 4 5 6 7 8 9 10 11 |
--- /usr/bin/vmware-config-tools.pl 2013-09-09 09:43:13.000000000 +0200 +++ vmware-config-tools.pl 2013-09-09 09:43:04.000000000 +0200 @@ -6880,7 +6880,7 @@ my $txt = $1; if ($txt =~ m/{vendor}=="VMware/is) { # Get the udev device path from this node - if ($txt =~ m/'(.*?)':/s) { + if ($txt =~ m/^'(.*?)':/s) { unshift(@scsiNodes, $1); unshift(@nodeText, $txt); } else { |