From owner-freebsd-current@FreeBSD.ORG Fri May 13 07:27:17 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 10FC016A4CE for ; Fri, 13 May 2005 07:27:17 +0000 (GMT) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 721AF43D79 for ; Fri, 13 May 2005 07:27:16 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j4D7RDOT018123 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 13 May 2005 17:27:14 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])j4D7RDEa036250; Fri, 13 May 2005 17:27:13 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.13.1/8.13.1/Submit) id j4D7RDT8036249; Fri, 13 May 2005 17:27:13 +1000 (EST) (envelope-from peter) Date: Fri, 13 May 2005 17:27:13 +1000 From: Peter Jeremy To: Andrey Chernov , current@freebsd.org Message-ID: <20050513072713.GB34537@server.vk2pj.dyndns.org> References: <20050513041929.GA34210@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050513041929.GA34210@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i 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:27:17 -0000 On Fri, May 13, 2005 at 08:19:29AM +0400, Andrey Chernov wrote: >With today's kernel I get > >Trying to mount root... >exec /sbin/init: error 20 >exec /sbin/oinit: error 20 >exec /sbin/init.bak: error 20 Errno 20 is ENOTDIR. Have you possibly hosed your /sbin? >And only reboot is possible at this stage. I am sure I clean everything >several times and have all things fresh including user base (and init >too). Old kernel works nicely at the same time even with new code base. If you mean that you can boot your old kernel with the same userland then 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. Peter