From owner-freebsd-current Wed May 12 1:34:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 6032D152D8; Wed, 12 May 1999 01:34:14 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id F3A9B189D; Wed, 12 May 1999 03:33:44 +0000 (GMT) Date: Wed, 12 May 1999 03:33:44 +0000 From: Robert Garrett To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: simple (but important) task for junior kernel hacker Message-ID: <19990512033344.E21016@phc.igs.net> References: <3694.926496249@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3694.926496249@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote: > > I don't have time just now to attend this particular detail, which > manifests itself by swapinfo/pstat -p showing "/dev/(null)" for > device name. > > The problem in short is that libkvm:kvm_getswapinfo.c has it's > fingers in the kernels memory and pulls out a dev_t without knowing > how to (and it shouldn't be taught this!) convert it to a udev_t. > > The Right Way to solve this problem is to rewrite libkvm:kvm_getswapinfo.c > to pick up the information using some (for this purpose constructed) > sysctl variables (sysctlbyname(3) please!), and let the kernel convert > the dev_t to udev_t before passing it out to userland. > > So for any aspiring kernel hackers out there: have at it. Patches > accepted. > > In general libkvm should not grovel around in a running kernel but > only use sysctlbyname(3). > > -- the only place in the entire libkvm where a dev_t is used is kvm_proc.c line 230 this particular section completely looses me Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message