Manual Pages  — INTRO

The device abstraction generally provides a common set of system calls, which are dispatched to the corresponding device driver by the upper layers of the kernel. The set of system calls available for devices is chosen from open(2), close(2), read(2), write(2), ioctl(2), select(2), and mmap(2). Not all drivers implement all system calls; for example, calling mmap(2) on a keyboard device is not likely to be useful.

Aspects of the device abstraction have changed significantly in FreeBSD over the past two decades. The section Historical Notes describes some of the more important differences.

The devfs(5) filesystem creates or removes device nodes automatically according to the physical hardware recognized as present at any given time. For pseudo-devices, device nodes may be created and removed dynamically as required, depending on the nature of the device.

Access restrictions to device nodes are usually subject to the regular file permissions of the device node entry, instead of being enforced directly by the drivers in the kernel. But since device nodes are not stored persistently between reboots, those file permissions are set at boot time from rules specified in devfs.conf(5), or dynamically according to rules defined in devfs.rules(5) or set using the devfs(8) command. In the latter case, different rules may be used to make different sets of devices visible within different instances of the devfs(5) filesystem, which may be used, for example, to prevent jailed subsystems from accessing unsafe devices. Manual changes to device node permissions may still be made, but will not persist.

Drivers need not be statically compiled into the kernel; they may also be loaded as modules, in which case any device nodes they provide will appear only after the module is loaded (and has attached to suitable hardware, if applicable).

Buffered devices were accessed through a buffer cache maintained by the operating system; historically this was the system's primary disk cache, but in FreeBSD this was rendered obsolete by the introduction of unified virtual memory management. Buffered devices could be read or written at any byte position, with the buffer mechanism handling the reading and writing of disk blocks. In contrast, raw disk devices can be read or written only at positions and lengths that are multiples of the underlying device block size, and write(2) calls are synchronous, not returning to the caller until the data has been handed off to the device.