OS X Mavericks App Store link
itunes.apple.com
itunes.apple.com
/Install OS X Mavericks.app/Contents/SharedSupport/InstallESD.dmg sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/USBSTICK --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction
NOTE: This uses sudo because it needs permission to write to the device. It also has the potential of destroying external drives, internal drives and boot drives. Please change the value for the 'volume' flag to point to the mounted path of the USB stick or SD card you wish to use as the bootable install disk. It will overwrite all the data on that disk. I am not responsible for any data loss using this command. Please double check all paths, all commands and all flags before running this.The Mavericks installer was not accepting the password to unlock FileVault in the installer itself after reboot. It turns out that the password prompt is in QWERTY despite the language input icon indicating that it was in Dvorak. That is a profoundly annoying bug.
You do need to sign up for a free developer account to use it.
Also, it may not even be fully rebooting, but instead doing something like killing all processes except init (launchd) which then starts up the installer. I haven't run it, so I don't know exactly what it's doing, but there are several ways to "reboot" without fully rebooting.
The interesting question is this: How well did Apple sanitize whatever bit of disk or flash memory ended up storing the key through the two reboots Mavericks needed to do to complete the upgrade?
pythonbrew is actually the python equivalent of rvm - https://github.com/utahta/pythonbrew
I fixed it by doing:
easy_install --upgrade pip
sudo pip install virtualenvwrapper
I don't usually use sudo to install virtualenv, you can use the method here and it will work: http://stackoverflow.com/questions/4324558/
I had some trouble reloading an existing vagrant box and virtualbox, seems to have resolved itself after using each providers uninstall tool bundled with the latest versions of Vagrant and Vbox and installing fresh versions after.
Looks like Xcode is using lldb for debugging, and I can use lldb on the command line. I guess lldb is now the standard 1st-party debugger? Guess I will be figuring out how to install gdb manually..
xcode-select --install xistence$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix
Command line tools for Mavericks are a separate download, it is no longer available in the Xcode downloads section. Start Xcode, click Xcode in the top left next the Apple in the menu bar, select "Open Developer Tool", click "More Developer Tools" to go directly to the site, log in with your apple developer ID and download the command line tools.The command line tools also make sure to install a whole range of standard headers that are not included with Xcode so that you can build curses based apps and all that fun stuff!
---
With gcc missing, so is libstdc++ for linking/compiling against.
This doesn't appear(?) to be an unintentional early leak or anything. I'm installing it on a secondary partition, happy to report if it explodes :)
edit: so far so good. I like what I'm seeing for the most part, took very close to 30 minutes from "click install" to "booted into 10.9" on my non-stock SSD. I'm not claiming any responsibility for other people's problems, but it seems to work from here, I'd say go for it if you're feeling adventurous.
edit: have to re-install Java, XCode wants to reinstall a few things, re-enable accessibility (shortcat/dterm), all in all similar to a new install. so far all apps work fine.
For anyone not yet using a hard drive analysis tool for discovering what's taking up all that space, DaisyDisk has served me well. For analysing Time Machine backups, BackupLoupe works well for identifying backup bloaters.
When you installed it, after reboot, did you absolutely get a window saying it was successful? (for me, the window took 45-60 seconds to pop up, and it failed twice before it worked (didn't want to install on battery)).
Try reloading the updates section of the Mac App Store again, and again.
Me asking similar question - https://twitter.com/stefek99/status/392755432105603072 - I want to find .iso, make bootable USB and wipe everything, start fresh.
I would also want to see some shas of the files distributed from Apple before I would use something from TPB.
I finally assumed that it had probably fried my HDD somehow, so I powered off and ordered an SSD online since I was looking to upgrade anyway. I unplugged it from the wall and turned it on and it suddenly found the Mavericks installer again.
It seems to be working now.
http://povolotski.me/2013/10/12/osx-mavericks-gm-out-bootabl...