From owner-freebsd-current Sat May 30 14:00:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02446 for freebsd-current-outgoing; Sat, 30 May 1998 14:00:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp154.0.mmtl.videotron.net [207.253.0.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02434 for ; Sat, 30 May 1998 14:00:25 -0700 (PDT) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id RAA00236 for ; Sat, 30 May 1998 17:02:14 -0400 (EDT) (envelope-from sepotvin@videotron.ca) Message-ID: <357073D6.64199B09@videotron.ca> Date: Sat, 30 May 1998 17:02:14 -0400 From: "Stephane E. Potvin" Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <199805301537.XAA22245@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe this will seems a stupid question but why in the first place would someone want to delete a device from a devfs /dev? Or put differently why is not devfs append-only so someone would be able to make new links but not able to delete existing devices? Stephane E. Potvin POS and Industry Helpdesk IBM Canada Ltd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message