Simplifying Embedded Linux Device Management with Devtmpfs

What is Devtmpfs?

Devtmpfs (Device Temporary File System) is a special file system provided by the Linux kernel that automatically creates device nodes early in the system boot process without user space intervention. This feature was introduced in Linux version 2.6.32 and has become the standard solution for device management in modern embedded systems.

Unlike methods that require user space tools (such as mdev or udev) to create device nodes, devtmpfs is entirely managed by the kernel, significantly simplifying the boot process and device management of embedded systems.

Advantages of Devtmpfs

1. Faster Boot Speed: The kernel creates device nodes during the initialization phase, eliminating the need to wait for user space tools to start.
2. Lower Resource Usage: No need to run additional user space daemons.
3. Higher Reliability: Reduces device access issues caused by failures in user space tools.
4. Simpler Configuration: No complex rule files or configuration scripts are required.

Kernel Configuration Requirements

To use devtmpfs, the following options need to be enabled in the Linux kernel:

CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

The first option enables the devtmpfs feature, while the second option allows the kernel to automatically mount devtmpfs to the <span>/dev</span> directory at boot time.

This is achieved in our build script with the following commands:

./scripts/config --file "${LINUX_BUILD_DIR}/.config" --enable DEVTMPFS
./scripts/config --file "${LINUX_BUILD_DIR}/.config" --enable DEVTMPFS_MOUNT

File System Configuration

After using devtmpfs, file system configuration becomes very simple. The main requirements are:

1. Mount devtmpfs

In the system startup script (usually <span>/etc/init.d/rcS</span>), devtmpfs needs to be mounted:

mount -t devtmpfs devtmpfs /dev

2. Basic Directory Structure

Ensure that the basic device-related directories exist:

mkdir -p /dev/pts  # Pseudo terminal support
mkdir -p /dev/shm  # Shared memory support

3. Initialization Script Example

Our script creates the following initialization configuration:

/etc/inittab:

::sysinit:/etc/init.d/rcS
ttyPS0::respawn:/bin/sh
::ctrlaltdel:/sbin/reboot

/etc/init.d/rcS:

#!/bin/sh
mount -t proc proc /proc
mount -t sysfs sysfs /sys
mount -t tmpfs tmpfs /tmp
mount -t devtmpfs devtmpfs /dev
hostname "$(cat /etc/hostname)"

Practical Verification

We provide a complete build script that demonstrates how to configure and use devtmpfs:

1. Get the Code:

   git clone https://gitee.com/znvm/elab.git
   cd elab
   

2. Run the Script:

   ./run-device-devtmpfs.sh
   

3. Observe the Results: The script will automatically compile the kernel and BusyBox, create the root file system, and start the system in QEMU. After booting, you can check the contents of the <span>/dev</span> directory to confirm that the device nodes have been automatically created by the kernel.

Notes

1. Although devtmpfs automatically creates most device nodes, some devices that require specific permissions or ownership may still need user space tools for post-adjustments.
2. For dynamic devices (such as hot-plugging USB devices), additional mechanisms (like udev or mdev) may be needed for handling.
3. Ensure that the kernel version supports devtmpfs (≥ 2.6.32).

Conclusion

Devtmpfs greatly simplifies device management in embedded Linux systems, reducing boot time and resource usage. By automatically handling device node creation with built-in kernel functionality, developers can focus more on application development rather than low-level system configuration.

Visit https://gitee.com/znvm/elab to view the complete code and running scripts, and experience the convenience brought by devtmpfs. You can validate it using the QEMU emulator without the need for actual hardware devices.

Follow us for more exciting content on embedded Linux development in the future!

#Linux #EmbeddedLinux #busybox #qemu #devtmpfs