Date: Sat, 30 Jul 2005 16:13:03 +0200 From: Marc Fonvieille <blackend@freebsd.org> To: Erik =?iso-8859-1?B?TsO4cmdhYXJk?= <norgaard@math.ku.dk> Cc: questions@freebsd.org Subject: Re: scanimage -L doesn't work as normal user Message-ID: <20050730141302.GD596@gothic.blackend.org> In-Reply-To: <Pine.LNX.4.40.0507301518160.15996-100000@shannon.math.ku.dk> References: <20050730120218.GC596@gothic.blackend.org> <Pine.LNX.4.40.0507301518160.15996-100000@shannon.math.ku.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 30, 2005 at 03:42:54PM +0200, Erik Nørgaard wrote: > On Sat, 30 Jul 2005, Marc Fonvieille wrote: > > > On Sat, Jul 30, 2005 at 01:41:20PM +0200, Erik Nørgaard wrote: > > > > Wrong perms on ugen0, read carefully: > > 7.6.4 Allowing Scanner Access to Other Users > > if you want ugen0 appears with the right permissions once you plug your > > scanner. The current devfs scheme you use (Cf. your previous mail) > > should work if you boot directly with your scanner plugged and not if > > you plug it later. > > According to the man-pages, this should be solved by adding the > folowing rules to /etc/devfs.rules: > > # Allow any user to access uscanner and ugen devices rw > add path 'usb0' mode 0666 > add path 'ugen*' mode 0666 > add path 'uscanner*' mode 0666 > you should add a ruleset line before your lines. > I restarted devfs but the devices were created with the wrong > permissions when I plugged in the scanner? > I don't understand the "?" > If I restart devfs after plugging in the scanner permissions are > corrected. But I think this is rather annoying - is this intended? > no problem report has been filed on this issue... [...] I think it's a ruleset issue as I said above. Another thing devfs.rules is for pluggable devices, devfs.conf for devices present at boot time. Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050730141302.GD596>