{
    "content": [
        {
            "type": "text",
            "text": "# mknod (info)\n\n## Sections\n\n- **File: coreutils.info,  Node: mknod invocation,  Next: readlink invocation,  Prev: mkfifo invocation,  Up: Special file types** (1 subsections)\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "mknod",
        "section": "",
        "mode": "info",
        "summary": null,
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "File: coreutils.info,  Node: mknod invocation,  Next: readlink invocation,  Prev: mkfifo invocation,  Up: Special file types",
                "lines": 1,
                "subsections": [
                    {
                        "name": "12.5 'mknod': Make block or character special files",
                        "lines": 57
                    }
                ]
            }
        ],
        "sections": {
            "File: coreutils.info,  Node: mknod invocation,  Next: readlink invocation,  Prev: mkfifo invocation,  Up: Special file types": {
                "content": "",
                "subsections": [
                    {
                        "name": "12.5 'mknod': Make block or character special files",
                        "content": "'mknod' creates a FIFO, character special file, or block special file\nwith the specified name.  Synopsis:\n\nmknod [OPTION]... NAME TYPE [MAJOR MINOR]\n\nUnlike the phrase \"special file type\" above, the term \"special file\"\nhas a technical meaning on Unix: something that can generate or receive\ndata.  Usually this corresponds to a physical piece of hardware, e.g., a\nprinter or a flash drive.  (These files are typically created at\nsystem-configuration time.)  The 'mknod' command is what creates files\nof this type.  Such devices can be read either a character at a time or\na \"block\" (many characters) at a time, hence we say there are \"block\nspecial\" files and \"character special\" files.\n\nDue to shell aliases and built-in 'mknod' functions, using an\nunadorned 'mknod' interactively or in a script may get you different\nfunctionality than that described here.  Invoke it via 'env' (i.e., 'env\nmknod ...') to avoid interference from the shell.\n\nThe arguments after NAME specify the type of file to make:\n\n'p'\nfor a FIFO\n\n'b'\nfor a block special file\n\n'c'\nfor a character special file\n\nWhen making a block or character special file, the major and minor\ndevice numbers must be given after the file type.  If a major or minor\ndevice number begins with '0x' or '0X', it is interpreted as\nhexadecimal; otherwise, if it begins with '0', as octal; otherwise, as\ndecimal.\n\nThe program accepts the following options.  Also see *note Common\noptions::.\n\n'-m MODE'\n'--mode=MODE'\nSet the mode of created files to MODE, which is symbolic as in\n'chmod' and uses 'a=rw' as the point of departure.  MODE should\nspecify only file permission bits.  *Note File permissions::.\n\n'-Z'\n'--context[=CONTEXT]'\nWithout a specified CONTEXT, adjust the SELinux security context\naccording to the system default type for destination files,\nsimilarly to the 'restorecon' command.  The long form of this\noption with a specific context specified, will set the context for\nnewly created files only.  With a specified context, if both\nSELinux and SMACK are disabled, a warning is issued.\n\nAn exit status of zero indicates success, and a nonzero value\nindicates failure.\n"
                    }
                ]
            }
        }
    }
}