Ed Harrison wrote:

James Knott wrote:

...

In OpenSUSE 11.0, I just tried using the sux command but apparently it's no longer available. What replaces it?

tnx jk

su Su is there, as always, but it does not allow the use of X displays. For example, if you use su and then start yast2, you'll get the ncurses display, instead of the X version. On earlier version, you'd use sux, to run X apps.

-- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 22 June 2008 18:15:58 Ed Harrison wrote:

James Knott wrote:

...

Ed Harrison wrote:

...

James Knott wrote:

...

In OpenSUSE 11.0, I just tried using the sux command but apparently it's no longer available. What replaces it?

tnx jk

su

Su is there, as always, but it does not allow the use of X displays. For example, if you use su and then start yast2, you'll get the ncurses display, instead of the X version. On earlier version, you'd use sux, to run X apps.

On my 10.3, /usr/bin/sux is just a link to /bin/su. If I type "su" and enter password, I get a red command prompt.

yast gives me ncurses; yast2 gives me the graphical interface. Only thing in 11.0 is the sux symlink is missing.

Ed

Have you tried 'kdesu' in lieu of 'sux'? P. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

Ed Harrison wrote:

...

James Knott wrote:

...

Ed Harrison wrote:

...

James Knott wrote:

...

In OpenSUSE 11.0, I just tried using the sux command but apparently it's no longer available. What replaces it?

tnx jk

su Su is there, as always, but it does not allow the use of X displays. For example, if you use su and then start yast2, you'll get the ncurses display, instead of the X version. On earlier version, you'd use sux, to run X apps.

On my 10.3, /usr/bin/sux is just a link to /bin/su. If I type "su" and enter password, I get a red command prompt.

yast gives me ncurses; yast2 gives me the graphical interface. Only thing in 11.0 is the sux symlink is missing.

Ed I just created that link and it doesn't fix the problem. The ncurses version of yast2 still comes up. One thing to bear in mind is that an application can examine the name used to call it and then react accordingly. So, in 10.3, su would do something different when called with sux, than when called with su.

It works now, after logging out and back in again (via ssh). I wonder who forgot that symlink? -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-22 at 13:36 -0400, James Knott wrote:

...

...

...

...

James Knott wrote:

...

In OpenSUSE 11.0, I just tried using the sux command but apparently it's no longer available. What replaces it?

...

...

On my 10.3, /usr/bin/sux is just a link to /bin/su. If I type "su" and enter password, I get a red command prompt.

...

I just created that link and it doesn't fix the problem. The ncurses

It works now, after logging out and back in again (via ssh). I wonder who forgot that symlink?

It is intentional. You should use "su -" and it should just work. If it doesn't, it is a bug and you should report it to bugzilla. By the way, 'yast' calls the ncurses interface, whereas 'yast2' calls the graphical one. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIXqovtTMYHG2NR9URAnaqAJoCFw0Zr6CornDHEcJh/45zvhgdEQCgg6RC h3rybI0tZ4bGqOogkT0pNzk= =Zlgg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-22 at 16:01 -0400, James Knott wrote:

...

It is intentional.

You should use "su -" and it should just work. If it doesn't, it is a bug and you should report it to bugzilla.

By the way, 'yast' calls the ncurses interface, whereas 'yast2' calls the graphical one.

I am well aware of the difference between yast & yast2 and was calling yast2.

Ok then, if you type "su -" and then "yast2" and you get the ncurses interface, it is a bug you should report in bugzilla. sux is deprecated and shouldn't be there. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIXs+PtTMYHG2NR9URAnBJAKCHvroon4EQpuwPX+bdSEcOyb9UfgCdHLUp eMlxPhkc+oIze5zgr7qhdgc= =la6V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, Jun 22, 2008 at 3:21 PM, John Andersen wrote:

On Sun, Jun 22, 2008 at 3:17 PM, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-06-22 at 16:01 -0400, James Knott wrote:

...

...

It is intentional.

You should use "su -" and it should just work. If it doesn't, it is a bug and you should report it to bugzilla.

By the way, 'yast' calls the ncurses interface, whereas 'yast2' calls the graphical one.

I am well aware of the difference between yast & yast2 and was calling yast2.

Ok then, if you type "su -" and then "yast2" and you get the ncurses interface, it is a bug you should report in bugzilla.

Not a bug, Carlos, its a feature! (Documented).

Yast2, sensing no X server available, drops back to yast (ncurses). Its by design.

Happens on ssh too if your forget to forward X session.

From man yast2:

YaST2 comes with three frontends: GTK , QT and ncurses. All frontends are functionally equivalent. The correct frontend is selected automat‐ ically based on the available components and the current environment (the DISPLAY variable). -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Carlos E. R." To: "OS-en" Sent: Sunday, June 22, 2008 6:44 PM Subject: Re: [opensuse] No sux in 11.0? The Sunday 2008-06-22 at 15:30 -0700, John Andersen wrote:

...

...

Ok then, if you type "su -" and then "yast2" and you get the ncurses interface, it is a bug you should report in bugzilla.

Not a bug, Carlos, its a feature! (Documented).

