James Knott wrote:

Susemail wrote:

...

How am I, a humble user, able to use programs like konsole that are owned by root?

Konsole (and all other KDE programs) is owned by root, but the permissions are set 755 making them executable by anyone. However, if you're looking for a root Konsole window, look below.

You have my permission to use them. ;-)

Actually, there are few ways. One, is to open a text session, and using the sux command, become route.

This does not work by default in SuSE... You will get this error: "cannot connect to X server linux.site:0.0" There are various reasons for this, one of them being security. Use the command kdesu [program that you wish to run]. An example: bmo@linux:~> kdesu konsole &<enter> This will open a new konsole window with a root prompt. -- BMO

Doug B wrote:

su will give you the error

sux will work (I think of it as su(for)x).

That's weird. I typed sux and then tried to open a konsole like above and I got the x server error above, but when I used the full path /usr/X11R6/bin/sux, it worked. And now when I tried sux again, without the path, it worked. Whee. Something is broken, obviously...and I'm not gonna look at this point. Is there a gnomesu? Why yes, yes there is! Ah, this is how Linux (and unix) is... a zillion ways to skin the same cat. -- BMO

On Sunday 02 January 2005 05:21 pm, Daniel Podgurski wrote:

Doug B wrote:

...

su will give you the error

sux will work (I think of it as su(for)x).

That's weird. I typed sux and then tried to open a konsole like above and I got the x server error above, but when I used the full path /usr/X11R6/bin/sux, it worked.

And now when I tried sux again, without the path, it worked. Whee. Something is broken, obviously...and I'm not gonna look at this point.

I can confirm that behavior. For the first time I can remember, sux - gave me the cannot connect to X server doug.at-random:0.0 error. Exit and sux - again and it worked. Doug

On Mon, 2005-01-03 at 04:27, Daniel Podgurski wrote: snip

...

Actually, there are few ways. One, is to open a text session, and using the sux command, become route.

This does not work by default in SuSE...

You will get this error: "cannot connect to X server linux.site:0.0" There are various reasons for this, one of them being security.

Use the command kdesu [program that you wish to run].

An example:

bmo@linux:~> kdesu konsole &<enter>

This will open a new konsole window with a root prompt.

Dear Daniel, Thank you very much for this "kdesu program name & <enter>" It does what sux and quite a few other suggestions I have seen do not do in Suse. sux - seems to work in other distros but not in Suse. I've been looking for a fix for quite a while. Gustav Degreef.

rada and gus writes:

... sux - seems to work in other distros but not in Suse.

It sounds funny since, IMHO, SuSE was the first distro that contained the command. Just have a look who its author is: $ cat /usr/X11R6/bin/sux ... # Copyright 2000 SuSE GmbH # Copyright 2004 SuSE LINUX AG # Author: Werner Fink ... It works OK here (9.2, 9.1, ...) -- A.M.

rada and gus wrote:

...

$ cat /usr/X11R6/bin/sux ... # Copyright 2000 SuSE GmbH # Copyright 2004 SuSE LINUX AG # Author: Werner Fink

Hello I guess you have discovered another new headachce caused by security. While logged in as a user In a xterm or konsole log in as root (su or sux), try to execute anything. Error! Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key myprogram: cannot connect to X server :0.0 This is another reason that root is not equal to "su" or "sux" Error! cannot connect to X server mysite.org:0.0 Remember that you have been told you should not be logged in as "root". That is evil! Long and short is that SuSE and/or X.org have rigged xlib for security (I guess) that root can not share the X server with a user. I think this started around SuSE 9.0 This is similar to the permission problems found in the past with xcdroast and a /dev/cdrom. root was told xcdroast was dangerous and a user could use the CD but xcdroast would work. -- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316

rada and gus writes:

...

...

... sux - seems to work in other distros but not in Suse. ... It works OK here (9.2, 9.1, ...)

Thanks, you're right. I'm using 9.1 pro. I tried it again here today and it does work. It's quite odd, sometimes it does not work, this has happened on more than one machine. Could it be some process I've turned on/off at times?

Are you sure the problem is with sux and not KDE? You can test the access to your X-server with for instance "xterm". This command shouldn't be affected by problems with KDE configuration. -- A.M.

The Saturday 2005-01-08 at 20:12 +0530, rada and gus wrote:

...

Are you sure the problem is with sux and not KDE? You can test the access to your X-server with for instance "xterm". This command shouldn't be affected by problems with KDE configuration.

