Re: systemd-resolved

This is a multi-part message in MIME format...

------------=_1785347625-1024790-6369
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit



On 7/29/26 13:50, Pocket ([email protected] via lfs-support Mailing 
List) wrote:
> 
> On 7/29/26 13:40, Bruce Dubbs ([email protected] via lfs-support 
> Mailing List) wrote:
>> On 7/29/26 12:20 PM, Pocket ([email protected] via lfs-support 
>> Mailing List) wrote:
>>>
>>>     Version r13.0-152-systemd
>>>
>>>
>>>     Published July 15th, 2026
>>>
>>> I am getting the following:
>>>
>>> systemctl status systemd-resolved
>>>
>>> ● systemd-resolved.service - Network Name Resolution
>>>       Loaded: loaded (/usr/lib/systemd/system/systemd- 
>>> resolved.service; enabled; preset: enabled)
>>>       Active: active (running) since Wed 2026-07-29 12:52:41 EDT; 
>>> 8min ago
>>>   Invocation: ede09af4600849f5ad0c959bb88aff86
>>> TriggeredBy: ● systemd-resolved-varlink.socket
>>>               ● systemd-resolved-monitor.socket
>>>         Docs: man:systemd-resolved.service(8)
>>>               man:org.freedesktop.resolve1(5)
>>> https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
>>> https://systemd.io/WRITING_RESOLVER_CLIENTS
>>>     Main PID: 162 (systemd-resolve)
>>>       Status: "Processing requests..."
>>>        Tasks: 1 (limit: 19149)
>>>          CPU: 49ms
>>>       CGroup: /system.slice/systemd-resolved.service
>>>               └─162 /usr/lib/systemd/systemd-resolved
>>>
>>> Jul 29 12:52:40 lfs systemd[1]: Starting Network Name Resolution...
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: Positive Trust Anchors:
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: . IN DS 20326 8 2 
>>> e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: . IN DS 38696 8 2 
>>> 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: Negative trust anchors: 
>>> home.arpa 10.in- addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 
>>> 18.172.in-addr.arpa 19.172.in- addr.arpa 20.172.in-addr.arpa 
>>> 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in- addr.arpa 
>>> 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 
>>> 27.172.in- addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 
>>> 30.172.in-addr.arpa 31.172.in- addr.arpa 170.0.0.192.in-addr.arpa 
>>> 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa 
>>> ipv4only.arpa resolver.arpa corp home internal intranet lan local 
>>> private test
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: Shared library 
>>> 'libcrypto.so.3' is not available: libcrypto.so.3: cannot open shared 
>>> object file: No such file or directory
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: Shared library 
>>> 'libssl.so.3' is not available: libssl.so.3: cannot open shared 
>>> object file: No such file or directory
>>> Jul 29 12:52:41 lfs systemd-resolved[162]: Using system hostname 'lfs'.
>>> Jul 29 12:52:41 lfs systemd[1]: Started Network Name Resolution.
>>>
>>>
>>> resolvectl:
>>>
>>>
>>> Global
>>>         Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported
>>> resolv.conf mode: foreign
>>>        DNS Domain: home.arpa
>>>
>>> Link 2 (end0)
>>>      Current Scopes: DNS
>>>           Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS 
>>> DNSSEC=yes/supported
>>> Current DNS Server: 192.168.0.2
>>>         DNS Servers: 192.168.0.2
>>>          DNS Domain: home.arpa
>>>       Default Route: yes
>>>
>>>
>>> There isn't libcrypto.so.3 or libssl.so.3
>>>
>>> find /usr/lib -name 'libcrypto*'
>>> /usr/lib/pkgconfig/libcrypto.pc
>>> /usr/lib/libcrypto.so
>>> /usr/lib/libcrypto.so.4
>>>
>>> find /usr/lib -name 'libssl*'
>>> /usr/lib/pkgconfig/libssl.pc
>>> /usr/lib/libssl.so
>>> /usr/lib/libssl.so.4
>>> /usr/lib/libssl3.so
>>
>> It looks like you have portions of both openssl3 and openssl4 
>> present.  Check the contents of libcrypto.pc and libssl.pc.   What 
>> version of systemd do you have? There are a lot of changes needed for 
>> openssl4 if you are doing an in-place update.
>>
>> You are using a development version of LFS (r13.0-152-systemd) which 
>> is quite a bit out of date.  The current version is -160 and there 
>> will be a new version on Saturday with some significant package updates.
>>
>>   -- Bruce
> 
> 
> I cloned the lfs.git repo and made the book myself
> 
> This build is straight from that book version I posted
> 
> Systemd-261.1
> 
> OpenSSL-4.0.1
> 
> 
> The .pc files are as follows
> 
> libcrypto.pc
> 
> prefix=/usr
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> includedir=${prefix}/include
> modulesdir=${libdir}/ossl-modules
> 
> Name: OpenSSL-libcrypto
> Description: OpenSSL cryptography library
> Version: 4.0.1
> Libs: -L${libdir} -lcrypto
> Libs.private: -ldl -pthread
> Cflags: -I${includedir}
> 
> 
> libssl.pc
> 
> prefix=/usr
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> includedir=${prefix}/include
> 
> Name: OpenSSL-libssl
> Description: Secure Sockets Layer and cryptography libraries
> Version: 4.0.1
> Requires.private: libcrypto
> Libs: -L${libdir} -lssl
> Cflags: -I${includedir}
> 
> 
> I am of the opinion that resolved will not link to /usr/lib/libssl.so.4 
> and /usr/lib/libcrypto.so.4
> 
> Archlinux has not update to openssl 4 as of today, so I think is is an 
> issue with systemd
> 
> Things may still be i a state of flux.
> 
Oh I forgot to add that I copied my build to a USB and booted to that 
and rebuilt systemd after I determined that there is a openssl3 
libraries laying around.

As you see from my find version 3 is miss in action.

-- 
Hindi madali ang maging ako


------------=_1785347625-1024790-6369
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page
------------=_1785347625-1024790-6369--