Rainer Dorsch wrote:
Hi,
>> Chances are the coldplugging happens from the initrd and your script
>> isn't available in the initrd. So check that.
>
> How would I check if coldplugging happens from the initrd?
Well anyway it should be redone once the root FS is mounted and the
/dev/tmpfs is mou
Am Samstag, 26. April 2008 schrieb Julien BLACHE:
> Rainer Dorsch wrote:
>
> Hi,
>
> > The script works now reasonably robust (for now) when I plug the USB
> > scanner. My problem is though, that the script does not get called when I
> > boot the system and the scanner is plugged already during bo
Rainer Dorsch wrote:
Hi,
> The script works now reasonably robust (for now) when I plug the USB scanner.
> My problem is though, that the script does not get called when I boot the
> system and the scanner is plugged already during bootup. Why is this?
Chances are the coldplugging happens fro
Am Donnerstag, 24. April 2008 schrieb Julien BLACHE:
> Johannes Meixner wrote:
>
> Hi,
>
> >> > Be careful with the labels you use. Always use a unique label name, or
> >> > you're asking for troubles. (been there, done that, accidentally
> >> > rendered a number of systems unbootable due to that
Hello,
On Apr 24 22:45 Julien BLACHE wrote (shortened):
> udev is an incredible piece of crap, but the good news is that this
> piece of crap is mostly stable those days. Which is a big step forward
> already.
>
> (and I'll refrain from saying anything at all about the genius who
> invented udev
Johannes Meixner wrote:
Hi,
>> > Be careful with the labels you use. Always use a unique label name, or
>> > you're asking for troubles. (been there, done that, accidentally
>> > rendered a number of systems unbootable due to that ...)
>
> Many thanks for this enlightening info!
> Impressive: A
Johannes Meixner wrote:
Hi,
> I wonder how "scanimage -L" causes any add or remove event at all.
> I cannot imagine that those add or remove events are the
> same add or remove events which happen when the device
> is plugged-in at the USB or plugged-off from the USB.
Not sure about this, but i
Johannes,
Am Donnerstag, 24. April 2008 schrieb Johannes Meixner:
> Hello,
>
> On Apr 23 22:53 Rainer Dorsch wrote:
> > Am Mittwoch, 23. April 2008 schrieb Julien BLACHE:
> > > Johannes Meixner wrote:
> > >
> > > Hi,
> > >
> > > >> umax1220u scripts are started in a sequence (i.e. not in parallel
Hello,
On Apr 23 22:53 Rainer Dorsch wrote:
> Am Mittwoch, 23. April 2008 schrieb Julien BLACHE:
> > Johannes Meixner wrote:
> >
> > Hi,
> >
> > >> umax1220u scripts are started in a sequence (i.e. not in parallel, when
> > >> one is completed the next one starts).
> >
> > When troubleshooting u
Am Mittwoch, 23. April 2008 schrieb Julien BLACHE:
> Johannes Meixner wrote:
>
> Hi,
>
> >> umax1220u scripts are started in a sequence (i.e. not in parallel, when
> >> one is completed the next one starts).
>
> When troubleshooting udev rules, use udevmonitor to actually see
> what's happening in
Johannes Meixner wrote:
Hi,
>> umax1220u scripts are started in a sequence (i.e. not in parallel, when one
>> is completed the next one starts).
When troubleshooting udev rules, use udevmonitor to actually see
what's happening in terms of udev events and their properties.
> ACTION!="add", GOT
Hello,
On Apr 22 22:18 Rainer Dorsch wrote (shortened):
> I want to call a script after I plugged my USB scanner. I use udev for this
> by
> adding a rule
...
> SYSFS{idVendor}=="1606", SYSFS{idProduct}=="0010", MODE="0664",
> GROUP="scanner", NAME="umax%n", RUN+="/usr/local/bin/umax1220u star
Hello,
I want to call a script after I plugged my USB scanner. I use udev for this by
adding a rule
rd at blackbox:/etc/udev/rules.d$ cat z_local.rules
SYSFS{idVendor}=="1606", SYSFS{idProduct}=="0010", MODE="0664",
GROUP="scanner", NAME="umax%n", RUN+="/usr/local/bin/umax1220u start",
rd at b
13 matches
Mail list logo
