{"id":2848,"date":"2022-12-20T15:17:29","date_gmt":"2022-12-20T18:17:29","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/makedev-man8\/"},"modified":"2022-12-20T15:17:29","modified_gmt":"2022-12-20T18:17:29","slug":"makedev-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/makedev-man8\/","title":{"rendered":"makedev (man8)"},"content":{"rendered":"

makedev<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
CUSTOMIZATION<\/a>
DEVICES<\/a>
CONFIGURATION<\/a>
FILES<\/a>
BUGS<\/a>
HISTORY<\/a>
RETURN VALUE<\/a>
SEE ALSO<\/a>
AUTHORS<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

makedev \u2212 create devices<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

makedev []<\/b><\/p>\n

DESCRIPTION <\/a> <\/h2>\n

makedev<\/b> is a program that will create the device files in \/dev<\/tt> used to interface with drivers in the kernel.<\/p>\n

Note that programs giving the error \u2018\u2018ENOENT: No such file or directory\u2019\u2019 usually means that the device file is missing, whereas \u2018\u2018ENODEV: No such device\u2019\u2019 usually means the kernel does not have the driver configured or loaded.<\/p>\n

OPTIONS <\/a> <\/h2>\n

<\/b><\/p>\n

The directory where to create the device files.<\/p>\n

<\/b><\/p>\n

Only create device nodes that match (wich can be either a canonical name or a regexp). eg:<\/p>\n

makedev \/dev \u2019dvb.*\u2019<\/i> will create \/dev\/dvb\/adapter0\/*<\/p>\n

makedev \/dev hda<\/i> will create \/dev\/hda<\/p>\n\n\n
\n

CUSTOMIZATION <\/a> <\/h2>\n

Since there is currently no standardization in what names are used for system users and groups, it is possible that you may need to modify makedev<\/b>\u2019s configuration files to reflect your site\u2019s settings.<\/p>\n

DEVICES <\/a> <\/h2>\n

Certain devices are required for minimal functionality. These are:<\/p>\n

mem<\/b> \u2212 access to physical memory; kmem<\/b> \u2212 access to kernel virtual memory; null<\/b> \u2212 null device (infinite sink); port<\/b> \u2212 access to I\/O ports; zero<\/b> \u2212 null byte source (infinite source); core<\/b> \u2212 symlink to \/proc\/kcore<\/b> (for kernel debugging); full<\/b> \u2212 always returns ENOSPACE on write; ram<\/b> \u2212 ramdisk; tty<\/b> \u2212 to access the controlling tty of a process.<\/p>\n

Virtual Terminals<\/b>
console<\/i><\/p>\n

This creates the devices associated with the console. These are the virtual terminals tty<\/b>x<\/i>, where x<\/i> can be from 0 though 63. The device tty0<\/i> is the currently active VT, and is also known as console<\/tt>. For each VT, there are two devices: vcs<\/b>x<\/i> and vcsa<\/b>x<\/i>, which can be used to generate screen-dumps of the VT (vcs<\/b>x<\/i> is just the text, and vcsa<\/b>x<\/i> includes the attributes).<\/p>\n

Serial Devices<\/b>
ttyS{0..63}<\/i><\/p>\n

Serial ports.<\/p>\n

Pseudo Terminals<\/b>
pty[p-s]<\/i><\/p>\n

Each possible argument will create a bank of 16 master and slave pairs. The current kernel (1.2) is limited to 64 such pairs. The master pseudo-terminals are pty[p-s][0-9a-f]<\/b>, and the slaves are tty[p-s][0-9a-f]<\/b>.<\/p>\n

Parallel Ports<\/b><\/p>\n\n\n
<\/td>\n\n

lp<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Standard parallel ports. The devices are created lp0<\/b>, lp1<\/b>, and lp2<\/b>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Bus Mice<\/b>
busmice<\/i><\/p>\n

The various bus mice devices. This creates the following devices: logimouse<\/b> (Logitech bus mouse), psmouse<\/b> (PS\/2-style mouse), msmouse<\/b> (Microsoft Inport bus mouse) and atimouse<\/b> (ATI XL bus mouse) and jmouse<\/b> (J-mouse).<\/p>\n

Joystick Devices<\/b><\/p>\n\n\n
<\/td>\n\n

js<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Joystick. Creates js0<\/b> and js1<\/b>.<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Disk Devices<\/b>
fd[0-7]<\/i><\/p>\n

Floppy disk devices. The device fd<\/b>x<\/i> is the device which autodetects the format, and the additional devices are fixed format (whose size is indicated in the name). The other devices are named as fd<\/b>xLn<\/i>.<\/b> The single letter L<\/i> identifies the type of floppy disk (d = 5.25″ DD, h = 5.25″ HD, D = 3.5″ DD, H = 3.5″ HD, E = 3.5″ ED). The number n<\/i> represents the capacity of that format in K. Thus the standard formats are fd<\/b>x<\/i>d360<\/b>,<\/i> fd<\/b>x<\/i>h1200<\/b>,<\/i> fd<\/b>x<\/i>D720<\/b>,<\/i> fd<\/b>x<\/i>H1440<\/b>,<\/i> and fdx<\/i>E2880.<\/i><\/p>\n

For more information see Alain Knaff\u2019s fdutils package.<\/p>\n

Devices fd0<\/b>*<\/i> through fd3<\/b>*<\/i> are floppy disks on the first controller, and devices fd4<\/b>*<\/i> through fd7<\/b>*<\/i> are floppy disks on the second controller.<\/p>\n

hd[a-d]<\/i><\/p>\n

AT hard disks. The device hd<\/b>x<\/i> provides access to the whole disk, with the partitions being hd<\/b>x<\/i>[0-20].<\/b> The four primary partitions are hd<\/b>x<\/i>1<\/b> through hd<\/b>x<\/i>4,<\/b> with the logical partitions being numbered from hd<\/b>x<\/i>5<\/b> though hd<\/b>x<\/i>20.<\/b> (A primary partition can be made into an extended partition, which can hold 4 logical partitions). By default, only the devices for 4 logical partitions are made. The others can be made by uncommenting them.<\/p>\n

Drives hda and hdb are the two on the first controller. If using the new IDE driver (rather than the old HD driver), then hdc and hdd are the two drives on the secondary controller. These devices can also be used to acess IDE CDROMs if using the new IDE driver.<\/p>\n

sd[a-z], sd[a-c][a-z], sdd[a-x]<\/i><\/p>\n

SCSI hard disks. The partitions are similar to the IDE disks, but there is a limit of 11 logical partitions (sdx<\/i>5 through sdx<\/i>15). This is to allow there to be 128 SCSI disks.<\/p>\n\n\n
<\/td>\n\n

loop<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Loopback disk devices. These allow you to use a regular file as a block device. This means that images of filesystems can be mounted, and used as normal. This creates 16 devices loop0 through loop15.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Tape Devices<\/b>
st[0-7]<\/i><\/p>\n

SCSI tapes. This creates the rewinding tape device st<\/b>x<\/i> and the non-rewinding tape device nst<\/b>x<\/i>.<\/b><\/p>\n\n\n\n
<\/td>\n\n

qic<\/i><\/p>\n<\/td>\n

<\/td>\n\n

QIC-80 tapes. The devices created are rmt8<\/b>, rmt16<\/b>, tape-d<\/b>, and tape-reset<\/b>.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

ftape<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Floppy driver tapes (QIC-117). There are 4 methods of access depending on the floppy tape drive. For each of access methods 0, 1, 2 and 3, the devices rft<\/b>x<\/i> (rewinding) and nrft<\/b>x<\/i> (non-rewinding) are created. For compatability, devices ftape<\/b> and nftape<\/b> are symlinks to rft0<\/b> and nrft0<\/b> respectively.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

CDROM Devices<\/b>
sr[0-7]<\/i><\/p>\n

SCSI CD-ROM\/DVD drives.<\/p>\n

scd[0-7]<\/i><\/p>\n

For compatibility reason (aka historical \u2018\u2018compatibility\u2019\u2019 with RedHat), we provide a \/dev\/scd<\/b>x<\/i> entry for each \/dev\/sr<\/b>x<\/i> device.<\/p>\n\n\n\n
<\/td>\n\n

Audio<\/b><\/p>\n<\/td>\n

<\/td>\n <\/td>\n<\/tr>\n
<\/td>\n\n

sound<\/i><\/p>\n<\/td>\n

<\/td>\n\n

This creates the audio devices used by the sound driver. These include mixer<\/b>, sequencer<\/b>, dsp<\/b>, and audio<\/b>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Miscellaneous<\/b><\/p>\n\n\n\n\n
<\/td>\n\n

sg<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Generic SCSI devices. The devices created are sga<\/b> through sgh<\/b> and sg0<\/b> through sg7<\/b>. These allow arbitary commands to be sent to any SCSI device. This allows for querying information about the device, or controlling SCSI devices that are not one of disk, tape or CDROM (e.g. scanner, CD-R, CD-RW).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

fd<\/i><\/p>\n<\/td>\n

<\/td>\n\n

To allow an arbitary program to be fed input from file descriptor x<\/i>, use \/dev\/fd\/<\/b>x<\/i> as the file name. This also creates \/dev\/stdin<\/b>, \/dev\/stdout<\/b>, and \/dev\/stderr<\/b>. (Note, these are just symlinks into \/proc\/self\/fd).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

apm<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Devices for power management.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Other Devices<\/b><\/p>\n

Note that the present list of devices above is not exhaustive. makedev<\/b> can create more devices nodes. Its aim is to be able to create everything listed in the devices.txt<\/b> file distributed with Linux 2.4.<\/p>\n

CONFIGURATION <\/a> <\/h2>\n

makedev<\/b> doesn\u2019t actually know anything about devices. It reads all of the information from files stored in \/etc\/makedev.d.<\/i> makedev<\/b> will read any and all files in the subdirectory, processing lines in them like so:
devices<\/b><\/p>\n

[b|c]<\/b> mode owner group major minor inc count fmt [base]
count<\/i> devices will be created, with permissions set to mode<\/i> and owned by owner<\/i> and group<\/i>. The first device will be named fmt<\/i>, and additional devices will be created if count<\/i> is larger than 1. If fmt<\/i> contains a C-style formatting string, it will be filled with the sum of base<\/i> and zero. Subsequent devices will be filled with the sum of base<\/i> and n<\/i> bodies manpages.csv script_extrae_body.sh script.sh usr inc<\/i>, where n<\/i> is the order this device is being created in. If the format string did not already include a format specifier, a “%d” will automatically be appended to it to make this work.<\/p>\n

symbolic links<\/b><\/p>\n

l<\/b> linkname target
A symbolic link pointing to target<\/i> named linkname<\/i> will be created.<\/p>\n

aliases<\/b><\/p>\n

a<\/b> alias value
Any commands that create devices for alias<\/i> will also include devices that would be crated for value<\/i>.<\/p>\n

FILES <\/a> <\/h2>\n

The \/etc\/makedev.d\/*<\/i> files contains instructions that instrument makdev<\/b> to create the device files in \/dev.<\/p>\n

BUGS <\/a> <\/h2>\n

makedev<\/b> need to be run by root in order to work smoothly since mknod(2)\u00a0<\/b> won\u2019t work for non privilegied users (basically those who don\u2019t have EUID==0). Indeed, the mknod(2)\u00a0<\/b> syscall need the CAP_MKNOD<\/i> permissions (see linux\/capability.h<\/b>)
Usually, any problems we\u2019ll find will be confined to the configuration files, which were written by examining the devices.txt file.<\/p>\n

HISTORY <\/a> <\/h2>\n

Debian first come with a script building the \/dev\/*<\/i> devices files (the makedev<\/b> script).<\/p>\n

RedHat enhanced that idea with the MAKEDEV<\/b> package. This package was made of two parts :<\/p>\n\n\n\n
<\/td>\n\n

\u00a0<\/p>\n<\/td>\n

<\/td>\n\n

the first one is a set of config files and script that generate config files. These files usually reside in \/etc\/makedev.d\/<\/i>.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0<\/p>\n<\/td>\n

<\/td>\n\n

the second was MAKEDEV<\/b>, a program written in C that read the \/etc\/makedev.d\/*<\/i> files to create the actual devices files.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Mandrake further enhanced its predecessors in various ways :<\/p>\n\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

the generator scripts build configuration files that are faster to parse and to handle<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

there\u2019s a new makedev<\/b> perl program that create all devices in a very fast way<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

RETURN VALUE <\/a> <\/h2>\n

The exit code returned by makedev<\/b> is either 0 (\u2018\u2018no error\u2019\u2019) or 255. In that case, an error message will be displayed:
\u2018\u2018unrecognized macro MACRO at “LINE”\u2019\u2019<\/p>\n

makedev<\/b> didn\u2019t recognize the macro MACRO<\/i> on the quoted line LINE<\/i> (see makedev<\/b>(5) for further informations about macros)<\/p>\n

\u2018\u2018unrecognised line “LINE”\u2019\u2019<\/p>\n

makedev<\/b> failled in parsing the line quoted in LINE<\/i> ; the line did not begin by a character in the [bcls]<\/i> set<\/p>\n

SEE ALSO <\/a> <\/h2>\n

intro<\/b>(4), devfsd<\/b>(8), makdev<\/b>(5).<\/p>\n

AUTHORS <\/a> <\/h2>\n

Pascal Rigaux <pixel@mandrakesoft.com<\/i>>, 2002
Thierry Vignaud <tvignaud@mandrakesoft.com<\/i>>, 2002<\/p>\n

The device database is heavily inspirated by Redhat one.<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

makedev \u2212 create devices <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,198,4],"class_list":["post-2848","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-makedev","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/2848","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=2848"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/2848\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=2848"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=2848"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=2848"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}