Very Computer

I did a stupid thing in X-Windows on Red Hat 5.2.  I run a linux/Win95

network and my linux box has two ethernet cards.  One for a connection

to the internet, one for a connection to my Win95 box.  I used the
Network Configurator in X-Windows to change the IP address of the card

I use to connect to my Win95 box (device is eth0).  I had been
successfully using 10.0.0.1 as my linux IP and 10.0.0.2 as my Win95
IP.  I had heard that there were problems with using these IPs on a
private network and I should use something in the 192.168 range
instead.  So, I used the Network Configurator tool to change eth0 IP
to
a 192.168 address.  Re-boot the system and it starts complaining about

SIOCADDRT: Invalid argument and route: network address doesn't match
route address .  It took about half an hour for it to finish booting
(sysklogd and smbd just sat there till they timed out).  Once it
booted
I tried using ifconfig on the command line to reset eth0's settings
back to what I previously had, but no luck.  Ifconfig showed the
changes but when I re-booted, same crap.  What files does Network
Configurator touch?  I use X-Windows from my Win95 box, so I have to
edit the settings at the console on the command line (I don't run X-
Windows on the console, but that is another story).

Any help would be greatly appreciated.

Look in /etc/hosts. This is the trouble with "automated" tools - you
have no idea what is really going on.

Mark.

Mark Tranchant a crit :

Quote:> Look in /etc/hosts. This is the trouble with "automated" tools - you
> have no idea what is really going on.

> Mark.

In RedHat 5.2, it is not suffichient to look at /etc/hosts. You must see
also some files under /etc/sysconfig.
Another thing : ifconfig doesn't store any thing so when you reboot you
waste configuration set by using ifconfig on line.

Mohamad

Quote:>Mark Tranchant a crit :

>> Look in /etc/hosts. This is the trouble with "automated" tools - you
>> have no idea what is really going on.

>> Mark.

>In RedHat 5.2, it is not suffichient to look at /etc/hosts. You must see
>also some files under /etc/sysconfig.
>Another thing : ifconfig doesn't store any thing so when you reboot you
>waste configuration set by using ifconfig on line.

>Mohamad

All --

I have found it handy at times to use the find -newer argument.

Just before invoking the automated tool do:

   # # create a time stamp file:
   # touch /tmp/time-stamp-file

Invoke the tool and do your thing.  When done:

   # # use find to see what has been touched:
   # find / -newer /tmp/time-stamp-file -print 2>/dev/null |tee /tmp/file.lst
   # rm /tmp/time-stamp-file

Most times the config files will be under the /etc directory
so you could invoke:  find /etc -newer /tmp/time-stamp-file -print ...

However until you get the hang of it, it may be best to search
from the / dir.

There may be some chaff amongst the wheat but you _will_ have
a list of files changed since the time stamp file was made.

HTH.

-- kjh
--
------------------------------------------------------------

1111 Seacoast Dr.  Unit 41   |  home:   (619) 423-4451     |
Imperial Beach, CA   91932   |                             |