]>
Commit | Line | Data |
---|---|---|
b1830e79 GKH |
1 | Frequently Asked Questions about udev |
2 | ||
3 | ||
4 | Q: What's this udev thing, and what is it trying to do? | |
5 | A: Read the OLS 2003 paper about udev, available in the docs/ directory, | |
6 | and at: | |
7 | <http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf> | |
8 | There is also a udev presentation given at OLS 2003 available at: | |
9 | <http://www.kroah.com/linux/talks/ols_2003_udev_talk/> | |
10 | ||
11 | Q: How is udev related to devfs? | |
12 | A: udev works entirely in userspace, using /sbin/hotplug calls that the | |
13 | kernel makes whenever a device is added or removed from the kernel. All | |
14 | naming policy, and permission control is done in userspace. devfs | |
15 | operated from within the kernel. | |
16 | ||
17 | Q: Why was devfs marked OBSOLETE if udev is not finished yet? | |
18 | A: To quote Al Viro (Linux VFS kernel maintainer): | |
19 | - it was determined that the same thing could be done in userspace | |
20 | - devfs had been shoved into the tree in hope that its quality will | |
21 | catch up | |
22 | - devfs was found to have fixable and unfixable bugs | |
23 | - the former had stayed around for many months with maintainer | |
24 | claiming that everything works fine | |
25 | - the latter had stayed, period. | |
26 | - the devfs maintainer/author disappeared and stoped maintaining | |
27 | the code. | |
28 | ||
29 | Q: But udev will not automatically load a driver if a /dev node is opened | |
30 | when it is not present like devfs will do. | |
31 | A: If you really require this functionality, then use devfs. It is still | |
32 | present in the kernel. | |
33 | ||
10a479f5 GKH |
34 | Q: But wait, I really want udev to automatically load drivers when they |
35 | are not present but the device node is opened. It's the only reason I | |
36 | like using devfs. Please make udev do this. | |
37 | A: No. udev is for managing /dev, not loading kernel drivers. | |
38 | ||
39 | Q: Oh come on, pretty please. It can't be that hard to do. | |
40 | A: Such a functionality isn't needed on a properly configured system. All | |
41 | devices present on the system should generate hotplug events, loading | |
42 | the appropriate driver, and udev will notice and create the | |
43 | appropriate device node. If you don't want to keep all drivers for your | |
44 | hardware in memory, then use something else to manage your modules | |
45 | (scripts, modules.conf, etc.) This is not a task for udev. | |
46 | ||
47 | Q: I really like the devfs naming scheme, will udev do that? | |
b1830e79 GKH |
48 | A: Yes, udev can create /dev nodes using the devfs naming policy. A |
49 | configuration file needs to be created to map the kernel default names | |
10a479f5 GKH |
50 | to the devfs names. See the initial udev.conf.devfs file in the udev |
51 | release. It is the start of such a configuration file. If there are | |
52 | any things missing, please let the udev authors know. | |
b1830e79 GKH |
53 | |
54 | Q: What kinds of devices does udev create nodes for? | |
55 | A: All devices that are shown in sysfs will work with udev. If more | |
56 | support is added for devices to the kernel, udev will automatically | |
57 | start working for them. All block devices are currently supported, and | |
58 | almost all major char devices are supported. Kernel developers are | |
59 | working on adding support for all char devices at this time. See the | |
60 | linux-kernel mailing list for patches and status of these patches. | |
61 | ||
62 | Q: Will udev remove the limit on the number of anonymous devices? | |
63 | A: udev is entirely in userspace. If the kernel supports a greater number | |
64 | of anonymous devices, udev will support it. | |
65 | ||
66 | Q: Will udev support symlinks? | |
10a479f5 | 67 | A: Yes, It now does. Multiple symlinks per device node too. |
b1830e79 GKH |
68 | |
69 | Q: How will udev support changes to device permissions? | |
70 | A: On shutdown, udev will save the state of existing device permissions to | |
71 | its database, and then used the on the next boot time. | |
72 | ||
73 | Q: How will udev handle the /dev filesystem? | |
74 | A: /dev can be a ramfs, or a backing filesystem. udev does not care what | |
75 | kind of filesystem it runs on. | |
76 | ||
77 | Q: How will udev handle devices found before init runs? | |
78 | A: udev will be placed in initramfs and run for every device that is found. | |
79 | Work to get this implemented is still underway. | |
80 | ||
81 | Q: I have other questions about udev, where do I ask them? | |
82 | A: The linux-hotplug-devel mailing list is the proper place for it. The | |
83 | address for it is linux-hotplug-devel@lists.sourceforge.net | |
84 | Information on joining can be found at | |
85 | <https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel> | |
86 | Archives of the mailing list can be found at: | |
87 | <http://marc.theaimsgroup.com/?l=linux-hotplug-devel> | |
88 |