Hello,

I have a problem when setting (F2) french keyboard : the setup remains "french" after reboot, but the real llayout is back to default.

I've found that it is a bug in the "/etc/vmware/init/init.d/89.keymap" script : there is a line with :

KeyMap="$(</etc/keymap)"

it seems not working with this shell, but works with :

KeyMap="$(cat /etc/keymap)"

I tried to change this script (that works), but after reboot, the original script comes back. If I set the sticky bit (chmod +t), it remains for one reboot, but original script is back after two reboots !

How to have this change in script permanent ?

Thanks

That's interesting that it get's wiped after the 2nd reboot. After the 1st reboot, is the sticky bit still on?

It's odd that it doesn't stay on and thus get back into state.tgz, but since it doesn't i'd suggest creating an oem.tgz file for it.

Yes, the sticky bit is still on. But there is no more a ".#89.keymap" file. So after second reboot, it is back to original file, without sticky bit.

For "system" files in (for example) /etc with the sticky bit on, I saww that after reboot, there are still the ".#xxxx" files. So, I suppose the processus is more complex than only setting the sticky bit.

You give a tip to disable IPMI modifying the init script, after setting on the sticky bit of the script. I tried, same result... back to original file after second reboot.

Do you know how to report to VMware development that tthere is a bug in this keyboard init script ?

Sorry for the tardy display but vacation got in the way .

To log a support call you can try here - http://www.vmware.com/go/support_request/.

Can someone provide instructions on how to permanently modify a file? I am running into the same problem, where after a second reboot the file is back to the original state.

Thanks.

You can create an oem.tgz file with the modified file that you want. You'll then need to edit boot.cfg to include an entry to that file. See the home page for an article on creating an oem.tgz file.