From owner-freebsd-current Sat May 20 19:42:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA20622 for current-outgoing; Sat, 20 May 1995 19:42:41 -0700 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA20611 for ; Sat, 20 May 1995 19:42:38 -0700 Received: from ast.com by relay1.UU.NET with SMTP id QQyqpu06804; Sat, 20 May 1995 22:42:35 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA14562 (5.67b/IDA-1.5 for uunet!freebsd.org!current); Sat, 20 May 1995 19:42:48 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Sat, 20 May 95 21:42 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0sD0oX-0004vzC; Sat, 20 May 95 21:32 CDT Message-Id: Date: Sat, 20 May 95 21:32 CDT To: current@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sat May 20 1995, 21:32:21 CDT Subject: 5/19 current sticks on startup Cc: uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk [0]The 5/19 current, upon rebooting, will start routed, then hang until [0]Control-C is pressed. It looks like this: [0] [0] starting routing daemons: routed. [0] _ [0] [0]...And the cursor sits there. When I Control-C, I see this: [0] [0] ^Cclearing /tmp I have also seen this when you boot a kernel not named "kernel". I was using "kernel.exp" on a system to do test work with no NFS active at all and it would routinely hang if the kernel name wasn't "kernel". Hit ^C and it kept going. This started happening (for me anyway) around the 032x SNAP. You might consider that possible cause if you aren't running NFS and can't be having the NFS-related problems. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983