QUOTE(HighKing @ Mar 23 2010, 07:55 PM)

Ok we need to rethink something... after installing the live system to disk the live halt stays in place. This is wrong, but since the installer isn't ours we can't do much about that. How does One handle this? Does it use a custom halt script at all?
One idea that came to my mind is keeping the hmconfig script enabled after booting, and create a check in that script that checks if the system is live or installed and removes the live halt whenever running from an installed system. Then the hmconfig script can disable itself after the first boot from an installed system. I would prefer the installer to do this for us though... but I'm affraid that's not possible.
* I can remember that I edited the MDV live install script (on the old mcnlive), it's a perl script, to put the original halt back, but I'm not 100% sure, I 'think' that they do similiar things with MDV One and the live install. Someone with more time and a recent MDV One could have a look what halt scripts there are on the live system?
When we follow the same naming scheme, it could be solved.
* Another option would be to edit the original halt script in a way that all changes first check: is it a live system, then do ... blah blah. If not use the original code. Then we'd have one halt script, and all this mv and mv back isn't necessary.
* Your/our halt doesn't do any harm atm, if I'm not mistaken, even on an installed system.