[BRLTTY] Are changes needed for systemd 247.1?

[Alexander Epaneshnikov]

09.12.2020 01:39, Dave Mielke пишет:
> [quoted lines by Alexander Epaneshnikov on 2020/12/09 at 01:30 +0300]
>
>> that was recommendation from upstream systemd.
>> snip from systemd news:
>>>             • All rule files that currently use a header guard similar to
>>>               ACTION!="add|change",GOTO="xyz_end" should be updated to use
>>>               ACTION=="remove",GOTO="xyz_end" instead, so that the
>>>               properties/tags they add are also applied whenever "bind" (or
>>>               "unbind") is seen. (This is most important for all physical device
>>>               types — those for which "bind" and "unbind" are currently
>>>               generated, for all other device types this change is still
>>>               recommended but not as important — but certainly prepares for
>>>               future kernel uevent type additions).
>>>
>>>             • Similarly, all code monitoring devices that contains an 'if' branch
>>>               discerning the "add" + "change" uevent actions from all other
>>>               uevents actions (i.e. considering devices only relevant after "add"
>>>               or "change", and irrelevant on all other events) should be reworked
>>>               to instead negatively check for "remove" only (i.e. considering
>>>               devices relevant after all event types, except for "remove", which
>>>               invalidates the device). Note that this also means that devices
>>>               should be considered relevant on "unbind", even though conceptually
>>>               this — in some form — invalidates the device. Since the precise
>>>               effect of "unbind" is not generically defined, devices should be
>>>               considered relevant even after "unbind", however I/O errors
>>>               accessing the device should then be handled gracefully.
> Thanks. Now I can see what they want - all possible actins to be tagged with
> systemd. Please test the latest code. It now just tests for add and then goes
> to default.
>
now all is well.

-- 
Sincerely, Alexander.