From owner-freebsd-current Tue Oct 10 22:50:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4A62C37B66D for ; Tue, 10 Oct 2000 22:50:07 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA24413; Wed, 11 Oct 2000 16:49:50 +1100 Date: Wed, 11 Oct 2000 16:49:45 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jun Kuriyama Cc: Current Subject: Re: savecore cannot find device? In-Reply-To: <7mlmvwqi3i.wl@waterblue.imgsrc.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Oct 2000, Jun Kuriyama wrote: > My boot message of today said: > Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory > > And swap entry in /etc/fstab is: > /dev/ad0s1b none swap sw 0 0 > > This is non-DEVFS environment. Am I missing some point of updating? Probably that you shouldn't have downgraded savecore by updating it :-). savecore now uses devname() but devname() is too unreliable to use for anything except informational output. There are several failure modes. When devname() can't find the device name by looking up dev.db or using sysctl kern.devname, it invents a name of the above form. Apparently, the device name "ad0s1b" is not understood by the kernel when savecore is run (early in /etc/rc). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message