MAKEDEV(8)

πŸ“¦
version 2.3.1 Β· 2 versions
, in debian bookworm, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute

πŸ’… MAKEDEV(8) β€” Make Linux Devices ✨

πŸŽ€ NAME πŸŽ€

MAKEDEV β€” create devices πŸ’– (yes bestie, it literally just makes devices, that's the whole job)


πŸ“œ SYNOPSIS πŸ“œ

cd /dev; ./MAKEDEV [ -n ] [ -v ] [ update ]
cd /dev; ./MAKEDEV [ -n ] [ -v ] [ generic ] [ local ] [ group-keyword ... device ... ]
cd /dev; ./MAKEDEV [ -n ] [ -v ] [ -d ] device ...

🌸 DESCRIPTION 🌸

Okay so MAKEDEV is a script that will create the devices in /dev used to interface with drivers in the kernel. That's it, that's the vibe. ✨

Not me explaining the two errors you'll see in the wild, because they are NOT the same thing: programs giving the error ENOENT: No such file or directory normally means that the device file is missing, whereas ENODEV: No such device normally means the kernel does not have the driver configured or loaded. Two different problems, two different fixes, do not confuse them fr fr 😭

βš™οΈ OPTIONS βš™οΈ

  • -n β€” Do not actually update the devices, just print the actions that would be performed. It's giving dress rehearsal 🎭 β€” you see the whole show, nothing actually happens.
  • -d β€” Delete the devices. The main use for this flag is by MAKEDEV itself. Careful with this one bestie, it's the destructive one πŸ’€
  • -v β€” Be verbose. Print out the actions as they are performed. This is the same output as produced by -n. So basically same receipts, different energy ✨

πŸ› οΈ CUSTOMISATION πŸ› οΈ

Since there is currently no standardisation in what names are used for system users and groups, it is possible that you may need to modify MAKEDEV to reflect your site's settings. (society has no standards, we already knew this)

Near the top of the file is a mapping from device type to user, group and permissions (e.g. all CD-ROM devices are set from the $cdrom variable). If you wish to change the defaults, this is the section to edit πŸ‘‘


🌈 GENERAL OPTIONS 🌈

  • update β€” This only works on kernels which have /proc/interrupts (introduced during 1.1.x). This file is scanned to see what devices are currently configured into the kernel, and this is compared with the previous settings stored in the file called DEVICES. Devices which are new since then or have a different major number are created, and those which are no longer configured are deleted. It's giving glow up or go home β€” new devices get made, obsolete ones get deleted πŸ’…
  • generic β€” Create a generic subset of devices. This subset consists of the standard devices, plus floppy drives, various hard drives, CD-ROM drives, pseudo-terminals, console devices, basic serial devices, busmice, audio devices, video framebuffers, printer ports, and some specialized devices. The generic subset varies somewhat according to architecture; see the /dev/MAKEDEV script itself for details. It's the greatest hits album 🎡
  • local β€” This simply runs MAKEDEV.local. This is a script that can create any local devices. Your own personal corner of the universe, slay πŸ¦‹

🫢 DEVICE GROUPS 🫢

MAKEDEV creates groups of devices when passed keywords for the group. Each listing below shows the MAKEDEV keyword and then lists the devices which will be created. Many devices can also be specified individually. So like, you can get the whole bundle OR pick them one by one, no pressure, your choice bestie πŸ’–


⭐ STANDARD DEVICES ⭐

  • std β€” Creates this group of standard devices: mem for access to physical memory, kmem for access to kernel virtual memory, null the null device (infinite sink), port for access to I/O ports, zero the null byte source (infinite source), core, a symlink to /proc/kcore (for kernel debugging), full which always returns ENOSPACE on write, random and urandom random byte generators, and tty to access the controlling tty of a process.

The loopback disk devices loop0 through loop7 are also created in the std group. These allow you to use a regular file as a block device. A filesystem image can be mounted, and used as though it were a filesystem on a partition or other block device. loop may also be used as a separate keyword to create the 8 loop devices. Finally, the ram group of memory devices is also created by the std keyword (see below). Iconic bundle honestly πŸ‘‘


🧠 MEMORY DEVICES 🧠

  • ram β€” This is the keyword used to generate the ramdisk devices ram{0..16} and the ram symlink. This group does not include initrd. Read that again, bestie β€” no initrd in here πŸ™ˆ
  • initrd β€” Ramdisk which has been pre-initialized by a bootloader. initrd is not created in the ram group; it must be specifically included in the command line if you want it to be created. It's invite-only, it does not come with the group πŸ’…
  • cpu or microcode β€” Creates the CPU microcode update interface in the cpu/ folder, with devices microcode, and subfolders {0..3} each containing devices msr and cpuid.
  • rom β€” Creates the rom{0..7} rrom{0..7} flaxh{0..7} and rflash{0..7} flash memory card devices. rrom and rflash devices are read-only. (yes, flaxh β€” we did not make that up, it's in there, no cap 😭)

πŸ–₯️ CONSOLE DEVICES πŸ–₯️

  • console β€” This keyword creates virtual consoles; tty{0..63} devices, the corresponding vcs and vcsa devices which are used to generate screen-dumps, and the console device itself plus appropriate symlinks. To create the console device alone, use consoleonly. The device tty0 is the currently active virtual console. The console device serves the same function. Main character device behavior honestly πŸŽ€

🧚 PSEUDO TERMINALS 🧚

  • pty β€” This keyword creates the Pseudo-TTY masters pty{a..e,p..z} and corresponding tty{a..e,p..z} devices, along with ptmx. Each possible argument will create a bank of 16 master and slave pairs. The master pseudo-terminals are pty{p..s}{0..9a..f}, and the slaves are tty{p..s}{0..9a..f}. Sixteen pairs per argument, that's a whole squad 🌸

πŸ”Œ SERIAL DEVICES πŸ”Œ

  • ttyS{0..63} β€” Standard serial ports. There is no group keyword, you must specify these individually. However ttyS{0..3} are created under the generic option for most architectures. No group chat for these, you have to DM each one πŸ“±
  • cyclades or ttyC β€” Creates Cyclades ports ttyC{0..31}.
  • digi or ttyD β€” Creates Digiboard serial card ports ttyD{0..15}.
  • stallion or ttyE β€” Creates Stallion devices ttyE{0..255} and staliomem{0..3}.
  • computone or ttyF β€” Creates CompuTone serial card ports ttyH{0..255} and special devices ip2ipl{0,4,8,12} and ip2stat{1,5,9,13}.
  • chase or ttyH β€” Creates Chase serial card ports ttyH{0..15}.
  • isdnmodem or ttyI β€” Creates isdn4linux virtual modem ports ttyI{0..63}.
  • isdn-tty β€” Also creates isdn4linux virtual modem ports ttyI{0..7}.
  • isdnbri β€” Creates ISDN BRI driver devices isdn{0..63} isdnctrl{0..63} ippp{0..63} and isdninfo.
  • isdn-io β€” Also creates ISDN BRI driver devices isdn{0..7} isdnctrl{0..7} ippp{0..7} and isdninfo. The isdn-ippp keyword can be used separately to create only the ippp{0..7} devices.
  • ppp β€” Creates a device independent PPP interface.
  • dcbri β€” Creates Spellcaster DataComm/BRI ISDN card devices dcbri{0..3}.
  • riscom or ttyL β€” Creates Riscom serial card ports ttyL{0..15}.
  • PAM or ttyM β€” Creates PAM multimodem (or ISI serial card) ports ttyM{0..15}.
  • ESP or ttyP β€” Creates ESP ports ttyP{0..4}.
  • rocketport or ttyR β€” Creates Rocketport devices ttyR{0..63}.
  • ttyV β€” Creates Comtrol VS-1000 serial controller ports ttyV{0..15}.
  • specialixIO8 or ttyW β€” Creates Specialix IO8+ ports ttyW{0..15}.
  • specialix or ttyX β€” Creates Specialix ports ttyX{0..15}.
  • i2c β€” Creates i2c{0..7} devices for the I2C bus interface.
  • tlk β€” Philips SAA5249 Teletext signal decoder {2.6} ports tlk{0..3}.

πŸ–¨οΈ PARALLEL PORTS πŸ–¨οΈ

  • lp β€” Creates the standard parallel ports lp0, lp1, and lp2 normally used for printers. These correspond to ports at 0x3bc, 0x378 and 0x278. Hence, on some machines, the first printer port may actually be lp1. Plot twist 😭 numbering is not what you think it is.
  • par β€” Alternative to lp. The same ports are created, but are named par{0..2} instead of lp{0..2}.
  • parport β€” Creates raw parallel ports parport0, parport1, and parport2.
  • slm β€” Creates the Atari SLM ACSI laser printer (68k/Atari) ports slm{0..3}.
  • pg β€” Parallel port generic ATAPI interface (devices pg{0..3}.
  • paride β€” Parallel port IDE disk devices pd{a..d} with 15 partitions on each. Also creates pcd{0..3} and pf{0..3}.

🚌 OTHER BUS PORTS 🚌

  • netlink or tap β€” Creates NetLink devices route skip fwmonitor and tap{0..15} Ethertap devices. The tapx virtual ethernet device was designed as low level kernel support for Ethernet tunneling. Userland application can write Ethernet frame to /dev/tapX and the kernel will receive this frame from tapX interface. Every frame the kernel writes to a tapX interface can be read by a userland application from the corresponding /dev/tapX device. It's giving tunnel vision but make it networking πŸ¦‹
  • enskip β€” ENskip kernel encryption package.
  • qng β€” ComScire Quantum Noise Generator.
  • ipsec β€” The Free S/WAN implementation of IPSEC.
  • adb β€” On powerpc, creates adb for the Apple Data Bus and adbmouse. On m68k, adb creates the ACSI disk device adb and partitions adb1 through adb15. Two completely different personalities depending on architecture, dual citizenship ✨
  • hamradio β€” Creates the scc{0..7} and bc{0..3} device groups.
  • comx β€” Creates COMX devices comx{0..4}.
  • irda β€” Creates IrCOMM devices (IrDA serial/parallel emulation) ircomm0 ircomm1 irlpt0 and irlpt1.
  • comedi β€” Control and Measurement devices comedi{0..3}.

🐭 MOUSE DEVICES 🐭

  • busmice β€” This keyword creates the following devices: logibm (Logitech bus mouse), psaux (PS/2-style mouse), inportbm (Microsoft Inport bus mouse) and atibm (ATI XL bus mouse) and jbm (J-mouse). Whole mouse friend group right there 🫢
  • m68k-mice β€” Creates mouse devices for the m68k architecture, including: amigamouse, amigamouse1, atarimouse and adbmouse.
  • input β€” On powerpc, this keyword creates the input folder which groups input devices mice, mouse{0..3}, event{0..3}, and js{0..3} (joystick), and creates these devices inside.

πŸ•ΉοΈ JOYSTICK DEVICES πŸ•ΉοΈ

  • js β€” Joystick. Creates js0 and js1.
  • djs β€” Digital joystick. Creates djs0 and djs1.

πŸ”₯ USB DEVICES πŸ”₯

  • usb β€” USB is a general purpose I/O bus which can serve many purposes. The usb keyword creates a usb folder, and devices in the folder: lp{0..15} (printer), mouse{0..15} (USB connected mice), ez{0..15} (firmware loaders) scanner{0..15} (scanner interfaces), ttyACM{0..15} and ttyUSB{0..15} (dialout devices), and rio500 the Diamond Rio 500 device. One keyword, a whole folder of possibilities, versatility queen πŸ‘‘

πŸ’Ύ DISK DEVICES πŸ’Ύ

  • fd{0..7} β€” floppy disk devices, bestie. The device fdx is the one that autodetects the format (main character behaviour fr), and the extra devices are fixed format, with the size literally right there in the name. The rest go by fdx{dqhu}n. That one little letter (d, q, h or u) tells you the drive type: 5.25" Double Density (d), 5.25" Quad Density (q), 5.25" High Density (h) or 3.5" (any model, u). And the number n is the capacity of that format in K. So the standard formats are fdxd360, fdxh1200, fdx720, fdx1440, and fdx2880. ✨

Wanna know more? Go see Alain Knaff's fdutils package. 🫢

Devices fd0* through fd3* are floppy disks on the first controller, and fd4* through fd7* are floppy disks on the second controller. No cap.

  • fd{0..7}-bare β€” creates just the autodetecting floppy device you asked for, and none of the fixed format devices. Minimal. Clean. It's giving low-maintenance. πŸ’…
  • hd{a..l} β€” AT (ide) hard disks. The device hdx gives you the whole disk, and the partitions are hdx{1..63}. For i386, the four primary partitions are hdx1 through hdx4, with the logical partitions numbered from hdx5 though hdx20. (A primary partition can be turned into an extended partition, which can hold 4 logical partitions, iykyk.) Other architectures may not differentiate partition types. By default, devices for 20 logical partitions are made. The kernel supports up to 63 partitions per device. πŸ‘‘

Drives hda and hdb are the two on the primary controller, hdc and hdd are the two drives on the secondary controller. These devices can also be used to access IDE CDROMs, which is lowkey iconic. Additional devices hd{e..l} can be created.

  • xd{a..d} β€” XT hard disks. Partitions are the same as IDE disks, except only 8 partitions are created. Nostalgia-core. πŸ¦‹
  • sd{a..h} β€” SCSI hard disks. The partitions are similar to the IDE disks, but there's a limit of 11 logical partitions, sdx5 through sdx15, so that there can be 8 SCSI disks on a system (addresses 0 through 7). Math is mathing.
  • sd{i..z} and sd{a..d}{a..z} β€” the kernel (and MAKEDEV) can handle up to 128 SCSI disks (up to sddx). 15 partition devices are created for each. That's a lot of disks, bestie.
  • eda edb β€” MCA ESDI hard disk. Partitions are handled the same as hd. Simple, consistent, we love that. πŸ’–
  • dasd{a..z} β€” Direct Access Storage Devices for the s390 architecture. Currently only one device partition is created (for example, dasda1).
  • ada{a..p} β€” ACSI disk (68k/Atari). 15 partitions are created for each.
  • dac960.{0..7} β€” Mylex DAC960 PCI RAID controller. For this device, an rd directory is created. 32 logical devices cxd{0..31} are created for each unit x you specify, each with 7 partitions cxd{0..31}p{1..7}. The dac960 keyword will create all 7 units at once. Overachiever energy. πŸ”₯
  • dpti β€” Adaptec I2O RAID and DPT SmartRAID V I2O controllers. Creates 7 devices for handling up to 7 controllers.
  • ataraid.{0..7} β€” Obsolete, device not in current devices.txt. 🚨 For this device, an ataraid directory is created. dx is created for each unit x specified, and 15 partitions dxp{1..15}. The ataraid keyword will create all 7 units at once. Old but remembered. πŸ’€
  • i2o.hd{a..d}{a..z} β€” I2O based harddisk drives. Device nodes are located in the i2o directory. The filename is followed by a number that specifies the partition on each disk. The numbers are handled the same as hd.
  • ida.{0..7} β€” Compaq Intelligent Drive Array. For this device, an ida directory is created. 16 logical devices cxd{0..15} are created for each unit x specified, each with 15 partitions cxd{0..15}p{1..15}. The ida keyword will create the first three units.
  • cciss.{0..7} β€” Compaq Next Generation Drive Array. For this device, a cciss directory is created. 16 logical devices cxd{0..15} are created for each unit x specified, each with 15 partitions cxd{0..15}p{1..15}. The cciss keyword will create the first three units.
  • md β€” creates a Metadisk (RAID) disk array with 16 devices. Slay. πŸ’…

πŸ“Ό TAPE DEVICES πŸ“Ό

  • st{0..7} β€” SCSI tape devices. This creates the rewinding tape device stx and the non-rewinding tape device nstx, for each of modes 0 through 3.
  • qic β€” QIC-11, -24, -120, and -150 tapes. The devices created are ntpqic11 tpqic11 ntpqic24 tpqic24 ntpqic120 tpqic120 ntpqic150 and tpqic150 tape devices, along with rmt8, rmt16, tape-d, and tape-reset. A whole squad. πŸŽ€
  • ftape β€” 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 qftx zqftx and rawqftx (rewinding) and nqftx nzqftx nrawqdtx (non-rewinding) are created. For compatibility, devices ftape and nftape are symlinks to qft0 and nqft0 respectively.
  • ht0 β€” creates IDE tape devices ht0 and nht0.
  • pt{0..3} β€” creates parallel port ATAPI tape devices pt{0..3} and npt{0..3}.

πŸ’Ώ CDROM DEVICES πŸ’Ώ

  • sr or scd or scd-all β€” creates scd{0..16} SCSI CD players and sr{0..16} symlinks for these devices. cdrom is a symlink which can be created by the user to the active CD device. It is not created by MAKEDEV β€” that one's on you, bestie. πŸ™ˆ
  • pktcdvd β€” provides packet writing devices pktcdvd{0..3} for CD/DVD.
  • pcd{0..3} β€” parallel port ATAPI CD-ROM devices.
  • sonycd β€” Sony CDU-31a CD-ROM.
  • mcd β€” Mitsumi CD-ROM.
  • mcdx β€” Obsolete, device not in current devices.txt. πŸ’€
  • cdu535 β€” Sony CDU-535 CD-ROM.
  • lmscd β€” Philips LMS CM-205 CD-ROM. The newer name for this device is cm205, but MAKEDEV creates only lmscd at this time. Glow-up pending, I guess. πŸ’…
  • cm206cd β€” Philips LMS CM-206 CD-ROM.
  • bpcd β€” MicroSolutions BackPack parallel port CD-ROM (Obsolete β€” use pcd). Please use pcd, fr fr. 🚨
  • sbpcd{0..15} β€” Matsushita (Panasonic/SoundBlaster) CD-ROM. Units {0..3} are created with the keyword sbpcd.
  • aztcd β€” Aztech/Orchid/Okano/Wearnes CD-ROM.
  • gscd β€” GoldStar CD-ROM.
  • optcd β€” Optics Storage CD-ROM.
  • sjcd β€” Sanyo CD-ROM.
  • hitcd β€” Hitachi CD-ROM.

πŸ–¨οΈ SCANNERS πŸ–¨οΈ

  • logiscan β€” Logitech ScanMan32 & ScanMan 256.
  • m105scan β€” Mustek M105 Handscanner.
  • ac4096 β€” A4Tek Color Handscanner.

πŸ”Š AUDIO DEVICES πŸ”Š

  • audio β€” this creates the audio devices used by the sound driver. These include mixer mixer{1..3} (Mixer controls), sequencer (Audio sequencer), dsp dsp{1..3} (Digital audio), sndstat (Sound card status information), audioctl (SPARC audio control device) and audio audio{1..3} (Sun-compatible digital audio). MIDI devices are midi00 through midi03, midi{0..3}, rmidi{0..3}, smpte{0..3}. In addition, devices mpu401data and mpu401stat are created. A whole festival of devices, periodt. 🎢
  • pcaudio β€” devices for the PC Speaker sound driver. These are pcmixer, pxsp, and pcaudio.

πŸ“Ί VIDEO DEVICES πŸ“Ί

  • fb β€” creates framebuffer devices fb{0..7}, fb{0..7}current, fb{0..7}autodetect.
  • fb{0..7} β€” if the framebuffer number x is specified, a group of fbxuser{0..7} devices is created.
  • 3dfx β€” is the 3Dfx Voodoo Graphics device. Retrowave vibes. 🌈
  • agpgart β€” AGP Graphics Address Remapping Table.
  • video video4linux v4l radio β€” each of these keywords produces the same result: Video capture/overlay devices video{0..63}, Radio devices radio{0..63}, Teletext devices vtx{0..31}, and Vertical blank interrupt devices vbi{0..31}. In addition, the winradio0 and winradio1 devices, and vtx and vttuner devices, and symlinks radio video and vbi are created.
  • srnd β€” miroMEDIA Surround board devices srnd0 and srnd1.
  • fgrab β€” Matrox Meteor frame grabber {2.6}. Creates mmetfgrab, wvisfgrab, iscc0, iscc1, isccctl0, isccctl1, dcxx0, and dcxx1.

🧚 MISCELLANEOUS DEVICES 🧚

  • sg or sg-all β€” generic SCSI devices. The devices created are sg0 through sg16. These allow arbitrary commands to be sent to any SCSI device, to query information or control SCSI devices that are not disk, tape or CDROM (for example, scanner or writeable CDROM). Powerful. Use responsibly. πŸ‘‘
  • fd β€” to allow an arbitrary program to be fed input from file descriptor x, use /dev/fd/x as the file name. This also creates /dev/stdin, /dev/stdout, and /dev/stderr. (Note, these are just symlinks into /proc/self/fd.) Sneaky but valid. ✨
  • ibcs2 β€” devices socksys spx (and symlinks nfsd XOR) needed by the IBCS2 emulation.
  • apm β€” apm_bios Advanced Power Management BIOS device.
  • dcf β€” driver for DCF-77 radio clock.
  • helloworld β€” kernel modules demonstration device. See the modules source.
  • xfs or arla β€” Arla XFS network file system.
  • capi β€” CAPI 2.0 interface ports capi20{01..20}.
  • ubd β€” user-mode block devices ubd{0..255}.
  • nb{0..7} β€” network block devices.
  • raw β€” creates the raw block device interface raw device, the rawctl symlink, and raw{1..8}.
  • raw1394 β€” IEEE 1394 (Firewire).
  • misc β€” this keyword creates all the following devices. You may find the device explanations in other categories in this man page, many under OTHER DEVICES below. logibm, psaux, inportbm, atibm, jbm, amigamouse, ataramouse, sunmouse, amigamouse1, smouse, pc110pad, adbmouse, beep, modreq, watchdog, temperature, hwtrap, exttrp, apm_bios, rtc, openprom, relay8, relay16, msr, pciconf, nvram, hfmodem, led, mergemem, pmu. The whole roster, no crumbs. πŸ”₯

🌐 Network Devices 🌐

Linux used to have devices in /dev for controlling network devices, but that is no longer the case. To see what network devices are known by the kernel, look at /proc/net/dev. Rip to the old days, bestie. πŸ’œ

✨ OTHER DEVICES ✨

Okay bestie, this next batch is the chaos drawer of device nodes πŸ’… a bunch of them are architecture-specific, meaning they only show up on certain machine types β€” so if you don't see yours, it's not you, it's your architecture. πŸ¦‹

  • scc β€” Z8530 HDLC driver, for HAM radio πŸŽ™οΈ
  • bc β€” Baycom radio modem, also HAM radio πŸ“»
  • cfs0 or cfs or coda β€” the Coda network file system, three names, one vibe ✨
  • sunmouse β€” Sun mouse 🐭
  • smouse β€” Simple serial mouse driver
  • pc110pad β€” IBM PC-110 digitizer pad
  • vrtpanel β€” Vr41xx embedded touch panel πŸ‘†
  • vpcmouse β€” Connectix Virtual PC Mouse
  • beep β€” fancy beep device πŸ”” (yes it gets its own node, iconic)
  • modreq β€” kernel module load request {2.6} πŸ“¦
  • watchdog β€” watchdog timer port πŸ•
  • temperature β€” machine internal temperature 🌑️
  • hwtrap β€” hardware fault trap ⚠️
  • exttrp β€” external device trap
  • rtc β€” Real Time Clock ⏰
  • efirtc β€” Real Time Clock
  • openprom β€” SPARC OpenBoot PROM
  • relay8 β€” Berkshire Products Octal relay card
  • relay16 β€” Berkshire Products ISO-16 relay card
  • msr β€” x86 model-specific registers {2.6}
  • pciconf β€” PCI configuration space
  • nvram β€” non-volatile configuration RAM
  • hfmodem β€” soundcard shortwave modem control {2.6}
  • graphics β€” Linux/SGI graphics device 🎨
  • opengl β€” Linux/SGI OpenGL pipe
  • gfx β€” Linux/SGI graphics effects device
  • lcd β€” front panel LCD display
  • led β€” front panel LEDs πŸ’‘
  • mergemem β€” memory merge device
  • pmu β€” Macintosh PowerBook power manager πŸ”‹
  • isictl β€” MultiTech ISICom serial control
  • ac β€” Applicom Intl Profibus card
  • nwbutton β€” Netwinder external button
  • nwdebug β€” Netwinder debug interface
  • nwflash β€” Netwinder flash memory
  • userdma β€” user-space DMA access
  • smbus β€” System Management Bus
  • lik β€” Logitech Internet Keyboard ⌨️
  • ipmo β€” Intel Intelligent Platform Management
  • vmmon β€” VMWare virtual machine monitor πŸ–₯️
  • tcldrv β€” Technology Concepts serial control
  • specialix_sxctl β€” Specialix serial control
  • specialix_rioctl β€” Specialix RIO serial control
  • smapi or thinkpad β€” IBM Thinkpad smapi device, plus a symlink named thinkpad πŸ”—
  • srripc β€” QNX4 API IPC manager
  • usemaclone β€” semaphore clone device
  • ipmi or ipmikcs β€” Intelligent Platform Management
  • uctrl β€” SPARCbook 3 microcontroller
  • gtrsc β€” Gorgy Timing radio clock πŸ•°οΈ
  • cbm β€” serial CBM bus
  • jsflash β€” JavaStation OS flash SIMM
  • xsvc β€” high-speed shared-mem/semaphore service
  • vrbuttons β€” Vr41xx button input device
  • toshiba β€” Toshiba laptop SMM support
  • perfctr β€” performance-monitoring counters πŸ“Š
  • intel_rng β€” Intel i8x0 random number generator 🎲
  • atomicps β€” atomic shapshot of process state data
  • irnet β€” IrNET device
  • smbusbios β€” SMBus BIOS
  • ussp_ctl β€” user space serial port control
  • crash β€” Mission Critical Linux crash dump facility πŸ’₯
  • nas_xbus β€” NAS xbus LCD/buttons access
  • d7s β€” SPARC 7-segment display
  • zkshim β€” Zero-Knowledge network shim control
  • sexec β€” signed executable interface
  • kchuid β€” inter-process chuid control
  • mptctl β€” Message passing technology (MPT) control
  • button/gulpb β€” Transmeta GULP-B buttons
  • compaq/cpqphpc β€” Compaq PCI Hot Plug Controller
  • compaq/cpqrid β€” Compaq Remote InsightDriver
  • elographics/e2201 β€” Elographics touchscreen E271-2201
  • fujitsu/apanel β€” Fujitsu/Siemens application panel
  • i2o/ctl β€” I2O configuration manager
  • impi/bt β€” IMPI coprocessor block transfer
  • impi/smic β€” IMPI coprocessor stream interface
  • input/mouse β€” Linux/SGI Irix emulation mouse 🐁
  • input/keyboard β€” Linux/SGI Irix emulation keyboard
  • modems/mwave β€” MWave modem firmware upload
  • mvista/hssdsi β€” Montavista PICMG hot swap system driver
  • mvista/hasi β€” Montavista PICMG high availability
  • net/tun β€” TAP/TUN network device 🌐
  • ni/natmotn β€” National Instruments Motion
  • scanners/cuecat β€” :CueCat barcode scanner 🐱 (yes, the cat-shaped one, we love a legend)
  • touchscreen/ucb1x00 β€” UCB 1x00 touchscreen
  • touchscreen/mk712 β€” MK712 touchscreen
  • video/em8300 β€” EM8300 DVD decoder control
  • video/em8300_mv β€” EM8300 DVD decoder video πŸ“Ή
  • video/em8300_ma β€” EM8300 DVD decoder audio πŸ”Š
  • video/em8300_sp β€” EM8300 DVD decoder subpicture
  • watchdogs/{0..3} β€” watchdog devices 0 through 3 🐢🐢🐢🐢

πŸ‘€ SEE ALSO πŸ‘€

  • Linux Allocated Devices, maintained by H. Peter Anvin, <Peter.Anvin@linux.org>, and devices.txt in the Linux kernel source.

Like, if you wanna go deeper than this page ever could, that's your girl fr fr πŸ’–


πŸ‘‘ AUTHOR πŸ‘‘

Nick Holloway, rewritten and updated by Chris Tillman ✨


And that's a wrap bestie!! πŸŽ€ This whole page lives under Linux and it's dated May 17 2002 β€” a true vintage queen, older than most of the devices it describes, and still serving. Go make some nodes, you got this. πŸ’…πŸ«Ά

πŸ“¦ where this page comes from