On 02/09/16 23:39, Ralph Ronnquist wrote:
Dave Turner wrote on 02/09/16 20:12:
On 02/09/16 01:38, Ralph Ronnquist wrote:
Ralph Ronnquist wrote on 01/09/16 08:51:
My worry is that the OS_TYPE=255/255/255 condition is not distinct
enough to make the action apply exactly and only for scanners.
Dave Turner wrote on 02/09/16 20:12:
On 02/09/16 01:38, Ralph Ronnquist wrote:
Ralph Ronnquist wrote on 01/09/16 08:51:
My worry is that the OS_TYPE=255/255/255 condition is not distinct
enough to make the action apply exactly and only for scanners. Comparing
with udev rules, you'll find
The key here is that linux doesn't assume one user. You get to answer, from
first principles, whether a particular USB device belongs to user x or to
root, etc. The mac has a stronger assumption that your mac belongs to you
(which is why the default hostname is "Dave Turner's Mac", etc) and
On 02/09/16 01:38, Ralph Ronnquist wrote:
Ralph Ronnquist wrote on 01/09/16 08:51:
My worry is that the OS_TYPE=255/255/255 condition is not distinct
enough to make the action apply exactly and only for scanners. Comparing
with udev rules, you'll find there are more than a few rules for USB
Ralph Ronnquist wrote on 01/09/16 08:51:
My worry is that the OS_TYPE=255/255/255 condition is not distinct
enough to make the action apply exactly and only for scanners. Comparing
with udev rules, you'll find there are more than a few rules for USB
devices, and almost all of them make their
fsmithred wrote on 01/09/16 06:17:
...
OS_TYPE=255/255/255
...
My worry is that the OS_TYPE=255/255/255 condition is not distinct
enough to make the action apply exactly and only for scanners. Comparing
with udev rules, you'll find there are more than a few rules for USB
devices, and
On 08/31/2016 11:08 AM, info at smallinnovations.nl wrote:
> On 31-08-16 16:38, fsmithred wrote:
>> On 08/31/2016 07:17 AM, fsmithred wrote:
>>> On 08/31/2016 05:03 AM, Ralph Ronnquist wrote:
>> Our discussion in irc was productive. The following works with the stock
>> permissions.sh (without the
On 31-08-16 16:38, fsmithred wrote:
On 08/31/2016 07:17 AM, fsmithred wrote:
On 08/31/2016 05:03 AM, Ralph Ronnquist wrote:
Our discussion in irc was productive. The following works with the stock
permissions.sh (without the lines for setfacl). The acl does not get set,
but the scanner works.
On 08/31/2016 07:17 AM, fsmithred wrote:
> On 08/31/2016 05:03 AM, Ralph Ronnquist wrote:
>> Ralph Ronnquist wrote on 31/08/16 15:54:
>>> Ralph Ronnquist wrote on 31/08/16 10:21:
fsmithred wrote on 31/08/16 07:54:
> ...
> I got it to work. Here's the action file and the
On 08/31/2016 05:03 AM, Ralph Ronnquist wrote:
> Ralph Ronnquist wrote on 31/08/16 15:54:
>> Ralph Ronnquist wrote on 31/08/16 10:21:
>>>
>>>
>>> fsmithred wrote on 31/08/16 07:54:
...
I got it to work. Here's the action file and the helper script. The
helper
script is a
Ralph Ronnquist wrote on 31/08/16 15:54:
Ralph Ronnquist wrote on 31/08/16 10:21:
fsmithred wrote on 31/08/16 07:54:
...
I got it to work. Here's the action file and the helper script. The
helper
script is a modified permissions.sh. I added a test for $VDEV_MAJOR and
$VDEV_MINOR to trigger
Ralph Ronnquist wrote on 31/08/16 10:21:
fsmithred wrote on 31/08/16 07:54:
...
I got it to work. Here's the action file and the helper script. The
helper
script is a modified permissions.sh. I added a test for $VDEV_MAJOR and
$VDEV_MINOR to trigger setfacl. Scanner now works on my
fsmithred wrote on 31/08/16 07:54:
...
I got it to work. Here's the action file and the helper script. The helper
script is a modified permissions.sh. I added a test for $VDEV_MAJOR and
$VDEV_MINOR to trigger setfacl. Scanner now works on my installation.
...
Great. I'll roll it into the
On 08/16/2016 08:35 PM, fsmithred wrote:
> On 08/16/2016 07:54 PM, Ralph Ronnquist wrote:
>> fsmithred wrote on 17/08/16 09:34:
>>> On 08/16/2016 12:49 PM, shraptor wrote:
On 2016-08-16 18:19, shraptor wrote:
> On 2016-08-16 18:11, shraptor wrote:
>>> I got the scanner working.
On 08/16/2016 07:54 PM, Ralph Ronnquist wrote:
> fsmithred wrote on 17/08/16 09:34:
>> On 08/16/2016 12:49 PM, shraptor wrote:
>>> On 2016-08-16 18:19, shraptor wrote:
On 2016-08-16 18:11, shraptor wrote:
>> I got the scanner working.
>>
>> If I boot with udev, the scanner works,
fsmithred wrote on 17/08/16 09:34:
On 08/16/2016 12:49 PM, shraptor wrote:
On 2016-08-16 18:19, shraptor wrote:
On 2016-08-16 18:11, shraptor wrote:
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the device
look like this:
ls -l /dev/bus/usb/002/
On 08/16/2016 12:49 PM, shraptor wrote:
> On 2016-08-16 18:19, shraptor wrote:
>> On 2016-08-16 18:11, shraptor wrote:
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the device
look like this:
ls -l /dev/bus/usb/002/
On 08/16/2016 08:24 PM, fsmithred wrote:
On 08/16/2016 12:29 PM, aitor_czr wrote:
>
>I can't boot the system with vdev:
>
>
> Booting the kernel.
>
> [ . ] Failed to execute / init ( error - 13 )
>
> can't run '/etc/init.d/rsC' No such file or directory
>
If you're
On Tue, 2016-08-16 at 18:29 +0200, aitor_czr wrote:
>
> Hi fsmithred,
>
>
> I can't boot the system with vdev:
>
>
> Booting the kernel.
>
> [ . ] Failed to execute / init ( error - 13 )
>
> can't run '/etc/init.d/rsC' No such file or directory
This is a
On 08/16/2016 12:49 PM, shraptor wrote:
> On 2016-08-16 18:19, shraptor wrote:
>> On 2016-08-16 18:11, shraptor wrote:
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the device
look like this:
ls -l /dev/bus/usb/002/
On 08/16/2016 12:29 PM, aitor_czr wrote:
>
> I can't boot the system with vdev:
>
>
> Booting the kernel.
>
> [ . ] Failed to execute / init ( error - 13 )
>
> can't run '/etc/init.d/rsC' No such file or directory
>
If you're lucky, the fix will be as simple as
On 2016-08-16 18:19, shraptor wrote:
On 2016-08-16 18:11, shraptor wrote:
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the
device
look like this:
ls -l /dev/bus/usb/002/
crw-rw-r--+ 1 root root 189, 137 Aug 16 10:30 010
and with vdev, it looks
Hi fsmithred,
On 08/16/2016 05:36 PM, fsmithred wrote:
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the device
look like this:
ls -l /dev/bus/usb/002/
crw-rw-r--+ 1 root root 189, 137 Aug 16 10:30 010
and with vdev, it looks like this:
crw---
On 2016-08-16 18:11, shraptor wrote:
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the
device
look like this:
ls -l /dev/bus/usb/002/
crw-rw-r--+ 1 root root 189, 137 Aug 16 10:30 010
and with vdev, it looks like this:
crw--- 1 root root 189,
I got the scanner working.
If I boot with udev, the scanner works, and the permissions on the
device
look like this:
ls -l /dev/bus/usb/002/
crw-rw-r--+ 1 root root 189, 137 Aug 16 10:30 010
and with vdev, it looks like this:
crw--- 1 root root 189, 131 Aug 16 10:39 004
I changed the
On 08/15/2016 01:36 PM, aitor_czr wrote:
>
>
> On 08/15/2016 07:12 PM, fsmithred wrote:
>> More testing:
>>
>> Scanner (ScanMaker 4800) is not found by xsane. If I boot with udev
>> instead of vdev, scanner works normally.
>>
>> I installed live-boot, live-config, live-boot-initramfs-tools,
>>
26 matches
Mail list logo
