Date: Sat, 14 Feb 1998 15:25:43 +0000 (GMT) From: Adam David <adam@veda.is> To: mike@smith.net.au (Mike Smith) Cc: julian@whistle.com, gibbs@plutotech.com, pst@juniper.net, mike@smith.net.au, core@FreeBSD.ORG, junichi@jp.freebsd.org, committers@FreeBSD.ORG Subject: Re: devfs persistance Message-ID: <199802141525.PAA00707@veda.is> In-Reply-To: <199802140028.QAA05427@dingo.cdrom.com> from Mike Smith at "Feb 13, 98 04:28:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> That's getting there, but you are leaving out phk's (very valid) desire > to be able to prototype attributes for nonexistent nodes. > > To me, this speaks of two entities: > > - A set of rules, which are scanned as the node is being created. > Having passed through these rules, the node may have had its > attributes, etc. modified before it appears in the namespace. > These allow the implementation of the "prototyping" behaviour. > - A list of explicit nodename : attribute associations. These allow > the implementation of the DWIM chown/chmod behaviour. > > IMHO, these should be stored in files under the mountpoint. The devfs > code would have to look this file up during the mount, and keep it open. > > You could also supply a systemwide copy of the data either from a > configuration file or via inheritance from the first mount of the devfs. > > If you didn't like persistence, then you could simply ignore it. You might also want a custom set of rules/data to be specified for the mount. -- Adam David <adam@veda.is> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802141525.PAA00707>