Date: Thu, 5 Mar 2009 18:45:22 +0100 (CET) From: Juergen Lock <nox@jelal.kn-bremen.de> To: kalinoj1@iem.pw.edu.pl Cc: freebsd-emulation@freebsd.org Subject: Re: kqemu and devfs - any luck? Message-ID: <200903051745.n25HjMvK004963@saturn.kn-bremen.de> In-Reply-To: <20090305010525.GA69474@volt.iem.pw.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20090305010525.GA69474@volt.iem.pw.edu.pl> you write: >Hello, > >I'm trying to set up kqemu (kqemu-devel from -current) to be accessible to usual >non-wheel users. I've created a ruleset that looks like this: > ># devfs rule show >100 path kqemu mode 666 Try: path 'kqemu*' ... (kqemu uses device cloning.) >200 path kqemu unhide > Not sure that works with cloning as expected, at least it doesn't do anything here... >than I do ># devfs rule applyset > That also didn't work here, I did: /etc/rc.d/devfs restart >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.. 7-stable here... HTH, Juergen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903051745.n25HjMvK004963>