From owner-freebsd-small Tue Apr 24 9:29: 4 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id E924F37B424 for ; Tue, 24 Apr 2001 09:29:00 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3OGT1A17714; Tue, 24 Apr 2001 11:29:06 -0500 Message-ID: <3AE5A9B6.FF7546CC@aurora.regenstrief.org> Date: Tue, 24 Apr 2001 16:28:38 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrzej Bialecki Cc: freebsd-small@freebsd.org Subject: Re: PicoBSD's kernel, /dev/kmem, and the kernfs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > Well, the general trend in FreeBSD kernel development is to phase out all > /dev/kmem access, even when wrapped with libkvm calls, using sysctl(9) > instead. Groping through kernel memory is Bad. Sysctl(9) presents > consistent, safe, and well-defined interface. ... > Consequently, my POV on this is: if ipfilter uses /dev/kmem, then it > should be fixed. This makes perfect sense to me, thanks for the clarification. regards, -Gunther Sometimes it is hard to keep up with a world that is constantly getting better :-) -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message