From owner-freebsd-current Tue Jul 20 14:12: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D400315196; Tue, 20 Jul 1999 14:11:43 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA22436; Tue, 20 Jul 1999 23:10:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Brian F. Feldman" Cc: "Steven G. Kargl" , freebsd-current@FreeBSD.org Subject: Re: is dumpon/savecore broken? In-reply-to: Your message of "Tue, 20 Jul 1999 17:08:17 EDT." Date: Tue, 20 Jul 1999 23:10:44 +0200 Message-ID: <22434.932505044@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Bria n F. Feldman" writes: >On Tue, 20 Jul 1999, Poul-Henning Kamp wrote: > >> In message , "Bria >> n F. Feldman" writes: >> >> >> /ddname = find_dev/s/BLK/CHR/ >> > >> >No, that's wrong. You cannot do buffered-type IO on a cdev. I committed >> >a workaround, and now it works. There's no easy way around this, except >> >possibly making kern.dumpdev a string (makes quite a bit of sense there...) >> >> Indeed. a dev_t should never be exported as such from the kernel >> anymore, in particular not for bdevs. dumps and swap are the two >> offenders left. > >Should I commit a similar workaround for the swap code too? Quite >simple to do... Please so, but I would appreciate if you would do me the favour of hiding the guts of this monstrosity in kern/kern_conf.c in a function called dev2budev() ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message