From owner-freebsd-current Mon Jul 13 14:52:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16258 for freebsd-current-outgoing; Mon, 13 Jul 1998 14:52:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.falcon.com (appp12.sysnet.net [206.142.16.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16246 for ; Mon, 13 Jul 1998 14:52:07 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id RAA10426 for ; Mon, 13 Jul 1998 17:42:37 -0400 (EDT) X-Sender: patton@mail.sysnet.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 12 Jul 1998 17:48:20 -0400 To: freebsd-current@FreeBSD.ORG From: Matthew Patton Subject: living without PROCFS Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to eliminate the use of procfs from -current? I discovered what happens when you leave it out of the kernel config file. Or is /proc a really useful device that is for now and forevermore "standard"? It used to be, that there existed all sorts of security problems with PROCFS. Notably on slowaris. -------- "If I were called upon to identify briefly the principal trait of the 20th Century, here too I would be unable to find anything more precise and pithy than to repeat once again: Men have forgotten God." - Aleksander Solzhenitsyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message