Dynamic device management in Udev


Article from Issue 71/2006
Author(s): , Author(s): , Author(s):

After three years of hanging around on the sidelines, Udev has finally ousted the legacy Dev-FS system. We take a look under the hood at the Udev device management system inside your Linux system.

Linux inherited the classic Unix adage “Everything is a file.” This abstraction has allowed programs to use device nodes (device files) to access computer hardware as if they were accessing an ordinary file. These special device files, which are opened, read, written to, or closed using the same system calls as text files, are distinguished by their names, types (block or character device), major numbers, and minor numbers. PreviouslyToo Static Device files are created by the mknod command during the installation phase, assuming legacy management. This approach creates a permanent entry in /dev for each device the admin might connect to the system at any time in the future, and this can easily mean thousands of entries.

Buy Linux Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Hotplugging

    Hardware which just works is what every user wants. Current Linux distributions go a long way to fulfilling that dream. In this article, we will be investigating how the hotplug system works.

  • Hardware Detection

    Udev, HAL, and D-Bus provide automated hardware configuration, even if you plug in on the fly. We'll help you easily access new devices.

  • Command Line: Using udev

    Learn how to create your own udev rules and deploy command-line tools to monitor and control udev events to clear your way through the Linux device jungle.

  • Free X.org Server 1.8.0 with udev to Replace HAL

    The X.org project's X server uses udev instead of HAL on Linux and introduces a configuration directory.

  • Ask_Klaus!
comments powered by Disqus