Announcement

Collapse
No announcement yet.

Asynchronous Device/Driver Probing For The Linux Kernel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Originally posted by gens View Post
    even more then that the systemd udev does not anymore change network interface names to be persistent after reboot
    but for some reason they decided to give them dumb names (it's still a good thing; thank dell for that)
    *they are now names from bios/firmware/whatever
    the physical path to the device, that is

    Comment


    • #22
      Originally posted by nanonyme View Post
      You mean like out-of-order results with probing? That sounds sensible
      Yes, something along those lines where devices can be queried and the system will not necessarily wait for a response thus moving on. Slow devices might respond a little later on to udev's query then udev will then load the driver for that device and initialize it. So then this does sound like udev firing off queries and then not waiting for the responses but will then act on responses as they are received from devices.

      Comment


      • #23
        Originally posted by liam View Post
        That's certainly the way it was when udev was in userspace, but are you sure that's still the case?

        Yeah, sure it is.

        Originally posted by liam View Post
        Do you recall all the moaning around having udev merged with systemd and, subsequently, integrated into the kernel?
        The only thing that happend to udev was moving the code into systemd's repository. There is still no runtime dependency on systemd (as PID 1).

        Comment

        Working...
        X