From owner-freebsd-questions  Fri Jun 28 08:35:48 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA08536
          for questions-outgoing; Fri, 28 Jun 1996 08:35:48 -0700 (PDT)
Received: from okeefe.bestweb.net (root@jordyn.dialup.cloud9.net [168.100.205.62])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA08530
          for <freebsd-questions@freebsd.org>; Fri, 28 Jun 1996 08:35:43 -0700 (PDT)
Received: from jordyn.dialup.cloud9.net.could9.net (degas.bestweb.net [192.168.1.240]) by okeefe.bestweb.net (8.7.5/8.7.3) with SMTP id LAA01314 for <freebsd-questions@freebsd.org>; Fri, 28 Jun 1996 11:37:32 -0400 (EDT)
Message-Id: <2.2.32.19960628153729.00679b90@pop.bestweb.net>
X-Sender: jordyn@pop.bestweb.net
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 28 Jun 1996 11:37:29 -0400
To: freebsd-questions@freebsd.org
From: "Jordyn A. Buchanan" <jordyn@bestweb.net>
Subject: Slow booting
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello:

One of our machines is stalling as it boots.  Not stalling, really but
pausing for about five minutes before moving on.  Here's what I see:

>lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 16384
>        inet 127.0.0.1 netmask 0xff000000
>ed1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 192.168.1.15 netmask 0xffffff00 broadcast 192.168.1.255
>         ether 00:40:33:3b:d8:1d
---THIS IS WHERE THE DELAY OCCURS---
>clearing /tmp

Initially I had thought something in the static routes might be causing the
hang, but I took those out and the problem persists.  I have two other
systems with the exact same NE2000-compatible networking card on almost the
exact same configuration (the others have slightly more RAM and use SCSI
instead of IDE drives) so I haven't a clue what's causing the problem.

If I hit control-C while the system is paused, the boot will continue
normally, and I don't notice any adverse effects.  Obviously, some idea of
what is causing the boot process to hang would be better than needing to
manually abort something every time, though.  (And I'd rather know what I
was aborting too.)

Thanks for your help,

Jordyn

P.S. We're testing this system behind a firewall before we get our actual
'Net feed next month, hence the 192.168. network numbers...