This question already has an answer here:

shutdown now kills everything and then powers down the machine. halt kills everything and then... there is no step 2. It will sit, running but not doing anything, until people stop arguing over whether Emacs or Vim is better.

Why doesn't halt actually power down the machine? Is there a historical reason?

marked as duplicate by slm, Anthon, jasonwryan, rahmu, Renan Nov 16 '13 at 17:37

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.


See @bahamat's answer to this question titled: Halt and poweroff options for shutdown command.

.... halt was used before ACPI (which today will turn off the power for you)*. It would halt the system and then print a message to the effect of "it's ok to power off now". Back then there were physical on/off switches, rather than the combo ACPI controlled power button of modern computers. ...

The halt command would also do other things to put the system into a known good state prior to halting, such as syncing the disks and sending the commands to the CPU so that it knew to HALT.

See the Wikipedia page on HCF - Halt and Catch Fire.


Halt and Catch Fire, known by the mnemonic HCF, refers to several computer machine code instructions that cause the CPU to cease meaningful operation. The expression "catch fire" is intended as a joke; the CPU does not catch fire. It is also occasionally referred to as "SDI" for "Self Destruct Immediate".

Not the answer you're looking for? Browse other questions tagged or ask your own question.