Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.
No, seriously the program "mkdir" is *in* the bin directory which is entirely recursively removed! I ran this script and it blew away the entire /bin directory and then proceeded to fail. Then, I read it and realized it couldn't possibly work. So, if everyone is saying that it works, then I am doing something wrong. Is there *another* bin folder that I should be removing recursively besides /bin? #!/bin/sh set -e echo VMware ESXi 5.0 Unlocker 1.1.0 echo ============================== echo Copyright: Dave Parsons 2011-12 # Ensure we only use unmodified commands export PATH=/bin:/sbin:/usr/bin:/usr/sbin # Make sure working files are removed rm -f darwin.tgz rm -rf ./bin <-------------------kiss all your standard command line programs goodbye! # Patch the vmx files and place into bin folder echo Patching files... rm -rf ./bin <------------------- do it again for some unknown reason mkdir bin <------------------- Fails. Guess where mkdir was? /bin!!! But.... "./bin" is not the same as "/bin". So, is there another "bin" directory that I should be removing? - Slog
I'm feeling kind of dopey, because this ESXi unlocker script can't possibly work. "rm -rf ./bin" will remove the entire contents and all subdirectories of the /bin folder. "mkdir bin" then can't be run, because "mkdir" is now missing! Unless there's another "bin" folder that is supposed to be accessed? I'm really confused how anybody got this to work. - Slog