From owner-freebsd-questions Thu Feb 22 21:30:56 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA11697 for questions-outgoing; Thu, 22 Feb 1996 21:30:56 -0800 (PST) Received: from netcomsv.netcom.com (uucp5.netcom.com [163.179.3.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA11690 for ; Thu, 22 Feb 1996 21:30:54 -0800 (PST) From: bluese@kbbs.com Received: from kbbs.com by netcomsv.netcom.com with UUCP (8.6.12/SMI-4.1) id VAA17648; Thu, 22 Feb 1996 21:25:18 -0800 Date: Thu, 22 Feb 1996 21:25:18 -0800 Received: by kbbs.com (UUPM-1.51) id D1181HS Thu, Feb 22, 1996 21:06:58 PST Message-Id: <9602222106.D1181HS@kbbs.com> X-Mailer: UUPlus Mail 1.51 To: questions@freebsd.org Subject: Boot problem w/net config Organization: KBBS Los Angeles http://www.kbbsnet.com Sender: owner-questions@freebsd.org Precedence: bulk Date: Thu, 22 Feb 96 21:06:58 PST I am running 2.0.5 on a pentium machine with a 3COM 3C509 adaptor. All non-used devices have been "deleted" with the -c boot option program. The wierd problem I have encountered is as follows, and I certainly appreciate any advice you can give me - Upon booting, after the devices have been probed, and after the initial fsck, the system hangs 3 different times, but eventually boots sucessfully and with no error messages or time out msgs. I am concerned with a problem appearing on the net at a later date tho, and wanted to know if you have encountered this. The first hang is right after this console msg EP0: flags=863 mtu 1500 inet 206.29.15.68 netmask 0xffffffc0 broadcast 206.29.15.127 ether 00:0a:24:2b:6b:f3 This hangs for about 3 minutesd Then the next 2 msgs Lo0:flags=8009 mtu 16384 inet 127.0.01 netmask 0xff000000 add net default: gateway 206.29.15.65 AT this point the sys hangs for about 5-7 minutes after which the sys gives another msg add net 244.0.0.0 gateway namesrv (the machine name itself) another long hang and then add net 244.0.0.0 gateway localhost - Any ideas? Or does this even indicate a prob? The system is functional as a nameserver after boot up, so it appears to work as far as I can tell. Thanks