You may be asked to open a terminal and give the result of a command. Sometimes you will need to be su - This is just to show you how. Open a terminal, type su - (Notice the - ) and hit enter. It will request your root password, enter it (by default nothing displays as you type - but just type) hit enter and you should see the end of the prompt turn to # and probably the colour of the line will change. http://thumbnails18.imagebam.com/5906/69215059051496.gif](http://www.imagebam.com/image/69215059051496)
No complaints please about this being too simple. It’s for Noobs;)
[EDIT] I have changed previously quoted su to su -
which after consulting the members, is the more accurate way. The right/correct way. Thanks. This is the benefit of the forum friends. I stand corrected.
When as a noob’s you are asked to post the results of su <command> output to us here in a forum, it can be helpful to describe an easy way to copy/paste the output to the forums. I use an arkayic method cause for some reason my copy paste doesn’t seem to work in a terminal.
sudo <command> >>$HOME/cmd.txt
then open open cmd.txt in editor and copy paste from there.
If you create a launcher in the panel with the command kdesu konsole, then every time you need it just click and type your password. Simple and faster.
On Sun, 01 Nov 2009 09:08:20 +0000, palladium wrote:
>> type su and hit enter
>
> i suggest it should read
>
> type su - (don’t forget the dash) and press enter or type “su -”
> (without the quotes) and hit enter
Actually, either should work just fine. The difference between the two
is that adding “-” initiates a login shell, but I’ve never run into a
situation where the ‘-’ was absolutely required. That might be because
my paths for root and non-root tend to be the same, and I don’t care if
the system puts me in root’s home directory or not.
Too funny! I’ve been copy pasting by piping to text file then copy pasting from there and now I see ‘shift’ + ctrl. Mouse method works with actual mouse but my touchpad won’t do copy paste even in text editor.
I don’t think it will magically change by itself the more you keep using the system
I’ve never had to change anything on various SUSE versions and it has always been like that so I never had problems with ‘su’ which would force me to use a login shell with ‘su -’
below are a baker’s dozen quotes followed by a cite all from opensuse.org sources (i’ll look outside our walls later, if i remember):
“There is a problem starting YaST with the new Qt/KDE if you don’t
have a login shell as root (in other words, if you do “su” instead of
“su -” for example). The symptom is that YaST does not show any Qt UI
(note the control center works, just launching any YaST module
hangs).” <http://en.opensuse.org/KDE/KDE4>
“The PATH is still “my” PATH. I do not know if this is correct (as
said, I never realy studied sudo). But I always stick to
Code: su -
(mind the - ) or a real log in (as with the terminal) because it gives
root its own environment. Much better for scurity. The user PATH can
contain all sorts of places (like ./ ) where a program may have the
same name as a tool you want to use as root!”
<http://forums.opensuse.org/applications/405254-sudo-whatever-command-not-found-2.html#post1929115>