A minor issue, but I''m seeing that when we generate a application skeleton using the "rails" command, the generated script files follow the symlink of our ruby installation. On our machines, ruby is installed under /usr/pkg/ruby/ruby182/ with a symlink /usr/pkg/ruby/ruby -> /usr/pkg/ruby/ruby182/ Our sysadmins like using the symlinks as a way of managing the potential for having muliple revs of ruby installed. When we write our own Ruby scripts, we just use the symlink: #!/usr/pkg/ruby/bin/ruby ... And we execute rails from that same path (/usr/pkg/ruby/bin). But all the scripts that rails generates use: #!/usr/pkg/ruby182/bin/ruby Is there a way to change this behavior? Again, it''s a minor issue, but it diminishes our ability to shift to a new rev of Ruby super-easily.