On 23:14 05 Apr 2002, Robert Monical <[EMAIL PROTECTED]> wrote:
| I am a Solaris user trying to get up to speed on Red Hat. Using RH 7.2. I'm 
| liking a lot of things about Linux/Gnome verses Solaris/CDE.

Nearly anything beats CDE :-(

| Is there a guide to Linux for Solaris Admins out there?

Not sure.

| Here are some Solaris actions that I cannot figure out the (low 
| level)  Linux equivalent. I think the GUI tool is KAPUT.
| Change hostname: edit /etc/hostname.<interface_id>

Edit /etc/sysconfig/network.
BTW, editing /etc/hostname.<interface_id> on Solaris doesn't do the
hostname either. It sets the interface IP address (via /etc/hosts).

| Change IP address tied to an interface: edit /etc/hosts

Edit /etc/sysconfig/network-scripts/ifcfg-<interface_id>.

| Change gateway: edit /etc/defaultrouter

Add
        GATEWAY=n.n.n.n
to the appropriate /etc/sysconfig/network-scripts/ifcfg-<interface_id> file.

| Change netmask edit /etc/netmasks

Also set in the ifcfg-<interface_id> file.

| Linux seems to combine all of this in an interface specific file in 
| /etc/sysconfig.

Yes.

| But it seems like it cannot be changed after installation

Sure it can. With any text editor.

| I use the GUI tool.

I don't.

| But it does not take. For example, I enter the IP 
| address and hostname for eth0, but it never makes into hosts.

Ok. Clue: Hostnames have _nothing_ to do with interfaces.
Interfaces have IP addresses and netmasks.
This is also true under Solaris.
Hostnames fall out of the reverse IP lookup (which is why one must set up
/etc/hosts). The value returned by the "hostname" command is an entirely
separate item.

Edit /etc/hosts by hand to put in the minimum set of host information.
Example:

        127.0.0.1       localhost.home localhost loghost loghost.home
        192.168.1.3     alpha-eth0 alpha-eth0.home alpha alpha.home

which does my alpha box. Note I have the host-iface suffix name first
so that things like netstat et al tell me an interface specific name
when they recite a name for some IP - very handy.

| As I fool around, I periodically lose the ability to run the window 
| manager. Then I edit a file called network, and it comes back.

You'd have to track these changes yourself.

| I got to where I could boot up (get an IP address used by another 
| interface) error initializing eth0 . [ ... then I can set things by hand ... ]
| The error on boot for eth0 is :
| some other host already uses address 192.168.60.45.  Much to the surprise 
| of the other systems on the subnetwork.
| ifup reaches this conclusion after running a program called arping.  So I 
| comment that check out, and all seems to be well.

arping will be using the address resolution protocol to ask the ethernet
"who has 192.168.60.45?" This is the core method for making ethernet
packets, because the ethernet packets are delivered to ethernet addresses,
not IP addresses. So the first time your machine uses a particular IP
address is uses ARP to find out the corresponding ethernet address for
the packet.

Now, if arping is telling you that 192.168.60.45 is already in use,
then it _is_!  Something out there is answering the request.

Find out by running the "arp" command _before_ manually setting up your
ethernet (or by setting up the athernet to some other address, so as
not to trash the entry in the ARP table). Then find out which machine
has the recited ethernet card.

| Is IP interface management simply broken in this release of Red Hat?

Generally not, no. It's worked for me for every RH release I've ever used
(this is pretty fundamental stuff, and so much would not work if it were
broken that this kind of bug doesn't escape into the wild.)

Suggestion: hack the config file by hand, or by running:

        netconfig

which will do some of it. Stay away from the GUI - that could well have
arbitrary bugs - I couldn't say, since I don't use it.

But first, find that rogue machine using your IP address - it looks to
me much like you're set up ok, but the sanity checking is protecting you.

| Are there more bugfixes I need?
| Is there such a thing as a consolidated patch download?

Yep - look up the up2date command.
--
Cameron Simpson, DoD#743        [EMAIL PROTECTED]    http://www.zip.com.au/~cs/

A feature is a bug with seniority.



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to