4 ms·
DNS is pretty straight forward though, because systemd-resolved runs the stub-resolver. So if your /etc/resolv.conf points to it (as it usually will) then every
by XorNot 4y ago
DNS is pretty straight forward though, because systemd-resolved runs the stub-resolver. So if your /etc/resolv.conf points to it (as it usually will) then everything will "just work" fine since it's all DNS requests.
What we really need is something similar for doing users and groups when you get down to it: which we should have because at the end of the day we're really just asking the system tell us some UIDs and GIDs, or what names to assign to such things.
- arccy 4y agoThe answer is, of course, more systemd: https://go.dev/issue/38810 https://go.dev/issue/38810
- aragilar 4y agoWe do, it's nss (which you can configure via nsswitch.conf), which is what the go toolchain is no longer compiling against.
- XorNot 4y agoBut it's not an socket API you can talk to generically: NSS wants you to be linked into libc, is my point. The DNS situation you just implement the protocol and you're done.
- aragilar 4y agoExcept using a socket involves a different process, so you may get a different result than you expect (given namespaces). I'm not that familiar with plan9 (which is where I think most of the namespacing concepts came from), does it allow direct syscalls, or is linux the only system where you can syscall directly?