From owner-freebsd-current@FreeBSD.ORG  Mon Oct 20 04:44:56 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6333E16A4B3; Mon, 20 Oct 2003 04:44:56 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E9D0743FDD; Mon, 20 Oct 2003 04:44:52 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id h9KBio4b009572;
	Mon, 20 Oct 2003 13:44:50 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Andreas Klemm <andreas@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 20 Oct 2003 13:35:14 +0200."
             <20031020113514.GA875@titan.klemm.apsfilter.org> 
Date: Mon, 20 Oct 2003 13:44:50 +0200
Message-ID: <9571.1066650290@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: USB problem: /dev/ugen* dynamically auto-reconfigures to
	root:operator 644, so non-root user unable to access USB devices
	even if wanted 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Oct 2003 11:44:56 -0000

In message <20031020113514.GA875@titan.klemm.apsfilter.org>, Andreas Klemm writ
es:

>1) /etc/devfs.conf with:
>        perm    ugen1   0666
>        perm    ugen1.1 0666
>        perm    ugen1.2 0666
>        perm    ugen1.3 0666

I would probably just use a wildcard:

	perm	ugen* 0666

>1st needs a command like
>	devfs ruleset 100

This makes the rules only apply to devices arriving in the future,
you also need:

	devfs rule applyset

to make them apply to currently available devices.

>3. step, try to access camera
>   by klick on the Canon PowerShot G5 line in digikam
>
>"failed to initialize the camera"
>
>root@titan[ttyp2]{6} ~ ls -l /dev/ugen*
>crw-r--r--  1 root  operator  114,   0 Oct 20 13:14 /dev/ugen0
>crw-r--r--  1 root  operator  114,   2 Oct 20 13:14 /dev/ugen0.2
>crw-rw-rw-  1 root  operator  114,  16 Oct 20 13:14 /dev/ugen1
>crw-r--r--  1 root  operator  114,  17 Oct 20 13:14 /dev/ugen1.1
>crw-r--r--  1 root  operator  114,  18 Oct 20 13:14 /dev/ugen1.2
>crw-r--r--  1 root  operator  114,  19 Oct 20 13:14 /dev/ugen1.3
>
>And voila, ther permission are wrong again.

I have no idea what goes on here.

>And BTW, shouldn't the devfs(8) manpage have a reference
>to devfs.conf ? I understand, that /etc/devfs.conf is only
>used by the /etc/rc.d/devfs startup script, to setup permissions
>via chmod commands and such .... so no real relationship to the
>devfs command.

Yes, probably a good idea.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.