On Sun, 18 May 2003, Patrick Shanahan wrote:

* David List [05-18-03 08:47]:

...

I have a system with SuSE Linux 7.3 installed, and I believe some of the system packages need updating. The system is running without monitor and keyboard, I administrate it through ssh sessions.

What can I do to use SuSE's update service? When I issue 'yast2', I get a message about the X11 connection being rejected (of course!).

?? I would try 'yast', the cl version, not 'yast2', the graphic version. ?? Just a guess.

It's just that I don't see any options in the old YaST for updating the system. I had that in YaST2 which I had access to while having monitor and keyboard on the system right after I did the installation. Is there any way of invoking the YaST2 version coming with SuSE Linux 7.3 so that it can be used from a tty? I know it is possible with the YaST2 versions coming with newer SuSE Linux versions. Best regards, David List

On Sun, 18 May 2003, Charles Philip Chan wrote:

Turn X11 forwarding on and if you usually log in to the machine as a regular user then su to root- make sure you use sux instead.

That worked. Thanks.

Of course you can do it in good old YaST1. Just go to install software, choose ftp as the source and point it to the 7.3 update directory on the SuSE site or the mirror of your choice.

Hmmm...will try that also. Thank you for your answer. Best regards, David List

On Sun, 18 May 2003, Jason wrote:

You might like to have a look at the Fou4s script: http://fou4s.gaugusch.at/ A replacement for YOU. I used it before updating to 8.2, because YOU in 8.1 took an absolute age to work.

I'll have a look at it.

You could also try connecting to your server using "ssh -X" and starting Yast2. The Yast window should be forwarded to your local screen.

I am doing just that right now. It worked. Thank you for your answer. Best regards, David List

"Carlos E. R." [18 May 2003 22:04:54 +0200 (CEST)]:

Funny: that yast2 is able to run in console, but when it sees the X session it tries it.

What it's looking for is a set DISPLAY environment variable.

I wonder if there is an option to force it to use the console? In suse 8.1, yast will run yast2 in text mode.

Simply do 'DISPLAY= yast2' this will effectively make DISPLAY unset and thus the text mode UI will be used. Philipp

The 03.05.19 at 07:12, David List wrote:

On Mon, 19 May 2003, Philipp Thomas wrote:

...<snip>...

...

Simply do 'DISPLAY= yast2' this will effectively make DISPLAY unset and thus the text mode UI will be used.

I get y2controlcenter: cannot connect to X server yast2 after having issued # export DISPLAY=yast2 on my SuSE Linux 7.3 system.

I have not my 7.3 running right now, but try something like: DISPLAY=; yast2 or unset DISPLAY; yast2 or unset DISPLAY; su - 'DISPLAY= yast2' will set DISPLAY to yast2, instead of running yast2 with DISPLAY unset, which was what Philipp meant, I guess. -- Cheers, Carlos Robinson

On Monday 19 May 2003 11.33, Carlos E. R. wrote:

'DISPLAY= yast2' will set DISPLAY to yast2, instead of running yast2 with DISPLAY unset, which was what Philipp meant, I guess.

I very much suspect he meant DISPLAY= yast2, with a space between = and yast2. This will unset the environment variable DISPLAY for the command only, and not for the rest of the session. DISPLAY=<space>yast2

On Monday 19 May 2003 14.33, Jerry Feldman wrote:

On Mon, 19 May 2003 14:14:48 +0200

Anders Johansson wrote:

...

I very much suspect he meant DISPLAY= yast2, with a space between = and yast2. This will unset the environment variable DISPLAY for the command only, and not for the rest of the session.

DISPLAY=<space>yast2

This shouold cause an error message.

What makes you think that? Naturally I didn't mean you should actually write the character for less-than, followed by s p a c e, folllowed by the character for greater than. I just wrote it that way for emphasis, since spaces have a tendency to disappear in some fonts

Also, DISPLAY=yast2 will set the local shell variable, DISPLAY, not the environment variable. To set an environment variable, you must either export a shell variable: export DISPLAY

or set it: export DISPLAY=yast2

There is no theoretical difference, only a difference in scope. setting a variable the way you mention will set it for the current shell, and all programs run from that shell. Setting it the way I mentioned above (and Philipp, in a previous mail) will set it for the current command only. That command will see it in its environment array

On Mon, 19 May 2003 14:38:02 +0200 Anders Johansson wrote:

What makes you think that? Naturally I didn't mean you should actually write the character for less-than, followed by s p a c e, folllowed by the character for greater than. I just wrote it that way for emphasis, since spaces have a tendency to disappear in some fonts Next time, I'll finish my first coffee before I respond :-)

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

The 03.05.19 at 14:14, Anders Johansson wrote:

On Monday 19 May 2003 11.33, Carlos E. R. wrote:

...

'DISPLAY= yast2' will set DISPLAY to yast2, instead of running yast2 with DISPLAY unset, which was what Philipp meant, I guess.

I very much suspect he meant DISPLAY= yast2, with a space between = and yast2. This will unset the environment variable DISPLAY for the command only, and not for the rest of the session.

DISPLAY=<space>yast2

Could be, but it doesn't work. His intention, i think, was to unset DISPLAY, but it can not be done that way; Look: cer@nimrodel:~> set |grep DISPLAY DISPLAY=:0 cer@nimrodel:~> DISPLAY= set |grep DISPLAY DISPLAY=:0 You see? With two spaces, "display" is still set. However, if I su to root like this (a login shell): cer@nimrodel:~> su - Password: nimrodel:~ # set |grep DISPLAY nimrodel:~ # it is also solved - this is the way I normally work when I have to be root, by the way. -- Cheers, Carlos Robinson

David List [Mon, 19 May 2003 07:12:13 +0200 (CEST)]:

...

Simply do 'DISPLAY= yast2' this will effectively make DISPLAY unset and thus the text mode UI will be used.

y2controlcenter: cannot connect to X server yast2 after having issued # export DISPLAY=yast2 on my SuSE Linux 7.3 system.

You misunderstood me. Don't do the export but issue *as one command*: DISPLAY= yast2 ^ This space is significant Philipp

The 03.05.19 at 14:51, Philipp Thomas wrote:

You misunderstood me. Don't do the export but issue *as one command*:

DISPLAY= yast2 ^ This space is significant

It doesn't work, not on an xterm: cer@nimrodel:~> set | grep DISPLAY DISPLAY=:0 cer@nimrodel:~> DISPLAY= set | grep DISPLAY DISPLAY=:0 cer@nimrodel:~> However: cer@nimrodel:~> DISPLAY= ;set | grep DISPLAY DISPLAY= cer@nimrodel:~> -- Cheers, Carlos Robinson

The 03.05.20 at 01:46, Anders Johansson wrote:

set is a shell builtin, and so is echo. That must be why it doesn't work for them, they must handle things differently compared to normal programs.

I stand corrected: cer@nimrodel:~> DISPLAY= bash -c set | grep DISPLAY DISPLAY=

Did you look at the C prog I posted? It's very short

Grumble, grumble :-) [...] Mmm, it needs "#include " as well. cer@nimrodel:~/bin> DISPLAY= testenvironment | grep DISPLAY env 1 is DISPLAY= DISPLAY is set to Ok, then it works for binaries, but not for builtins. What about scripts? [...] #!/bin/bash set | grep DISPLAY cer@nimrodel:~/bin> DISPLAY= ./testenvironmentscript DISPLAY= Ok, it works as well, because it gets it's own shell. Interesting... -- Cheers, Carlos Robinson