| 1 |
[Introduction] |
| 2 |
|
| 3 |
devnode is a translator that creates the device file for the kernel device. It provides another way for other programs to open the kernel device. |
| 4 |
The device file should be created in /dev with the device name as its file name, so clients can find the device file easily. |
| 5 |
Clients need to get the port to the devnode translator by calling file_name_lookup() and uses this port as a master device port to open the device by calling device_open(). The device name used in device_open() is specified by '-n' option of devnode. |
| 6 |
|
| 7 |
|
| 8 |
[Usage] |
| 9 |
|
| 10 |
Usage: devnode [OPTION...] device |
| 11 |
Hurd devnode translator. |
| 12 |
|
| 13 |
-n, --name=DEVICENAME Accept open from clients only with DEVICENAME |
| 14 |
-M, --master_device=FILE Get a pseudo master device port |
| 15 |
-?, --help Give this help list |
| 16 |
--usage Give a short usage message |
| 17 |
-V, --version Print program version |
| 18 |
|
| 19 |
The '-n' option specifies the device name used by clients in device_open(). It can be optional. If it's specified, clients must use the name to open the device. Otherwise, every device name used by clients in device_open() is acceptable. |
| 20 |
The '-M' option specifies the file where devnode can get the master device port. This option can be useful to open the virtual interface created by eth-multiplexer, for example. |
| 21 |
|
| 22 |
|
| 23 |
[Internal] |
| 24 |
|
| 25 |
devnode is very simple. It implements the server side functions in device.defs, so it can receive the request of opening a device from clients. Only ds_device_open is actually implemented, which opens the device and returns the port to the device. Normally, devnode shouldn't get other requests. |