Skip to main content
deleted 4 characters in body
Source Link
NickD
  • 3k
  • 1
  • 14
  • 23

However, I see videos that teach how to use system calls directly, like this one, where it accesses the read|() and write() system calls.

Despite the fact that wikipedia also calls read and write system calls, I would never think of them as such, and I suspect the author of "Operating System Concepts" you quoted would agree with me. Those functions are instead are members of the POSIX API. Your C code that uses those functions will be portable across POSIX-compliant machines. The API hides the machine- and device-dependent nature of those functions. The implementations of read and write will vary across machines, and they will almost certainly will be system calls in those implementations. But that does not mean that read and write are system calls.

However, I see videos that teach how to use system calls directly, like this one, where it accesses the read|() and write() system calls.

Despite the fact that wikipedia also calls read and write system calls, I would never think of them as such, and I suspect the author of "Operating System Concepts" you quoted would agree with me. Those functions are instead are members of the POSIX API. Your C code that uses those functions will be portable across POSIX-compliant machines. The API hides the machine- and device-dependent nature of those functions. The implementations of read and write will vary across machines, and they will almost certainly will be system calls in those implementations. But that does not mean that read and write are system calls.

However, I see videos that teach how to use system calls directly, like this one, where it accesses the read|() and write() system calls.

Despite the fact that wikipedia also calls read and write system calls, I would never think of them as such, and I suspect the author of "Operating System Concepts" you quoted would agree with me. Those functions are instead members of the POSIX API. Your C code that uses those functions will be portable across POSIX-compliant machines. The API hides the machine- and device-dependent nature of those functions. The implementations of read and write will vary across machines, and they will almost certainly will be system calls in those implementations. But that does not mean that read and write are system calls.

Source Link

However, I see videos that teach how to use system calls directly, like this one, where it accesses the read|() and write() system calls.

Despite the fact that wikipedia also calls read and write system calls, I would never think of them as such, and I suspect the author of "Operating System Concepts" you quoted would agree with me. Those functions are instead are members of the POSIX API. Your C code that uses those functions will be portable across POSIX-compliant machines. The API hides the machine- and device-dependent nature of those functions. The implementations of read and write will vary across machines, and they will almost certainly will be system calls in those implementations. But that does not mean that read and write are system calls.