From owner-freebsd-current  Fri Jul 26 10:27:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA10629
          for current-outgoing; Fri, 26 Jul 1996 10:27:53 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10619
          for <freebsd-current@FreeBSD.ORG>; Fri, 26 Jul 1996 10:27:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id LAA28387; Fri, 26 Jul 1996 11:27:20 -0600 (MDT)
Message-Id: <199607261727.LAA28387@rover.village.org>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s 
Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users)
In-reply-to: Your message of Fri, 26 Jul 1996 00:42:56 PDT
Date: Fri, 26 Jul 1996 11:27:19 -0600
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


: It would also allow you to make links, like:
: 
: 	ln -s /dev/cuaa0 /dev/mouse
: 
: Which get recreated automagically when devfs is next mounted.  Yes,
: you could accomplish the same effect with a handful of commands in
: /etc/rc.local, but the point is to make it transparent and so obey the
: principle of least astonishment.

Hmmm, sounds like what is needed is a file system that maintains a
file, lets call it /etc/devperms to invent a name.  When you mount
this file system, it reads that file.  When you hack this file system,
it hacks that file for you.  When you unmount, nothing would happen to
that file.  All of this is dependent, of course, on the existance of
real devices on the system.

I don't know how hard something like that would be to do, but I think
that's what people are asking for....

Warner