From owner-freebsd-current  Tue Sep 16 23:17:43 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA20367
          for current-outgoing; Tue, 16 Sep 1997 23:17:43 -0700 (PDT)
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20358
          for <current@freebsd.org>; Tue, 16 Sep 1997 23:17:40 -0700 (PDT)
Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id XAA22858; Tue, 16 Sep 1997 23:17:39 -0700 (PDT)
Date: Tue, 16 Sep 1997 23:17:39 -0700 (PDT)
From: Sean Eric Fagan <sef@Kithrup.COM>
Message-Id: <199709170617.XAA22858@kithrup.com>
To: current@freebsd.org
Subject: Re: Does this idea have merit? 
References: Your message of "Tue, 16 Sep 1997 18:39:10 PDT."
             <Pine.BSF.3.96.970916183810.3894D-100000@zippy.dyn.ml.org> 
Organization: Kithrup Enterprises, Ltd.
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <1565.874467750.kithrup.freebsd.current@orion.webspan.net>
Gary writes:
>kernfs is the proper place to put non-process related infromation. I
>am not at all comfortable with the linux idea of sticking everything
>possible into /proc ... kernfs is the `cleaner' place to put such info
>if you want to do file style I/O, or of course there is now sysctl,
>available through a syscall.

I agree.  Most of the stuff in Linux' /proc does not belong there -- and
/kern is a great place to put things like that.  (Making /kern/kernel a
symlink to the booted kernel would be a great idea, for example ;).)

If you want to add nodes to kernfs, I'm willing to listen.