...rs to the third DOS "primary" partition on the second one. They are typically created by: mknod -m 660 /dev/hda b 3 0 mknod -m 660 /dev/hda1 b 3 1 mknod -m 660 /dev/hda2 b 3 2 .…...[0-3] are character devices for the serial terminal lines. They are typically created by: mknod -m 660 /dev/ttyS0 c 4 64 # base address 0x3f8 mknod -m 660 /dev/ttyS1 c 4 65 # ba…...ss is not allowed but accessing memory-mapped PCI regions is. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file /dev/kmem is the same as …...ss is not allowed but accessing memory-mapped PCI regions is. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file /dev/kmem is the same as …...ss is not allowed but accessing memory-mapped PCI regions is. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file /dev/kmem is the same as …...s return bytes containing zero ('\0' characters). These devices are typically created by: mknod -m 666 /dev/null c 1 3 mknod -m 666 /dev/zero c 1 5 chown root:root /dev/null /de…...s return bytes containing zero ('\0' characters). These devices are typically created by: mknod -m 666 /dev/null c 1 3 mknod -m 666 /dev/zero c 1 5 chown root:root /dev/null /de…...device is a block device to access the ram disk in raw mode. It is typically created by: mknod -m 660 /dev/ram b 1 1 chown root:disk /dev/ram FILES /dev/ram SEE ALSO chown (1), …...s) and copyright conditions. Note that these can be different from page to page! SEE ALSO mknod (1), mknod (2), standards (7)...m does not have /dev/full created already, it can be created with the following commands: mknod -m 666 /dev/full c 1 7 chown root:root /dev/full DESCRIPTION The file /dev/full h…...es for the first eight virtual consoles may be created by: for x in 0 1 2 3 4 5 6 7 8; do mknod -m 644 /dev/vcs$x c 7 $x; mknod -m 644 /dev/vcsa$x c 7 $[$x+128]; done chown root…...es for the first eight virtual consoles may be created by: for x in 0 1 2 3 4 5 6 7 8; do mknod -m 644 /dev/vcs$x c 7 $x; mknod -m 644 /dev/vcsa$x c 7 $[$x+128]; done chown root…...ched to a terminal and does not need to detach itself. FILES /dev/tty SEE ALSO chown (1), mknod (1), ioctl (2), ioctl_console (2), ioctl_tty (2), termios (3), ttyS (4), vcs (4),…...random and /dev/urandom created already, they can be created with the following commands: mknod -m 666 /dev/random c 1 8 mknod -m 666 /dev/urandom c 1 9 chown root:root /dev/ran…...random and /dev/urandom created already, they can be created with the following commands: mknod -m 666 /dev/random c 1 8 mknod -m 666 /dev/urandom c 1 9 chown root:root /dev/ran…...e drives with two minor numbers for different options.) Devices are typically created by: mknod -m 666 /dev/st0 c 9 0 mknod -m 666 /dev/st0l c 9 32 mknod -m 666 /dev/st0m c 9 64…...T) Resets the printer. No argument is used. FILES /dev/lp* SEE ALSO chmod (1), chown (1), mknod (1), lpcntl (8), tunelp (8)...does not have /dev/initrd already created, it can be created with the following commands: mknod -m 400 /dev/initrd b 1 250 chown root:disk /dev/initrd Also, support for both "RA…...R FUSE_GETLK FUSE_GETXATTR FUSE_IOCTL FUSE_LINK FUSE_LISTXATTR FUSE_LSEEK FUSE_MKDIR FUSE_MKNOD FUSE_NOTIFY_REPLY FUSE_POLL FUSE_READDIRPLUS FUSE_READLINK FUSE_REMOVEXATTR FUSE_…