Colin Law wrote: > I don't know about Solaris but on Ubuntu sudo gem install is the way to > do it.
This is also true on Mac OS X/Darwin UNIX. > bash-3.00$ rake db:migrate > bash: /opt/coolstack/bin/rake: Permission denied > bash-3.00$ ls -ltr /opt/coolstack/bin/rake > -rwxr-x--- 1 root root 374 Sep 16 07:17 /opt/coolstack/ > bin/rake I'm thinking the OP has bigger problems than the "to sudo or not to sudo" issue. According to this output only root or members of the root group can execute rake. That's not going to work unless your logged in as root, which is a bad idea, of course. Here's the permission for rake on Mac OS X: -rwxr-xr-x 1 root wheel 387 May 18 16:28 rake rake is installed in /usr/bin, since Ruby on Rails is a standard install on Mac OS X. Notice here that only root has write permission, but anyone can execute rake. > At any rate, you should never have to use a mode of 777. +1 on this. 777 is a copout for lazy system admins. Server hackfest anyone? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
