Can I use a system call? (justine.lol)

Article summary

The article discusses the use of system calls, specifically in the context of Cosmopolitan libc. The comments reveal that the article explores the complexities of system calls and their interactions with different operating systems. The discussion delves into the details of system call implementation, portability, and the role of libc. The article's content is not directly available, but the comments provide insight into the topics covered.

Main themes

• system calls
• libc and portability
• operating system compatibility
• vDSO and kernel ABI
• alternative libcs
• system call stability and compatibility

What commenters say

• System calls are provided by the operating system and can be accessed directly or through a C library.
• Using libc is not always necessary or desirable, and alternative approaches are possible.
• Some operating systems, like macOS, have a complex relationship between system calls and libc, making direct system calls problematic.
• The stability of system call ABIs varies across operating systems, with some, like Linux, having a stable ABI, while others, like Windows, do not.
• The use of vDSO (virtual dynamic shared object) can provide a way to access system calls without linking against libc.
• The development of alternative libcs, like Cosmopolitan libc, is possible and can be beneficial, but may face opposition from those who believe in the primacy of the system's libc.
• The portability of system calls across different operating systems is a significant challenge.
• Direct system calls can be useful for avoiding dependencies on system libs, but may require additional considerations for compatibility and stability.