In message <20031020113514.GA875_at_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_at_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_at_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.Received on Mon Oct 20 2003 - 02:44:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:26 UTC