Every OS has them. Every kernel needs them. You call them drivers and you rarely question it.

So why “driver”?

The plain meaning:

A driver is someone or something that drives: it controls movement, directs power, and keeps a machine on course. The device driver does the same for hardware. It sends commands. It controls timing. It translates what the kernel wants into what the device understands.

That is the literal explanation, and it is enough.

The technical meaning:

A device driver is a piece of kernel code that knows how to operate a specific device and present it through a common interface. It shields the rest of the system from the messy, proprietary details of hardware.

The kernel does not want to speak a hundred dialects. It delegates that to drivers.

The reason the name stuck:

The driver is not the device. The driver is the operator. It pushes the device, keeps it within limits, and absorbs its quirks so the rest of the system can treat it like a civilized citizen.

Drivers are translators, but they are also controllers. They drive the hardware. The name fits.

They could have called them conductors, but that name is reserved for my trains, traveling at 60 km/s. Drivers do not respect speed.

The FreeBSD reality:

FreeBSD keeps drivers inside the kernel, often built in or loaded as kernel modules. They live close to the metal because they must.

If you want to understand a system, follow the drivers. They are where the ideals of an operating system meet the brutal physics of devices.

That collision is why the word survives.

— Kim Jong Rails, Supreme Leader of the Republic of Derails