Yast2, sensing no X server available, drops back to yast (ncurses). Its by design.

Happens on ssh too if your forget to forward X session.

...

From man yast2:

YaST2 comes with three frontends: GTK , QT and ncurses. All frontends are functionally equivalent. The correct frontend is selected automat‐ ically based on the available components and the current environment (the DISPLAY variable).

Ok, but if you do "su -" and you can not start the graphical interface it is a bug. Try with another program, like "xeyes", or any other graphical program you choose. The "DISPLAY" must be set, if it is not, it is a bug, as sux is deprecated. I can't run now my factory setup and test it myself. -------------- su -c xlogo should work, as long as xhost/xauth allows it. su - -c xlogo should not work. sudo xlogo should work, as long as xhost/xauth allows it. gksudo xlogo should work. su - drops most of your current enviroment and starts a new, empty one, by design. That is specifically why su has the - option. Sometimes it's utterly wrong and dangerous and unexpected to have DISPLAY set to anything at all, let alone a valid x session. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-22 at 15:21 -0700, John Andersen wrote:

...

Ok then, if you type "su -" and then "yast2" and you get the ncurses interface, it is a bug you should report in bugzilla.

Not a bug, Carlos, its a feature! (Documented).

Documented where? :-?

Yast2, sensing no X server available, drops back to yast (ncurses). Its by design.

It doesn't on my 10.3 using "su -".

Happens on ssh too if your forget to forward X session.

But it shouldn't when using "su -" as there is an X session. That's a bug. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIXtRJtTMYHG2NR9URAobXAJ9WQM1IOE0buMZKGVHuubyMBCuG7ACbBoQc jHHFElkzQez45UATjwVfnBg= =g9q3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-22 at 15:41 -0700, John Andersen wrote:

...

Documented where? :-?

You replied too soon. I followed up with info from man yast2

Yep, saw it later :-)

...

But it shouldn't when using "su -" as there is an X session. That's a bug.

Its the DISPLAY environmental it looks for. Was that set?

In 10.3, it is: nimrodel:~ # echo $DISPLAY :0.0 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIXtcctTMYHG2NR9URAvOFAJ9mkZWuErqIV3J5WuoAGHX11d0jbgCeJ8qq mH0P5Ct9M138HTBt66qtX0k= =9SUz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "James Knott" To: "SUSE Linux" Sent: Sunday, June 22, 2008 12:56 PM Subject: Re: [opensuse] No sux in 11.0?

Ed Harrison wrote:

...

James Knott wrote:

...

In OpenSUSE 11.0, I just tried using the sux command but apparently it's no longer available. What replaces it?

tnx jk

su Su is there, as always, but it does not allow the use of X displays. For example, if you use su and then start yast2, you'll get the ncurses display, instead of the X version. On earlier version, you'd use sux, to run X apps.

gnomesu / kdesu for starters. Or just plain su / sudo and the clue that when you su, or especially su -, you move into a new environment and therefor may need to set & export some environment variables that didn't get passed along, like, export DISPLAY=:0, and possibly using xhosts before su to allow your new self permission to access your x session. Or setting up things so that root coming from loccalhost always has permission. Yeah, it's a little work, thats a teeny part of why I just use the text interface 99.9% of the time anyways. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Marcus Meissner wrote:

Well, I get the X version after using su... Since 10.3.

well... to help fixing the discussion (and help me :-) could you exactly list the commands necessary to have yast2 run in X mode on a remote server, when calling through ssh at home? because simply making ssh (...), su -, and yast2 gives ncurse (local 10.3, remote 10.2) thanks jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Jun 23, 2008 at 12:15 AM, Marcus Meissner wrote:

On Mon, Jun 23, 2008 at 09:07:53AM +0200, jdd sur free wrote:

...

Marcus Meissner wrote:

...

Well, I get the X version after using su... Since 10.3.

well... to help fixing the discussion (and help me :-) could you exactly list the commands necessary to have yast2 run in X mode on a remote server, when calling through ssh at home?

because simply making ssh (...), su -, and yast2 gives ncurse (local 10.3, remote 10.2)

do you start yast2 on the 10.2 or 10.3 machine?

I just did: ssh -X meissner@103machine su - yast2

gives me the nice graphical interface.

Ciao, Marcus

This works for me on 10.3 as well. But the original post indicate a problem doing this to 11.0 -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-23 at 09:15 +0200, Marcus Meissner wrote:

I just did: ssh -X meissner@103machine su - yast2

gives me the nice graphical interface.

Yes, in 10.3 it works, but not in 11.0. And it works if instead of 'su' you use 'sux', but you have to create the 'sux' symlink first. The allegation (made by Brian) is that exporting DISPLAY may be dangerous and contrary to the policy of "su -" of dropping the original user's environment. So a clarification of all this would be needed, from someone in the know, so that we know if it is intentional or accidental (thus a bug), and if the solution is to create the symlink again, manually, or to use "su" instead of "su -", or we should use another incantation ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIX33ytTMYHG2NR9URAh4EAJ4nS7k3Sp7b5kqXEfNoZIhL6Yce/gCfR9wW kp4BpBUYO7qZ0M4Wh6TBqg4= =I4nE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-23 at 13:00 +0200, jdd sur free wrote:

