From owner-freebsd-current  Tue Jul 20 11: 5:33 1999
Delivered-To: freebsd-current@freebsd.org
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
	by hub.freebsd.org (Postfix) with ESMTP id CEB1A153B1
	for <freebsd-current@FreeBSD.ORG>; Tue, 20 Jul 1999 11:05:23 -0700 (PDT)
	(envelope-from kargl@troutmask.apl.washington.edu)
Received: (from kargl@localhost)
	by troutmask.apl.washington.edu (8.9.3/8.9.1) id LAA04373;
	Tue, 20 Jul 1999 11:09:36 -0700 (PDT)
	(envelope-from kargl)
From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>
Message-Id: <199907201809.LAA04373@troutmask.apl.washington.edu>
Subject: Re: is dumpon/savecore broken?
In-Reply-To: <21539.932493344@critter.freebsd.dk> from Poul-Henning Kamp at "Jul 20, 1999 07:55:44 pm"
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Date: Tue, 20 Jul 1999 11:09:35 -0700 (PDT)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Poul-Henning Kamp:
> In message <199907201742.KAA04068@troutmask.apl.washington.edu>, "Steven G. Kar
> gl" writes:
> >
> >During the boot process I see
> 
> >   dumpon: crash dumps to /dev/da0s1b (4, 131073)
> >   checking for core dump...savecore: can't find device 13/131073
> 
> >It seems that the the major device number is reset from 4 to 13.
> 
> Yes, all dev_t's which make it out of the kernel have cmajor
> numbers now.
> 
> Try this change to savecore:
> 
> 	/ddname = find_dev/s/BLK/CHR/
> 

Thanks, Poul. 

I forgot to mention that this is after a "make world" and new kernel
from today (1000 PST).

-- 
Steve


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message