After some fair time playing with SuSE 7.2, I regret to say I still have some gaps in my knowledge which often give rather fundamental problems with installation of software outside YAST's framework. Hey, I *CAN* do things like set up Cups with Gimp Print and configure Samba, Apache and Tomcat etc., so (hopefully!) I'm not a complete dummy - But the following STILL elude me... 1) X-applications work OK under a user account but I often have problems when some applications or (graphical?) installation procedures require "su"-ing or indeed run under root because of errors like: Xlib: connection to ":0.0" refused by server etc. etc. ISTR on unix systems setting and exporting the DISPLAY variable but can't get anywhere far with that one. Fwiw, all my users and root echo $DISPLAY as ":0.0" Now I kinda "know" the display should be a bit more substantial than just ":0.0" but WHERE is that "0.0" being set up and WHERE do I correct it and to WHAT?? I use the default bash shell and can e.g. make changes to my .bashrc file or whatever is most appropriate... 2) Next: For networking applications, I don't MIND the system being identified as "linux", "localhost" (or whatever it b*** well wants! <grin> but I'd *like* it to be called something more imaginative- like "anubis", so WHERE do I set that up?? I notice e.g. where I set up the NIC I/P address (192.168.0.1) under "YAST > Network/Basic", it allows for a "hostname" & "domain name" - set to "linux" and "local" at the moment. But is THAT the correct place?? Or should I be doing something with /etc/hosts etc. Is the "domain" name above also likely to be the workgroup name ("ennead") that I use for identifying my windows systems? 3) (Finally!) Some applications FAIL with problems with a "LOCALE" setting. Some just warn and default to "C" - But some others just bomb out. I thought the locale WAS correctly set up correcly... for the UK - under the dialog for YAST>Personalization>Country&Language, but maybe I'm missing something? Sorry for being a bit verbose and for the confusion, but I just want to get some of these things NAILED finally - No urgency, but if someone has the patience, I'd be very grateful! :-) Chris
On Friday 28 June 2002 03.41, Chris Roberts wrote:
After some fair time playing with SuSE 7.2, I regret to say I still have some gaps in my knowledge which often give rather fundamental problems with installation of software outside YAST's framework. Hey, I *CAN* do things like set up Cups with Gimp Print and configure Samba, Apache and Tomcat etc., so (hopefully!) I'm not a complete dummy - But the following STILL elude me...
1) X-applications work OK under a user account but I often have problems when some applications or (graphical?) installation procedures require "su"-ing or indeed run under root because of errors like:
Xlib: connection to ":0.0" refused by server etc. etc.
ISTR on unix systems setting and exporting the DISPLAY variable but can't get anywhere far with that one. Fwiw, all my users and root echo $DISPLAY as ":0.0" Now I kinda "know" the display should be a bit more substantial than just ":0.0" but WHERE is that "0.0" being set up and WHERE do I correct it and to WHAT?? I use the default bash shell and can e.g. make changes to my .bashrc file or whatever is most appropriate...
All access permissions to the running X server are owned by the user that started it. X doesn't care about root or superuser, only about owner. There are three ways of giving permission 1. As the user that started X, run "xhost +inet:localhost" This will allow any user running on the local machine to use the X server. 2. Instead of "su" use "sux". sux is a little script written by SuSE that automate the giving of access permissions. 3. As root, after su, and after setting DISPLAY to :0.0, do "export XAUTHORITY=/home/<user>/.Xauthority" where <user> is the user that started X.
2) Next: For networking applications, I don't MIND the system being identified as "linux", "localhost" (or whatever it b*** well wants! <grin> but I'd *like* it to be called something more imaginative- like "anubis", so WHERE do I set that up?? I notice e.g. where I set up the NIC I/P address (192.168.0.1) under "YAST > Network/Basic", it allows for a "hostname" & "domain name" - set to "linux" and "local" at the moment. But is THAT the correct place??
yes.
Or should I be doing something with /etc/hosts
/etc/hosts is the old way of translating hostnames to ip numbers. If you set a hostname you will want to make an entry in that file translating the hostname to 127.0.0.1, but yast will do that for you.
etc. Is the "domain" name above also likely to be the workgroup name ("ennead") that I use for identifying my windows systems?
No, it is the internet domain your computer is on.
3) (Finally!) Some applications FAIL with problems with a "LOCALE" setting. Some just warn and default to "C" - But some others just bomb out. I thought the locale WAS correctly set up correcly... for the UK - under the dialog for YAST>Personalization>Country&Language, but maybe I'm missing something?
What is it set to? I'm guessing it's set to something@euro. Edit this in /etc/rc.config and remove the @euro part. Or change it to en_IE@euro. IIRC Irish English is the only locale set up for euro support. regards Anders -- `When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.'
2002-06-28 02.50 skrev Anders Johansson: :: There are three ways of giving permission :: ... and yet another: sudo Here's a mini-howto: 1. run visudo Visudo requires basic vi skills; if you don't know vi run the program "vimtutor" or -close to blasphemy- export EDITOR=mcedit. 2.add the follwing line Chris ALL=(ALL) NOPASSWD:ALL Alternatively add yourself to the group wheel and add %wheel ALL=(ALL) NOPASSWD:ALL instead Now you just type "sudo yast2" or whatever you want to run in X as root. Best regards Anders -- Today is the tomorrow you worried about yesterday
Thank you Anders and those who replied to this one. Most of these little Gremlins are now laid to rest :-) The "sux" command proved particularly userful. Various warnings about locale occasionally come up, but I now know how to get round these. I suspect there are some funnies with changing locales via YAST with SuSE 7.2, but doubtless I will upgrade sometime, so these can be circumvented. Some of the applications e.g. my version of OpenOffice do indeed find it difficult to cope with Euro enabled locales and THAT was the problem here. Maybe that's a sign of the times - or a portent <G> Thanks again, Chris On Friday 28 June 2002 00:50, you wrote:
3) (Finally!) Some applications FAIL with problems with a "LOCALE" setting. Some just warn and default to "C" - But some others just bomb out. I thought the locale WAS correctly set up correcly... for the UK - under the dialog for YAST>Personalization>Country&Language, but maybe I'm missing something?
What is it set to? I'm guessing it's set to something@euro. Edit this in /etc/rc.config and remove the @euro part. Or change it to en_IE@euro. IIRC Irish English is the only locale set up for euro support.
regards Anders
Chris Roberts wrote:
After some fair time playing with SuSE 7.2, I regret to say I still have some gaps in my knowledge which often give rather fundamental problems with installation of software outside YAST's framework. Hey, I *CAN* do things like set up Cups with Gimp Print and configure Samba, Apache and Tomcat etc., so (hopefully!) I'm not a complete dummy - But the following STILL elude me...
1) X-applications work OK under a user account but I often have problems when some applications or (graphical?) installation procedures require "su"-ing or indeed run under root because of errors like:
Xlib: connection to ":0.0" refused by server etc. etc.
xhost +localhost before su
ISTR on unix systems setting and exporting the DISPLAY variable but can't get anywhere far with that one. Fwiw, all my users and root echo $DISPLAY as ":0.0" Now I kinda "know" the display should be a bit more substantial than just ":0.0" but WHERE is that "0.0" being set up and WHERE do I correct it and to WHAT?? I use the default bash shell and can e.g. make changes to my .bashrc file or whatever is most appropriate...
2) Next: For networking applications, I don't MIND the system being identified as "linux", "localhost" (or whatever it b*** well wants! <grin> but I'd *like* it to be called something more imaginative- like "anubis", so WHERE do I set that up?? I notice e.g. where I set up the NIC I/P address (192.168.0.1) under "YAST > Network/Basic", it allows for a "hostname" & "domain name" - set to "linux" and "local" at the moment. But is THAT the correct place?? Or should I be doing something with /etc/hosts etc. Is the "domain" name above also likely to be the workgroup name ("ennead") that I use for identifying my windows systems?
3) (Finally!) Some applications FAIL with problems with a "LOCALE" setting. Some just warn and default to "C" - But some others just bomb out. I thought the locale WAS correctly set up correcly... for the UK - under the dialog for YAST>Personalization>Country&Language, but maybe I'm missing something?
Sorry for being a bit verbose and for the confusion, but I just want to get some of these things NAILED finally - No urgency, but if someone has the patience, I'd be very grateful! :-)
Chris
participants (4)
-
Anders Dahlqvist -
Anders Johansson -
Chris Roberts -
Dominique Michel