{"id":4138,"date":"2022-12-20T17:39:30","date_gmt":"2022-12-20T20:39:30","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/kernelcommandline-man7\/"},"modified":"2022-12-20T17:39:30","modified_gmt":"2022-12-20T20:39:30","slug":"kernelcommandline-man7","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/kernelcommandline-man7\/","title":{"rendered":"KERNEL&minus;COMMAND&minus;LINE (man7)"},"content":{"rendered":"<h1 align=\"center\">KERNEL\u2212COMMAND\u2212LINE<\/h1>\n<p> <a href=\"#NAME\">NAME<\/a><br \/> <a href=\"#SYNOPSIS\">SYNOPSIS<\/a><br \/> <a href=\"#DESCRIPTION\">DESCRIPTION<\/a><br \/> <a href=\"#CORE OS COMMAND LINE ARGUMENTS\">CORE OS COMMAND LINE ARGUMENTS<\/a><br \/> <a href=\"#SEE ALSO\">SEE ALSO<\/a><br \/> <a href=\"#NOTES\">NOTES<\/a> <\/p>\n<hr>\n<h2>NAME <a name=\"NAME\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">kernel-command-line \u2212 Kernel command line parameters<\/p>\n<h2>SYNOPSIS <a name=\"SYNOPSIS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">\/proc\/cmdline<\/p>\n<h2>DESCRIPTION <a name=\"DESCRIPTION\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">The kernel, the initial RAM disk (initrd) and basic userspace functionality may be configured at boot via kernel command line arguments. In addition, various systemd tools look at the EFI variable &#8220;SystemdOptions&#8221; (if available). Both sources are combined, but the kernel command line has higher priority. Please note that <i>the EFI variable is only used by systemd tools, and is ignored by the kernel and other user space tools<\/i>, so it is not a replacement for the kernel command line.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">For command line parameters understood by the kernel, please see <b><font color=\"#0000FF\">kernel\u2212parameters.html<\/font><\/b> <small><font color=\"#000000\">[1]<\/font><\/small> <font color=\"#000000\">and <b>bootparam<\/b>(7).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\">For command line parameters understood by the initial RAM disk, please see <b>dracut.cmdline<\/b>(7), or the documentation of the specific initrd implementation of your installation.<\/font><\/p>\n<h2>CORE OS COMMAND LINE ARGUMENTS <a name=\"CORE OS COMMAND LINE ARGUMENTS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.unit=<\/i>, <i>rd.systemd.unit=<\/i>, <i>systemd.dump_core<\/i>, <i>systemd.early_core_pattern=<\/i>, <i>systemd.crash_chvt<\/i>, <i>systemd.crash_shell<\/i>, <i>systemd.crash_reboot<\/i>, <i>systemd.confirm_spawn<\/i>, <i>systemd.service_watchdogs<\/i>, <i>systemd.show_status<\/i>, <i>systemd.status_unit_format=<\/i>, <i>systemd.log_target=<\/i>, <i>systemd.log_level=<\/i>, <i>systemd.log_location=<\/i>, <i>systemd.log_color<\/i>, <i>systemd.default_standard_output=<\/i>, <i>systemd.default_standard_error=<\/i>, <i>systemd.setenv=<\/i>, <i>systemd.machine_id=<\/i>, <i>systemd.unified_cgroup_hierarchy<\/i>, <i>systemd.legacy_systemd_cgroup_controller<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the system and service manager to control system behavior. For details, see <b>systemd<\/b>(1).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.mask=<\/i>, <i>systemd.wants=<\/i>, <i>systemd.debug_shell<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Additional parameters understood by <b>systemd-debug-generator<\/b>(8), to mask or start specific units at boot, or invoke a debug shell on tty9.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.run=<\/i>, <i>systemd.run_success_action=<\/i>, <i>systemd.run_failure_action=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Additional parameters understood by <b>systemd-run-generator<\/b>(8), to run a command line specified on the kernel command line as system service after booting up.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.early_core_pattern=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">During early boot, the generation of core dump files is disabled until a core dump handler (if any) takes over. This parameter allows specifying an absolute path where core dump files should be stored until a handler is installed. The path should be absolute and may contain specifiers, see <b>core<\/b>(5) for details.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.restore_state=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">This parameter is understood by several system tools to control whether or not they should restore system state from the previous boot. For details, see <b>systemd-backlight@.service<\/b>(8) and <b>systemd-rfkill.service<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.volatile=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">This parameter controls whether the system shall boot up in volatile mode. Takes a boolean argument, or the special value &#8220;state&#8221;. If false (the default), normal boot mode is selected, the root directory and \/var are mounted as specified on the kernel command line or \/etc\/fstab, or otherwise configured. If true, full state\u2212less boot mode is selected. In this case the root directory is mounted as volatile memory file system (&#8220;tmpfs&#8221;), and only \/usr is mounted from the file system configured as root device, in read\u2212only mode. This enables fully state\u2212less boots were the vendor\u2212supplied OS is used as shipped, with only default configuration and no stored state in effect, as \/etc and \/var (as well as all other resources shipped in the root file system) are reset at boot and lost on shutdown. If this setting is set to &#8220;state&#8221; the root file system is mounted read\u2212only, however \/var is mounted as a volatile memory file system (&#8220;tmpfs&#8221;), so that the system boots up with the normal configuration applied, but all state reset at boot and lost at shutdown. If this setting is set to &#8220;overlay&#8221; the root file system is set up as &#8220;overlayfs&#8221; mount combining the read\u2212only root directory with a writable &#8220;tmpfs&#8221;, so that no modifications are made to disk, but the file system may be modified nonetheless with all changes being lost at reboot. For details, see <b>systemd-volatile-root.service<\/b>(8) and <b>systemd-fstab-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>quiet<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameter understood by both the kernel and the system and service manager to control console log verbosity. For details, see <b>systemd<\/b>(1).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>debug<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameter understood by both the kernel and the system and service manager to control console log verbosity. For details, see <b>systemd<\/b>(1).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>\u2212b<\/i>, <i>rd.emergency<\/i>, <i>emergency<\/i>, <i>rd.rescue<\/i>, <i>rescue<\/i>, <i>single<\/i>, <i>s<\/i>, <i>S<\/i>, <i>1<\/i>, <i>2<\/i>, <i>3<\/i>, <i>4<\/i>, <i>5<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the system and service manager, as compatibility and convenience options. For details, see <b>systemd<\/b>(1).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>locale.LANG=<\/i>, <i>locale.LANGUAGE=<\/i>, <i>locale.LC_CTYPE=<\/i>, <i>locale.LC_NUMERIC=<\/i>, <i>locale.LC_TIME=<\/i>, <i>locale.LC_COLLATE=<\/i>, <i>locale.LC_MONETARY=<\/i>, <i>locale.LC_MESSAGES=<\/i>, <i>locale.LC_PAPER=<\/i>, <i>locale.LC_NAME=<\/i>, <i>locale.LC_ADDRESS=<\/i>, <i>locale.LC_TELEPHONE=<\/i>, <i>locale.LC_MEASUREMENT=<\/i>, <i>locale.LC_IDENTIFICATION=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the system and service manager to control locale and language settings. For details, see <b>systemd<\/b>(1).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>fsck.mode=<\/i>, <i>fsck.repair=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the file system checker services. For details, see <b>systemd-fsck@.service<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>quotacheck.mode=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameter understood by the file quota checker service. For details, see <b>systemd-quotacheck.service<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.journald.forward_to_syslog=<\/i>, <i>systemd.journald.forward_to_kmsg=<\/i>, <i>systemd.journald.forward_to_console=<\/i>, <i>systemd.journald.forward_to_wall=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the journal service. For details, see <b>systemd-journald.service<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>vconsole.keymap=<\/i>, <i>vconsole.keymap_toggle=<\/i>, <i>vconsole.font=<\/i>, <i>vconsole.font_map=<\/i>, <i>vconsole.font_unimap=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the virtual console setup logic. For details, see <b>vconsole.conf<\/b>(5).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>udev.log_priority=<\/i>, <i>rd.udev.log_priority=<\/i>, <i>udev.children_max=<\/i>, <i>rd.udev.children_max=<\/i>, <i>udev.exec_delay=<\/i>, <i>rd.udev.exec_delay=<\/i>, <i>udev.event_timeout=<\/i>, <i>rd.udev.event_timeout=<\/i>, <i>udev.timeout_signal=<\/i>, <i>rd.udev.timeout_signal=<\/i>, <i>udev.blockdev_read_only<\/i>, <i>rd.udev.blockdev_read_only<\/i>, <i>net.ifnames=<\/i>, <i>net.naming\u2212scheme=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Parameters understood by the device event managing daemon. For details, see <b>systemd-udevd.service<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>plymouth.enable=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">May be used to disable the Plymouth boot splash. For details, see <b>plymouth<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>luks=<\/i>, <i>rd.luks=<\/i>, <i>luks.crypttab=<\/i>, <i>rd.luks.crypttab=<\/i>, <i>luks.name=<\/i>, <i>rd.luks.name=<\/i>, <i>luks.uuid=<\/i>, <i>rd.luks.uuid=<\/i>, <i>luks.options=<\/i>, <i>rd.luks.options=<\/i>, <i>luks.key=<\/i>, <i>rd.luks.key=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Configures the LUKS full\u2212disk encryption logic at boot. For details, see <b>systemd-cryptsetup-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>fstab=<\/i>, <i>rd.fstab=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Configures the \/etc\/fstab logic at boot. For details, see <b>systemd-fstab-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>root=<\/i>, <i>rootfstype=<\/i>, <i>rootflags=<\/i>, <i>ro<\/i>, <i>rw<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Configures the root file system and its file system type and mount options, as well as whether it shall be mounted read\u2212only or read\u2212write initially. For details, see <b>systemd-fstab-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>mount.usr=<\/i>, <i>mount.usrfstype=<\/i>, <i>mount.usrflags=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Configures the \/usr file system (if required) and its file system type and mount options. For details, see <b>systemd-fstab-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>roothash=<\/i>, <i>systemd.verity=<\/i>, <i>rd.systemd.verity=<\/i>, <i>systemd.verity_root_data=<\/i>, <i>systemd.verity_root_hash=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Configures the integrity protection root hash for the root file system, and other related parameters. For details, see <b>systemd-veritysetup-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.gpt_auto=<\/i>, <i>rd.systemd.gpt_auto=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Configures whether GPT based partition auto\u2212discovery shall be attempted. For details, see <b>systemd-gpt-auto-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.default_timeout_start_sec=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Overwrites the default start job timeout <i>DefaultTimeoutStartSec=<\/i> at boot. For details, see <b>systemd-system.conf<\/b>(5).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.watchdog_device=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Overwrites the watchdog device path <i>WatchdogDevice=<\/i>. For details, see <b>systemd-system.conf<\/b>(5).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.cpu_affinity=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Overrides the CPU affinity mask for the service manager and the default for all child processes it forks. This takes precedence over <i>CPUAffinity=<\/i>, see <b>systemd-system.conf<\/b>(5) for details.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>modules_load=<\/i>, <i>rd.modules_load=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Load a specific kernel module early at boot. For details, see <b>systemd-modules-load.service<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>resume=<\/i>, <i>resumeflags=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Enables resume from hibernation using the specified device and mount options. All <b>fstab<\/b>(5)\u2212like paths are supported. For details, see <b>systemd-hibernate-resume-generator<\/b>(8).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.firstboot=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Takes a boolean argument, defaults to on. If off, <b>systemd-firstboot.service<\/b>(8) will not query the user for basic system settings, even if the system boots up for the first time and the relevant settings are not initialized yet. Not to be confused with <i>systemd.condition\u2212first\u2212boot=<\/i> (see below), which overrides the result of the <i>ConditionFirstBoot=<\/i> unit file condition, and thus controls more than just systemd\u2212firstboot.service behaviour.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.condition\u2212needs\u2212update=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Takes a boolean argument. If specified, overrides the result of <i>ConditionNeedsUpdate=<\/i> unit condition checks. See <b>systemd.unit<\/b>(5) for details.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.condition\u2212first\u2212boot=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Takes a boolean argument. If specified, overrides the result of <i>ConditionFirstBoot=<\/i> unit condition checks. See <b>systemd.unit<\/b>(5) for details. Not to be confused with <i>systemd.firstboot=<\/i> which only controls behaviour of the systemd\u2212firstboot.service system service but has no effect on the condition check (see above).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.clock\u2212usec=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Takes a decimal, numeric timestamp in \u00b5s since January 1st 1970, 00:00am, to set the system clock to. The system time is set to the specified timestamp early during boot. It is not propagated to the hardware clock (RTC).<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.random\u2212seed=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Takes a base64 encoded random seed value to credit with full entropy to the kernel&#8217;s random pool during early service manager initialization. This option is useful in testing environments where delays due to random pool initialization in entropy starved virtual machines shall be avoided.<\/font><\/p>\n<p style=\"margin-left:17%; margin-top: 1em\"><font color=\"#000000\">Note that if this option is used the seed is accessible to unprivileged programs from \/proc\/cmdline. This option is hence a security risk when used outside of test systems, since the (possibly) only seed used for initialization of the kernel&#8217;s entropy pool might be easily acquired by unprivileged programs.<\/font><\/p>\n<p style=\"margin-left:17%; margin-top: 1em\"><font color=\"#000000\">It is recommended to pass 512 bytes of randomized data (as that matches the Linux kernel pool size), which may be generated with a command like the following:<\/font><\/p>\n<p style=\"margin-left:23%; margin-top: 1em\"><font color=\"#000000\">dd if=\/dev\/urandom bs=512 count=1 status=none | base64 \u2212w 0<\/font><\/p>\n<p style=\"margin-left:17%; margin-top: 1em\"><font color=\"#000000\">Again: do not use this option outside of testing environments, it&#8217;s a security risk elsewhere, as secret key material derived from the entropy pool can possibly be reconstructed by unprivileged programs.<\/font><\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><i>systemd.hostname=<\/i><\/font><\/p>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">Accepts a hostname to set during early boot. If specified takes precedence over what is set in \/etc\/hostname. Note that this does not bar later runtime changes to the hostname, it simply controls the initial hostname set during early boot.<\/font><\/p>\n<h2>SEE ALSO <a name=\"SEE ALSO\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><font color=\"#000000\"><b>systemd<\/b>(1), <b>systemd-system.conf<\/b>(5), <b>bootparam<\/b>(7), <b>dracut.cmdline<\/b>(7), <b>systemd-debug-generator<\/b>(8), <b>systemd-fsck@.service<\/b>(8), <b>systemd-quotacheck.service<\/b>(8), <b>systemd-journald.service<\/b>(8), <b>systemd-vconsole-setup.service<\/b>(8), <b>systemd-udevd.service<\/b>(8), <b>plymouth<\/b>(8), <b>systemd-cryptsetup-generator<\/b>(8), <b>systemd-veritysetup-generator<\/b>(8), <b>systemd-fstab-generator<\/b>(8), <b>systemd-gpt-auto-generator<\/b>(8), <b>systemd-volatile-root.service<\/b>(8), <b>systemd-modules-load.service<\/b>(8), <b>systemd-backlight@.service<\/b>(8), <b>systemd-rfkill.service<\/b>(8), <b>systemd-hibernate-resume-generator<\/b>(8), <b>systemd-firstboot.service<\/b>(8), <b>bootctl<\/b>(1)<\/font><\/p>\n<h2>NOTES <a name=\"NOTES\"><\/a> <\/h2>\n<table width=\"100%\" border=\"0\" rules=\"none\" frame=\"void\" cellspacing=\"0\" cellpadding=\"0\">\n<tr valign=\"top\" align=\"left\">\n<td width=\"12%\"><\/td>\n<td width=\"3%\">\n<p style=\"margin-top: 1em\"><font color=\"#000000\">1.<\/font><\/p>\n<\/td>\n<td width=\"2%\"><\/td>\n<td width=\"34%\">\n<p style=\"margin-top: 1em\"><font color=\"#000000\">kernel-parameters.html<\/font><\/p>\n<\/td>\n<td width=\"49%\"> <\/td>\n<\/tr>\n<\/table>\n<p style=\"margin-left:17%;\"><font color=\"#000000\">https:\/\/www.kernel.org\/doc\/html\/latest\/admin-guide\/kernel-parameters.html<\/font><\/p>\n<hr>\n","protected":false},"excerpt":{"rendered":"<p>  kernel-command-line \u2212 Kernel command line parameters <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[971],"tags":[973,1215,972],"class_list":["post-4138","post","type-post","status-publish","format-standard","hentry","category-7-miscelanea","tag-973","tag-kernel-command-line","tag-man7"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4138","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=4138"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4138\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}