Rebooting problems

Wed, 1 Jan 2003 20:15:21 -0800

This is a multi-part message in MIME format.

------=_NextPart_000_0049_01C2B1D2.82EFFE50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Well I am back up and running but I did experience some problems. Mainly =
when I shut down and then rebooted my Linux box the eth0 failed and then =
the eth1 failed also. When I checked into it I found that eth1 had been =
set up with the same IRQ and I/O assignments as eth1. After I changed =
them it works good. Anyway I'll ask once more: Is this the way Linux =
works? Do I have to re-configure the NIC's everytime I have to reboot =
for some reason or is there something I am failing to do here? Any help =
is appreciated. Happy New Year to all.  Cliff
------=_NextPart_000_0049_01C2B1D2.82EFFE50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>Well I am back up and running but I did experience some problems. =
Mainly=20
when I shut down and then rebooted my Linux box the eth0 failed and then =
the=20
eth1 failed also. When I checked into it I found that eth1 had been set =
up with=20
the same IRQ and I/O assignments as eth1. After I changed them it works =
good.=20
Anyway I'll ask once more: Is this the way Linux works? Do I have to=20
re-configure the NIC's everytime I have to reboot for some reason or is =
there=20
something I am failing to do here? Any help is appreciated. Happy New =
Year to=20
all.&nbsp; Cliff</DIV></BODY></HTML>

------=_NextPart_000_0049_01C2B1D2.82EFFE50--