488889
225
Zoom out
Zoom in
Previous page
1/530
Next page
12
Dynamic Kernel Device
Management with udev
The kernel can add or remove almost any device in a running system. Changes in the
device state (whether a device is plugged in or removed) need to be propagated to
userspace. Devices need to be congured as soon as they are plugged in and recognized.
Users of a certain device need to be informed about any changes in this device's recog-
nized state. udev provides the needed infrastructure to dynamically maintain the device
node les and symbolic links in the /dev directory. udev rules provide a way to plug
external tools into the kernel device event processing. This enables you to customize
udev device handling by, for example, adding certain scripts to execute as part of
kernel device handling, or request and import additional data to evaluate during device
handling.
12.1 The /dev Directory
The device nodes in the /dev directory provide access to the corresponding kernel
devices. With udev, the /dev directory reects the current state of the kernel. Every
kernel device has one corresponding device le. If a device is disconnected from the
system, the device node is removed.
The content of the /dev directory is kept on a temporary le system and all les are
rendered at every system start-up. Manually created or modied les do not, by design,
survive a reboot. Static les and directories that should always be present in the /dev
directory regardless of the state of the corresponding kernel device can be placed in the
/lib/udev/devices directory. At system start-up, the contents of that directory
Dynamic Kernel Device Management with udev 207
225


Need help? Post your question in this forum.

Forumrules


Report abuse

Libble takes abuse of its services very seriously. We're committed to dealing with such abuse according to the laws in your country of residence. When you submit a report, we'll investigate it and take the appropriate action. We'll get back to you only if we require additional details or have more information to share.

Product:

For example, Anti-Semitic content, racist content, or material that could result in a violent physical act.

For example, a credit card number, a personal identification number, or an unlisted home address. Note that email addresses and full names are not considered private information.

Forumrules

To achieve meaningful questions, we apply the following rules:

Register

Register getting emails for Suse openSUSE 12.2 at:


You will receive an email to register for one or both of the options.


Get your user manual by e-mail

Enter your email address to receive the manual of Suse openSUSE 12.2 in the language / languages: English as an attachment in your email.

The manual is 8,65 mb in size.

 

You will receive the manual in your email within minutes. If you have not received an email, then probably have entered the wrong email address or your mailbox is too full. In addition, it may be that your ISP may have a maximum size for emails to receive.

Others manual(s) of Suse openSUSE 12.2

Suse openSUSE 12.2 Quick start guide - English - 284 pages


The manual is sent by email. Check your email

If you have not received an email with the manual within fifteen minutes, it may be that you have a entered a wrong email address or that your ISP has set a maximum size to receive email that is smaller than the size of the manual.

The email address you have provided is not correct.

Please check the email address and correct it.

Your question is posted on this page

Would you like to receive an email when new answers and questions are posted? Please enter your email address.



Info