From owner-freebsd-current Sat May 29 7: 7: 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 4FEC515006 for ; Sat, 29 May 1999 07:07:05 -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 QAA10093; Sat, 29 May 1999 16:05:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: ache@nagual.pp.ru, dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: savecore too (Re: kvm_getswapinfo is broken) In-reply-to: Your message of "Sat, 29 May 1999 22:21:11 +1000." <199905291221.WAA28838@godzilla.zeta.org.au> Date: Sat, 29 May 1999 16:05:08 +0200 Message-ID: <10091.927986708@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905291221.WAA28838@godzilla.zeta.org.au>, Bruce Evans writes: >>Just found that savecore is broken in the same way. What is proper >>procedure to fix it? I.e. is it must be fixed in the kernel, leaving >>userland programs as is or in userland, leaving kernel as is? > >The kernel needs to maintain (or create as necessary for return by >sysctl()) udev_t versions of most (all?) device numbers that are accessed >in userland. I think the proper way to do this will be to maintain a >udev_t for each dev_t in the kernel too. udev_t should be named dev_t, >the current dev_t should be named something like kdev_t and should be >a pointer to a struct containing the (user) dev_t. The kernel needs >something like this for fast conversions in old interfaces like stat(2). ... But since renaming dev_t in the kernel will totally hose all device driver writers, we don't rename it, but suffer the trouble of the overloaded name. The structure thing will happen RSN. -- 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