On Di, 05.02.19 13:08, Martin Wilck ([email protected]) wrote:
> On Mon, 2019-02-04 at 13:19 +0100, Lennart Poettering wrote:
> >
> > reading sysfs attrs is problematics from "remove" rules, as the sysfs
> > device is likely to have vanished by then, as rules are executed
> > asynchronously to the ev
On Mon, 2019-02-04 at 13:19 +0100, Lennart Poettering wrote:
>
> reading sysfs attrs is problematics from "remove" rules, as the sysfs
> device is likely to have vanished by then, as rules are executed
> asynchronously to the events they are run for.
>
> udev will import the udev db from the last
On 04.02.2019 13:19, Lennart Poettering wrote:
> On Do, 31.01.19 14:46, Ziemowit Podwysocki
> ([email protected]) wrote:
>
>> Hello,
>>
>> I have multiple exactly same USB devices. Each device enumerates
>> multiply ttyACM ports under /dev directory. Each port has it unique
>> p
On Mo, 04.02.19 20:22, Petr ([email protected]) wrote:
> Hello,
>
> I have custom linux on embedded machine generated with Buildroot
> using emmc drive which contains root filesystem on /dev/mmcblk0p2
> and application data on /dev/mmcblk0p4. The root fileystem is
> mounted pretty quickly, but the
On 2/4/19 7:22 PM, Petr wrote:
Hello,
I have custom linux on embedded machine generated with Buildroot
using emmc drive which contains root filesystem on /dev/mmcblk0p2
and application data on /dev/mmcblk0p4. The root fileystem is mounted
pretty quickly, but the application data are mount