Date: Thu, 05 Mar 2009 10:13:31 -0800 From: Bakul Shah <bakul@bitblocks.com> To: Jedrzej Kalinowski <kalinoj1@iem.pw.edu.pl> Cc: freebsd-emulation@freebsd.org Subject: Re: kqemu and devfs - any luck? Message-ID: <20090305181331.A0F875B5E@mail.bitblocks.com> In-Reply-To: Your message of "Thu, 05 Mar 2009 02:05:26 %2B0100." <20090305010525.GA69474@volt.iem.pw.edu.pl> References: <20090305010525.GA69474@volt.iem.pw.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 05 Mar 2009 02:05:26 +0100 Jedrzej Kalinowski <kalinoj1@iem.pw.edu.pl> wrote: > Hello, > > I'm trying to set up kqemu (kqemu-devel from -current) to be accessible to us > ual > non-wheel users. I've created a ruleset that looks like this: > > # devfs rule show > 100 path kqemu mode 666 > 200 path kqemu unhide > > than I do > # devfs rule applyset > > but sadly my /dev/kqemu are still owned by root:wheel and have 660 > permissions. I'm proceeding exactly in the way that's described in man 8 devfs > > Maybe someone else succeded with this and could give me a tip on how to > cope with this issue? Or maybe someone can at least confirm that it does > not work, and the PR should be posted? I'm working on a -CURRENT > system.. > For loadable modules you can use devfs.conf so try something like the following as root. # cat >> /etc/devfs.conf <<EOF perm kqemu0 0666 perm kqemu1 0666 EOF # /etc/rc.d/devfs restart But changing permissions to 0666 is a bad idea in my view. A slightly better idea is to use the following in devfs.conf own kqemu0 foo:bar if you want to allow user foo to gain access to kqemu0.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090305181331.A0F875B5E>