|
|
|
|
|
|
by 1718627440
239 days ago
|
|
|
> If it ever breaks, it's a bug in the Linux kernel. No, your program will still instruct the kernel to do the same. It will just cause conflicts with the other OS internals. > Can you give concrete examples of this? Adding another encoding as a gconv module. The DNS issues everyone is talking about. I don't know what that gets you compared to using syscall(2) and -static. When you want your program to depend on the kernel API instead of the OS API, then you should really link libc statically. |
|
|
But not with the kernel.
"Other OS internals" are just replaceable components. The idea is to depend on Linux only, not on Linux+glibc.
> Adding another encoding as a gconv module. The DNS issues everyone is talking about.
Those are glibc problems, not Linux problems. Linux does not perform name resolution or character encoding conversion.