From owner-freebsd-current@FreeBSD.ORG Fri May 13 07:49:51 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D43716A4CE for ; Fri, 13 May 2005 07:49:51 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id A80D443D82 for ; Fri, 13 May 2005 07:49:50 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.3/8.13.3) with ESMTP id j4D7nnUx042174; Fri, 13 May 2005 11:49:49 +0400 (MSD) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.3/8.13.3/Submit) id j4D7nn62042173; Fri, 13 May 2005 11:49:49 +0400 (MSD) (envelope-from ache) Date: Fri, 13 May 2005 11:49:48 +0400 From: Andrey Chernov To: Peter Jeremy Message-ID: <20050513074948.GA41987@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Peter Jeremy , current@freebsd.org References: <20050513041929.GA34210@nagual.pp.ru> <20050513072713.GB34537@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050513072713.GB34537@server.vk2pj.dyndns.org> User-Agent: Mutt/1.5.9i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.30.0.12; VDF: 6.30.0.175; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (nagual.pp.ru [0.0.0.0]); Fri, 13 May 2005 11:49:49 +0400 (MSD) cc: current@freebsd.org Subject: Re: Who/what broke -current kernel? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2005 07:49:51 -0000 On Fri, May 13, 2005 at 05:27:13PM +1000, Peter Jeremy wrote: > Errno 20 is ENOTDIR. Have you possibly hosed your /sbin? No, see below. > If you mean that you can boot your old kernel with the same userland then Yes, old kernel with the same userland booted fine. fsck passed fine too. > I can't help you. You might like to do a verbose boot which should report > slightly more about what it is trying to do. I'll try, but I doubt it helps, if directory is not found. It looks line someone damage ufs code or softupdates (I have them). -- http://ache.pp.ru/