| 1 |
<meino.cramer <at> gmx.de> writes: |
| 2 |
|
| 3 |
|
| 4 |
> But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") |
| 5 |
> REBOOTS the system instead of powering it down. |
| 6 |
|
| 7 |
What about "halt"? man halt |
| 8 |
|
| 9 |
> What is the difference here? |
| 10 |
> Isn't it, that all shutdown applications only send some instructions |
| 11 |
> to the kernel and the kernel is the main actor in bringing the system |
| 12 |
> down? |
| 13 |
|
| 14 |
> Meino |
| 15 |
|
| 16 |
|
| 17 |
Meino, "it's an embedded system". That can mean unique hardware, via |
| 18 |
the SoC, hidden codes via the in-situ firmware, or a myriad of things |
| 19 |
hidden in the "recommended" kernel(s). Many embedded developers |
| 20 |
forked off their own "embedded kernel" form linux via the 2.2 or 2.4 |
| 21 |
kernel series. |
| 22 |
|
| 23 |
So, you have to "fully characterize" the system. Which is difficult to |
| 24 |
impossible, as the vendor wants to retain control in most circumstances. |
| 25 |
The good news is most "hardware vendors" are dumb, when it comes to codes; |
| 26 |
so there is most always a work-around; hence "man halt" as for your |
| 27 |
next leg of the journey? |
| 28 |
|
| 29 |
hth, |
| 30 |
James |
Archives