51–60 of 88 posts
As always, you can make yourself a dandy boot disk or USB drive by opening the installer's app bundle, and writing the following file to your favourite medium using the "restore" tab in Disk Utility. /Install OS X Mavericks.app/Contents/SharedSupport/InstallESD.dmg
Does anyone know if Apple has a general bug report mechanism for the public? 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.
http://bugreport.apple.com You do need to sign up for a free developer account to use it.
Does anyone know how installing Mavericks affects hard drive space? I'm running on an 128GB SSD and space is always at a premium for me.
My MBP has a 128G SSD system drive as well (+ a big HDD for the data) and I got over 50G free, that's including some pretty big things (=25GB) in the Applications folder. /Library and /System folders come in at about 14GB together, I'd say a fresh Mavericks install should be around 30GB total.
First hitch I've noticed with 10.9: "gdb" seems to be missing. Gcc is still there. I've looked around to see if there's another optional download that I'm missing (like a Command Line Tools for Mavericks), but I don't see one. 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 manual…
Earlier quoted context omitted.
My MBP has a 128G SSD system drive as well (+ a big HDD for the data) and I got over 50G free, that's including some pretty big things (=25GB) in the Applications folder. /Library and /System folders come in at about 14GB together, I'd say a fresh Mavericks install should be around 30GB total.
The install is ~8GB
So I'm doing the upgrade on an mbp with filevault2. The installer "reboots" the machine and goes into the rest of the installation. But I'm never prompted for a disk password. So... how'd that happen?
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.
Earlier quoted context omitted.
Lots of people have reported having to install that thing more than once. 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.
The firmware update gave me a success message after I had installed it, and I don't see it available again in the updates. So no luck there.
Earlier quoted context omitted.
Isn't 2.0.0-p247 the system ruby? My rvm install was p195; after running "rvm use system" it's now p247 (ruby 2.0.0p247 (2013-06-27 revision 41674) [universal.x86_64-darwin13])
http://robots.thoughtbot.com/post/54109839209/psa-do-not-use...
Earlier quoted context omitted.
http://robots.thoughtbot.com/post/54109839209/psa-do-not-use...
Is there nothing equivalent to virtualenv for Ruby? It'd be nice to be able to use the system Ruby and just get gem to install into an isolated project specific location.