Re: USB scanners and PR 50340

2016-03-31 Thread Greg Troxel
Thomas Klausner writes: > On Sun, Mar 20, 2016 at 08:24:33AM -0400, Greg Troxel wrote: >> That's not entirely clear. In theory programs that use that, rather >> than how SANE has changed, might still want it. Whether there are any >> such programs that any actual user wants

Re: USB scanners and PR 50340

2016-03-21 Thread Stephen Borrill
On Fri, 18 Mar 2016, Gary Duzan wrote: =>Dave Tyson writes: => =>> I note that PR 50340 has been closed and with the latest pkgsrc =>>under current (amd64) my Mustek 1200 UB scanner seems to work OK =>>- but I have comment out the uscanner device in the kernel and use

Re: USB scanners and PR 50340

2016-03-20 Thread Thomas Klausner
On Sun, Mar 20, 2016 at 08:24:33AM -0400, Greg Troxel wrote: > That's not entirely clear. In theory programs that use that, rather > than how SANE has changed, might still want it. Whether there are any > such programs that any actual user wants to use is unclear. Do you know any such

Re: USB scanners and PR 50340

2016-03-20 Thread Greg Troxel
Nick Hudson writes: > On 03/19/16 19:12, Greg Troxel wrote: >> Martin Husemann writes: >> >>> On Sat, Mar 19, 2016 at 07:17:50PM +0200, Andreas Gustafsson wrote: I think we should disable uscanner in GENERIC now. I have been doing that on my own

Re: USB scanners and PR 50340

2016-03-20 Thread Nick Hudson
On 03/19/16 19:12, Greg Troxel wrote: Martin Husemann writes: On Sat, Mar 19, 2016 at 07:17:50PM +0200, Andreas Gustafsson wrote: I think we should disable uscanner in GENERIC now. I have been doing that on my own systems for years, as uscanner has never worked for me.

Re: USB scanners and PR 50340

2016-03-19 Thread Michael van Elst
On Sat, Mar 19, 2016 at 05:12:11PM +0100, Martin Husemann wrote: > > The ACL would be evaluated in addition to filesystem > > permissions and would match attributes like class/vendor/product/serial/... > > The driver and/or a sysctl setting could determine how an empty > > ACL is handled,

Re: USB scanners and PR 50340

2016-03-19 Thread Greg Troxel
Martin Husemann writes: > On Sat, Mar 19, 2016 at 07:17:50PM +0200, Andreas Gustafsson wrote: >> I think we should disable uscanner in GENERIC now. I have been doing >> that on my own systems for years, as uscanner has never worked for me. >> The permissions issues can be

Re: USB scanners and PR 50340

2016-03-19 Thread Martin Husemann
On Sat, Mar 19, 2016 at 07:17:50PM +0200, Andreas Gustafsson wrote: > I think we should disable uscanner in GENERIC now. I have been doing > that on my own systems for years, as uscanner has never worked for me. > The permissions issues can be fixed later. I agree. Martin

Re: USB scanners and PR 50340

2016-03-19 Thread Greg Troxel
Dave Tyson writes: > I note that PR 50340 has been closed and with the latest pkgsrc under current > (amd64) my Mustek 1200 UB scanner seems to work OK - but I have comment out > the uscanner device in the kernel and use it as a ugen device. It seems that > this is the

Re: USB scanners and PR 50340

2016-03-19 Thread Greg Troxel
Do people think that solving the permissions issue should be related to disabling uscanner in */GENERIC? Here's the list of what I'd change: ./alpha/conf/GENERIC:uscanner* at uhub? port ? ./amd64/conf/GENERIC:uscanner* at uhub? port ? ./amd64/conf/XEN3_DOM0:uscanner* at uhub? port ?

Re: USB scanners and PR 50340

2016-03-19 Thread Martin Husemann
On Sat, Mar 19, 2016 at 03:12:08PM +0100, Michael van Elst wrote: > Changing ownerships of the filesystem entries isn't sufficient. > After all some ugen* can be changed quickly. I expected devpubd to deal with that for us - not sure what you mean here. > I'd prefer either some separate ACLs

Re: USB scanners and PR 50340

2016-03-19 Thread Michael van Elst
On Sat, Mar 19, 2016 at 11:29:09AM +0100, Martin Husemann wrote: > On Sat, Mar 19, 2016 at 08:45:59AM +, Michael van Elst wrote: > > That's a can of worms. You don't even know what a particular ugen* > > device is until you opened and queried it. > > Here is my original suggestion: > >

Re: USB scanners and PR 50340

2016-03-19 Thread Robert Elz
Date:Fri, 18 Mar 2016 20:48:07 -0400 From:"Gary Duzan" Message-ID: <20160319004807.2b63d115...@xen1.duzan.org> | In Message , |Greg Troxel wrote: | =>Perhaps if we had something called

Re: USB scanners and PR 50340

2016-03-19 Thread Michael van Elst
mar...@duskware.de (Martin Husemann) writes: >I tried to get the non-libusb (i.e. uscanner0) version to work with latest >sane-backends, but failed. Does it work in FreeBSD (with /dev/usb/scanner0) ? >Instead we should improve our device ownership handling in a more >general way. Jared

Re: USB scanners and PR 50340

2016-03-19 Thread Martin Husemann
On Fri, Mar 18, 2016 at 09:04:32PM +, Dave Tyson wrote: > I am of the same opinion as the PR originator that it is easier to control > access permissions with a uscanner device rather than having to open up a > whole raft of ugen devices, but I guess the sane developers feel that using >

Re: USB scanners and PR 50340

2016-03-18 Thread Gary Duzan
In Message , Greg Troxel wrote: =>Dave Tyson writes: => =>> I note that PR 50340 has been closed and with the latest pkgsrc =>>under current (amd64) my Mustek 1200 UB scanner seems to work OK =>>- but I have comment out