Linux-Misc Digest #465, Volume #24               Sun, 14 May 00 11:13:02 EDT

Contents:
  Re: Redhat6.2 Network bug ?? ([EMAIL PROTECTED])
  Re: Boot Disk (Leonard Evens)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: tw.bbs.comp.linux,comp.os.linux.setup,comp.os.linux.networking
Subject: Re: Redhat6.2 Network bug ??
Date: Sun, 14 May 2000 14:26:53 GMT

May be you will ask why you so worries about this problem?

Think... if my network structure is like the following...

If either RJ45-A or RJ45-B unplug and replug that cause the important
Gateway-A lost connection(cannot pickup again) then all of my Zone-B is
dead dead .....


|------------------|
|(RJ45 --A)        |100Mb Switch (A)
|------------------|
     |     |     |_______Redhat6.x
     |     |
     |     --------------------Redhat 6.x
   |---|
   |   |
   |   | Gateway (A) Redhat 6.2
   |   |
   |---|
     |
=====|=============================Zone B====
     |(RJ 45 -- B)                          |
|------------------|                        |
|                  |100Mb Switch (B)        |
|------------------|                        |
     |    |    |________Redhat6.x           |
     |    |                                 |
     |     ------------------Redhat 6.x     |
   |---|                                    |
   |   |                                    |
   |   | Gateway (B) Redhat 6.x             |
   |   |                                    |
   |---|                                    |
     |                                      |
     |                                      |
=====|=============================Zone B====






In article <8fjpqd$qsg$[EMAIL PROTECTED]>,
  [EMAIL PROTECTED] wrote:
> After 3 days of testing the new redhat 6.2, I had found a bug of the
new
> redhat networking problem. I hope this is not the new linux kernal
> problem.
>
> Hardware:
> switch = 3com office connect 10/100 switch  &
>        dlink DES 1008 10/100 switch &
>        Netgear 10/100 h/f duplex switch
> NetworkCard = 3c905c, Netgear 10/100
> Intel PIII700 / Asus b3p-f / 128mb-pc100-Ram
> HDD IBM U-2 SCSI with Tekram U-2 SCSI card
>
> *I have difference hardware here to ensure this is not my hardware
> problem, and all of these hardware has been work with 6.1 for quite a
> while.
>
> --------------------------10/100/half/full duplex switch
>    |              |
> |-----|        |-----|    RedHat6.2 Server A: 192.168.0.2
> |     |        |     |    RedHat6.2 Server B: 192.168.0.3
> |     |        |     |
> |  A  |        |  B  |
> |     |        |     |
> |_____|        |_____|
>
> Test 1/ server A>      ping 192.168.0.3 from 192.168.0.2
>                        64 bytes from 192.168.0.2: time=0.1 ms
>       No problems, there is a reply............
>
> Test 2/ ��server B>      ping 192.168.0.2 from 192.168.0.3
>                         64 bytes from 192.168.0.3: time=0.1 ms
>       No problems, there is a reply too............
>
> Test 3/ server A unplug its RJ45 on the switch for "15" seconds, and
> then re-plug the RJ45 back to the switch.
>         server A> ping 192.168.0.3
>         64 bytes from 192.168.0.3: time=0.1 ms
>         From 192.168.0.2: Destination Host Unreachable<--- just broken
> for a while
>         From 192.168.0.2: Destination Host Unreachable
>         From 192.168.0.2: Destination Host Unreachable
>         64 bytes from 192.168.0.3: time=0.1 ms        <--- it picks up
> again
>       No problems, it could pick up again............
>
> THE PROBLEM IS --> when I unplug the server A RJ45 on the switch for
> more then "300" seconds, and then re-plug the RJ45 back to the switch.
>
>         server A> ping 192.168.0.3
>         From 192.168.0.2: Destination Host Unreachable
>         From 192.168.0.2: Destination Host Unreachable
>         From 192.168.0.2: Destination Host Unreachable
>         From 192.168.0.2: Destination Host Unreachable
>         From 192.168.0.2: Destination Host Unreachable
>       I cannot get any reply any more... even after 2 hours of pluged
> in, I still get unreachable messages.
>       I have to reboot the server to get the server A eth0 up again.
>
> Finally: This bug only appears in the enviroment of 100mb with switch
> (same problems exists on difference network cards and switch). If I
> change the switch to 10Mb Hub then it problem will not appears.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Boot Disk
Date: Sun, 14 May 2000 09:10:28 -0500

Scott wrote:
> 
> I have a problem.   I've got two hard drives (one Windows, one Linux).  The
> computer boots using LILO.  I would like to get rid of LILO an boot to my
> windows disk, but still have the option of booting to my Linux disk using a
> floppy.  Anyone know how to go about doing this?
> 
> I have to do it because running both drives makes my Linux disk overheat and
> not operate.  Then, because, I guess, it is the disk that's actually
> booting, I can't boot the windows disk no matter what (not even with a
> Windows Startup disk).
> 
> Any help would be appreciated.
> 
> Scott

First make a boot floppy.   If your distribution has mkbootdisk,
use it to make a boot floppy.  See the man page for syntax.
One warning though.  On some newer computers, that boot floppy will
take a very long time to start booting.
Alternately you can copy the  kernel to a floppy.  Say your kernel
is vmlinuz-2.2.14-5.0.   Then use
cd /boot
dd if=vmlinuz-2.2.14-5.0 of=/dev/fd0
Then tell the kernel on the floppy what your root partition is,
say it is /dev/hda2
rdev /dev/fd0 /dev/hda2
That will also produce a boot floppy.
Test your boot floppy and make some copies.

Then run
/sbin/lilo -u
That should remove the lilo boot loader from your master boot
record on the first disk.   (That is what is going to the second
disk to see what to do next.)   If that doesn't work, boot from
a DOS/Windows startup floppy, and run
fdisk/mbr
That will clear the MBR of lilo.

All this assumes you put the lilo boot loader in the master
boot record of the first disk, which sounds very likely from
what you describe.  Alternately, it could be in the first
sector of some other partition on the first disk with that
partition the active partition.   In that case, you just
use the linux fdisk to make the Windows partition the active
partition.
-- 

Leonard Evens      [EMAIL PROTECTED]      847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to