#4745: systemd-247
--------------------+-----------------------
Reporter: renodr | Owner: renodr
Type: task | Status: assigned
Priority: normal | Milestone: 10.1
Component: Book | Version: SVN
Severity: normal | Resolution:
Keywords: |
--------------------+-----------------------
Comment (by ken@…):
Replying to [comment:9 renodr]:
>
> {{{
> CHANGES WITH 247:
>
> * KERNEL API INCOMPATIBILITY: Linux 4.14 introduced two new
uevents
> "bind" and "unbind" to the Linux device model. When this
kernel
> change was made, systemd-udevd was only minimally updated to
handle
> and propagate these new event types. The introduction of these
new
> uevents (which are typically generated for USB devices and
devices
> needing a firmware upload before being functional) resulted in
a
> number of issues which we so far didn't address.
}}}
If you are able to read lwn,net, this was discussed a while ago.
[ https://lwn.net/SubscriberLink/837033/8e8a3f0c499d267c/ ]
The real problem is that nobody reported it to the kernel devs for over a
year, by which time it was a bit late.
The way I read it, anything which causes a bind or unbind event will now
likely break some udev rules (example - a fedora rule which skipped if the
action was not 'add' or 'change', fix to change the rule to skip only if
the action was 'remove'.)
That kernel change happened three years ago. An original report (one
where 4.12 was blamed, for debian) can be found at
[https://github.com/systemd/systemd/issues/8221]. What sounds like a
sensible reply from Lennart Poettering (!) was to list negatives instead
of positives (for bind events).
Long story short - any added udev rules might need to be adapted.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/4745#comment:12>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://lists.linuxfromscratch.org/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
