Date: Tue, 5 Nov 2002 13:41:46 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Dima Dorfman <dima@trit.org> Cc: Andrew Lankford <arlankfo@141.com>, current@FreeBSD.ORG Subject: Re: What's the status of devfs(8)? Message-ID: <20021105194146.GB35777@dan.emsphone.com> In-Reply-To: <20021105185757.GB641@trit.org> References: <20021105044708.LIEA1469.out010.verizon.net@verizon.net> <20021105185757.GB641@trit.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Nov 05), Dima Dorfman said: > Andrew Lankford <arlankfo@141.com> wrote: > > When I try commands like: > > > > #devfs rule add path speaker mode 666 > > Did you set a ruleset before this? > > devfs ruleset 10 > > > devfs rule: ioctl DEVFSIO_RADD: Input/output error > > This is telling you that you're trying to modify ruleset 0. From the > man page: > > Ruleset number 0 is the default ruleset for all new > mount-points. It is always empty, cannot be modified or > deleted, and does not show up in the output of showsets. Then it should return EPERM, EACCESS, EINVAL, or basically anything except EIO, imho. I got bit by this as well, and thought /sbin/devfs was simply broken or not fully coded until I saw this post. Or maybe allow ruleset 0 to be modified like any other? Is there a benefit to having an invisible, immutable default ruleset? -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021105194146.GB35777>