|
|
namei(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
nanotime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
nanouptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
NDINIT(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
panic(9) -- Bring down system on fatal error
|
|
The panic() function makes the OpenBSD system terminate. The message fmt is a printf(9) style format string. The message is printed to the console and the location pointed to by the global char pointe... |
|
pfind(9) -- find process / process group by number
|
|
The pfind() and pgfind() functions retrieve process and progress group structures from process and process group IDs. Both functions return NULL if the requested ID can't be found. |
|
pgfind(9) -- find process / process group by number
|
|
The pfind() and pgfind() functions retrieve process and progress group structures from process and process group IDs. Both functions return NULL if the requested ID can't be found. |
|
pgsignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
physio(9) -- initiate I/O on raw devices
|
|
physio() is a helper function typically called from character device read and write routines to start I/O on a user process buffer. It calls back on the provided strategy routine one or more times to ... |
|
pmap(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_clear_modify(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_clear_reference(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_collect(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
