Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
quick help using terminal
- Thread starter rema
- Start date
- Sort by reaction score
Ah okay.
Firstly get Terminal open (spotlight it if you don't know where it is, can't remember off the top of my head).
After that's up, enter 'sudo su (then your user password)' <-- without the quotation marks or brackets
Then just copy and paste the lines into terminal afterwards one-by-one, pressing enter after each one.
That should get you done.
Firstly get Terminal open (spotlight it if you don't know where it is, can't remember off the top of my head).
After that's up, enter 'sudo su (then your user password)' <-- without the quotation marks or brackets
Then just copy and paste the lines into terminal afterwards one-by-one, pressing enter after each one.
That should get you done.
Open up Terminal.app (in /Applications/Utilities). Type in
sudo su
This will prompt you for your password. Once authenticated, you are now the 'root' superuser (i.e. almighty God), so you now have write permission the /etc/hosts file. Then cut and paste those lines one by one into the terminal.
What it's doing is backing up the original hosts file to hosts.bak, and appending the hosts file with the hostnames and IP addresses of messenger.hotmail.com, etc. This is so it doesn't have to look these up through DNS.
An alternative way to do this is, in Finder, copy /etc/hosts to a new file: /etc/hosts.bak, then with your favorite text editor (Text Edit say), cut and paste those lines at the end of the /etc/hosts file (you will be prompted for a password for write permission).
sudo su
This will prompt you for your password. Once authenticated, you are now the 'root' superuser (i.e. almighty God), so you now have write permission the /etc/hosts file. Then cut and paste those lines one by one into the terminal.
What it's doing is backing up the original hosts file to hosts.bak, and appending the hosts file with the hostnames and IP addresses of messenger.hotmail.com, etc. This is so it doesn't have to look these up through DNS.
An alternative way to do this is, in Finder, copy /etc/hosts to a new file: /etc/hosts.bak, then with your favorite text editor (Text Edit say), cut and paste those lines at the end of the /etc/hosts file (you will be prompted for a password for write permission).
thanks for getting back to me guys,
ok this is whats happening i open terminal
the box pops up and say
i then type in sudo su superfish and its says this
then when i try it again its says
not sure what i am doing wrong
(i changed the computer name and password in the qoutes wasnt sure if someone could hack my mac or something)
ok this is whats happening i open terminal
the box pops up and say
i then type in sudo su superfish and its says this
then when i try it again its says
not sure what i am doing wrong
(i changed the computer name and password in the qoutes wasnt sure if someone could hack my mac or something)
I've gotten the same message as well. I quickly realized that I had to log into a privileged account (one with administrator privileges as opposed to my day-to-day normal user account). Give that a try.
Wait a minute...
Surely on the first line, you wouldn't put your password, you'd put your username.
Then press enter and when it prompts for the password, then you give it.
Try that out, it works for me. I think the original instructions were a bit wrong.
Thought it looked odd..
So it would be:
Surely on the first line, you wouldn't put your password, you'd put your username.
Then press enter and when it prompts for the password, then you give it.
Try that out, it works for me. I think the original instructions were a bit wrong.
Thought it looked odd..
So it would be:
Just whom are you trying to su to? Root? That's not how to do it*.
Anyway.. why switch to root? Why not just use sudo for what (unix)god intended it for?
*: It would be:
OR
Anyway.. why switch to root? Why not just use sudo for what (unix)god intended it for?
Code:
sudo cp /etc/hosts /etc/hosts.bak
sudo echo 65.54.239.20 messenger.hotmail.com >> /etc/hosts
sudo echo 65.54.179.216 nexus.passport.com >> /etc/hosts
sudo echo 65.54.183.203 login.live.com >> /etc/hosts*: It would be:
Code:
sudo -s
<enter admin password>
Code:
su -
<enter root password>Look at the user account properties (in control panel > Accounts) and see if your account is set up as a system administrator or standard.
Given that you have just one user account, I'd imagine that you're set up as Administrator already though.
The other possibility is that you've not set up the root account yet (Seems like I remember that this has to be done before using sudo, Can anyone confirm?). Sorry I can't help with setting that up (I'm not on my Mac right now so I'm doing this off the top of my head).
Given that you have just one user account, I'd imagine that you're set up as Administrator already though.
The other possibility is that you've not set up the root account yet (Seems like I remember that this has to be done before using sudo, Can anyone confirm?). Sorry I can't help with setting that up (I'm not on my Mac right now so I'm doing this off the top of my head).
Or just type in "id" in the Terminal. See yourself as part of Group 80? Yes, admin. No, not admin.
Code:
null:~ yellow$ id
uid=501(yellow) gid=501(yellow) groups=501(yellow), 81(appserveradm), 79(appserverusr), [B]80(admin)[/B]No, root does not need to be enabled to use sudo.
And finally.. if your password is superfish, please change it.
you are taking this way too literally I think.
type: sudo su
press the enter key
it'll ask for a password, use your admin password
you are now in super user mode, do your commands and exit the terminal.
sudo su puts you in super user mode, it works just fine.
I cannot issue "su -" and get a password to work. I guess I don't have root enabled on my machine, 'sudo su' however gets me there just fine.
Folks, su does not equal root. The command su means substitute user, not "superuser". With no argument, it assumes you want to su to root. But since you're using sudo (which means "do as sub'd user") with no argument it means "do as root".
So,
sudo su effectively means: "do as root switch to root", which is pointless, since all the commands above can be done simply by adding sudo before them, meaning, do the following command as root.
But if you really need to do this, just use the -s flag.
Code:
sudo -sYou're now logged in as root.
Anyway..
Without root enabled, no you cannot.
pointless? it's a keystroke saver. Once you do sudo su you are in a 'super user' shell. As if I just did su -. And yes yes, sudo -s does the same thing, whatever. Semantics.
Then do sudo -s.
sudo su is not the "proper" way to do it. Besides, root commands are not logged anywhere. Using sudo, all commands are logged to the syslog.
For security purposes, particularly when one doesn't know what they are doing (which the original poster clearly does not), stick with the safe method, ya?
If you want to argue it that way, sudo -s isn't either
once upon a time all you had was su.I get the distinct impression yellow has more of a clue about unix than the rest of us at the moment. Or at least makes it look like that.
But it seems this thread has gotten rather complicated for such a simple thing
To the OP:
Once you got to the stage where it said bash-3.2$ on the command line, instead of putting in a password, just try inputting the commands.
All these instructions are getting confusing...though it is rather late at night.
But it seems this thread has gotten rather complicated for such a simple thing
To the OP:
Once you got to the stage where it said bash-3.2$ on the command line, instead of putting in a password, just try inputting the commands.
All these instructions are getting confusing...though it is rather late at night.
If you want to argue it that way, sudo -s isn't either
Yes.. su for substitute user. With no argument, it assumed you want to sub to root. That is still possible. Assuming one has root enabled on their Mac. Which is not necessary, nor advised if one doesn't know what they are doing.
Just do this. You'll only be asked for your admin password the first time, the rest of the commands will (should!) fall within your 5 minute alloted timeout for sudo'd authentication.
sorry guys im getting a bit confused
sudo -s
sudo su
both of those seem to have worked. your prompt changed.