...

And it works if instead of 'su' you use 'sux', but you have to create the 'sux' symlink first.

I fail to understand why a symlink may change a command behavior?? is there some alias working?

It is an interesting trick. See, the editor 'joe' behaves in a certain way. But if you call it via 'jstar' it behaves like wordstar. If you call it via 'jpico', then it behaves like 'pico'. The trick: lrwxrwxrwx 1 root root 3 2007-11-03 02:12 /usr/bin/jstar -> joe* lrwxrwxrwx 1 root root 3 2007-11-03 02:12 /usr/bin/jpico -> joe* The code determines at start under which name it has been called and changes its own behaviour. This way you only nees a binary with a set of akas. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIX43QtTMYHG2NR9URAnJWAKCJqRzugO41nvDoKAS/1sULBXj3VACfXJ8Z sjY4OnVxmHkS4UWh+E8Jy6A= =QnZB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

And it works if instead of 'su' you use 'sux', but you have to create the 'sux' symlink first.

I fail to understand why a symlink may change a command behavior?? is there some alias working?

It's a common thing that lots of programs do. They look at the name they were called by and behave differently, accordingly. It's as old as the hills and not unique to unix. A simple and old example is vi / view vi and view are the same program, vi, view is a symlink to vi. When you run vi you get the normal full vi. When you run view, you get a read-only mode of vi. There are tons of similar things. gzip/gunzip, bzip2/bunzip2, mc/mcedit/mcview, some programs have several modes. star recognizes and behaves differently in reaction to being called as, star, tar, gtar, pax, ustar, and I think a few others besides. Probably the most extreme example is busybox. One binary that replaces most of /bin and /usr/bin -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Jun 23, 2008 at 12:41:53PM +0200, Carlos E. R. wrote:

The Monday 2008-06-23 at 09:15 +0200, Marcus Meissner wrote:

...

I just did: ssh -X meissner@103machine su - yast2

gives me the nice graphical interface.

Yes, in 10.3 it works, but not in 11.0. And it works if instead of 'su' you use 'sux', but you have to create the 'sux' symlink first.

The allegation (made by Brian) is that exporting DISPLAY may be dangerous and contrary to the policy of "su -" of dropping the original user's environment.

So a clarification of all this would be needed, from someone in the know, so that we know if it is intentional or accidental (thus a bug), and if the solution is to create the symlink again, manually, or to use "su" instead of "su -", or we should use another incantation ;-)

I just tried with my 11.0 Laptop. ssh -X marcus@110laptop su - yast2 -> yast2 graphical interface on the machine where I ran ssh from. I do not see your problem I am afraid. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Jun 23, 2008 at 12:07 AM, jdd sur free wrote:

Marcus Meissner wrote:

...

Well, I get the X version after using su... Since 10.3.

well... to help fixing the discussion (and help me :-) could you exactly list the commands necessary to have yast2 run in X mode on a remote server, when calling through ssh at home?

because simply making ssh (...), su -, and yast2 gives ncurse (local 10.3, remote 10.2)

Well the risk of allowing root to log in with ssh2 is minimal, especially if you don't allow passwords or insist on long passwords. So, in my opinion the easiest way it to just allow root login via ssh, then set sshd on the target machine to only honor ssh2 and (optionally) disallow passwords, (requiring your public key being installed on the target machine). This is the first mention of ssh being involved, and its a slightly different problem than doing it at the console. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2008-06-23 at 09:07 +0200, jdd sur free wrote:

because simply making ssh (...), su -, and yast2 gives ncurse (local 10.3, remote 10.2)

thanks jdd Was that an omission in your post, or were you not using "ssh -X"? That would limit you to the ncurses terminal connection, and prevent you from running the graphical yast2...

Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Jun 24, 2008 at 7:46 AM, Greg Freemyer wrote:

To be explicit, from my workstation I did:

ssh -X <server> su yast2

To add to this thread, if you fix the site-wide /etc/ssh/ssh_config or your personal .ssh/ssh_config by un-commenting the line that says ForwardX11 yes then the -X is never necessary. * This is where the paranoid folks jump up and say if you ssh into a malicious site they will be able to use the X server on your machine for the duration of the connection. To which I reply: I don't have an account on any malicious site. -- ----------JSA--------- "Ubuntu" is an African word meaning "Suse is too hard for me". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Jun 24, 2008 at 2:45 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Tuesday 2008-06-24 at 10:46 -0400, Greg Freemyer wrote:

...

Maybe sux is no longer needed?

I'm still running 10.3, but I just tested ssh -X / su / yast2 (not sux) and it seemed to work fine (ie. I got an X-windows GUI presentation of yast).

This is not the OP problem. The problem is in 11.0 and without ssh:

su - yast2 --> gives no X access, thus the ncurses interface.

In 10.3 it works fine without sux.

On a local machine under 10.3, I use Alt-f2 - kdesu yast2. Does that work for kde in 11.0? No idea if gnome has an equivalent. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org