Date: Fri, 13 Feb 1998 16:32:36 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Mike Smith <mike@smith.net.au> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, committers@FreeBSD.ORG Subject: Re: wfd block major number reassignment from 24 to 1 Message-ID: <Pine.BSF.3.95.980213162023.23295Q-100000@current1.whistle.com> In-Reply-To: <199802140018.QAA05385@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
1/ see my response to justin. On Fri, 13 Feb 1998, Mike Smith wrote: > > Which is the right thing to do, I may not even want all the devices > > to come across... > > Sure. I agree entirely. > > Count the lines, and the breaks in paradigm, between what you suggest I > want and what you want. Your desire is for a more complicated, > inconsistent, non-extensible technique. That's Bad. I would like to point out that poul's method is not longer.. he is just showing two different cases. Mike, there is no 'consistant' manner of handling new unexpected devices, except to not show them.. or to give them some default permission (not show them would be a special case of this really). an example.. I use 24 ptys. I hav egiven them perms.. one day I user 25. (ptys are probably going to become dynamic) what does it do for the 25th?. there are a few options: 1/ sysctl -w hw/devices/ptys/perms=577 sysctl -w hw/devices/ptys/owner=root.wheel 2/ echo "pty* perm=577 owner=root.wheel" >> /etc/devperms /sbin/devdaemon& (the devdaemon would be notified of arrival events) my scheme for adding unionfs like characteristics to devfs would give semantics similar to what we have now, but not solve the problem given above. 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?Pine.BSF.3.95.980213162023.23295Q-100000>