General :: Difference Between The Commands "su" And "sudo -i"?
May 31, 2010
What is the difference between the commands "su" and "sudo -i"?
When I do sudo -i, it asks me the password and after typing my password, I login.
But when I do "su",it asks for my password, and I type the same password as for the sudo -i, but the terminal shows su: Authentication failure Why is it so? Does these commands have different passwords? If so I've forget password for "su". Now what to do?
Does the nohup command make a process immune to the HUP signal by sending the process to the background or does it achieve this by some other means? If it it does send it to the background, then are all background processes immune to the HUP signal? If yes, then we can make processes go to the background for getting immunity against HUP by using the bg command as well can't we?
Having a problem with sudo. I'm down as a user who can run all commands as root provided I enter my password. The relevant line from my /etc/sudoers file :
Code:
user1 ALL=(ALL) ALL
There are several commands that I run quite frequently such as mount and fdisk but would like to avoid having to enter a password each time I use them. What would be the appropriate change to the sudoers file ?
UPDATE: I neglected to scroll down to the bottom of the /etc/sudoers file where there was the line :
Code:
%admin ALL=(ALL) ALL
and since user1 was a member of the admin group any predeeding lines were being overidden by this. Commenting out this line and adding
I just started learning network on linux platform. Today I came across two commands ethtool and miitool. Both of them seems to do similar kind of jobs. Now I am confused what is the difference between them.
Customer asked me to create a menu for linux he also asked me to do this: Open like a command like where a user can execute commands...so for this the users have sudo enabled. The code below works OK. But it has an issue when a command is executed but the command does not need sudo
Like for instance Code: cd / sudo: cd: command not found
How can I allow a user to execute all commands when a command does not need sudo Code: echo -e "Press Control+C to finish" #echo -e " " while true; do read whichcmd?"Insert Command: " sudo $whichcmd done
I did some digging on the sudo command and I do know the config file is /etc/sudoers Read the manual for sudoers and found out that I must use visudo to edit the file I read some of the examples at the bottom of the file and tried entering my own account in following the example. one of the commands I was trying to allow my account to perform without root login is the mount command So I tried adding this in (kreid8 /bin/mount ALL) I then saved & exited the file and logged out of root and tried sudo mount -t vfat /dev/sdc1 /media. I got an error saying I had to be root in order to do that But when I use the visudo -l option it shows that I have that privellege. Did I edit the file incorrectly?
since a recent upgrade to Mandriva 2010.1 I am not able to 'sudo' as administrator or when I use the 'root' password. I am the only user on this machine (Dell Inspiron 530S multi-booted with Window's Vista Home Premium, Ubuntu 10.4, and Mandriva 2010.1). I can get into the 'Manage Users' section of the control center by authenticating as 'root' but I can't access 'sudoers file' from command line.
I need to clarify a few things about Veritas Cluster Services Example There is a solaris10, 2node vcs cluster running. There is a Rhel5 2node vcs cluster running. Is ther any difference between VCS commands in solaris10 and rhel5. I heard that VCS commands are same for all the platforms, only configuration files location is differ. Is this correct.
I was following a guide to stop Ubuntu from always asking the root password. And apparently i messed something up in vsudo edit or something like that i was in... So now when i put in a sudo command i get this...
Quote:
>>> /etc/sudoers: syntax error near line 18 <<< sudo: parse error in /etc/sudoers near line 18 sudo: no valid sudoers sources found, quitting
trying to devise a new sudoers configuration while building a new SOE and would like to force everyone (including system administrators) to use rootsh in favour of doing things like sudo -s, sudo bash, sudo tcsh and so forth. Effectively, use sudo to use any shell other than rootsh. Is there a way to allow users to run anything they want except shells. I realise this is a default permit which inherently is defective, but I'm not convinced that going through the 1559 executable commands of my (as yet incomplete) built system to decided on the likely 1000+ commands I would want to be genuinely allowed. As I said this is for system administrators first, and I'd like to forcibly instil the habit of sudo <command> or using rootsh to get an audited shell. But I know people are already not doing enough sudo <command> as it stands, rather they switch to bash.
I'm currently looking at a Mac Terminal tutorial:[URL]... I want to learn about Linux Terminal, is there a difference between the Mac Terminal and Linux Terminal commands and Internet tutorials?
is there a way to edit which commands require a sudo? or some programs, like the CPU frequency monitor on panel, requires a password to change. where would i start if i want to change this?
I am a Mac/ Windows user, forced to use Linux for my college work. I do not know where to enter commands like $ sudo /usr/etc/eth0 mvntz -do4i or how to make them work
I had a problem - the Wi-fi card in my laptop was not working. All the forums were useless. They wanted me to READ about wireless networking !
Finally a good friend solved the problem in a simple way : it appears Ubuntu has not installed the drivers for my Broadcom wireless card since it was not open source. I had to download it myself. Here is how : Go to System menu on the top bar. Choose administration/ hardware devices. Tell it to activate the device. It will download the drivers through the cable attached to DSL modem and install.
Then clicked the network icon, selected edit connections, and entered my wireless network name and password. This solved all problems.
Why doesn't Linux give me a warning that the driver for something is not yet installed ? When I was struggling with the network setup wizard for the whole day, there was no clue about the missing driver.
What are the differences if I build (./configure, make, make install) an app when log in as root vs a "regular" user other than I have to use sudo for make install? If an app is built from a non-root account, will it be available to every other user on the system?