xterm runs just fine. Maybe it is a KDE configuration problem. Makes sense since sux seems to work just fine for most people. Where to look for the problem since some others seem to also to have had the problem? Thanks for the feedback. Gustav Degreef.

After doing "sux -", start some graphic program, but not a kde one. Or try several, some kde, some generic, some gnome, for example. Maybe try ethereal, gkrellm, yast... -- Cheers, Carlos Robinson

I use kwrite to edit config files or files owned by root and I use konqueror to navigate in folders that I do not have access or write permissions. So it is very handy to sux - from a user console, edit a file with kwrite, close kwrite and exit from root back to my user console. Same with konqueror.

I am sure there are other ways of doing the same things (I've tried joe, emacs and vi but find them too complex for simple tasks), but at my level this seems the most intuitive and the quickest. A quicker way might be to use mc. This has got to be one of the most useful apps for me. It has a file manager (2 panes), a very intuitive editor (much easier to use than vi), plus many more features. It is to Linux what Norton Commander was to DOS, but even better. It is faster

rada and gus wrote: than a GUI (great for using over ssh) but is as easy to use. I highly recommend it. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871

On Mon, 2005-01-10 at 21:27, Carlos E. R. wrote:

The Monday 2005-01-10 at 15:50 +0530, rada and gus wrote:

...

...

After doing "sux -", start some graphic program, but not a kde one. Or try several, some kde, some generic, some gnome, for example. Maybe try ethereal, gkrellm, yast

Thanks for the input.

When I try it on my 9.1 system now it seems to run everything fine after sux - xgnokii, kwrite, gmplayer, gtoaster, konqueror all seem to run fine. Seems I can't reproduce it.

Yesterday on my friends dell laptop running 9.2 I had constant problems "can't connect to X-server", though periodically it would work - can't precisely recall how and when.

The problem is not critical but also not academic. I am not a newbie, but far from an expert. I use two main programs from a root console - namely kwrite and konqueror. I use kwrite to edit config files or files owned by root and I use konqueror to navigate in folders that I do not have access or write permissions. So it is very handy to sux - from a user console, edit a file with kwrite, close kwrite and exit from root back to my user console. Same with konqueror.

Well, then it seems clear that there is some problem with 9.2. But it is too foggy. My guess is that it is related to kde, so try some gnome editor instead: for example gedit.

As for navigating directories, I concur with Joe: I simply love 'mc'. It is text based, but menu driven (accepts mouse input), very fast and practical. And you can use it over a modem link.

Thanks for the suggestions Joe and Carlos about mc and gedit. Sounds good. I think you are right about it being a KDE problem, though I have not been able to prove it. I remembered I had recently upgraded KDE in 9.1 via Yast and I thinking back perhaps that's when the problem went away on 9.1 - and in the 9.2 systems where it seems to be a problem I had not upgraded KDE. I'll have to check that out. Gustav Degreef.

On Friday 07 January 2005 9:13 pm, Carlos E. R. wrote:

The Friday 2005-01-07 at 22:13 +0530, rada and gus wrote:

...

Thank you very much for this "kdesu program name & <enter>" It does what sux and quite a few other suggestions I have seen do not do in Suse. sux - seems to work in other distros but not in Suse. I've been looking for a fix for quite a while. Gustav Degreef.

The command "sux -" has always worked for me in several suse versions, since I tried it time ago. I'm currently using version 9.1. I must add my voice to Carlos and the others .. I've never had it fail to work here. 5 boxen mainly 9.2 and one waiting for it's new video card to upgrade from9.1- 9.2

-- j nemo me impune lacessit 'Quis custodiet ipsos custodiates?'

On Sunday 02 January 2005 13:00, Doug B wrote:

On Sunday 02 January 2005 04:31 pm, Susemail wrote:

...

How am I, a humble user, able to use programs like konsole that are owned by root?

I'm going to interpret your question a little different from James.

~> ls -l /opt/kde3/bin/konsole -rwxr-xr-x 1 root root 8123 2004-10-05 12:26 /opt/kde3/bin/konsole

Disregard the first '-' in '-rwxr-xr-x' for this.

the rwx are owner permissions Read - Write - eXecute the next r-x are group permissions read - execute only... no changing it. the next r-x are permisions for everyone else. read and execute.

In this case, the great root has decided to share the right to execute this program that it owns.

But then, maybe that isn't what you wanted to know...

Or, maybe it is exactly what I needed to know! Why yes, yes it is! Thanks, Jerome

Doug