1makedev.d(5) Linux System Administrator's Manual makedev.d(5)
2
6 makedev.d - configuration files for devices creation through MAKEDEV
7
9 The behavior of MAKEDEV is instrumented by the configuration files in
10 /etc/makedev.d/ directory. They're read and "executed" by MAKEDEV(8) on
11 post installation of the MAKEDEV package.
12 These configuration file consists of a set of lines.
14 All empty lines, and all text on a line after a '#', will be ignored.
16 The remaining lines should all conform to one of the following formats:
18
20 This is a description of the four basic legal directives.
21 =NAME expanded text
23 this define a macro. eg: =BURNER 660 root cdwriter will make
24 MAKEDEV expand $BURNER when encountered.
25 b mask owner group major minor minor_step dev_number root_name base
27 this directive define some block (``b'') device(s) creation.
28 They will be owned by owner and group and will have the major
29 and minor as major and minor numbers.
30 The dev_number arguments define how many devices will be cre‐
31 ated. If dev_number is different from 1, then dev_number devices
32 will be created, their minor number being incremented by
33 minor_step at each step.
34 If only one device is created, it will be named root_name.
35 Else, the devices will be named with regards to the following
36 rules :
37 · If root_name does not contains ``%d'', then ```%d'' is
39 appended to its end.
40 · If base is not set, it is initialized to zero.
42 · Then, at each step, the name of the device we have to
44 created is obtained by incrementing base and replacing
45 ``%d'' by base. This is equivament to these statements :
46 $base++; $file = sprintf($name, $base);
47 c mask owner group major minor minor_step dev_number root_name base
49 is quite the same directive as the previous one, exept its pur‐
50 pose is character devices (``c'') creation.
51 l destination source
53 will make makdev symlink source on destination.
54
56 Since there is currently no standardization in what names are used for
57 system users and groups, it is possible that you may need to modify
58 MAKEDEV's configuration files to reflect your site's settings.
59
61 # /etc/makedev.d/test sample
62 #
63 # the following line create (```c'') the famous /dev/null entry
65 # with 666 mask (file access permissions), with 1 as major and
66 # 3 as minor
67 c 666 root root 1 3 1 1 null
68 # the following line define the STORAGE macro that specify a 660
71 # mask for file permissions, root as owner and disk as group
72 =STORAGE 660 root disk
73 # the following line create 16 /dev/hdaX entries (/dev/hda0 to
75 # /dev/hda15) with the permissions and ownership defined above,
76 # and with 22 as major
77 b $STORAGE 22 0 1 16 hda%d
78 # this one link /dev/snd on alsa entry in procfs
80 # (usually mounted in /proc)
81 l snd ../proc/asound/dev
82
85 The name of the file may contain some ``/'' characters : makdev will
86 create the necessary directories if the node to create must be in a sub
87 directory.
88 Comments must begin on first line character.
89 Files are parsed one by one, after having been sorted by name in alpha‐
90 betical order.
91
93 The /etc/makedev.d/* files contains instructions that instrument makdev
94 to create the device files in /dev. Especially,
95 /etc/makedev.d/00macros define most frequently used macros.
96
98 Linux Allocated Devices
99 It can be found in /usr/share/doc/kernel-doc-<VERSION>/Documenta‐
100 tion/devices.txt if the kernel-doc package is installed. <VERSION> is
101 the version number of the installed kernel (eg: 2.6.32).
102 MAKEDEV(8)
104
106 Thierry Vignaud <tvignaud@mandrakesoft.com>, 2002
107 Hans de Goede <hdegoede@redhat.com>, 2010
108Red Hat Linux 1 June 2010 makedev.d(5)