[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

"m. allan noah" wrote: > I am aware. That is why I asked if it is possible for this smaller, > third-party files to avoid it. Yes, sorry for that. Complete answer this time around ;) Yes it's possible, if they're short enough. It's really an optimization in our rules file because it's so big.

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

On Tue, Nov 17, 2009 at 7:53 PM, Alesh Slovak wrote: > OK, so this thread has sort of exploded. yes- there is a bit of frustration here :) > So the idea so far, is that we want to install the udev/HAL rules generation > tool (with some possible modifications) along with all the .desc files. > >

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

"m. allan noah" wrote: > Ouch. I don't want us to do anything like that. I wonder if it will be > possible for the 'third party' files to avoid using LABEL? We use LABELs already. JB. -- Julien BLACHE

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Johannes Meixner wrote: Hi, >> That was a change in the USB layer in the kernel that needed a >> new/modified udev rule to create the device nodes. > > Perhaps you misunderstood me. > I meant it as an example to show which awkward workarounds are needed > to make this thingy hopefully work for a

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

"m. allan noah" wrote: Hi, > question- If the distro is already producing a modified version of our > tool to turn .desc files into whatever format is required, can we not > install that tool as part of sane? And, can we not modify it such that > it can take arguments to find the .desc file? The

[sane-devel] Canon Lide 35 - invalid argument

On Tue, 17 Nov 2009 14:48:05 +0100, m. allan noah wrote: > On Tue, Nov 17, 2009 at 3:25 AM, Joachim Bergerhoff > wrote: >> Xsane on Ubuntu 9.10 does recognise my Canon Lide 35 scanner and is >> ready to >> work, but gets stuck by this message when attempting a preview or scan: > > There wa

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Hello, On Nov 17 08:42 m. allan noah wrote (shortened): > On Tue, Nov 17, 2009 at 6:42 AM, Julien BLACHE wrote: >> Johannes Meixner wrote: >> >>> What the heck has udev libsane.rules to do >>> with a particular kernel minor version number? >> >> That was a change in the USB layer in the kernel

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Hello, On Nov 17 12:42 Julien BLACHE wrote (shortened): > Johannes Meixner wrote: > >> What the heck has udev libsane.rules to do >> with a particular kernel minor version number? > > That was a change in the USB layer in the kernel that needed a > new/modified udev rule to create the device nod

[sane-devel] 6400 dpi on Epson V700?

David Heinrich writes: > On Mon, Nov 16, 2009 at 4:13 AM, Alessandro Zummo towertech.it> > wrote: > > On Mon, 16 Nov 2009 00:14:34 -0500 > David Heinrich wrote: > > > How do I do that? From the command line, I see the following sane > commands: > > > > sane-config >

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

On Tue, Nov 17, 2009 at 1:47 PM, Julien BLACHE wrote: > "m. allan noah" wrote: > >> Ouch. I don't want us to do anything like that. I wonder if it will be >> possible for the 'third party' files to avoid using LABEL? > > We use LABELs already. I am aware. That is why I asked if it is possible fo

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

On Tue, Nov 17, 2009 at 12:46 PM, Julien BLACHE wrote: > "m. allan noah" wrote: > > Hi, > >> question- If the distro is already producing a modified version of our >> tool to turn .desc files into whatever format is required, can we not >> install that tool as part of sane? And, can we not modify

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Johannes Meixner wrote: Hi, > What the heck has udev libsane.rules to do > with a particular kernel minor version number? That was a change in the USB layer in the kernel that needed a new/modified udev rule to create the device nodes. Now remember that the same people that brought you that un

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Alesh Slovak wrote: > that there is a reason many third party SANE backend providers screw > up when it comes to scanner permissions. I am not trying to blame Yup, and we all know what those reasons are: - developers that know zilch about UNIX development - developers that know zilch about int

[sane-devel] Canon Lide 35 - invalid argument

On Tue, Nov 17, 2009 at 11:14 AM, Wolfram Heider wrote: > On Tue, 17 Nov 2009 14:48:05 +0100, m. allan noah > wrote: > >> On Tue, Nov 17, 2009 at 3:25 AM, Joachim Bergerhoff >> wrote: >>> >>> Xsane on Ubuntu 9.10 does recognise my Canon Lide 35 scanner and is ready >>> to >>> work, but gets stu

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Hello, On Nov 16 08:53 Alesh Slovak wrote (shortened): > ... distro policy ... udev rules ... ... > We can't use a static rules file because each distro > uses slightly different syntax. ... > ... changes distros themselves keep making to their udev rules ... ... > ... breakage nearly every time

[sane-devel] Canon Lide 35 - invalid argument

he scanner ? Finally, I also try a Lide 20 on Xsane and the error message is about the I/O module. Thanks for all good suggestions ! Joachim -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20091117/0d440c

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

Julien BLACHE wrote: > Alesh Slovak wrote: >> We can't use a static rules file because each distro uses slightly >> different syntax. And even then, we can't keep up with all the changes >> distros themselves keep making to their udev rules files resulting in >> breakage nearly every time a new ve

[sane-devel] Canon Lide 35 - invalid argument

On Tue, Nov 17, 2009 at 3:25 AM, Joachim Bergerhoff wrote: > Xsane on Ubuntu 9.10 does recognise my Canon Lide 35 scanner and is ready to > work, but gets stuck by this message when attempting a preview or scan: There was no error given here? > With or without sudo, scanimage -L returns this: >

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

On Tue, Nov 17, 2009 at 6:42 AM, Julien BLACHE wrote: > Johannes Meixner wrote: > > Hi, > >> What the heck has udev libsane.rules to do >> with a particular kernel minor version number? > > That was a change in the USB layer in the kernel that needed a > new/modified udev rule to create the devic

[sane-devel] As instructed by /etc/udev/rules.d/libsane.rules

m. allan noah wrote: > I was under the impression that certain scanners also required > proprietary plugins, but that is irrelevant to this discussion. Yes. > well, its more than just udev, it is also hal .fdi files too. but > certainly the distros could compile the script such that its default >