From owner-freebsd-current  Sun May 31 12:48:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA07905
          for freebsd-current-outgoing; Sun, 31 May 1998 12:48:16 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07894
          for <current@FreeBSD.ORG>; Sun, 31 May 1998 12:48:14 -0700 (PDT)
          (envelope-from rvb@sicily.odyssey.cs.cmu.edu)
From: rvb@sicily.odyssey.cs.cmu.edu
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: I see one major problem with DEVFS...
References: <199805300626.XAA01190@antipodes.cdrom.com>
Date: 31 May 1998 15:48:00 -0400
In-Reply-To: Mike Smith's message of Fri, 29 May 1998 23:26:48 -0700
Message-ID: <yzsn2bykyrz.fsf@sicily.odyssey.cs.cmu.edu>
Lines: 18
X-Mailer: Gnus v5.4.46/Emacs 19.34
Source-Info:  Sender is really rvb@sicily.odyssey.cs.cmu.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith <mike@smith.net.au> writes:

> > > Yes, but you can't *look*at* the template mount to find out what these 
> > > numbers *are*.
> > 
> > Why *not*? :-)
> 
> Because it ain't mounted anyhere.  Think: user says:
> 
> # rm /dev/foo0
> <expletive>
> # mknod /dev/foo0 c ???
> 
Would it be too strange to just not let you delete this kind of file?
A long long time ago . and .. where files and root could delete them
and/or make cycles.  Now the fs abstraction is slightly different and
(I hope) this is illegal.  Well, if there is irreplaceablt info in
these devfs files, just make them immutable.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message