In message <[EMAIL PROTECTED]>, David Malone writes: >On Sun, Mar 03, 2002 at 09:26:11PM +0100, Poul-Henning Kamp wrote: >> >I presume you'd push the rules in using sysclt or did you have >> >something more filesystem like in mind? >> >> Nope, just a sysctl. > >I guess then you just need a sysctl which lets you read the rules >for a given devfs mount point and another which lets you set the >rules for a given defvs mount point. I don't know if we also need >a global ruleset which is applied if the mount point speficic rules >fail to match.
True, forgot that. In that case lets make them a mount option using mux@ new nmount(2) systemcall. >The rules should be able to chmod and chown the nodes. Should it >also be able to prevent the creation matching nodes also? Yes. >You mentioned matching on the names drivers and nodes. Are there >any other sorts of matching we are likely to need? Ideally I would want to match on names, driver names and types, ie: name=="ttyd0", driver=="sio" and type=="tty", but I think the important thing here is to make it exensible in the future. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
