[SLE] Hostname in Suse 9.2 changes oddly - how to get the big pic on this (long)
Hi,
My PC had a reasonable host name, "linux" I think it was.
Then one gloomy day it somehow changed to "129". Now I am
looking for information about how the host setting works
in Suse 9.2; inspite of reading a wad of stuff and searching
and oggling web postings I seem not to understand the basic
concept of it and of the web settings related to it; like
domain name 'site'.
If you can point me to a source of good overview & necessary
details please do so. I'd be happiest if hit with terminology
one would use for describing quantum physics to an exceptionally
stupid rodent.
For some reason all the Linux books are either too complicated
(=only the variable details mentioned, not the context explained)
or if they are not, they entirely skip over the concept of
'How Linux understands and manages the internet / host settings
(or any other settings, for that matter) and what they
represent in the real world'.
Most of the info stuff is like "The Crdlbsklrching of Drdlbb
can be done either via skndrlzching the vrldnb instead of
drdlbb or, setting the variable BRLDFGGING=false or by modyifying
the respective settings of kjdhkjhkjhkj.conf or the file
kjdhkjhkjhkj.conf.local or by doing whatever your distro uses
for it's drdlbbsklrching."
Thanks,
Mike P.S.
If anyone has perverse fixation in the details of messed host
settings, the littany desribing mine is below. But rather than
getting a single thing fixed via external or divine intervention
I'd like to _understand_ how it all works. If that is possible.
On Monday 24 January 2005 13:17, Dumb Waiter wrote:
Hi,
My PC had a reasonable host name, "linux" I think it was. Then one gloomy day it somehow changed to "129". Now I am looking for information about how the host setting works in Suse 9.2; inspite of reading a wad of stuff and searching and oggling web postings I seem not to understand the basic concept of it and of the web settings related to it; like domain name 'site'.
If you can point me to a source of good overview & necessary details please do so. I'd be happiest if hit with terminology one would use for describing quantum physics to an exceptionally stupid rodent.
Oooh! Oooh! I know this one. Use the YaST configuration tool: YaST->Network Services->Host Names -or- YaST->Network Devices->Network Card->Change->Edit Select the "129" entry and edit it. If you're on a private network (or a standalone box) you can set the host name and domain name to anything you like. Enter something like "192.168.0.1", "myhost.mydomain", "myhost" in the fields. Save and your done. Jeff
On Mon, 24 Jan 2005 13:40:16 -0500, Jeffrey Laramie
On Monday 24 January 2005 13:17, Dumb Waiter wrote:
Hi,
My PC had a reasonable host name, "linux" I think it was. Then one gloomy day it somehow changed to "129". Now I am looking for information about how the host setting works in Suse 9.2; inspite of reading a wad of stuff and searching and oggling web postings I seem not to understand the basic concept of it and of the web settings related to it; like domain name 'site'.
If you can point me to a source of good overview & necessary details please do so. I'd be happiest if hit with terminology one would use for describing quantum physics to an exceptionally stupid rodent.
Oooh! Oooh! I know this one. Use the YaST configuration tool:
YaST->Network Services->Host Names -or- YaST->Network Devices->Network Card->Change->Edit
Select the "129" entry and edit it. If you're on a private network (or a standalone box) you can set the host name and domain name to anything you like. Enter something like "192.168.0.1", "myhost.mydomain", "myhost" in the fields. Save and your done.
Jeff
Jeff, Maybe you did not see it in my original posting (in the 'optional' part of my msg) but even though doing just what you told me to do DID change the host name in resp setting _in Yast_ and it remains changed there, the host name I get in KDE console _prompt_ still remains '129' and the _printenv_ command still prints HOSTNAME and HOST as being '129'. If I somehow have caused this persistence myself by the command 'export HOST/HOSTNAME=129 + allexport (which I did after my earlier modification trials halted my net connection) then how could I undo that 'exporting' so that changing the values in Yast would also change the host name in the KDE terminal prompt? I am still quite confused about all the places where Suse saves these parameters, what is the preference of hierarchy among them, and how one could expunge the heretical host names for good and replace them with saner ones. Should you bump into a tutorial on these things, please let me know. Information on editing this file and that file doesn't reveal the big picture, that I should have, before I try to couple my two Suse machines in a harmonious home network. And maybe a WinME Pc - or maybe not. Mike
Maybe you did not see it in my original posting (in the 'optional' part of my msg) but even though doing just what you told me to do DID change the host name in resp setting _in Yast_ and it remains changed there, the host name I get in KDE console _prompt_ still remains '129' and the _printenv_ command still prints HOSTNAME and HOST as being '129'.
If I somehow have caused this persistence myself by the command 'export HOST/HOSTNAME=129 + allexport (which I did after my earlier modification trials halted my net connection) then how could I undo that 'exporting' so that changing the values in Yast would also change the host name in the KDE terminal prompt?
Take a look in the home directory of the user for a hidden file ".bashrc". By default this holds the user's default environmental variable values for the bash shell. If you use a different shell the file may have a different name but the purpose is the same. Jeff
I am still quite confused about all the places where Suse saves these parameters, what is the preference of hierarchy among them, and how one could expunge the heretical host names for good and replace them with saner ones.
Should you bump into a tutorial on these things, please let me know. Information on editing this file and that file doesn't reveal the big picture, that I should have, before I try to couple my two Suse machines in a harmonious home network. And maybe a WinME Pc - or maybe not.
Mike
Op maandag 24 januari 2005 22:05, schreef Dumb Waiter:
Maybe you did not see it in my original posting (in the 'optional' part of my msg) but even though doing just what you told me to do DID change the host name in resp setting _in Yast_ and it remains changed there, the host name I get in KDE console _prompt_ still remains '129' and the _printenv_ command still prints HOSTNAME and HOST as being '129'.
Wild guess. If you are automatically handed an IP address at start up by your ISP via DHCP (Yast->Network Services) it may be that the host name gets changed automagically if the relevant box has been checked in Yast->Network Services->DNS and hostname 129 seems a bit odd as a hostname, but my beautiful "regina" has been changed to the unredeemably ugly "kf-pij-tg01-0852". This is not all of a Bad Thing though, since now I can be looked up by a nameserver using this hostname. So I'm not sure you should continue your pursuit of getting your old hostname back. :-) Best regards, -- Jos van Kan
The Monday 2005-01-24 at 20:17 +0200, Dumb Waiter wrote:
And when tried to change host name to something else in YAST / Network services/ DNA and Host Name/ two things happened:
_A) I was instantly confused by the message: "The resolver configuration (/etc/resov.conf) has been temporarily modified by DHCPCD. You have to options: 1. Modify the current (changed!) version of the file 2. Press 'Accept' now and conntinue editing other (non-roselver) data. You could return to his dialog later when the above sefvice has terminated."
Although I understand the individual words, the real meaning of my two choices remains utterly obscure to me - what does that information try to say to me?
This matches with what Jos van Kan told you on another email. You are getting your name through DHCP. So, you have to drop your internet connection, and then try yast again, it will probably show another name. Then, in the network properties, you probably have selected the option to allow DHCP to alter your hostname. There you can change it, if you want and if it is really advisable, as Jos van Kan says. I think you can, but it is just an opinion. -- Cheers, Carlos Robinson
participants (4)
-
Carlos E. R. -
Dumb Waiter -
Jeffrey Laramie -
Jos van Kan