New answers tagged

1

On any POSIX system, the interface between applications and the kernel is a few function calls: open, read, write, close, etc. An application such as cat calls those functions; it doesn't care how the functions are implemented under the hood. On Unix systems, those functions are actually system calls: the application calls the kernel. Inside the kernel, a ...


2

The Unix/Linux system offers the POSIX system calls open(2)/close(2)/read(2)/write(2) and stat(2) and some higher-level functions like opendir(3)/closedir(3)/readdir(3), which are enough to write the tools stated (it is easier using the C wrappers). Part of the hard job of the kernel is precisely to make them work on the various filesystems offered, and make ...


1

For most tools, the underlying layer is the C Standard Library ("libc"). libc provides a number of low-level file handling routines, such as open, read, and write. These routines in turn interface to the filesystem layer in the kernel, which sits on top of the kernel's block device layer, the device drivers, and finally the hardware. One implementation of ...


0

There's CocoTron under an MIT license, but I can't tell if it is still alive or not. https://github.com/cjwl/cocotron . Has code checked in from 6 months ago but don't see much on the net about it.



Top 50 recent answers are included