From owner-freebsd-emulation@FreeBSD.ORG Thu Mar 5 18:23:37 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31EBB106566B for ; Thu, 5 Mar 2009 18:23:37 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 138CE8FC14 for ; Thu, 5 Mar 2009 18:23:37 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id A0F875B5E; Thu, 5 Mar 2009 10:13:31 -0800 (PST) To: Jedrzej Kalinowski In-reply-to: Your message of "Thu, 05 Mar 2009 02:05:26 +0100." <20090305010525.GA69474@volt.iem.pw.edu.pl> References: <20090305010525.GA69474@volt.iem.pw.edu.pl> Comments: In-reply-to Jedrzej Kalinowski message dated "Thu, 05 Mar 2009 02:05:26 +0100." Date: Thu, 05 Mar 2009 10:13:31 -0800 From: Bakul Shah Message-Id: <20090305181331.A0F875B5E@mail.bitblocks.com> Cc: freebsd-emulation@freebsd.org Subject: Re: kqemu and devfs - any luck? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2009 18:23:37 -0000 On Thu, 05 Mar 2009 02:05:26 +0100 Jedrzej Kalinowski 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 <