Date: Thu, 5 Mar 2009 19:28:25 +0100 From: Jedrzej Kalinowski <kalinoj1@iem.pw.edu.pl> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: freebsd-emulation@freebsd.org Subject: Re: kqemu and devfs - any luck? Message-ID: <20090305182825.GA24816@volt.iem.pw.edu.pl> In-Reply-To: <200903051745.n25HjMvK004963@saturn.kn-bremen.de> References: <20090305010525.GA69474@volt.iem.pw.edu.pl> <200903051745.n25HjMvK004963@saturn.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thu, Mar 05, 2009 at 06:45:22PM +0100, Juergen Lock napisał(a): > 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 > You were right, I was missing the proper wildcard, I can confirm it works fine: # devfs rule add path 'kqemu*' mode 666 group wheel # devfs rule show 100 path kqemu* group wheel mode 666 # devfs rule apply 100 > > 7-stable here... > > HTH, > Juergen Thanks for your help, Jedrzej Kalinowski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090305182825.GA24816>