So it is time to replace dhcpcd with ISC dhclient? Slackware bundles the ISC dhcp package anyway, so what is the point of using dhcpcd? It doesn't even support DHCPv6.

The code that generates this error was introduced after dhcpcd 6.0.5 (version that ships with Slackware 14.1). You should mention your system is not stock Slackware.

To see if I could reproduce, I built dhcpcd 6.1.2, which does have the relevant code, on stock Slackware64-14.1.

Unlike yours, my dhcpcd looks for & finds udev.so in /usr/lib64/dhcpcd/dev (not /lib/dhcpcd/dev) and has no issue getting the address for dev_init (symbol confirmed present).

I did nothing special. Here's my configure line:

--mancha

RandomTroll, did you perhaps install dhcpcd from a binary package, rather than building it from a SlackBuild or compiling it from sources?

Technically you probably could import LFS's systemd-extracted udev package for Slackware, but you'd need to possibly adjust the scripts for the rule sets accordingly, and to install install other extras for things like gudev, gobject files, and keymaps you'd need their dependencies, which I know those require gobject-introspection, Glib, Gperf, as well as optionals like pciutils, usbutils, and acl to function.

I don't know how much of systemd-udev is different from classic udev, but from my experience with it, it works fairly much the same.

I build dhcpcd from source. I started doing it because I had a problem with dhcpcd and wanted to see if a custom build would solve it. I found out that my problem was my own ignorance about how dhcpcd worked. I keep on building my own version because I want its log entries to go to a file dedicated for that purpose, so I wrote a script to modify the source for that; I'm on the developer's mailing list so I get alerts of upgrades.

This particular problem, dev_init not being found, doesn't seem to cause me a problem. I told the dhcpcd developer in case the information would be of use to him; maybe a problem lurks. He suggested it could be my udev. That's what sent me to looking into more recent udev packages. I only mentioned it because enorbet asked. Finding out about the status of udev in Slackware filled my bill. I wasn't expecting a kind of Spanish Inquisition.

Ummm did I miss something? I didn't see anyone treat OP disrespectfully. The questions are either to gain advantage to help OP or oneself. Don't forget that even face-to-face speech can easily be misinterpreted. Text with zero body language even moreso. It seems wise to avoid being quick to taking offense online, IMHO.

I don't know whether you missed anything. I didn't take offense; I didn't think anyone treated me disrespectfully; I didn't say anyone did.

I asked one question. I got an answer. Then enorbet asked me a peripheral question about why I wanted a new udev. I was glad to answer. Then people tried to diagnose the cause of the warning dhcpcd reported, the reason why I asked the original question. I didn't mind, but I didn't ask for it. I hoped that the reference to the Spanish Inquisition would tip readers to irony deployed for humorous purpose. Perhaps I'm too old: kids these days aren't up on their Monty Python.

'Tis but a scratch

and now for something completely different -----

1 members found this post helpful.