From owner-freebsd-current  Fri Nov 21 16:24:55 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA27316
          for current-outgoing; Fri, 21 Nov 1997 16:24:55 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27290
          for <current@freebsd.org>; Fri, 21 Nov 1997 16:24:46 -0800 (PST)
          (envelope-from jas@flyingfox.com)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id QAA05276;
	Fri, 21 Nov 1997 16:25:55 -0800 (PST)
Date: Fri, 21 Nov 1997 16:25:55 -0800 (PST)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199711220025.QAA05276@biggusdiskus.flyingfox.com>
To: j_mini@efn.org
Subject: Re: Stripping the kernel
Cc: current@freebsd.org
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Jonathan Mini <j_mini@efn.org> writes:

> Evan, you are absolutely right. It is Bad and Evil to read things out
> of the kernel memory. I have hated it from the start. However, look at
> the uses of the kernel tompling, and come up with an effective
> efficient way to do the same things, and I will even write it for
> you. :)

Tompling?

There are plenty of alternatives, all in use today:

	ioctl (think SIOCGIFCONF);
	sysctl
	/proc file system
	special sockets (think PF_ROUTE);
	good old poking through the kernel nlist.

Take your pick.  Or invent yet more.  Question to think about:
how many of the above can be used on kernel dump files?

Jim Shankland
Flying Fox Computer Systems, Inc.