There may come a time when you need to set up a second user account on a Mac while attempting to resolve a user account issue. As Setup Assistant assumes the account it is creating to be the first, it is always given administrator privileges. Setup Assistant is designed to run on the first boot of a fresh install of OS X, which is why you'll only see it when booting up a a brand-new Mac or one that has been erased and had OS X reinstalled.īesides options for keyboard layout, time zone and asking if you'd like to register, Setup Assistant also lets you create a new user account. Using some command-line trickery, we can do just this without having to erase and reinstall OS X. Under certain circumstances, it can be advantageous to re-run the Setup Assistant. You can find my setup for that at my blog.When you first start using a brand-new Mac or performed a clean install of OS X, you are presented with Setup Assistant, allowing you to create the first user account and specify some initial information, such as keyboard layout and locale. Also, maybe more importantly, you put the MacPorts path in front of the default PATH, so it will find that one first. Add in this line and save: echo PATH="/opt/local/bin:/opt/bin:$PATH"īasically you add the MacPorts ruby into your PATH, so the system looks for ruby in the /opt folder too. bash_profile, located in your user folder (if you have textmate, you can do mate ~/.bash_profile). If which ruby returns /usr/bin/ruby, then it's still finding the default ruby that comes with OSX, which is 1.8.6. If you're using MacPorts, that command should return /opt/local/bin/ruby. you still have your PATH set to the old Ruby, which is why you're getting 1.8.6 on ruby -v.įirst you gotta figure out where OSX is looking for your ruby by typing which ruby. To fix that you can do port install ruby19+nosuffixĢ.
To access it, you'd have to type ruby19 in place of ruby.so ruby19 script/generate, ruby19 -v.etc. If you ran port install ruby19, then you installed ruby 1.9, but under the name ruby19. If you just ran port install ruby, then you installed the old version, which explains why ruby -v still shows 1.8.6. You installed the wrong ruby with MacPorts
0 kommentar(er)
