SuSE 7.3 sparc64

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: George Toft
Date:  
Subject: SuSE 7.3 sparc64
slr wrote:
>
> > /etc/hosts has nothing to do with what the real hostname. It's better if it
> > does list the name, but that's not required.
>
> if /etc/hosts has nothing to do with what the real hostname is. then why in
> the /etc/rc.config file right above the statement:
>
> FQHOSTNAME=blah.hostname.com
>
> does it state:
>
> Hostname of the system (full name)
> Don't forget to edit your /etc/hosts appropriately
>
> and BTW, thx George for the clue to /etc/rc.config.


No problem.


>
> > /etc/HOSTNAME is probably either read or written at boot time, but should
> > otherwise be ignored.
>
> sl in SuSE is YaST the preferred way of making system changes?


Yes, and this drove me batty. I cut my teeth learning config files and
making symlinks in the start up scripts, so YaST was a major annoyance.
Now, I live with YaST because SuSE supports the Linux Standards Base,
and some other distros do not. Today's YaST really rocks, so I am
getting used to doing the point and click administration.

I wanted to install my WinTV card. Point-click, YaST set it up - easy.
I wanted to monitor my CPU temperature. I installed the sensors
package, and YaST installed the proper entries in /etc/modules.conf for
me.

The "gotcha" with YaST is when you install a new service, like LDAP, you
must enable the new service in YaST, because every init script asks YaST
if that service is supposed to start up. The other "gotcha" is that
YaST2 does not manage Logical Volumes correctly - use YaST1 for that.

George